Applying a Support and an Enhancement Package
Stack
Use
You can update all software components of SAPproducts that are deployed on the system by applying a support and enhancement package stack. These stacks are defined by SAP collections of support packages for software components that work best together. In addition, you can apply a support and enhancement package stack, which contains newer versions of SAP software components that have been modified in the NWDI.
Before you can apply a support and enhancement package stack you should read the appropriate guides for your product. For more information, see SAP Service Marketplace on http://service.sap.com/instguides ® Maintenance.
Before you can apply a support and enhancement package stack of a given level, you have to update JSPM to the same level by applying it as a single support package. For more information, see Updating Java Support Package Manager.
The update of JSPM does not require a restart of the J2EE Engine and does not affect the system operation.
If the stack is produced for this system by the Maintenance Optimizer, this option will:
■ upgrade with the included components all components that are already deployed on the system to a higher release or to the same release but a higher support/patch level
■ install new components if there are any in the support package stack.
More information at http://help.sap.com ® SAP Solutions ® SAP Solution Manager ® select a language ® Change Management ® Maintenance Optimizer
Prerequisites
...
● The settings of your system are according to note 723909.
●
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.
●
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 https://service.sap.com/sp-stacks.
●
If the support
package stack you want to apply includes the Enterprise Portal, the SDM
timeout for the automatic start/stop of the J2EE Engine has been increased to
2 hours. For more information about
increasing the SDM timeout, see
SDM
Troubleshooting.
● The <SID>adm user has Read permissions for the global EPS inbox directory /usr/sap/trans/EPS/in.
● The database and the SDM repository have been synchronized. For more information, see JSPM Does Not Update the Versions of the Deployed Components.
● There is enough disk space. For more information, see Requirements for Free Disk Space.
● If you need to include the latest patches for a particular component during the update process you should apply SAP Note 1080821.
Procedure
...
1. Start JSPM
2. 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.
Select Package Type
3. Select Support and Enhancement Package Stack.
If the content of the new package stack requires extension of any of the already installed usage types, then the necessary components are also installed.
4. Choose Next.
Support and enhancement package stacks that are available for deployment from the global EPS inbox directory are displayed.
The following components are displayed so that you can select them for deployment if 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
If your system is not used for NWDI development, or is either TEST or PROD system, these components are not proposed for deployment. They do not contain deployable content but only development content required for DEV and CONS systems.
Specify Queue
5. To view the details about the software components that are part of the 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 stack. The details about all software components that are part of these stacks are displayed.
If JSPM has
found any modified software components, they are marked with 
.
6. Select a stack you want to apply.
By default, the target SP level is the latest available SP.
7. If you do not want to apply the latest stack, from the Target SP Level dropdown box, select the SP level you want and choose Next.
Check Queue
In this step, JSPM checks the deployment queue. The status of the components of the selected stack can be:
● OK
You can go on with the deployment.
● 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, JSPM informs you that it 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, JSPM informs you that it has found newer versions of modified software components in the global EPS inbox directory. It will also 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
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.
8. You will be informed if the J2EE Engine will be restarted during the deployment.
If such a restart is not suitable for your system at the moment you can cancel the process by choosing Cancel.
9. If the status of the selected stack is OK or WARNING, choose Start.
If you have cancelled the previous check, a dialog box will show you the previously validated components. You will have the chance to continue with the deployment of the components from the previous validation or skip them and continue with the current set of components.
If the support package stack includes a kernel, you
will be prompted to stop any running dialog instances. For more information,
see
Starting
and Stopping the J2EE Engine. In addition, on Microsoft Windows you will
be prompted to close the Microsoft Management Console (MMC).
Deploy Queue
JSPM starts the deployment of the software components that are part of the selected stack. The status of all software components changes to SCHEDULED.
If the stack includes a kernel, and if your system is distributed, during the deployment you will be first prompted to stop the central services instance and any running dialog instances, and to choose Next. You will be then prompted to start the central services instance and to choose Next.
To avoid failover of your SAP system, while patching it, temporarily disable the SAP system failover/restart capabilities in your high availability (HA) software. The patch procedure might require the SAP system to be down for a while, which will conflict with the restart/failover actions that are triggered by the HA software. To disable the SAP system failover/restart capabilities, stop the SAP instance, using the HA software, stop the HA software and start the SAP system manually before starting the patch procedure. After the patch procedure has finished, stop the SAP system manually and start it again using the HA software. For more information, contact your HA implementation partner.
Completed
The deployment of the components of the stack can finish with the one of the following statuses:
● DEPLOYED
If the 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 status
of the modified software components is always NOT DEPLOYED. JSPM has
transported the software components of the support package stack, both
modified and not modified, to the CMS
transport directory. The deployment of the modified software components is
handled by NWDI (see
Import of Support
Packages into Follow-On Systems).
10. 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.
11. If the deployment of the support package stack has finished with status DEPLOYED, you can choose New Deployment or Exit.
...
Result
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.
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, including saposcol (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