Help Documentation on NWDI

http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b /frameset.htm

Netweaver Development Infrastructure

Central source file management in the Design Time Repository (DTR) Central build and archive management in the Component Build Service (CBS) Central landscape and transport management in the Change Management Service (CMS). The applications you develop are split into software components (SCs) (the installation units) and development components (DCs) (which are exactly on the granularity of projects and contain all development objects plus the aforementioned metadata).

Development is performed in what is called a track The track also takes care of the phases development and consolidation and all transport processes from start to finish when the application is deployed to the productive system or delivered to customers. In this way you have better control over the development versions and the exact source development.

Design

Local Java Installation

CMS, DTR & CBS

CMS defines source management (DTR) and archive management (CBS) for the new development project. Usually, almost everything you develop is stored in a database. A connection to the database for the software catalog is obtained to keep a track of what is developed. There are also runtime systems for automated deployment during all project phases. They are accessed by the developers either using the Developer Studio or the workplace. The DTR overcomes many of the limitations of file-based versioning systems for all kinds of development objects required in the development process. Java sources, XML files, and so on, are stored in a database, but still they are exposed to the client as files and folders, visible in the Developer Studio. The limitation we overcome is that the file version history is always transported together with the file, so that we can synchronize different DTR over repository boundaries by simple file transports. The CBS is responsible for building the sources that are stored in the DTR and is the central build environment. Unlike in other central builds, the CBS also centrally hosts and makes available the latest archives and build results for all developers. The CBS also makes the integration available on the archives level, even for those objects that are still under development. The build is component-based; if a build fails, only a component is delayed. All other components will simply use the latest valid (that is successfully built) version in a central build. In contrast to the conventional build tools, the goal of the CBS is to automate the build process in an incremental fashion. That is, only the changed files, as well as files that have a dependency on them, are built instead of building all sources from scratch. This incremental builds concept dramatically reduces the source code correction cycles. In addition, in CBS dependent objects are only rebuilt if the public parts they use have been changed

Component Model
Software components (SCs) are delivery and installation units; they group development components without overlapping. For more information, see Software Components. Products these are the overlapping selections of software components. One software component can be part of several products Development components (DCs) are development and build units; they group development objects without overlapping. Development objects created in the context of development components; they are stored as versioned files in the Design Time Repository (DTR).

User Management
2 main groups - NWDI.Developer and NWDI.Administrators User name Cmsadm assigned to NWDI.Administrators group

To allow communication with the SLD, you must additionally assign the UME groups to the following security roles in the J2EE engine: Administrators need the security role LcrInstanceWriterAll Developers need the security role LcrInstanceWriterNR

Team oriented Development

Prepare NWDS http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667 c2b/frameset.htm Create USER1, USER2 and CMSADM in the UME of AS Java of NWDI and SLD. IF SLD and NWDI are on different host. Ensure identical password. The AS Java requires that you change the initial password of a user at the first logon. Therefore, after creating the users, log on to the AS Java once with every user and change the initial password. USER1 Group : NWDI.Developers USER2 Group : NWDI.Developers CMSADM Group : NWDI.Administrators Track Management Create a software component in the SLD that contains the development track Register Prefix Create Domain Create Track Checking In Software Component

Create a software component in the SLD that contains the development track

Define software component

Define product

Define Dependencies
Under Software Catalog, choose the Software Components tab page Define the following dependencies : SAP J2EE ENGINE <Release> (SAP-JEE <Release>) SAP BUILD TOOL <Release> (SAP_BUILDT <Release>) SAP JAVA TECHNOLOGY SERVICES <Release> (SAP_JTECHS <Release>)

Register Prefix
The name server checks the uniqueness of the names and enables you to define name prefixes. The name server is a role of a SLD. The other role is the landscape server role. The setup of the name server takes place in the same way as the setup of the SLD server. Execute the following steps:

Select the landscape type NWDI System. Enter a name for the landscape, for example NWDI. Choose Create. The new landscape is displayed. Select the new landscape. You see the details on the landscape. Choose Systems and then choose Add System to Landscape. Choose the hosted system type System Landscape Directory. You see the installed SLD. Choose OK. Select the SLD. The Details view appears. Select the roles Landscape Server (and/) or Name Server. Save your changes.

Register Prefix II

Development Name Reservation Define Namespace Prefix

Creating DOMAIN
a domain in the Change Management Service (CMS). In this way, you make the development configuration for component-based development available to the SAP NetWeaver Developer Studio, and you define a transport environment. You use this transport environment to transport the software components (SCs) you develop through consolidation and quality assurance to production use. You can specify the Domain ID and the CMS Name only once. If you specified the name Tst already in another example, you must first delete the domain data in the SLD.

Click on Update CMS to retrieve latest SC from SLD

Create a TRACK

SC assigned to this track Note: This is the SC we just defined on SLD

Example ESS (SAP_ESS 600)

Example ESS SLD (see dependencies)

Transport with NWDI Transport Studio

Procedure Check-in archives Import (change request or component) Change Request and Software Component CMS imports the source code into the appropriate repository CMS triggers the activation of the imported changes A central build is performed Import Check If you have modified SAP software component versions in your development track, these modifications can be overwritten by any updates to the component that you import into the track Restore System State Assembly (http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/fram eset.htm) extracts the current state of the software in the DTR workspace of the consolidation system, gets the required archives from CBS, and uses these to assemble a uniquely defined state of the software component. assembly process packs the software component into an archive of type Software Component Archive (SCA). BROKEN - The SC contains broken DCs at assembly and is therefore technically inconsistent DIRTY - The SC contains dirty DCs at assembly. This means that the last SC build process has not yet finished or was stopped in an inconsistent state

Using CTS and NWDI

Using Change and Transport System (CTS) and SAP NetWeaver Development Infrastructure (NWDI) separately CTS for ABAP and NWDI for Java-based Using CTS combined with NWDI. CTS for ABAP and mixed and NWDI for Java-based development single tool to transport parts of one and the same application instead of using different tools for transporting parts of one and the same application. Configure the AS Java System RFC destination - sap.com/com.sap.tc.di.CTSserver Visual Administrator (Cluster Server Services Destinations) Connection Settings, enter the connection data of your CTS server. Under Logon Data, select the Current User (Logon Ticket) option as authentication for the connection to your CTS server. We recommend that you use Single Sign-On (SSO). Use client number set under NON_ABAP_WBO_CLIENT Configure CMS track. You must mark the track as Connected to CTS In the Transport Studio, open the Approval tab. Choose Release to CTS from History button