This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Applies to: SAP NetWeaver, Enterprise Portal, NWDI/JDI. For more information, visit the Portal and Collaboration homepage.
Summary This document explains how to begin with implementation of NWDI and how to create the tracks. NWDI (NetWeaver Development Infrastructure) provides consistent development landscape for the developers and helps us to develop software during the life cycle of a product. Connectivity to the NWDI is provided through NWDS (NetWeaver Developer Studio).
Author: Ameya Subhash Pimpalgaonkar
Company: L&T Infotech
Created on: 23rd October 2007
Author Bio
Ameya Subhash Pimpalgaonkar is an Enterprise Portal Consultant at L&T Infotech.
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Table of Contents Getting Started....................................................................................................................................................3
Downloading SCA files....................................................................................................................................3 Special case for SAP NetWeaver 2004s ........................................................................................................3 Deploying SCA files through SDM..................................................................................................................3
Basic Configurations...........................................................................................................................................3 Configure the jdbc connector ..........................................................................................................................3
UME ROLES.......................................................................................................................................................4 Assigning roles for administrator user.............................................................................................................4 Assigning role for Developer user...................................................................................................................5 Security Provider & SLD Roles .......................................................................................................................5 Roles for developer user.................................................................................................................................5 Roles for administrator user............................................................................................................................5
Configuration of CBS (Component Build Service)..............................................................................................6 Logging on to the SLD........................................................................................................................................7 Defining new products ........................................................................................................................................8
Adding dependencies....................................................................................................................................10 Configuration of Domain ...................................................................................................................................13 Result................................................................................................................................................................16 Related Content................................................................................................................................................18 Disclaimer and Liability Notice..........................................................................................................................19
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Getting Started SAP NetWeaver Developer Studio provides the connectivity with the NWDI providing consistent development landscape for the developers and helps us to develop software during life cycle of a product. Here we will explain some of the basic terminologies that are used in NWDI.
• Design Time Repository (DTR): Versioning source code management. Distributed development of software in teams. Transport and replication of sources.
• Component Build Service (CBS): Central build based on the component model.
• Change Management Service (CMS): Central administration of the Java development landscape and the transports covering the entire software life cycle.
• Software Deployment Manager (SDM): Manual and automatic deployment of archives in central runtime systems.
• System Landscape Directory (SLD): Information on the system landscape.
Downloading SCA files
All the SCA files for implementing NWDI, you will get at https://www.service.marketplace.com.
You should possess an S-User id to gain access to these files.
To install NWDI following support packages from SAP Service Marketplace must be downloaded. The support packages are:-
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Assigning role for Developer user
Create the role as JDI.Developer & assign following actions
1) CBS.Developer
2) CMS.Display
3) CMS.Export
UME Groups
Now Create a new group named JDI.Administrators and assign JDI.Admin role to it, similarly create the group named JDI.Developers and assign the JDI.Developer role to it. You can also create the test user to be able to work with the JDI, assign the Administrator user to the JDI.Administrators group.
Security Provider & SLD Roles
Now we will edit the security provider property, in visual admin tool.
Choose the tab Runtime Æ Policy Configuration Æ Security Roles.
In the Components section, choose the application sap.com/com.sap.lcr*sld. Æ Choose add Æ Select the Groups tab Æ choose Search. A list of available UME groups appears. Choose the NWDIAdministrators group and then add to SAP_J2EE_Engine_upload and click on OK. The data will be saved.
Roles for developer user Assign the LcrInstanceWriterNR security role to the JDI.Developers group.
Roles for administrator user Assign the LcrInstanceWriterAll security role to the JDI.Administrators group
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Adding dependencies
Now select your product, a detail tab-strip screen will appear, in that select software unit tab. In this select the software component created by you to add the usage dependencies. You use usage dependencies to define the software components on which the new software component is based, and to define the dependencies for the central build.
Click on “Dependencies” tab.
You have to add three usage dependencies and those are:
How to Implement NetWeaver Development Infrastructure and NetWeaver Development Infrastructure Tracks
Now click on transport studio and you will get the following screen, Select the Check-in tab.
Here check-in all the components, these archives are checked in to the track and placed in the import queue of the development system.
In the Transport Studio, choose the Development tab page. • The checked in software components are in the import queue with the status “Waiting for import”.
• Choose Select All and then Import. If the import is successful, the status changes to Import
finished. • Repeat these steps for all systems for which you have configured the track.
Now click on Import & you will get the following screen
Look at the status now its showing Import finished. Your track is now configured & ready to use for development component in NWDS.
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.