Starting the Upgrade Process 

Use

When you use SAPJup to import the new release of the software components into the first runtime system in the sequence, you start a process in which the software components are imported into the runtime system of the NWDI-driven landscape.

Procedure

...

       1.      Start the import of the software components with SAPJup

A dialog box is displayed in which you have to specify the following:

○       Is Web AS Java configured as a runtime system in an NWDI track?

Answer this question with Yes.

If you answer this question with No, modified software components are replaced by new SAP versions. This can stop your own applications from working.

○       What is the role of the system in the track?

Answer this question with DEV or CONS.

If the first runtime system that receives the upgrade from SAPJup is configured as a test or production system in the corresponding NWDI track, you must respond to the query about its role with DEV or CONS; this enables you to make modifications in the logical development system of NWDI. Otherwise, SAPJup will search for replacement components for the modified software components without success.

Result

The SAPJup upgrade process takes place with the execution of two modules: PREPARE and UPGRADE modules. The SCA files are copied during the execution of the  PREPARE module and the deployment takes place during the execution of the UPGRADE module. SAPJup copies all SCAs to the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME)

at the end of its PREPARE module.