Upgrading Follow-On Systems
Follow-on systems are systems located on the transport routes that come after the logical development system of the track.
If a runtime system is configured in the consolidation system, use SAPJup to import the same software components here as in the development system. When you do this, the archives are again copied to $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME); however, they are no longer needed by Change Management Service (CMS).
You have imported the source code files of the software components into the development system of NWDI and you have adjusted the modifications there.
Import into the Consolidation System
In the Transport Studio of CMS, choose the Consolidation tab page. The imported software components (SCs) and the change requests resulting from the adjustment of modifications are waiting to be imported.
Import the SCs and change requests in the proposed order.
If you have already made repairs to SCs in the consolidation system, you may need to adjust the modifications again. (See Adjusting Modifications with the NWDI .)
Then choose the Assembly tab page and assemble the modified SCs and all SCs that depend on them. After the SCs have been assembled successfully, the CMS copies the resulting software component archives (SCAs) automatically to the directory $(TRANSDIR)EPS/in/assembled. Here they can be processed further by SAPJup and deployed to the test and production system.
Import into the Test System and Production System
In contrast to the development and consolidation system, the SAPJup tool handles SCs differently in the test and production systems. If SCs have been modified, SAPJup searches the directory $(TRANSDIR)EPS/in/assembled for replacement components. A replacement component is an SC that is a valid successor version both for the modified version of the SC and for the new SAP version of the SC.
If replacement components are found for all modified SCs, SAPJup deploys the replacement components and all other successors of the unmodified SAP components that are detected, in a single action.
If SAPJup cannot find replacement components of the modified SCs (for example, the SC was modified on a different NWDI server), it prompts the user to provide a valid replacement component.
After SAPJup has imported the SCs into the test and production systems, you must empty the import queues of the NWDI. To do this, go to the CMS Transport Studio and choose the Test tab page.
Disable the import lock and import the waiting imports.
In the same way, import the waiting imports into the production system.
The import into the test and production systems is required to update the system status information in NWDI. The NWDI does not deploy the SCAs again.
You have adjusted modifications with the new release of the SAP software components successfully and have successfully upgraded the runtime systems of an NWDI track.