You have set up SAP NetWeaver Development Infrastructure on NW 04 and developed your own software components (SCs). Now some time has passed, and you want to upgrade your landscape to NetWeaver 2004s, which also makes it necessary to move your SCs to a new version.
So how would you do this? First of all, a few remarks on terminology and the technical background:
- The terms Release in NWDI and Version in SLD are synonymous. So if you create a software component version 1.0 in SLD, it will appear as Release 1.0 in CMS after the data has been transferred (i.e. after you have performed Update CMS).
- The Software Component Name in NWDI is labeled Name in SLD. The name with which you see the software component version in SLD maps to the caption of it in NWDI.
- On the basis of the Software Component Name, NWDI checks whether a software component can be transported via a track connection. The release number is not relevant for this check.
Now back to the task at hand.
You want to migrate your SCs from NW 04 to NW 2004s. The following graphic shows what you need to do.
In detail, you need to do the following:
- Create a new version of your developed SCs in SLD with new dependencies. For example, if you have an SC Application version 1.00 depending on DI BUILD TOOL 6.40, create a version 2.00 of Application that depends on DI BUILD TOOL 7.00). Your SC might also require new SC dependencies (EPBC, KM, BASETABLES). See the documentation for the specific applications for details.
Note that the Software Component Name must not change for version 1.00 and version 2.00. Otherwise, the track connection will prevent the import into the new track. In our example, Application must stay Application and cannot change its name from one version to the next.
- Update CMS.
- Define a new track in CMS using the newer versions.
- Create a track connection of type Transport from the old track to the new track.
Note that the package type for your software components needs to be set to Source or Source and Archive. This setting defines that the source code for your developed SCs is packed into the SCA during assembly. Otherwise, you wont be able to change the sources in the new track. If you dont want your customers to receive the source code for your SCs, you need to define an additional track with package type Archive through which you can route your deliveries, so that the source code is separated from your delivered product.
(For more information, see http://help.sap.com/saphelp_nw2004s/helpdata/en/24/1909dbc6024c8e81951b1e0d646910/content.htm in the documentation.)
- Assemble your version 1 in the old track and approve it for delivery to the next track.
- Transport all sources from your old track to the new track.
- Import new 04s/7.00 archives to trigger the rebuild.