Applying a Support Package StackYou can update all software components of SAP products that are deployed on the system by applying a support package stack. Support package stacks are defined by SAP collections of support packages for software components that work best together. In addition, you can apply a support package stack, which contains newer versions of SAP software components that have been modified in the NWDI.

Before you can apply a support package stack of a
given level, you have to update JSPM to the same level. More information:
Updating Java
Support Package Manager
The update of JSPM does not require a restart of AS Java and does not affect the system operation.

When updating native binaries (Kernel, SAPJVM, IGS), JSPM has to restart all the instances in the cluster (SID).
■ Make sure that one OS user and password can control (start/stop) all the instances.
■ Remote instances especially those on UNIX may need additional configuration at OS level (such as PAM) so JSPM can control them. For details see SAP note 927637.
...
●
If the system is
running in a high availability environment, execute the steps described in
Preparing Systems
That Run in High Availability Environment
● Read the respective SP Stack Guide as it contains a step-by-step description of the procedure.
● The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up. For more information, see Backing Up and Restoring AS Java.
● Directories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap/<SID>/SYS/exe and /usr/sap/<SID>/SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.
●
If your database is
MaxDB, the overwrite mode for the log area has been set. For more information,
see
Changing
Log Settings.
● If your database is MaxDB, configure appropriately the number of database connections as described in SAP Note 757914.
● The support package stack you want to apply and the corresponding stack definition XML file have been downloaded to the global EPS inbox directory /usr/sap/trans/EPS/in. For more information about SAP products, see SAP Service Marketplace at service.sap.com/sp-stacks.
● The <SID>adm user has Read permissions for the global EPS inbox directory /usr/sap/trans/EPS/in.
●
There is enough
disk space. For more information, see
Requirements for Free
Disk Space.
●
JSPM is started.
More information:
Starting
JSPM
...
1. Choose the Deployment tab.
JSPM guides you through the process of applying a support package stack via a wizard, which consists of the following five steps: Select Package Type, Specify Queue, Check Queue, Deploy Queue, and Completed.
JSPM also detects the NWDI role of the system. It can be one of:
○ development/consolidation
○ test/production
○ no role
2. Select Support Package Stack.
3. Choose Next.
Support package stacks that are available for deployment from the global EPS inbox directory are displayed.

The following components will be displayed so that you can select them for deploymentif your system is used for NWDI development, and it is either a DEV or a CONS system, and if JSPM has found them in the global EPS inbox directory:
■ sap.com/SAP_BUILDT
■ sap.com/EP_BUILDT
■ sap.com/TEALEAF
■ sap.com/STRUTS
■ sap.com/SAP-CRMJAV
■ sap.com/SAP-SHRJAV
■ sap.com/SAP-IPCMSA
■ sap.com/SAP-CRMWEB
■ sap.com/SAP-SHRWEB
■ sap.com/VTP_BUILDT
■ sap.com/MOIN_BUILDT
■ sap.com/ESMP_BUILDT
■ sap.com/ESCONF_BUILDT
■ sap.com/BPEM-BUILDT
If your system is not used for NWDI development, or is either TEST or PROD system, these components will not be proposed for deployment. They do not contain deployable content but only development content required for DEV and CONS systems.
4. To view the details about the software components that are part of a support package stack, choose Show Details.
One stack definition XML file may contain many product support package stacks. For each product, however, there may be only one support package stack. The details about all software components that are part of these support package stacks are displayed.
If JSPM has
found any modified software components, they are marked with
.
5. Select a support package stack you want to apply.
By default, the target SP level is the latest available SP.
6. If you do not want to apply the latest support package, from the Target SP Level dropdown box, select the SP level you want and choose Next.
In this step, JSPM checks the deployment queue. The status of the components of the selected support package stack can be:
● OK
● WARNING
You can go on with the deployment or you can change the content in the global EPS inbox directory and go back to the Select Package Type wizard step. We recommend that you view the details about the component by choosing Show Details:
○ If your system is used for NWDI development, and it is either a DEV or a CONS system, you will be informed that JSPM will not deploy the modified software components, but only transport them, together with the other software components of the support package stack that are not modified, to the CMS transport directory /usr/sap/trans/EPS/in/CMS<hostname><SID>. JSPM will deploy only the software components that are not modified.
○ If your system is not used for NWDI development, or if your system is used for NWDI development and it is either a TEST or a PROD system, you will be informed that JSPM has found newer versions of modified software components in the global EPS inbox directory, and will automatically replace the original versions with the newer versions. JSPM will deploy all software components that are not modified and the replaced versions of the modified software components.

If your system is used for NWDI development, and it is either a DEV or a CONS system, these components will always be with status WARNING if you select them:
■ sap.com/SAP_BUILDT
■ sap.com/EP_BUILDT
■ sap.com/TEALEAF
■ sap.com/STRUTS
■ sap.com/SAP-CRMJAV
■ sap.com/SAP-SHRJAV
■ sap.com/SAP-IPCMSA
■ sap.com/SAP-CRMWEB
■ sap.com/SAP-SHRWEB
■ sap.com/VTP_BUILDT
■ sap.com/MOIN_BUILDT
■ sap.com/ESMP_BUILDT
■ sap.com/ESCONF_BUILDT
■ sap.com/BPEM-BUILDT
If you have selected the component for deployment, JSPM will never deploy it, but only transport it to the CMS transport directory.
● REVISE
You cannot go on with the deployment.
You can view the details about the component by choosing Show Details.
If your system is not used for NWDI development, or if your system is used for NWDI development, and it is either a TEST or a PROD system, and you want to apply a support package stack that includes modified software components for which JSPM does not find newer versions in the global EPS inbox directory, these software components will always be with status REVISE.
You have to change the content in the global EPS inbox directory and go back to the Select Package Type wizard step.
7. If the status of the selected support package stack is OK or WARNING, choose Start.

You will be informed if the AS Java will be restarted during the deployment.

If the support package stack includes a kernel, you
will be prompted to stop any running additional application server instances.
For more information, see
Starting and Stopping
the Application Server Java (AS Java). In addition, on Microsoft Windows
you will be prompted to close the Microsoft Management Console (MMC).

If the JSPM is running on a distributed system, it could request you to enter <SID>adm user and password before the deploy operation.
JSPM starts the deployment of the software components that are part of the selected support package stack. The status of all software components changes to SCHEDULED.

If the support package stack includes a kernel, and if your system is distributed, during the deployment you will be first prompted to stop the primary application services instance and any running dialog instances, and to choose Next. You will be then prompted to start the primary application services instance and to choose Next.

If deployment stops before all SDAs are deployed, the SCA is half-deployed but SC version is updated. If the update is restarted from the beginning, JSPM will not deploy remaining SDAs from the aborted SCA because it sees the SC as updated.
You have to resume the deployment with the existing queue in JSPM. To do so, in the JSPM GUI you should press the Resume button.
The deployment of the components of the support package stack can finish with the one of the following statuses:
● DEPLOYED

If the support package stack includes the JSPM, when it has been updated, for the update to take effect, you will be prompted to restart it. If there are still components in status NOT DEPLOYED, JSPM will proceed with their deployment when you start it again.
Bear in mind that you must not change the content of the global EPS inbox directory before the deployment has finished.
● DEPLOYED WITH WARNING
The component has been deployed but it is possible that it will not work properly with other deployed software components.
You can view the details about the component by choosing Show Details.
You can also
view the details about the component by choosing the Deployed Components tab (see
Viewing the Deployed
Components).
You can also
check the log files. For more information, see
Viewing Log Files.
● ERROR
An error has occurred during the deployment of the component. You can proceed as described for a deployment that finished with status DEPLOYED WITH WARNING.
In addition, if you receive an error during deployment message, you have the following options:
○ If you have corrected the error, but not by changing the content of the global EPS inbox directory, you can choose Resume.
The deployment is resumed from the Deploy Queue wizard step.
○ If you have corrected the error by changing the content of the global EPS inbox directory, you can choose New Deployment and try to deploy the stack again.
○ You can stop JSPM by choosing Exit.
Next time you launch JSPM, the Broken Deployment screen appears and you will have the two options: to resume the deployment or to start a new deployment.
● NOT DEPLOYED
JSPM has not attempted to deploy the component.
○ If your system is not used for NWDI development, you can proceed as described for a deployment that finished with status ERROR.
○
If your system is
used for NWDI development, and it is either a DEV or a CONS system, the
deployment of the modified software components is handled by NWDI (see
Import of Support
Packages into Follow-On Systems).
8.
To view some
statistics for your patch procedure and to send feedback to SAP about your
experience with JSPM, choose Evaluation Form. For
more information, see
Evaluation Feedback
and Statistics Form.
9. If the deployment of the support package stack has finished with status DEPLOYED, you can choose New Deployment or Exit.
...
The deployed components on the system are updated to the newer versions defined in the support package stack you have selected.
On the Deployed Components tab page, the details about the SP level and counter of the respective deployed components are updated.
Upon successful deployment any inactive usage with all of its components deployed is activated. This is done only for active products.

If your system is used for NWDI development, and it is either a DEV or a CONS system, on the Deployed Components tab page, the details about the modified software components are not updated. JSPM has transported the software components of the support package stack, both modified and not modified, to the CMS transport directory.

On a UNIX operating system, if you have applied a support package stack that includes the kernel, you have to execute the saproot.sh script to configure the ownership and permissions of some kernel files (see Executing the saproot.sh Script).

On an IBM eServer iSeries system, if you have applied a support package stack that includes the kernel, a new kernel library is installed during the patch procedure and applied to the system. If you want to use the current name of your kernel library, you have to rename the libraries manually after the patch. The pattern for the name of the new kernel library is the following <SID>KRN<n>, where n is the next available number. For example, if the existing kernel library for a system is <SID>KRN1, the new kernel library will be <SID>KRN2.
See also:
Maintaining Modified
Java Runtime Systems Using NWDI