Maintenance of an NWDI-Driven System Landscape 

Use

SAP provides standard software for the Java Stack of the SAP NetWeaver Application Server. This software can either be implemented directly by customers or adapted to customer-specific processes. This software is subject to maintenance processes that can run in different ways. An important aspect of these maintenance processes is importing software updates into the existing Java runtime systems. Use the SAPInst, JSPM, and SAPJup tools when installing, maintaining, and upgrading the standard SAP system. During these processes, these tools can support you in the process of importing the SC archives (SCAs) directly into the relevant Java runtime systems. These tools cover the following aspects (depending on how you use the software applications):

·        Installation.

Use the SAPInst tool.

·        Support Package imports.

Use the Java Support Package Manager (JSPM) tool.

·        Upgrades.

Use the SAPJup tool.

·        Software developments in customer landscapes and modifications to the standard SAP system.

Use the SAP NetWeaver Development Infrastructure (NWDI).

If a customer has developed modifications and enhancements for the standard SAP system using NWDI and wants to update the modified SCs with corrections delivered by SAP, the NWDI and JSPM (for updates) and SAPJup (for upgrades) need to work together to ensure a consistent Java runtime system after the update.

This documentation describes the interaction of the tools in system landscapes whose Java runtime systems have been added to the NWDI configuration. The information that the NWDI has about the software components (SCs) in these landscapes is essential for stable upgrades. Note that the term maintenance refers to both upgrades using SAPJup and Support Package imports using JSPM.

Procedure

...

       1.      Plan your update using JSPM or upgrade using SAPJup. Take the required Preparation Steps.  

       2.      Continue with the steps of the update or the upgrade.

¡        For update, see Update Using JSPM.

¡        For upgrade, see Upgrade Using SAPJup.

       3.      If the NWDI server and the runtime system do not share one and the same transport directory, for example due to security reasons or caused by the physical distance between the NWDI server and the runtime system. You have to make manual copies of files at certain points in the process. You can use operating system utilities (ftp, cp, or copy) to make these file transfers. You must intervene the process at the following stages:

...

¡        During an import into a J2EE system that acts as a Dev or Cons system within an NWDI track, JSPM and SAPJup copy all SCAs into the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME). You have to copy these files manually into the corresponding directory on the NWDI server.

¡        After the assembly of the modified software components in the NWDI track, the modified SCAs are available in the directory $(TRANSDIR)/EPS/in/assembled on the NWDI server. You have to copy these files manually into the corresponding directory on the J2EE runtime system. See Importing Support Packages into Follow-On Systems.