You are on page 1of 15

UPDATE GUIDE SAP ENHANCEMENT PACKAGE 1 FOR

SAP SOLUTION MANGER 7.0
SIMILARITIES AND DIFFERENCES IN SAP NETWEAVER & SAP SOLUTION MANAGER

Version 1.02 / March 2009

Caution:

The following note ONLY applies to SAP customers in Germany and Austria.
The extent of the usage of the software package „SAP Enhancement Package 1 for SAP Solution Manager 7.0“
depends upon the type of maintenance contract you have signed.
If you have a signed contract for:
- SAP Enterprise Support,
- SAP Product Support for Large Enterprises,
- SAP Premium Support, or
- SAP MaxAttention,
you are authorized to use all functions in the software package, without any restrictions.

If you have signed exclusively standard support contracts, you are allowed to install this software package, but you
are only allowed to use a restricted functionality. You are not allowed to use the following Enterprise Edition functions:
- Business Process Change Analyzer
- Quality Gate Management
- Custom Development Management Cockpit

Der folgende Hinweis betrifft NUR SAP-Kunden in Deutschland und Österreich.
Die Nutzungsmöglichkeiten des Softwarepaketes „SAP Enhancement Package 1 for SAP Solution Manager 7.0“ sind
von Ihrem Pflegevertrag abhängig.
Wenn Sie über einen Vertrag über
- SAP Enterprise Support,
- SAP Product Support for Large Enterprises,
- SAP Premium Support oder
- SAP MaxAttention
verfügen, sind Sie berechtigt, alle Funktionen des Softwarepaketes ohne Einschränkungen zu nutzen.

Wenn Sie ausschließlich Standard-Support-Verträge abgeschlossen haben, dürfen Sie dieses Softwarepaket
installieren und mit eingeschränktem Funktionsumfang nutzen. Die im folgenden aufgeführten Funktionen, die
Bestandteil der Enterprise Edition sind, dürfen nicht genutzt werden:
- Business Process Change Analyzer
- Quality Gate Management
- Custom Development Management Cockpit

...................0 With SAP enhancement packages (EHPs) you can implement functional updates without upgrading your SAP system to a higher release......... 5 Installation Scenarios for SAP Enhancement Packages.............. 6 Installation in Detail .................................................................. 5 Installation of Enhancement Packages for SAP Solution Manager 7. 2 SAP Enhancement Package 1 for SAP Solution Manager 7................................................................................................................. 3 Introduction ...............................................Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7........................................................................................................... This concept is introduced for SAP NetWeaver with SAP enhancement package 1 for SAP NetWeaver 7................0 and their installation procedure.................................. The user interface will be kept stable................................................................... 2 Differences to SAP Enhancement Packages for SAP NetWeaver .....................................0)....... 4 Essentials........................ 4 Target Group......................0 (this is occasionally also referred to as support package stack 18 for SAP Solution Manager 7.............................................................. Note that though the standard transactions for SAP Solution Manager will continue to exist.. 6 Impact of Installation............................................................................................................................................................... Differences to SAP enhancement packages for SAP NetWeaver and SAP ERP are discussed.. 4 SAP Enhancement Package Strategy................... 8 Overview This document gives you an overview of the SAP enhancement packages for SAP Solution Manger 7......................................................................................................................................................................0............................................................................... With the enhancement package concept SAP makes innovations for well-tried systems available in a safe way: SAP enhancement package rules are based on those for SAP‘s support packages (SPs): No table conversions or XPRAs are needed................................ 8 Tools Used for the Installation .......................... Executive Summary SAP Enhancement Package 1 for SAP Solution Manager 7.................................................................................................... new developments delivered with an enhancement package may require the work center user interface..................................................................................................................................................................................... 8 Installation Procedure............... ©SAP AG 2009 ................................0 and will be available for SAP enhancement package 1 for SAP Solution Manager 7............................ Compatibility is guaranteed: There are no changes with regard to inbound or outbound interfaces of components so that communication between systems in the landscape will not change....................................................................................................0 ........................ 6 Installation Strategy for SAP EHPs ...................... there will be no additional training costs.................................................................................................................................... 2 Executive Summary..........................................................................0 2 Table of Contents Table of Contents ..................................... 4 Purpose of this Document ......................................................................................................................

Differences to SAP Enhancement Packages for SAP NetWeaver All SAP enhancement packages serve the same purpose of allowing functional updates of systems without a system upgrade. the release strategy for enhancement packages for SAP Solution Manager differs from the release strategy for SAP enhancement packages for SAP NetWeaver and SAP Business Suite: As soon as the newest enhancement package is available this replaces the former maintenance via support packages. Only changed and new objects are delivered (delta shipment).0. SAP enhancement packages are installed optionally.0 3 With the installation of an SAP enhancement package for SAP Solution Manager. There is a clear separation of functional updates in SAP enhancement packages on the one hand and corrections of errors in support packages on the other – this means less risk of unexpected changes of system behavior. No migration of data or customizing is necessary – this means faster installation. However. Since SAP Solution Manager always has to support the complete range of SAP services and products including the latest versions. SAP Solution Manager is updated to EHP 1 using transaction SAINT and Java Support Package Manager. In case of SAP NetWeaver and SAP ERP. and SAP Solution Manager differ. The installation of an EHP for SAP NetWeaver is performed with SAP Enhancement Package Installer. which runs as a guided procedure in combination with SAP Solution Manager 7. SAP NetWeaver. Software maintenance for SAP Solution Manager is delivered via SAP enhancement packages.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. Therefore enhancement packages for SAP Solution Manager are part of its maintenance strategy and are not optional. generally no hardware upgrade is required so there will be no additional hardware costs in most cases. in some details EHPs for SAP ERP. most importantly in the following: The installation of EHPs for SAP ERP is a selective update of usages in a system. In case of EHPs for SAP NetWeaver and SAP Solution Manager you have one system which is updated as a whole. ©SAP AG 2009 .

this concept has become available for SAP NetWeaver 7.0 SP 17 SP 19* SPS 20* Package Package SPS 18 SPS 21* System Time Maintenance: New: SAP Enhancement Support Package Stack Packages for SAP Solution Manager • Corrections • New & improved functionality • Technically a set of • Mandatory. Getting familiar with these procedures will help you to minimize your installation efforts. The executive summary and introduction provide abstracts for other readers. so you should be experienced in SAP technology.0.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. incl.0 4 SAP Enhancement Packages for SAP Solution Manager Traditional SAP Application New SAP Solution Manager Innovation Lifecycle Lifecycle Cost Upgrade Upgrade to SAP to SAP Solution Solution EHP 1 EHP 2 Manager Manager Support Support incl. new software support packages components and patches *current planning. Target Group This document is written for technical consultants and SAP administrators dealing with SAP Solution Manager 7. SAP 3. updates. SAP Enhancement Package Strategy SAP enhancement packages include functional enhancements and simplifications. This document outlines the basic ideas of the new concept and discusses similarities and differences of SAP enhancement packages and their installations. Innovations.0 with EHP1 and now also for SAP Solution Manager 7. changes still possible Introduction Purpose of this Document SAP enhancement packages are a new way of software delivery that allows you to implement innovations without the need to upgrade your current system.0. which are shipped with SAP enhancement package 1 for SAP Solution Manager. Furthermore. ©SAP AG 2009 . are described later in this document. and upgrades. this document provides you with appropriate links to guides and notes available from SAP.2 7. Introduced for SAP ERP first.

the clear separation of functional updates and corrections means that you can install support packages without changing the applications in their functions or UI. enhancement packages allow you to add functions in smaller steps than during a release upgrade.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. in the equivalent support packages for SAP enhancement packages for SAP Solution Manager. On the other hand.0”. As before. There are three ways to SAP Solution Manager 7. Upgrade an existing SAP Solution Manager system using SAP upgrade tools. SAP enhancement packages for SAP Solution Manager have the same maintenance duration as the underlying SAP Solution Manager release. This guide describes the first scenario “Updating an Existing System of SAP Solution Manager 7.0 including enhancement package 1. SAP provides support packages on a regular basis during the defined maintenance period and. corrections will be available through support packages. ©SAP AG 2009 . Note: Keep in mind that – since EHP development follows support package rules with the exception of containing new features – the installation of an enhancement package for SAP Solution Manager is an update of your system.0 5 Figure 1: SAP’s enhancement package installation on SAP Solution Manager with ABAP and Java stack using transaction SAINT for ABAP and JSPM for the Java stack. Therefore. This update procedure is discussed in chapter “Installation in Detail”. side-effects are minimized and no learning should be required. while EHPs contain newly developed functions Adoption of functional enhancement faster than the SAP Solution Manager release cycle On the one hand. This installation is planned to be available in 2009. Directly install SAP Solution Manager 7. Essentials Some major characteristics comprise the key difference between SAP enhancement packages and previous deliveries and procedures: Clear separation of the shipment of patches and functions with SPs containing corrections. each SAP enhancement package is based on the previous one. Current SAP enhancement packages contain the entire content of earlier packages.0 system using SAINT / JSPM. As a result. Installation Scenarios for SAP Enhancement Packages This section gives you an overview of the dependencies of SAP Solution Manager running on top of SAP NetWeaver 7. in parallel. This upgrade is planned to be available in 2009. SAP enhancement packages are cumulative.0 EHP 1: Update an existing SAP Solution Manager 7.0 including SAP enhancement package 1 using SAPinst.

you can now continuously provide the newest functions to the system along with your regular maintenance activities. It will then be part of the download stack calculated by maintenance optimizer in SAP Solution Manager Installation of Enhancement Packages for SAP Solution Manager 7. Any system has to be updated as a whole. This minimizes the effort (for example. In addition.0 including enhancement package 1. SAP enhancement packages can be installed without causing disruption as a normal maintenance activity together with support packages. see SAP Service Marketplace at http://service.com/instguides SAP Components SAP Solution Manager Release 7. ©SAP AG 2009 . regarding the potential modification adjustment) since you install the enhancement package as part of your normal maintenance processes.0 6 Note: Since SAP Solution Manager is based on SAP NetWeaver 7. no definition of usage type is required for the download: All parts of SAP Solution Manager will be updated. for the Java stack). You cannot update one stack only or a single usage type in the system if there are others installed. Once an SAP enhancement package is installed.com/solutionmanager Media Library Technical Papers with a detailed description of the new and enhanced functions. even when implementing an SAP enhancement package.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. As with enhancement packages for SAP NetWeaver and SAP ERP. you cannot reverse the installation. This guide contains an update for enhancement package 1 including its enhancements.0 Several scenarios and variants are updated in SAP enhancement package 1 for SAP Solution Manager 7. use a sandbox system to explore the new functions. If you are not sure whether you want to leverage dedicated functions. there is a clear dependency: For SAP Solution Manager systems updated to EHP1 you will also need to update the underlying SAP NetWeaver with EHP1. Also see the Release Notes for SAP Solution Manager 7. The download stack defined in maintenance optimizer is installed using transaction SAINT (for the ABAP stack) and Java Support Package Manager (JSPM.0. New features will be delivered with enhancement packages. You can install the enhancement package and support packages using a single queue in transaction SAINT and in the Java Support Package Manager. Content of SAP Enhancement Package 1 for SAP Solution Manager 7.0 SAP enhancement packages for SAP Solution Manager are installed as a whole. Impact of Installation Identical to SAP enhancement packages for SAP NetWeaver. For a complete definitive list and the mapping of scenarios to installable software units. Note: Always install SAP enhancement packages together with a support package stack. You should also remember that EHPs have support packages of their own. together with the required support packages. SAP enhancement packages should be applied within one queue. Installation Strategy for SAP EHPs Since the installation process is coupled with the installation of support packages.0 EHP1 on SAP Service Marketplace at http://service.sap. In order to use synergy effects and to minimize effort. Using this strategy.sap. changes delivered with EHP1 for SAP Solution Manager become immediately visible with the installation because switches are practically not used in EHPs for SAP Solution Manager. Installation Procedure of SAP Enhancement Package 1 for SAP Solution Manager at a Glance SAP enhancement packages for SAP Solution Manager are installed as a whole.0. updating the support package level in SAP Solution Manager is part of the enhancement packages installation process.0 EHP 1 Master Guide for SAP Solution Manager 7.

Prepare the SAP system and update SAP Solution Manager and the installation tools. Compatibility is guaranteed: o No changes with regard to inbound interfaces of components o No changes with regard to other systems (outbound interfaces) Note: Installing an SAP enhancement package does not mean you perform an upgrade. 2.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. SAP enhancement package rules are built on the basis of SAP‘s support package rules: o No table conversions are needed. o Only After Import Methods are executed. Figure 2: What you need to install SAP enhancement package 1 for Solution Manager on a system. No additional hardware is needed. ©SAP AG 2009 . No database upgrade is needed (there might be exceptions for SAP MaxDB). SAP Enhancement Package Installation vs. Use maintenance optimizer in SAP Solution Manager to select the correct packages. 1.0 7 Check. which prerequisites must be met – refer to the section “Preparing the System – Prerequisites for Installation”. EHPs and any required support package stack are downloaded from SAP Service Marketplace and applied using transaction SAINT for the ABAP stack and JSPM for the Java stack (asterisks indicate updated parts of the system). if required. Use the SAP Add-On Installation Tool (transaction SAINT) and the Java Support Package Manager (JSPM) to install the components and support packages. Upgrade Installing SAP enhancement packages has no additional requirements: No DVDs are needed. Installing SAP enhancement packages does not change your landscape setup. Select and download the required components and support packages from SAP Service Marketplace using maintenance optimizer.

Prerequisites for the Installation The enhancement package that you want to install requires a specific support package level in your system. Installation Procedure This procedure follows the Update to SAP Solution Manager 7.Landscape data stack input . we provide an overview of the tools involved in the installation process. Java SAP Solution SAP Solution Manager 7. you can treat SAP enhancement packages like support packages and should combine the application of both in one queue. The installation of the files is performed with transaction SAINT for the ABAP stack and the Java Support Package Manager for the Java stack: install SMP <SID> input ABAP EHP 1 SCF SAINT … .com/instguides SAP Components SAP Solution Manager Release 7.0 Enhancement Package 1: Using SAINT/JSPM on SAP Service Marketplace at http://service.0 / … System Landscape Directory result load JSPM stack Manager 7.0 8 Installation in Detail This section gives you an overview of the steps required for installing an SAP enhancement package.sap. Note: Information on systems used by SAP Solution Manager stems from the System Landscape Directory. It is consumed by SAINT and JSPM – the latter also reads the stack configuration file (SCF) generated by maintenance optimizer. these dependencies are calculated automatically. This is recommended for systems based on SAP NetWeaver AS ABAP and highly recommended for systems based on SAP NetWeaver AS Java. from the point of view of the effort involved. All steps concerning the download of files can be automated by configuring the Software Lifecycle Manager (SLM). You have configured maintenance optimizer in SAP Solution Manager ©SAP AG 2009 . there are mutual dependencies to be taken into account. Maintenance optimizer automatically calculates all support packages that are a prerequisite for the enhancement package installation and includes them in the installation queue.0 SPS X Basket install Figure 3: SAP enhancement package installation process: the big picture of tools and steps involved with SAP Solution Manager 7. SAP Solution Manager takes into account the state of the system for the SAP enhancement package installation using the release/support package state and the contained software versions. With maintenance optimizer in SAP Solution Manager.System States … output input … Down. The download stack is defined in maintenance optimizer.0 EHP 1. However. Then we outline the process itself.0 SPS 15 and higher. The result is a stack configuration file listing the objects that need to be installed in the target system. Tools Used for the Installation As shown in section 2. First. No additional hardware is needed.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. plus the chosen SAP enhancement package. which is needed in JSPM.

see also SAP Note 822380. Then make sure the following requirements are met prior to the enhancement package installation: The system to be updated is fully functional. For more information. If possible use SP 15. Note: Dependend on the SP level of your SAP Solution Manager system there are three different ways to download the required files. Preparations Preparing the SAP Solution Manager System Install at least SAP Solution Manager 7. If you want to use the software lifecycle management capabilities of SAP NetWeaver in maintenance optimizer.0 EHP 1. For more information.01.1. Then you need to use option “Select files manually” in the guided procedure of maintenance optimizer.0 9 You have installed at least SPAM/SAINT version 031 JSPM has been updated to at least 7. Preparing the Java Support Package Manager Before working with JSPM have a look at SAP Note 891983 . Of course.) Update the SAP kernel to SAP kernel 7. . Use user <SAPSID>adm to perform the update.JSPM: Central SAP Note SAP NetWeaver 2004s AS Java. all backups are up-to-date.2.SP 9 – SP 14: Use SAP Service Marketplace + maintenance optimizer for the download with manual file selection Choose the target release. We recommend updating SAP Solution Manger to this state or higher as soon as possible.0 support package 9. Updating ABAP Installation Tools and SAP Kernel Make sure that you have installed at least SPAM/SAINT version 031 (We recommend to always importing the latest version of the SPAM/SAINT update before you import installation packages.SP 8 and lower: Use SAP Service Marketplace + Ticket for the download The software download from SAP Service Marketplace requires maintenance optimizer of SAP Solution Manager. see section Requirements for Free Disk Space in the Update to SAP Solution ©SAP AG 2009 . renamed. you can also include a higher support package level in the installation queue.SP 15 or higher: Use SAP Service Marketplace + maintenance optimizer for the automatic selection of the download With SP 15 the download definition in maintenance optimizer in SAP Solution Manager is fully functional.1and SAPCAR is on the latest version. . .Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. which was delivered with SP 9. Choose the target stack SAP Solution Manager 7. see SAP Note 1137683. or created any directories and files in the following directories and their subdirectories: /usr/sap/<SAPSID>/SYS/exe and /usr/sap/<SAPSID>/SYS/profile. There is enough disk space. The database and the Software Deployment Manager (SDM) repository have been synchronized. With SP 8 and lower use the following path to download the required data instead of using maintenance optimizer: SAP Service Marketplace at http://service.01. You have not deleted.sap. Make sure the user has the appropriate permissions. 09/19/2008 PUBLIC 9/28.0 EHP 1.com/swdc Download Installation and Upgrades Entry by Application Group SAP Technology Components SAP Solution Manager SAP Solution Manager 7.

proceed as follows: o Log on to the central instance host. Choose Enhancement Package Installation and then let maintenance optimizer find the download files. o Choose Save. You can change the password in the secure store as described in SAP Note 870445. o In the Global properties panel. maintenance optimizer supports you in selecting – with SP 9 . Select the product version. Starting with SP 15. you use maintenance optimizer of SAP Solution Manager if you are using SAP Solution Manager 7. The tools then use this information for installing the enhancement package files and support package stacks. The download stack will be applied to the system for both stacks of SAP Solution Manager separately. o Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration Managers ServiceManager. choose the solution for which you want to download enhancement package files and create a new Maintenance Transaction. and then choose Select Download Type and confirm the download. To prevent deployment errors during the enhancement package installation process. select whether you want to download them with the Software Lifecycle Manager (SLM) or with the download basket. set the Custom value of the EventTimeout property to 120.com/instguides SAP Components SAP Solution Manager Release 7. Make sure that the J2EE administrator password stored in the secure store for offline usage is identical with the one stored in the user management engine (UME).0 SP 9 or higher – for lower states. o Restart the Central Instance. Files that are not selected will not be included later in the download. To prevent the SDM from temporarily exceeding the available disk space during the update process. for which you want to install the enhancement package and the systems for which you want to install the enhancement package. see the note in section “Preparations”. Procedure In maintenance optimizer of SAP Solution Manager. Select the required files from the displayed lists (select all files that are assigned to the selected support package stack unless you have already downloaded them).com SAP Solution Manager. To download the files.0 EHP 1.sap. ©SAP AG 2009 . For more information about maintenance optimizer in SAP Solution Manager SP 18. see SAP Note 1274430. you can change the file transfer directory of SDM in a system of SPS 09 or higher.sap.0 10 Manager 7.0 Enhancement Package 1: Using SAINT/JSPM on SAP Service Marketplace at http://service. Prerequisites You have configured maintenance optimizer in SAP Solution Manager as described on SAP Help Portal at http://help.14 you need to use the option to manually select files for download in maintenance optimizer – and downloading all required enhancement package files and support packages.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. Downloading the Enhancement Package Stack To download SAP enhancement packages. maintenance optimizer generates an enhancement package stack configuration file and provides it to the software logistics tools for installation and upgrade using the EPS inbox of the SAP Solution Manager system. In addition.

the SAP Add-On Installation Tool prompts you to perform a modification adjustment during one of the subsequent phases. Decide whether to include modification adjustment transports in the installation queue. To complete the installation process. For the modification adjustment. JSPM is also used to install portal content. Choose between the conventional import mode and the downtime-minimized import mode.com/nw70 SAP NetWeaver 7. The system calculates the complete installation queue including any support package. Return to the initial screen of the SAP Add-On Installation Tool. The import process is completed for the ABAP stack. In the dialog box providing a list of configurations in maintenance optimizer that are available for your system choose the required configuration and confirm.sap. The passwords are available in SAP Note 1169247. In the subsequent installation phases. Check the selection and confirm. Procedure Unpack and load the installation packages. Call transaction SAINT and choose load the installation packages from the application server. see SAP Help Portal at http://help.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. (In case of IBM i5/OS. You have to enter a password for each component. program code and program texts that have been made obsolete by the imported objects are physically deleted from the database.0 11 Update of an ABAP Stack To install the ABAP components of the enhancement package. log on as user <SID>ADM or <SID>OFR. The list of uploaded packages is displayed. The unpacked packages are automatically displayed in the EPS inbox in the transport directory.0 Library <Language> SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Add-On Installation Tool. you use transactions SPAU and SPDD. Unpack the archive containing the packages with the following command using SAPCAR. Log on to the system in client 000 using the appropriate user and navigate to the transport directory. you use the Java Support Package Manager (JSPM). or if the included adjustment transports do not cover all objects that need adjusting. If you have modified SAP objects but have not included any adjustment transports. the packages for the selected configuration are listed. For a detailed description. Update of a Java Stack To install the Java components of the enhancement package.) Then start JSPM on the Deployment tab: ©SAP AG 2009 . In the Add On Selection dialog box.) Start the installation process and choose Stack Configuration. choose Continue. you can also proceed as described below. If the business function you want to realize requires the installation of portal content. you use the SAP Add-On installation Tool (transaction SAINT). (SAP recommends using five parallel R3trans processes for the import. Procedure Make sure you closed the SAP Management Console and the SDM remote GUI client and log on as user <sapsid>adm to the central instance host.

com/JSPM software component to the target SPS level. activate and then deactivate the end-to-end root cause analysis maintenance mode. when logged in as Solution Manager Administrator (by default. Login as J2EE Administrator and go to: Diagnostics Administration Managed systems Agent Administration. select the Java Support Package Manager option and update the sap. On the Deployment tab.0 12 o For JSPM SPS level 16 or higher. Note: You may get a warning telling you that there are patches installed in your system containing fixes. Login as J2EE Administrator and go to: Agent Administration Enable Maintenance Mode. You will get a warning message.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. SP 15 – SP17: Connect to end-to-end root cause analysis (also known as diagnostics) with your web browser. see SAP Note 1124030.com/JSPM software component to the target SPS level. the maintenance mode setting is accessible with transaction SOLMAN_WORKCENTER. Login as J2EE Administrator and go to: Diagnostics Administration Managed systems Agent Administration Enable Maintenance Mode. End-to-end root cause analysis generates self-check reports. select the Business Packages option and update the sap. the end-to-end root cause analysis maintenance mode still has to be activated before deploying further patch levels of the NW LMSERVICE component. consider applying the latest patches of the target SPS level. You will get a warning message. select the Support and Enhancement Package Stack option and choose Next. user SOLMAN_ADMIN). Before deploying the SP and EHP stack. o For JSPM SPS level 15 or lower. confirming that the maintenance mode is enabled. This is possible if you applied patches of the start SPS level that have been delivered later than the target SPS delivery date. Restart JSPM and log on with the SDM password. depending on the SP level of your SAP Solution Manager system: SP 9 and lower: Connect to end-to-end root cause analysis (also known as diagnostics) with your web browser. The EHP components and SP stacks available for deployment in the global EPS inbox directory are displayed. In order not to lose these fixes. Then start JSPM again. Note: When the SAP Solution Manager system is upgraded to EHP 1 and configured. stop JSPM after restart and apply SAP Note 1080821. o For JSPM SPS level lower than 11. Then go to: Root Cause Analysis Agent Administration. which might not be included in the target SPS. If you need to include the latest patches for a particular component during the update process with the SP and EHP stack option. For EHP 1. These self-check reports raise a flag if the maintenance mode hasn’t been activated before the SAP Solution Manager system upgrade. In that case. which are available once the automatic basic configuration of SAP Solution Manager has been performed – see the SAP Solution Manager master guide for further details. confirming that the maintenance mode is enabled. You can activate the end-to-end root cause analysis maintenance mode as follows. SP 10 – SP 14: Connect to end-to-end root cause analysis (also known as diagnostics) with your web browser. confirming that the maintenance mode is enabled. You will get a warning message. you must activate the end-to-end root cause analysis maintenance mode in the SAP Solution Manager system that is being upgraded. Note: ©SAP AG 2009 . Switch the Maintenance Mode radio button to On.

Recommendation: If you must update the kernel binaries of any dialog instances.. choose Next to start the kernel update. JSPM updates the kernel binaries of all instances (including dialog instances and SCS instances in a high availability environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile parameter SAPGLOBALHOST.JSPM performs various status validations and displays the result of each software component (SC) included in the stack definition XML file with the following possible states: o OK: Indicates that the SPS level of the corresponding software component is applicable. The deployment depends on whether the system is used in NWDI. must be updated individually – see “Manually Updating Instances with Kernel Directory Located on Separate Hosts“. JSPM restarts the system for further deployment of the remaining SPs of the stack. these components will be displayed here so that you can select them for deployment. ©SAP AG 2009 . See “Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms” below. Choose Show Details or examine the log files. make sure that the high availability software does not restart the instance automatically during the update If kernel binaries of the SCS instance must be updated individually. The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following steps: o JSPM stops the central instance automatically and requests you to stop all SCS and dialog instances. Note: If the system is running in a high availability environment. perform the update when JSPM is updating the remaining support packages of the stack in order to save time. The deployment cannot be performed until all problems have been resolved. The deployment of the enhancement package components and SPs can end with one of the following statuses: o DEPLOYED: The EHP component or support package has been successfully deployed. After the kernel update. o DEPLOYED WITH WARNING: The EHP component or SP has been deployed but it possibly may not work properly with other deployed components. whose kernel directories DIR_CT_RUN are not effectively linked to SAPGLOBALHOST. In any case. JSPM changes the status to “scheduled”. o After you have stopped all the instances. o WARNING: The corresponding software component comprises custom modifications in an NWDI- controlled system. and if JSPM has found any software components in the global EPS inbox directory. Caution: Kernel binaries of instances. o On UNIX platforms. the SCS kernel must be up- to-date before the next restart. you need to restart the SCS instance manually. you must adjust the ownership and permissions of the kernel binaries before you proceed.0 13 If your system is used for NWDI development and it is either a development (DEV) or a consolidation (CONS) system. choose Start to start the system update. We recommend checking the details. you must do this manually when JSPM is updating the kernel binaries of the central instance. If the status of the selected EHP and SP stack is OK or WARNING.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. o REVISE: Indicates inconsistencies with the corresponding SC. JSPM arranges the kernel update as the very first SP to be applied. Select the EHP components and SPS level. Choose Next in the dialog box when the SCS instance is running again. If the support package stack to be applied includes a kernel update higher than the current kernel’s patch level. After the kernel update. You can display the problems’ details.

again. you can resume deployment.sap. depends on whether the system is managed by NWDI.0 EHP 1 Update to SAP Solution Manager 7.com/instguides SAP Components SAP Solution Manager -> Release 7.0 systems. You can proceed as described for a deployment that finished with status DEPLOYED WITH WARNING. If the correction does not change the contents in the JSPM inbox.com/instguides SAP Components -> SAP Solution Manager Release 7. regardless whether you performed the update manually or by using JSPM. you must adjust the ownership and execution permissions of the kernel binaries after the update. see the following guides. RESOURCE WHERE TO FIND IT Master Guide: SAP Service Marketplace at http://service. Further Information For more information on SAP enhancement packages and the SAP Enhancement Package Installer and the installation of SAP enhancement packages on SAP Solution Manager 7. o NOT DEPLOYED: JSPM has not attempted to deploy the software component for certain reasons. Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms On UNIX platforms. redeploy the EHP components. because both update procedures are performed with the <sapsid>adm user as described in the aforementioned guide. This.0 EHP 1 Installation Guide: SAP Service Marketplace at http://service.sap. The import process is completed for the Java stack. View the details or examine the log files.0 14 o ERROR during the deployment.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. if the correction does changes the contents in the JSPM inbox.0 Enhancement Package 1: Using SAINT/JSPM ©SAP AG 2009 . You must correct the error to be able to continue with the EHP installation.

com. Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The information contained herein may be changed without prior notice. POWER5+. SAP NetWeaver. Intelligent Miner. All other product and service names mentioned are the trademarks of their respective companies. without representation or warranty of any kind. System z. i5/OS. ICA. Informix. if any. All rights reserved. xSeries. PostScript. IBM. pSeries. mySAP. DB2. text. and MultiWin are trademarks or registered trademarks of Citrix Systems. OSF/1. Oracle is a registered trademark of Oracle Corporation. System i5. OS/2. VideoFrame. Java is a registered trademark of Sun Microsystems. Nothing herein should be construed as constituting an additional warranty. mySAP. X/Open. AS/400. Citrix. Sweden. System z9. DB2 Universal Database. POWER. National product specifications may vary. S/390. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. XHTML and W3C are trademarks or registered trademarks of W3C®. AFP. xApps. Adobe. and SAP Group shall not be liable for errors or omissions with respect to the materials. System p5. including but not limited to. and SAP shall not be liable for errors or damages caused by the usage of the Code. graphics. special. used under license for technology invented and implemented by Netscape. System x. Parallel Sysplex. These materials are subject to change without notice. Outlook. the Adobe logo. System p. Inc.0 15 Copyright © Copyright 2009 SAP AG. and PowerPoint are registered trademarks of Microsoft Corporation. xApp. Inc. MetaFrame. These materials are provided “as is” without a warranty of any kind. iSeries. SAP does not warrant the correctness and completeness of the Code given herein. either express or implied.. z/OS. Data contained in this document serves informational purposes only. WinFrame. JavaScript is a registered trademark of Sun Microsystems. SAP shall not be liable for damages of any kind including without limitation direct.Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7. and Motif are registered trademarks of the Open Group. ©SAP AG 2009 . or consequential damages that may result from the use of these materials. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Acrobat. POWER5. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft. OS/400. except if such damages were caused by SAP intentionally or grossly negligent. Windows. AIX. R/3. SAP. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. WebSphere. MVS/ESA. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. Massachusetts Institute of Technology. Tivoli. links or other items contained within these materials. MaxDB is a trademark of MySQL AB. Inc. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the accuracy or completeness of the information. fitness for a particular purpose. indirect. OS/390. the implied warranties of merchantability. OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. zSeries. or non-infringement. Netfinity. UNIX. Program Neighborhood. World Wide Web Consortium. HTML. System i. XML.