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
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 2

Table of Contents
Table of Contents .................................................................................................................................................... 2
Executive Summary................................................................................................................................................. 2
SAP Enhancement Package 1 for SAP Solution Manager 7.0.............................................................................. 2
Differences to SAP Enhancement Packages for SAP NetWeaver ........................................................................ 3
Introduction ............................................................................................................................................................. 4
Purpose of this Document ................................................................................................................................... 4
Target Group....................................................................................................................................................... 4
SAP Enhancement Package Strategy.................................................................................................................. 4
Essentials................................................................................................................................................................ 5
Installation Scenarios for SAP Enhancement Packages....................................................................................... 5
Installation of Enhancement Packages for SAP Solution Manager 7.0 ................................................................. 6
Impact of Installation............................................................................................................................................ 6
Installation Strategy for SAP EHPs ...................................................................................................................... 6
Installation in Detail ................................................................................................................................................. 8
Tools Used for the Installation ............................................................................................................................. 8
Installation Procedure.......................................................................................................................................... 8

Overview
This document gives you an overview of the SAP enhancement packages for SAP Solution Manger 7.0 and their
installation procedure. Differences to SAP enhancement packages for SAP NetWeaver and SAP ERP are discussed.

Executive Summary
SAP Enhancement Package 1 for SAP Solution Manager 7.0
With SAP enhancement packages (EHPs) you can implement functional updates without upgrading your SAP system
to a higher release. This concept is introduced for SAP NetWeaver with SAP enhancement package 1 for SAP
NetWeaver 7.0 and will be available for SAP enhancement package 1 for SAP Solution Manager 7.0 (this is
occasionally also referred to as support package stack 18 for SAP Solution Manager 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. 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.
The user interface will be kept stable; there will be no additional training costs. Note that though the standard
transactions for SAP Solution Manager will continue to exist, new developments delivered with an enhancement
package may require the work center user interface.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 3

With the installation of an SAP enhancement package for SAP Solution Manager, generally no hardware upgrade is
required so there will be no additional hardware costs in most cases.
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.
Only changed and new objects are delivered (delta shipment). No migration of data or customizing is necessary –
this means faster installation.
Software maintenance for SAP Solution Manager is delivered via SAP enhancement packages.

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. However, in some details EHPs for SAP ERP, SAP NetWeaver, and SAP Solution Manager differ, 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.
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.0.
SAP Solution Manager is updated to EHP 1 using transaction SAINT and Java Support Package Manager.
In case of SAP NetWeaver and SAP ERP, SAP enhancement packages are installed optionally.
Since SAP Solution Manager always has to support the complete range of SAP services and products including the
latest versions, 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. Therefore
enhancement packages for SAP Solution Manager are part of its maintenance strategy and are not optional.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.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. incl.
SAP 3.2 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, new software
support packages
components
and patches

*current planning, 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. Introduced for SAP ERP first, this concept has become available for SAP
NetWeaver 7.0 with EHP1 and now also for SAP Solution Manager 7.0. This document outlines the basic ideas of the
new concept and discusses similarities and differences of SAP enhancement packages and their installations.
Furthermore, this document provides you with appropriate links to guides and notes available from SAP. Getting
familiar with these procedures will help you to minimize your installation efforts.

Target Group
This document is written for technical consultants and SAP administrators dealing with SAP Solution Manager 7.0, so
you should be experienced in SAP technology, updates, and upgrades. The executive summary and introduction
provide abstracts for other readers.

SAP Enhancement Package Strategy

SAP enhancement packages include functional enhancements and simplifications. Innovations, which are shipped with
SAP enhancement package 1 for SAP Solution Manager, are described later in this document.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.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.

SAP enhancement packages are cumulative. Current SAP enhancement packages contain the entire content of earlier
packages. As a result, each SAP enhancement package is based on the previous one. SAP enhancement packages
for SAP Solution Manager have the same maintenance duration as the underlying SAP Solution Manager release.
As before, corrections will be available through support packages. SAP provides support packages on a regular basis
during the defined maintenance period and, in parallel, in the equivalent support packages for SAP enhancement
packages for SAP Solution Manager.

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, while EHPs contain newly
developed functions
Adoption of functional enhancement faster than the SAP Solution Manager release cycle
On the one hand, the clear separation of functional updates and corrections means that you can install support
packages without changing the applications in their functions or UI. Therefore, side-effects are minimized and no
learning should be required. On the other hand, enhancement packages allow you to add functions in smaller steps
than during a release upgrade.
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.

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.0 including enhancement package 1. There are three ways to SAP Solution Manager 7.0 EHP
1:
Update an existing SAP Solution Manager 7.0 system using SAINT / JSPM.
This update procedure is discussed in chapter “Installation in Detail”.
Directly install SAP Solution Manager 7.0 including SAP enhancement package 1 using SAPinst.
This installation is planned to be available in 2009.
Upgrade an existing SAP Solution Manager system using SAP upgrade tools.
This upgrade is planned to be available in 2009.
This guide describes the first scenario “Updating an Existing System of SAP Solution Manager 7.0”.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 6

Note:
Since SAP Solution Manager is based on SAP NetWeaver 7.0 including enhancement package 1, 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. 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.0

SAP enhancement packages for SAP Solution Manager are installed as a whole. The download stack defined in
maintenance optimizer is installed using transaction SAINT (for the ABAP stack) and Java Support Package Manager
(JSPM, for the Java stack).

Impact of Installation
Identical to SAP enhancement packages for SAP NetWeaver, 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. As with enhancement packages for SAP NetWeaver and SAP ERP, updating the support package level in
SAP Solution Manager is part of the enhancement packages installation process. In addition, no definition of usage
type is required for the download: All parts of SAP Solution Manager will be updated.
New features will be delivered with enhancement packages.

Content of SAP Enhancement Package 1 for SAP Solution Manager 7.0

Several scenarios and variants are updated in SAP enhancement package 1 for SAP Solution Manager 7.0. For a
complete definitive list and the mapping of scenarios to installable software units, see SAP Service Marketplace at
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP 1 Master
Guide for SAP Solution Manager 7.0. This guide contains an update for enhancement package 1 including its
enhancements. Also see the Release Notes for SAP Solution Manager 7.0 EHP1 on SAP Service Marketplace at
http://service.sap.com/solutionmanager Media Library Technical Papers with a detailed description of the new
and enhanced functions.

Installation Strategy for SAP EHPs

Since the installation process is coupled with the installation of support packages, you can now continuously provide
the newest functions to the system along with your regular maintenance activities. In order to use synergy effects and
to minimize effort, SAP enhancement packages should be applied within one queue, together with the required support
packages. Using this strategy, SAP enhancement packages can be installed without causing disruption as a normal
maintenance activity together with support packages. If you are not sure whether you want to leverage dedicated
functions, use a sandbox system to explore the new functions. You should also remember that EHPs have support
packages of their own.
Note:
Always install SAP enhancement packages together with a support package stack. You can install the enhancement
package and support packages using a single queue in transaction SAINT and in the Java Support Package Manager.
This minimizes the effort (for example, regarding the potential modification adjustment) since you install the
enhancement package as part of your normal maintenance processes.
Once an SAP enhancement package is installed, you cannot reverse the installation.
Any system has to be updated as a whole. You cannot update one stack only or a single usage type in the system if
there are others installed, even when implementing an SAP enhancement package.

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.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 7

Check, which prerequisites must be met – refer to the section “Preparing the System – Prerequisites for Installation”.
Use maintenance optimizer in SAP Solution Manager to select the correct packages.
Prepare the SAP system and update SAP Solution Manager and the installation tools, if required.
1. Select and download the required components and support packages from SAP Service Marketplace using
maintenance optimizer.
2. Use the SAP Add-On Installation Tool (transaction SAINT) and the Java Support Package Manager (JSPM) to
install the components and support packages.

Figure 2: What you need to install SAP enhancement package 1 for Solution Manager on a system. 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).

SAP Enhancement Package Installation vs. Upgrade

Installing SAP enhancement packages has no additional requirements:
No DVDs are needed.
No database upgrade is needed (there might be exceptions for SAP MaxDB).
No additional hardware is needed.
Installing SAP enhancement packages does not change your landscape setup.
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.
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.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 8

Installation in Detail
This section gives you an overview of the steps required for installing an SAP enhancement package. First, we provide
an overview of the tools involved in the installation process. Then we outline the process itself.

Tools Used for the Installation

As shown in section 2, from the point of view of the effort involved, you can treat SAP enhancement packages like
support packages and should combine the application of both in one queue. However, there are mutual dependencies
to be taken into account. With maintenance optimizer in SAP Solution Manager, these dependencies are calculated
automatically. 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, plus the chosen SAP
enhancement package. The result is a stack configuration file listing the objects that need to be installed in the target
system. 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
… - Landscape data stack
input - System States
… output input
… Down- Java
SAP Solution SAP Solution Manager 7.0 / …
System Landscape Directory result load JSPM stack
Manager 7.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.0 SPS 15 and higher. The download stack is defined in maintenance optimizer. It is consumed by
SAINT and JSPM – the latter also reads the stack configuration file (SCF) generated by maintenance optimizer, which
is needed in JSPM. All steps concerning the download of files can be automated by configuring the Software Lifecycle
Manager (SLM).

Note:
Information on systems used by SAP Solution Manager stems from the System Landscape Directory. This is
recommended for systems based on SAP NetWeaver AS ABAP and highly recommended for systems based on SAP
NetWeaver AS Java.

Installation Procedure
This procedure follows the Update to SAP Solution Manager 7.0 Enhancement Package 1: Using SAINT/JSPM on
SAP Service Marketplace at http://service.sap.com/instguides SAP Components SAP Solution Manager
Release 7.0 EHP 1.

Prerequisites for the Installation

The enhancement package that you want to install requires a specific support package level in your system.
Maintenance optimizer automatically calculates all support packages that are a prerequisite for the enhancement
package installation and includes them in the installation queue.
No additional hardware is needed.
You have configured maintenance optimizer in SAP Solution Manager

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 9

You have installed at least SPAM/SAINT version 031

JSPM has been updated to at least 7.01.2.1.1and SAPCAR is on the latest version.
Of course, you can also include a higher support package level in the installation queue.

Preparations
Preparing the SAP Solution Manager System
Install at least SAP Solution Manager 7.0 support package 9. 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.
- 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,
which was delivered with SP 9. 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.sap.com/swdc Download Installation and
Upgrades Entry by Application Group SAP Technology Components SAP Solution Manager SAP Solution
Manager 7.0 EHP 1.
- SP 9 – SP 14: Use SAP Service Marketplace + maintenance optimizer for the download with manual file
selection
Choose the target release. Then you need to use option “Select files manually” in the guided procedure of
maintenance optimizer. Choose the target stack SAP Solution Manager 7.0 EHP 1.
- 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. We
recommend updating SAP Solution Manger to this state or higher as soon as possible.
If you want to use the software lifecycle management capabilities of SAP NetWeaver in maintenance optimizer, see
SAP Note 1137683.

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. For more information, see also SAP
Note 822380.)
Update the SAP kernel to SAP kernel 7.01. 09/19/2008 PUBLIC 9/28.

Preparing the Java Support Package Manager

Before working with JSPM have a look at SAP Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS
Java. Then make sure the following requirements are met prior to the enhancement package installation:
The system to be updated is fully functional; all backups are up-to-date.
You have not deleted, renamed, or created any directories and files in the following directories and their
subdirectories: /usr/sap/<SAPSID>/SYS/exe and /usr/sap/<SAPSID>/SYS/profile.
Use user <SAPSID>adm to perform the update. Make sure the user has the appropriate permissions.
The database and the Software Deployment Manager (SDM) repository have been synchronized. There is enough
disk space. For more information, see section Requirements for Free Disk Space in the Update to SAP Solution

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 10

Manager 7.0 Enhancement Package 1: Using SAINT/JSPM on SAP Service Marketplace at

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP 1.
To prevent the SDM from temporarily exceeding the available disk space during the update process, you can change
the file transfer directory of SDM in a system of SPS 09 or higher.
To prevent deployment errors during the enhancement package installation process, proceed as follows:
o Log on to the central instance host.
o Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager.
o In the Global properties panel, set the Custom value of the EventTimeout property to 120.
o Choose Save.
o Restart the Central Instance.
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). You can change the password in the secure store as described in
SAP Note 870445.

Downloading the Enhancement Package Stack

To download SAP enhancement packages, you use maintenance optimizer of SAP Solution Manager if you are using
SAP Solution Manager 7.0 SP 9 or higher – for lower states, see the note in section “Preparations”. Starting with SP
15, maintenance optimizer supports you in selecting – with SP 9 - 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.
In addition, 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. The
tools then use this information for installing the enhancement package files and support package stacks.
For more information about maintenance optimizer in SAP Solution Manager SP 18, see SAP Note 1274430.
Prerequisites
You have configured maintenance optimizer in SAP Solution Manager as described on SAP Help Portal at
http://help.sap.com SAP Solution Manager.
Procedure
In maintenance optimizer of SAP Solution Manager, choose the solution for which you want to download
enhancement package files and create a new Maintenance Transaction.
Select the product version, for which you want to install the enhancement package and the systems for which you
want to install the enhancement package.
Choose Enhancement Package Installation and then let maintenance optimizer find the download files.
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). Files that are not selected will not be included later in the
download.
To download the files, select whether you want to download them with the Software Lifecycle Manager (SLM) or with
the download basket, and then choose Select Download Type and confirm the download.
The download stack will be applied to the system for both stacks of SAP Solution Manager separately.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 11

Update of an ABAP Stack

To install the ABAP components of the enhancement package, you use the SAP Add-On installation Tool (transaction
SAINT).
For a detailed description, see SAP Help Portal at http://help.sap.com/nw70 SAP NetWeaver 7.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.
Procedure
Unpack and load the installation packages.
Log on to the system in client 000 using the appropriate user and navigate to the transport directory.
Unpack the archive containing the packages with the following command using SAPCAR.
The unpacked packages are automatically displayed in the EPS inbox in the transport directory.
Call transaction SAINT and choose load the installation packages from the application server.
The list of uploaded packages is displayed.
Return to the initial screen of the SAP Add-On Installation Tool. (SAP recommends using five parallel R3trans
processes for the import.)
Start the installation process and choose Stack Configuration.
In the dialog box providing a list of configurations in maintenance optimizer that are available for your system choose
the required configuration and confirm.
In the Add On Selection dialog box, the packages for the selected configuration are listed. Check the selection and
confirm.
You have to enter a password for each component. The passwords are available in SAP Note 1169247.
The system calculates the complete installation queue including any support package.
Decide whether to include modification adjustment transports in the installation queue.
Choose between the conventional import mode and the downtime-minimized import mode. If you have modified SAP
objects but have not included any adjustment transports, or if the included adjustment transports do not cover all
objects that need adjusting, the SAP Add-On Installation Tool prompts you to perform a modification adjustment
during one of the subsequent phases. For the modification adjustment, you use transactions SPAU and SPDD.
To complete the installation process, choose Continue. In the subsequent installation phases, program code and
program texts that have been made obsolete by the imported objects are physically deleted from the database.
The import process is completed for the ABAP stack.

Update of a Java Stack

To install the Java components of the enhancement package, you use the Java Support Package Manager (JSPM).
JSPM is also used to install portal content. If the business function you want to realize requires the installation of portal
content, you can also proceed as described below.
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. (In case of IBM i5/OS, log on as user <SID>ADM or <SID>OFR.)
Then start JSPM on the Deployment tab:

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 12

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

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 13

If your system is used for NWDI development and it is either a development (DEV) or a consolidation (CONS)
system, and if JSPM has found any software components in the global EPS inbox directory, these components will
be displayed here so that you can select them for deployment.
Select the EHP components and SPS level.- 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.
o WARNING: The corresponding software component comprises custom modifications in an NWDI-
controlled system. We recommend checking the details. The deployment depends on whether the
system is used in NWDI.
o REVISE: Indicates inconsistencies with the corresponding SC. The deployment cannot be performed
until all problems have been resolved. You can display the problems’ details.
If the status of the selected EHP and SP stack is OK or WARNING, choose Start to start the system update. JSPM
changes the status to “scheduled”.
If the support package stack to be applied includes a kernel update higher than the current kernel’s patch level,
JSPM arranges the kernel update as the very first SP to be applied. 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.
Caution:
Kernel binaries of instances, whose kernel directories DIR_CT_RUN are not effectively linked to SAPGLOBALHOST,
must be updated individually – see “Manually Updating Instances with Kernel Directory Located on Separate Hosts“.
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.
o After you have stopped all the instances, choose Next to start the kernel update.
Note:
If the system is running in a high availability environment, 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, you must do this manually when
JSPM is updating the kernel binaries of the central instance. In any case, the SCS kernel must be up-
to-date before the next restart. After the kernel update, you need to restart the SCS instance manually.
o On UNIX platforms, you must adjust the ownership and permissions of the kernel binaries before you
proceed. See “Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms” below.
Choose Next in the dialog box when the SCS instance is running again.
After the kernel update, JSPM restarts the system for further deployment of the remaining SPs of the stack.
Recommendation:
If you must update the kernel binaries of any dialog instances, perform the update when JSPM is updating the
remaining support packages of the stack in order to save time.
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.
o DEPLOYED WITH WARNING: The EHP component or SP has been deployed but it possibly may not
work properly with other deployed components. Choose Show Details or examine the log files.

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 14

o ERROR during the deployment. View the details or examine the log files. You must correct the error to
be able to continue with the EHP installation. 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, you can resume deployment; if the correction does changes the contents in the JSPM
inbox, redeploy the EHP components.
o NOT DEPLOYED: JSPM has not attempted to deploy the software component for certain reasons.
This, again, depends on whether the system is managed by NWDI.
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms, you must adjust the ownership and execution permissions of the kernel binaries after the update,
regardless whether you performed the update manually or by using JSPM, because both update procedures are
performed with the <sapsid>adm user as described in the aforementioned guide.
The import process is completed for the Java stack.

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.0 systems, see the following guides.

RESOURCE WHERE TO FIND IT

Master Guide: SAP Service Marketplace at http://service.sap.com/instguides SAP Components

SAP Solution Manager -> Release 7.0 EHP 1

Installation Guide: SAP Service Marketplace at http://service.sap.com/instguides SAP Components

-> SAP Solution Manager Release 7.0 EHP 1 Update to SAP Solution Manager
7.0 Enhancement Package 1: Using SAINT/JSPM

©SAP AG 2009
Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 15

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

©SAP AG 2009