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).
After importing and integrating updates of the software that do not correspond to the component model, follow the steps Detecting Conflicts and Solving Conflicts. The prerequisite is that development, modification and update are carried out using the Design Time Repository (DTR).
You can download SCA versions of SAP from SAP Services.
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.
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.
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.
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.
The used SCs are added automatically.
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.
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.
Make this comparison before you deploy the SP into the production systems.
Transferring Changes into the Modification Track
You copy the changes in the SP into the track where you have made your modifications.
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.
You see the conflicts that exist with the imported versions; the versions are compared as Resource and Colliding Version:
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 .
After the changes have been accepted in the SP, the import of other SPs will not cause any conflicts.
Your modifications are now available as an SCA and can be deployed in the production system.