Maintenance of an NWDI-Driven System
Landscape 
SAP provides standard software for the Java Stack of the SAP Web Application Server (SAP Web AS). 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.
SAP offers various tools that enable customers to import software into Java runtime systems. These tools cover the following aspects, depending on how a customer uses the software applications:
● Installations
Performed using the SAPinst tool
● Support Package imports
Performed using Java Support Package Manager (JSPM)
● Upgrades
Performed using the SAPJup tool
● Software developments in customer landscapes and modifications to the standard SAP system
Performed using SAP NetWeaver Development Infrastructure (NWDI)
This documentation describes the interaction of the various 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 in these landscapes is essential for stable upgrades. Here, the term “Maintenance” includes both upgrades using SAPJup and Support Package imports using JSPM.
For the NWDI, the upgrade process and the update process run on the same principles. This document will therefore concentrate in particular on the update process, on importing Support Packages. It applies in the same way to upgrades.
SAP Standard
SAPinst, JSPM, and SAPJup are used when installing, maintaining, and upgrading the standard SAP system. During these processes, the tools in question import the software component archives (SCAs) directly into the relevant Java runtime systems.
Modifications and Customer Developments
If a customer has developed modifications and enhancements for the standard SAP system using NWDI and wants to update the modified software components with corrections delivered by SAP, NWDI and JSPM (for updates) and SAPJup (for upgrades) need to work together in order to ensure a consistent Java runtime system after the update.
This means you need to perform the following actions, in addition to the deployment of the software components in the runtime systems with the NWDI:
● Import the source code files of the software components into the Design Time Repository (DTR).
● Start the required builds in the Component Build Service (CBS).
● Deploy the modified development components (DCs) in the relevant runtime systems.
● Update the information about the modified software components in the relevant runtime systems.
JSPM also requires the following information:
● What are the system roles in the individual Java runtime systems in the system landscape?
● What is the best installation or upgrade sequence for a software application in the system landscape?
Process Overview
If you use JSPM to update a Java runtime system, JSPM interrupts the import process and queries whether the runtime system is integrated into a NWDI landscape. If you answer yes, JSPM imports only the unmodified software components (SCs) to the runtime system and copies the modified SCs and their dependent SCs to directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME).
From this directory, you check these SCs into the NWDI, import them into the development system for the track and adjust the modifications.
Transport the adjusted modifications through the track and perform the assembly step. After the SC has been assembled successfully, a new SCA is available as a replacement component for the SAP standard in directory $(TRANSDIR)/EPS/in/assembled.
If replacement components are found for all modified SCs, JSPM deploys the modified SCs, together with their dependent SCs for the test and production system.
JSPM handles the NWDI systems Development and Consolidation differently from the Test and Production systems.
For Development and Consolidation, JSPM copies the modified SCs to the appropriate directories; for Test und Production, however, JSPM refuses to deploy until replacement components are made available.
For more information, see the following topics:
● Planning
● Import of Support Packages in the Development System
● Adjusting Modifications with the NWDI
● Importing Support Packages into Follow-On Systems