SAP Support Package Single Application

-

SAP Support packs Installation : Single Stack 


Applying Single Support Packages 


Use 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.

Before you can apply a support package 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 the AS Java and does not affect the system operation.

If you want to apply a support package stack, you must not use t
his procedure. Instead, you must use Applying a Support Package Stack.
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.
Prerequisites 
●  If the system is running in a high availability environment, execute the steps described in Preparing Systems That Run in High Availability Environment 
●  The 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 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  1.  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 Package Type  2.  Select Single Support Packages .  3.  Choose Next. Software components that are deployed on the system to which you can apply support packages are displayed.
The following components are displayed so that you can select them 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 ■  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 a TEST or PROD system, these components are not proposed for deployment. The reason is that they do not contain deployable content but only development content required for DEV and CONS systems.











Specify Queue  4.  To view the details about a support package, choose Show Details . If JSPM has found any modified software components, they are marked with .  5.  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. 
 6.  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.

If your system is used for NWDI development, and it is either a DEV or a CONS system, these components are always 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 one of these components 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 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.  7.  If the status of the selected support packages is OK, choose Start.
You are informed if the AS Java will be restarted during the deployment.

If you have selected to update the kernel, you are 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 are prompted to close the Microsoft Management Console (MMC).
Deploy Queue

If 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.

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 additional application server instances, and to choose Next. Then you are prompted to start the primary application server 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.









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.
Completed The deployment of the support packages can finish with the one of the following statuses: ●  DEPLOYED

If 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. 

●  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, 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 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. Fore more information, 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 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.

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.

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, including saposcol. For more information, see Executing the saproot.sh Script.

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.

Comments

Post a Comment

Popular posts from this blog

SAP NWA: Net Weaver Administration Tool

-
SAP ERP NWA Tool    SAP NetWeaver Administrator  Use SAP NetWeaver Administrator is a Web-based tool for administration and monitoring that offers a single entry point to configure, administer, and monitor your SAP NetWeaver system, its components, and the applications running on top of it. Prerequisites The Application Server Java (AS Java) is running. Features The SAP NetWeaver Administrator unifies the most important administration, monitoring, and troubleshooting tools. Some of the main SAP NetWeaver Administrator features are:  ●  A single, central tool for administration, troubleshooting, and problem analysis of your SAP NetWeaver system. You can perform administration tasks, such as starting and stopping instances, checking and modifying configuration settings, analyzing logs and traces, ensuring the error-free functioning of all system components by continuous system monitoring.  ●  An easy-to-use, task-oriented interface.  ...
Read more

Advanced JAVA

-
Advance JAVA : IT Training : Scope n Overview : Content Advanced Java Training 1  About Advanced Java Training 2  Advanced Java Training Course Prerequisite 3  Advanced Java Training Course Objective 4  Advanced Java Training Course Duration 5  Advanced Java Training Course Content Overview 6  JDBC 7  Servlets 8  JSP 8.0.1  share training and course content with friends and students: 8.1  Share this: About Advanced Java Training  The course builds a strong understanding of JDBC Technology. It gives in to demonstrate why Servlets are the cornerstone of Java’s Web platform. It then shows how JSP is built on the Servlet architecture. Additionally, the class shows students how to use JSTL, custom tags and expression language to reduce Java code in Web pages while adding tremendous power and capability to those pages. The class culminates in an exploration of Java MVC frameworks like Struts at...
Read more

SAP BASIS SPOOLING : Printing problems and general issues

-
Image
SAP BASIS Printing problems : General Issues How to Resolve SAP Printing Problems Print request from SAP R/3 is not printing. Try to print something else from a different application (for instance an email message or a page from Netscape) via the network. If you cannot print at all then the problem is not SAP printing, but the network. If you can print a file from a different application but not from SAP, then the problem is SAP printing and probably not the network. If you have a local IT support provider , report the problem to this person. Tell your IT support provider the four-character printer name, e.g. "wtpr". Remember to give the four-character name of the printer and its location. You can find this information in SAP by looking at your User Profile or opening the Print Screen List screen. the SAP system from which you sent the print request the spool request number displa...
Read more