SAP NetWeaver Development Infrastructure 

This release note describes functional enhancements of the SAP NetWeaver Development Infrastructure (short: NWDI, up to this release: SAP NetWeaver Java Development Infrastructure, JDI).

The NWDI combines the functionality of Change Management Service (CMS), Design Time Repository (DTR), and Component Build Service (CBS). Since they are integrated into a common development process and also work together, they will discussed together. The development is based on the SAP Component Model.

Technical Data

Function is	Changed
For Release	Software Component ·        Component: SAP NetWeaver ·        Release: 2004s
Assignment to the Application Components	·        <BC-CTS-CMS> <Change Management Service> ·        <BC-CTS-DTR> <Design Time Repository> ·        <BC-CTS-CBS> <Component Build Server and Component Infrastructure>
Country Setting	Valid for all countries

Use

The changes to functions of the SAP NetWeaver Development Infrastructure that are described here, make the development of Java-based software more efficient.

Component Model

A new type of development component (DC) is available: The DC type External Library allows you to make functions that exist only as jar files available in the SAP Component Model. Jar files are copied to a generated folder of the DC and made available via public parts. Creating the new DC type is supported by the wizards in the SAP NetWeaver Developer Studio.

Change Management Service (CMS)

Clearer overview of the CMS contents:

·        Clearer representation of the transports in the Transport View of the SAP NetWeaver Developer Studio: Canceled transports are collected in the "Failed" directory. "Restart export" can be chosen only from this directory.

·        The Change Request Details view now shows a list of the activities, which have been propagated with this change request.

Extended functionality:

·        In the assembly step you can determine how the Patch Level attribute is set.

·        The system information on the J2EE engine now contains information on components that have been deployed using the CMS.

Design Time Repository (DTR)

Changes in the Web UI of the DTR facilitate navigation:

·        In the Web UI, different icons are used for the different resource types file, folder and workspace.

·        The folders are now displayed in hierarchical order. Various administrative top-level folders have been hidden.

·        You can search for files and folders by names and paths. You can use wildcards in the search term.

·        The path /dtr/system-tools provides tools for setting the DTR display name and for integrating a name server.

¡        Administrative toolsallow you to commit or reverse temporary name reservations on the name server. To be able to use this functions, the J2EE engine must be configured for SSL use.

¡        Reporting tools allow you to search for activities, collisions, resource details, workspace comparison and workspace integrations.

·        When comparing workspaces, you are now able to select the comparison on the integrations level as well.

There are improvements concerning the handling of integration conflicts.

·        Deleting (discarding) versioned resources is now possible by means of open activities without immediate check-in.

·        Closed versions (discard versions) in open activities can be discarded.

Another enhancement improves the user management with LDAP.

·        For using group names, the DTR provides unique IDs.

Component Build Service (CBS)

The changes to the CBS concern the CBS Web UI:

·        Enhancements in the Buildspaces Details view: The Development Components tab page now shows the following information on development components (DCs). (You can open each of the following tab pages by choosing “view” in the drop-down list):

¡        Top-level development components

¡        OK development components

¡        Broken development components

¡        Dirty development components

·        You can filter the DCs display using the following criteria:

¡        All DCs – All development components of the selected software component (SC).

¡        Broken by itself DCs – All DCs with defective metadata or compilation errors.

¡        Broken due to Used DCs – All DCs that appear in a (prohibited) cyclic dependency or use broken DCs.

¡        All OK DCs – All DCs without build errors.

¡        Broken DCs – All DCs that cannot be built due to errors.

¡        Dirty DCs – All DCs that will be newly built or used in an automatic rebuild.

·        Filtering according to build variants. If no selection is made, the worst case will be displayed.

·        Enhancements of the Development Components tab page:

¡        Collisions – For all compartments you find a link to the DTR to check for existing collisions of a DC or its child DCs.

¡        Compile state – Shows the build status of the DCs.

¡        Metadata – Shows the status of the DC metadata.

¡        Cyclefree – Shows whether or not a DC has a cyclic dependency.

¡        Usages – Shows whether or not used DCs have the status broken (for the selected build variant).

¡        Pending activities – For all compartments that contain source files you find a link to the Activities view.

¡        Unreleased activities – You find a link to all compartments that contain source files. Unreleased activities of the DC are shown.

Effects on Existing Data

The changes have no effects on the development made so far in the development infrastructure.