Update Using JSPM
Use
When you use JSPM to update a Java runtime system, JSPM detects whether the runtime system is integrated into a NWDI landscape. JSPM imports all SCA files to the runtime system and also copies them from the inboxdirectory 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 the system is Test or Production, JSPM asks you to select which version to deploy for each modified component. You can select the original component or a replacement component.
JSPM handles the NWDI systems Development and Consolidation differently from the Test and Production systems. For Development and Consolidation, JSPM deploys and copies all SCAs to the appropriate directories; for Test and Production, however, JSPM asks you to select which component to deploy.
Prerequisites
If you have modified SAP software components in NWDI and you want to update those modified SCs with corrections delivered by SAP, you need to do a modification adjustment in NWDI before you deploy the updates to the runtime system. NWDI and JSPM need to work together for this 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 SCs in the runtime systems with the NWDI:
● Import the source code files of the SCs into the Design Time Repository (DTR).
● Start the required builds in the Component Build Service (CBS).
● Deploy the modified development components in the relevant runtime systems.
● Update the information about the modified SCs in the relevant runtime systems.
● Determine the best installation or upgrade sequence for a software application in your system landscape.
Procedure
Steps of Update Process
...
2. Start the import of the Support Packages with the JSPM. See Applying Single Support Packages.
When you use the JSPM to import the Support Packages into the first runtime system in the sequence, you start a process in which the Support Packages are imported into the runtime system of the NWDI-driven landscape. After the deployment, the JSPM copies all SCAs to the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME). This directory is a temporary import directory for CMS.
3. Adjusting Modifications with the NWDI
4. Importing Support Packages into Follow-On Systems.
5. Follow-On Tracks
If you have modified SAP software components in track A and created new modified replacement components as described, you must copy these replacement components from the directory $(TRANSDIR)/EPS/in/assembled to the directory $(TRANSDIR)/EPS/in. This enables JSPM and SAPJup to include these replacement components in follow-on tracks. If these replacement components are not modified further in follow-on tracks, JSPM and SAPJup can perform the deployment directly.
Modified software components can be detected and replaced both for individual Support Packages and for Support Package stacks, as well as for upgrades.
Special Cases
For information about how to exclude some of the files from deployment when updating, see Excluding Software Components from Deployment.