Header Ads

SAP NetWeaver – Step by Step Guide for NWDI Configuration

4:20 AM , , ,

SAP NetWeaver – Step by Step Guide for NWDI Configuration

Posted on 


7 Votes

SAP NWDI (NetWeaver Development Infrastructure) provides development environment for large teams where it is difficult to manage SAP Java WebDynpro based development components and respective code, especially when developers are situated at different geographical locations. NWDI provides common and online WD component + code repository that can be accessed from anywhere in enterprise premises.
Following are steps which covers complete details from initial NWDI configuration to start using tracks in SAP NWDS (NetWeaver Developer Studio).

1.    Creating and assigning required Roles and Actions in portal UME 

Create two groups for NWDI users in Portal UME.
  • NWDI.Administrators
  • NWDI.Developers
Create NWDI_Admin and NWDI_Developer users and add these users to corresponding groups NWDI.Administrators and NWDI.Developers simultaneously.
Search for NWDI.Administrator Role else Create and Assign it toNWDI.Administrators Group. Similarly search for NWDI.Developer Role else create and assign it to NWDI.Developers Group.
Open NWDI.Administrator Role and assign following Actions
  • CBS.Administrator
  • CMS.Administrate
Open NWDI.Developer Role and assign following Actions
  • CBS.Developer
  • CMS.Display
  • CMS.Export
2.    Assigning SLD Roles to Groups 
For respective groups assign corresponding security roles.
  • NWDI.Administrators               LcrInstanceWriterAll
  • NWDI.Developers                    LcrInstanceWriterNR
To assign above said security roles to NWDI groups, Go to Visual Administrator to set up user privileges for J2EE Engine. Visual Administrator can be opened via following path <SAP-install-dir>\<SID>\JC<instance no.>\j2ee\admin\go.bat
  • Login as Administrator
  • Open the navigation tree on left side of screen and go Server -> Services ->Security Provider
  • In the right-hand window, choose the tab Runtime -> Policy Configuration ->Security Roles.
  • In the Components section, choose the application sap.com/com.sap.lcr*sld.
  • Under Security Roles, select the security role LcrInstanceWriterAll.
  • Under Mappings you find the Groups field. Choose Add. The dialog window Choose Users or Groups appears.
  • Select the Groups tab page.
  • Choose Search. A list of the availableUMEgroups appears.
  • Choose the NWDI.Administrators group and then OK.
  • Your data is being saved.
  • Now assign the LcrInstanceWriterNR security role to the JDI.Developers group.

3.    Prepare System Landscape Directory (SLD)

  • Reach initial page of SLD under URL http://<server>:<port>/sld
  • Go to Products link under Software Catalog section.
  • To define New Product Version click on button available for same. Fill parameters and click create.
  • Product “Training, abc.com, 1.0” is created and define SAP Software Unit for same as shown below. Click Create button.
  • Add Software Component to created Product “Training..”.
  • Define SC Name, Version and setProductionStateparameter to Started from Drop Down list. Click on create to complete this step.
  • New Product and corresponding Software Component is created in SLD.

4.    Defining Software Component Dependencies

  • Go to Software Component to see created SC.
  • For this select Software Component value from drop down list of Software Type as mentioned in screen below.
  • Search for your SC in available components list. In our case it is “Demo”.
  • In SC, go to Dependencies Tab
  • Now, we need to define Build Time dependency on components like SAP-JEE,SAP_BUILDT, SAP_JTECHS.
  • To perform this select Build Time value from drop down and click Define Prerequisite Software Component Version button.
  • Following pop up screen appears displaying all available Software Components available.
  • Search for SAP-JEE component to define Build Time dependency for our SC.
  • Click on Define Prerequisite Software Components to add selected component.
  • Multiple selections are possible.
  • Similarly, Repeat above-mentioned step for SAP_BUILDT and SAP_JTECHScomponents and add one by one.
  • All added components would be enlisted in table under dependency tab.
  • By completion of this step, SLD configuration for NWDI use is over.
 5.    Configuration of Change management System or CMS 
  • In the browser, start the initial page of the SAP NetWeaver Java Netweaver Development Infrastructure with the following URL http://<host&gt;:<port number>/devinf 
  • Login using NWDI_Admin user. Following Home Page appears.
  • Click Change Management Service. System may prompt to re-enter user and password. Login using NWDI_Admin user. Following screen appears

6.  Create a Domain and Track in CMS 

  • Go to Landscape Configurator to Define Domain and Track for CMS Configuration.
  • Go to Domain Data tab to define a Domain in landscape for SC development.
  • Fill up required parameters with essential and correct information and click Save button to create a Domain.
  • Note: In transport directory, keep the default path as /usr/sap/Jtrans
  • Go to Track Data tab and create New Track.
  • Define Track Id, Track Name and Track Description for New Track
  • Define Development Configuration Path usually <TrackId>/1.0
  • In Software Component section, Add SC in Developed Software Component Table. 
  • New window pop up appears. Look for Software Component, which you have defined in SLD.
  • Select SC and click Add. Click Close to close window.
  • Software Component is added to Developed Software Components under Software Component Section.
  • Click on Save to Finish Track Creation.
  • Select Track on left side table and Go to Runtime Systems Tab on same Track Data Page.
  • Click on change button.
  • Check Development option.
  • There appears Runtime System Configuration Wizard.
  • Fill up required parameters and click next button.
  • In next screen fill required parameters and finish.
  • Runtime System for Development is configured.
  • With this “Training” Track is configured.
  • On completion of Track creation, DTR and CBS are also configured.

7.    Verify CBS and DTR Configuration

  • To check DTR contents use following link http://<host>:<port>/dtr
  • Or use Design Time Repository link available on CMS home page.
  • “Training” Track is available in DTR for use.
  • To check DTR contents use Component Build Service link available on CMS home page.

8.    Import Software Components into this track

The Software Component archives ( .sca files ) must be downloaded from the Service Marketplace ( http://service.sap.com/patches ) and placed into the inboxfolder of the CMS.  The inbox folder can be found under the following path: <CMS Transport Directory>\CMS\inbox, where the <CMS Transport Directory> is specified in the “Domain Data” tab of the CMS Landscape Configurator).
In our case, this path is /usr/sap/JTrans/CMS/inbox                 Or
The .sca archive files can be picked from j2ee server from following location/usr/sap/NWD/SYS/global/CMS_CBS/plugins  Or/usr/sap/NWD/DVEBMGS00/SDM/root/origin_sc/sap.com
 The following .sca files must be placed into the CMS inbox folder:
  • SAP_JTECHS.sca
  • SAP_BUILDT.sca
  • SAP-JEE.sca
Note: The names of .sca files could be different. They may include version numbers, vendor name etc.

9.    Check-In archives

Now we will resume CMS configuration and again go to CMS home page.
  • Open Transport Studio.
  • Select your defined track.
  • Go to Check in tab.
Select all available .sca archive components in table and click Check-In button.
On successful completion, you will get system acknowledgement.

10. Import the checked in archives into the Development system

  • Now go to Development tab, you will see all Checked-In archive components with following parameters for all:
  • State Import Check:                Not Executed
  • State:                                   Waiting for Import
  • Select a components and click on Import-Check button.
  • You will get confirmation dialog to proceed further.
  • After successful completion you will get State Import Check parameter as Check Finished.
  • Perform above step one by one for other available components also.
  • Select all components and click Import Button after completion of above steps.
  • It may take some time.
  • On successful CompletionState parameter of components is changed to Import Finished.

11. Import the checked in archives into the Consolidation system

  • Now go to Consolidation tab of Transport Studio and import checked in archives as done in development tab.
  • Repeat all steps mentioned above to complete this step.
  • By performing above steps, CMS is configured.

12. Configuring Design Time Repository (DTR) in SAP NWDS

Open SAP Netweaver Developer Studio on your client machine.
  • Go to Windows -> Preferences -> Java Development Infrastructure ->Development Configuration
  • Enter J2EE server URL http://<host>:<port> and Ping Server.
On successful connection, system will acknowledge with following message.
  • Go to Windows -> Preferences -> Team -> Ignored Resources
 Make sure that “.classpath” & “.project” resources are checked. This is to avoid their entry to DTR. See below fig for reference.
  • Go to Windows -> Open Perspective -> Others -> Design Time Repository 
  • Repeat same step to open Development Configurations Perspective.
Now Go to Design Time Repository Perspective by clicking on “dtr” icon as shown above in second fig.
  • Right click on offline and click on Create Client. 
Fill all parameters in prompt screen. Click Ok.
  • After client creation, Right click on Offline and Login to DTR system.
Note: Use CMS_Developer User for login to DTR.
You can see created track in your DTR perspective. 
Note: If your created track is not available in DTR, It will be available after following below steps
Switch Development Configurations Perspective.
Go to Local DC Section, shown in the middle of screen.
  • Right click to Import Configuration. 
Following screen appears shown below.
  • Select remote option to get all configurations from DTR.
All available tracks in DTR get displayed.
  • Select your tracks. Open it to level of <Track Name>_dev.
  • Select <Track Name>_dev and click next.
Click Finish button to complete remote configuration import.
On completion of this step, your imported track “DEMO” is available in DC perspective.
Left most area of above screen shows inactive DC’s. Here you can right click on DEMO track to create your new DC.
Active DC tab shows all available active DC’s in DTR. This tab also shows definedSoftware Component Dependencies available under track.
By performing above steps your NWDS is configured with DTR and is ready for use.

Post a Comment

Powered by Blogger.