Modifications and Comparisons with SPs Using the NWDI

When you use the SAP NetWeaver Development Infrastructure (NWDI) for your development, you can modify the Java-based software delivered by SAP. You receive this software in the form of software component archives (SCAs). You can compare your modifications with software delivered at a later time, which you receive, for example, in support packages (SPs).

• The software has been created using the NWDI.
• The software is delivered together with the source files.
• You use the NWDI to make your modifications.
• All used SCAs are available in the correct versions.

  You can download SCA versions of SAP from SAP Services.

• The software version is defined in your SLD, including the Usage Dependencies.

  If this is not yet true, you can import the current SLD content from SAP.

  You can also do this by manually adding the name, vendor, release and usage dependencies of every SC to be modified and of every SC in the Software Catalog, provided that the SLD information is not available.

  Note

  If you must enhance the content of the SLD manually and the information on the used SCs is not documented otherwise, as a workaround, you can find the data on the used SC versions in the file SAP_Manifest.MF in every software component archive as ReqComp.

  Tip

  The text below: "DevCompVendorexample.orgDevCompNameAPPLICATIONDevCompRelease1.0DevCompPackageTypeSRC_ARCReqCompVendorexample.orgReqCompNameTECHNOLOGYReqCompRelease1.0ReqCompPackageTypenullReqCompVendorsap.comReqCompNameSAP-JEEReqCompRelease6.30ReqCompPackageTypenull"

  means:

  SC Status	Vendor	Name	Release	Package Type
  In development	example.org	APPLICATION	1.0	Source files and archives
  used	example.org	TECHNOLOGY	1.0	null
  used	sap.com	SAP-JEE	6.30	null

  This indicates that the SC APPLICATION is (further) developed by a vendor with the Internet domain example.org in release 1.0 and that it exists in the form of source files and archives. APPLICATION uses the SCs TECHNOLOGY by the same vendor and SAP-JEE by SAP, for which no source files are required.

SAP delivers its software in the form of software component archives, the SCA files. You can modify them in tracks of the NWDI.

1. Copy all SCs involved (SCs to be modified and used SCs) as software component archives into the inbox of the used Change Management Service (CMS).
   Note

   By default, you find this directory under the path <NWDI Installationslaufwerk>:\usr\JTrans\CMS\inbox.

   The version must correspond to the version specified in the usage dependency of the used SC.

2. Create a track for your modification in the CMS Landscape Configurator.
3. Insert the SC(s) to be changed as Software Component for Development. If usage dependencies are defined between several SCs, they must also be defined in the SLD.

   The used SCs are added automatically.

4. Check in all SCs to be modified and all used SCs in the CMS Transport Studio and import all SCAs into this track.

   If this track is imported into a SAP NetWeaver Developer Studio, the DCs of the SCs to be modified as well as the DCs of the used SCs are available.

5. Make the modifications by adding new DCs or by changing existing ones.

   After the steps from Consolidation to Approval, the SC is available in the new version and can be used in the production system.

SPs are also delivered as SCAs. You can, for example, download them from SAP Service Marketplace to use the most recent version. If you do this and you want to keep parts or all of your modifications, you must make a comparison between the versions. Due to the global version history of all source files delivered from the DTR, this is possible also after a transport into a new DTR.

Transferring Changes into the Modification Track

You copy the changes in the SP into the track where you have made your modifications.

1. Copy the SCAs of the SPs into the CMS inbox. You find it under: <installation directory of CMS>/usr/sap/JTrans/CMS/inbox.
2. Check in the modified SC(s) in the CMS Transport Studio and import them into this track.

   When importing file versions that have been modified in a different system - which are thus neither predecessors nor successors of the existing modified version, which could be sorted into the version history - integration conflicts are generated. The DTR detects these conflict.

Detecting Conflicts

Conflicts caused by taking over new versions can be found in the DTR Web UI.

1. To open a collision search, in the DTR Web UI go to <http://<host>:<port>/dtr → system tools → reports → collision search.
2. In the development configuration, select the inactive workspace of every SC concerned by the SP.
3. Choose Show.

   You see the conflicts that exist with the imported versions; the versions are compared as Resource and Colliding Version:

4. Inform the owners of the DCs of the Colliding Version, whose task it is to solve the conflicts.
   Note

Solving Conflicts

Conflicts should be solved by the developer who is responsible for the DC concerned, because the changes must be correct not only formally but also on the semantic level. Developers are informed in the Developer Studio about the new version of the development configuration. All developers who work in this development configuration must remove the old version and import the new one.

Developers can view the conflicts in the SAP NetWeaver Developer Studio → Design Time Repository perspective → Integration Conflictsview. See Design Time Repository Conflicts .

1. The developer of the concerned DC resolves the found conflicts.
   Note

   After the changes have been accepted in the SP, the import of other SPs will not cause any conflicts.

2. The developer activates the changes and releases them.
3. Then proceed with the remaining steps up to the approval of the SC.

Your modifications are now available as an SCA and can be deployed in the production system.