Applying Single Support Packages 
If you want to update only particular software components that are deployed on the system and do not want to apply complete support package stacks, you can apply single support packages. The import time is shorter for single support packages than for support package stacks. In addition, you can apply newer support packages of SAP software components that have been modified in the NWDI.
Caution
Before you can apply a support package of a given level, you have to update JSPM. More information: Updating Java Support Package Manager
The update of JSPM does not require a restart of the AS Java and does not affect the system operation.
Caution
If you want to apply a support package stack, you must not use this procedure. Instead, you must use Applying a Support Package Stack.
Caution
When updating the system, JSPM may have to perform operations on remote 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.
Note
JSPM can undeploy some DCs if this is specified in respective SCA metadata.
Prerequisites
The AS Java and the database have been backed up. For more information, see Backup and Recovery.
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 was 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 packages you want to apply 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/swdc.
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
Procedure
Choose the Deployment tab.
JSPM guides you through the process of applying support packages 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
Select the Package Type
Select Single Support Packages.
Choose Next.
Software components that are deployed on the system to which you can apply support packages are displayed.
Specify the Queue
To view the details about a support package, choose Show Details.
If JSPM has found any modified software components, they are marked with
.JSPM will select for deployment the software component with the higher version as well as software components with the same version if they contain newer SDAs.
From the Target SP Level dropdown box, select:
<x.x>, where x.x is the support package and patch level, if you do not want to apply a modified software component
<x.x, Modified by NWDI>, if you want to apply a modified software component
skip, if you do not want to apply a software component
It is also possible that JSPM has not found a newer version in the global EPS inbox directory for a software component that is deployed on the system.
Choose Next.
Check Queue
In this step, JSPM checks the deployment queue. The status of the selected support packages 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 are informed that JSPM will not deploy the modified software components, but only transport them together with all other software components that you selected and that are not modified to the CMS transport directory /usr/sap/trans/EPS/in/CMS<hostname><SID>. JSPM deploys 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 are informed that JSPM has found newer versions of modified software components in the global EPS inbox directory, and automatically replaces the original versions with the newer versions. JSPM deploys all software components that are not modified and the replaced versions of the modified software components.
REVISE
You cannot go on with the deployment.
You can view the details about the software 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 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.
If the status of the selected support packages is OK, choose Start.
NoteYou are informed if the AS Java will be restarted during the deployment.
End of the note. NoteIf you have selected to update the kernel, you are prompted to stop any running dialog instances. For more information, see Starting and Stopping the Application Server Java (AS Java). In addition, on Microsoft Windows you are prompted to close the Microsoft Management Console (MMC).
End of the note.
Deploy Queue
Note
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 you selected. The status of all software components changes to SCHEDULED.
Note
If you have selected to update the kernel, and if your system is distributed, during the deployment you are first prompted to stop the primary application server instance and any running dialog instances, and to choose Next. Then you are prompted to start the primary application server instance and to choose Next.
Note
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 conflicts 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.
Note
If deployment stops before all SDAs are deployed, the SCA is half-deployed but SC version is updated. Even though JSPM sees the SC as updated, JSPM accepts for deployment such an SCA with the same version if it contains any newer SDA.
The progress bar shows the progress of the Deploy Queue step.
Completed
The deployment of the support packages can finish with the one of the following statuses:
DEPLOYED
The update is complete when the system and the applications are running.
NoteIf you have selected to update the JSPM when it has been updated, for the update to take effect, you are prompted to restart it. If there are still support packages in status NOT DEPLOYED, JSPM proceeds 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.
End of the note.DEPLOYED WITH WARNING
The support package has been deployed but it is possible that it does not work properly with other deployed software components.
You can view the details about the support package by choosing Show Details.
You can also view the details about the support packages by choosing the Deployed Components tab (see Viewing the Deployed Components).
You can also view the log files. For more information, see Viewing Log Files.
ERROR
An error has occurred during the deployment of the support package.
You can proceed as described for a deployment, which has finished with status DEPLOYED WITH WARNING.
In addition, if you receive an error during deployment message. The error message provides a link to proposed solutions. It also contains a link to an archive with all relevant log files that will help you find out the reason for this error. 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 support package again.
You can stop JSPM by choosing Exit.
Next time you launch JSPM, the Broken Deployment screen appears and you have two options: to resume the deployment or to start a new deployment.
NOT DEPLOYED
JSPM has not attempted to deploy the support package.
If your system is not used for NWDI development, you can proceed as described for a deployment that finished with the 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.
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.
If the deployment of the support packages has finished with status DEPLOYED, you can choose New Deployment or Exit.
Result
The support packages you have selected are deployed.
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.
Note
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 that you selected, both modified and not modified, to the CMS transport directory.
Note
On a UNIX operating system, if you have applied a single support package to update the kernel, you have to execute the saproot.sh script to configure the ownership and permissions of some kernel files. For more information, see Executing the saproot.sh Script.
Note
On an IBM eServer iSeries system, if you have applied a single support package to update 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 is <SID>KRN2.