42603024 Update Guide SAP Solution Manager 7 0 EHP 1 NEW

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 youare 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“ sindvon 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 Softwarepaketinstallieren und mit eingeschränktem Funktionsumfang nutzen. Die im folgenden aufgeführten Funktionen, dieBestandteil 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 FORSAP SOLUTION MANGER 7.0

SIMILARITIES AND DIFFERENCES IN SAP NETWEAVER & SAP SOLUTION MANAGER

Update Guide SAP Enhancement Package 1 for SAP Solution Manger 7.0 2

©SAP AG 2009

Table of ContentsTable 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

OverviewThis document gives you an overview of the SAP enhancement packages for SAP Solution Manger 7.0 and theirinstallation procedure. Differences to SAP enhancement packages for SAP NetWeaver and SAP ERP are discussed.

Executive SummarySAP Enhancement Package 1 for SAP Solution Manager 7.0With SAP enhancement packages (EHPs) you can implement functional updates without upgrading your SAP systemto a higher release. This concept is introduced for SAP NetWeaver with SAP enhancement package 1 for SAPNetWeaver 7.0 and will be available for SAP enhancement package 1 for SAP Solution Manager 7.0 (this isoccasionally 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: SAPenhancement package rules are based on those for SAP‘s support packages (SPs): No table conversions or XPRAsare needed. Compatibility is guaranteed: There are no changes with regard to inbound or outbound interfaces ofcomponents 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 standardtransactions for SAP Solution Manager will continue to exist, new developments delivered with an enhancementpackage may require the work center user interface.


©SAP AG 2009

With the installation of an SAP enhancement package for SAP Solution Manager, generally no hardware upgrade isrequired 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 oferrors 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 NetWeaverAll SAP enhancement packages serve the same purpose of allowing functional updates of systems without a systemupgrade. However, in some details EHPs for SAP ERP, SAP NetWeaver, and SAP Solution Manager differ, mostimportantly in the following:

The installation of EHPs for SAP ERP is a selective update of usages in a system. In case of EHPs for SAPNetWeaver 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 asa 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 thelatest versions, the release strategy for enhancement packages for SAP Solution Manager differs from the releasestrategy for SAP enhancement packages for SAP NetWeaver and SAP Business Suite: As soon as the newestenhancement package is available this replaces the former maintenance via support packages. Thereforeenhancement packages for SAP Solution Manager are part of its maintenance strategy and are not optional.


©SAP AG 2009

Traditional SAP ApplicationInnovation Lifecycle

Cos

t

EHP 1incl.

SPS 18

• Corrections

• Technically a set ofsupport packagesand patches

Maintenance:Support Package Stack

Upgradeto SAP

SolutionManager

3.2 SupportPackageSAP

System

New SAP Solution ManagerLifecycle

Time

• New & improved functionality

• Mandatory, new softwarecomponents

New: SAP EnhancementPackages for SAP Solution Manager

SAP Enhancement Packages for SAP Solution Manager

SupportPackage SP 17 SP 19*

Upgradeto SAP

SolutionManager

7.0EHP 2incl.

SPS 21*SPS 20*

*current planning, changes still possible

IntroductionPurpose of this DocumentSAP enhancement packages are a new way of software delivery that allows you to implement innovations without theneed to upgrade your current system. Introduced for SAP ERP first, this concept has become available for SAPNetWeaver 7.0 with EHP1 and now also for SAP Solution Manager 7.0. This document outlines the basic ideas of thenew 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. Gettingfamiliar with these procedures will help you to minimize your installation efforts.

Target GroupThis document is written for technical consultants and SAP administrators dealing with SAP Solution Manager 7.0, soyou should be experienced in SAP technology, updates, and upgrades. The executive summary and introductionprovide abstracts for other readers.

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


©SAP AG 2009

Figure 1: SAP’s enhancement package installation on SAP Solution Manager with ABAP and Java stack usingtransaction SAINT for ABAP and JSPM for the Java stack.

SAP enhancement packages are cumulative. Current SAP enhancement packages contain the entire content of earlierpackages. As a result, each SAP enhancement package is based on the previous one. SAP enhancement packagesfor 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 basisduring the defined maintenance period and, in parallel, in the equivalent support packages for SAP enhancementpackages for SAP Solution Manager.

EssentialsSome major characteristics comprise the key difference between SAP enhancement packages and previous deliveriesand procedures:

Clear separation of the shipment of patches and functions with SPs containing corrections, while EHPs contain newlydeveloped 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 supportpackages without changing the applications in their functions or UI. Therefore, side-effects are minimized and nolearning should be required. On the other hand, enhancement packages allow you to add functions in smaller stepsthan during a release upgrade.

Note:

Keep in mind that – since EHP development follows support package rules with the exception of containing newfeatures – the installation of an enhancement package for SAP Solution Manager is an update of your system.

Installation Scenarios for SAP Enhancement PackagesThis section gives you an overview of the dependencies of SAP Solution Manager running on top of SAPNetWeaver 7.0 including enhancement package 1. There are three ways to SAP Solution Manager 7.0 EHP1:

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

Note:

Since SAP Solution Manager is based on SAP NetWeaver 7.0 including enhancement package 1, there is a cleardependency: For SAP Solution Manager systems updated to EHP1 you will also need to update the underlying SAPNetWeaver with EHP1. It will then be part of the download stack calculated by maintenance optimizer in SAP SolutionManager

Installation of Enhancement Packages for SAP Solution Manager 7.0SAP enhancement packages for SAP Solution Manager are installed as a whole. The download stack defined inmaintenance optimizer is installed using transaction SAINT (for the ABAP stack) and Java Support Package Manager(JSPM, for the Java stack).

Impact of InstallationIdentical to SAP enhancement packages for SAP NetWeaver, changes delivered with EHP1 for SAP Solution Managerbecome immediately visible with the installation because switches are practically not used in EHPs for SAP SolutionManager. As with enhancement packages for SAP NetWeaver and SAP ERP, updating the support package level inSAP Solution Manager is part of the enhancement packages installation process. In addition, no definition of usagetype 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.0Several scenarios and variants are updated in SAP enhancement package 1 for SAP Solution Manager 7.0. For acomplete definitive list and the mapping of scenarios to installable software units, see SAP Service Marketplace athttp://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP 1 MasterGuide for SAP Solution Manager 7.0. This guide contains an update for enhancement package 1 including itsenhancements. Also see the Release Notes for SAP Solution Manager 7.0 EHP1 on SAP Service Marketplace athttp://service.sap.com/solutionmanager Media Library Technical Papers with a detailed description of the newand enhanced functions.

Installation Strategy for SAP EHPsSince the installation process is coupled with the installation of support packages, you can now continuously providethe newest functions to the system along with your regular maintenance activities. In order to use synergy effects andto minimize effort, SAP enhancement packages should be applied within one queue, together with the required supportpackages. Using this strategy, SAP enhancement packages can be installed without causing disruption as a normalmaintenance activity together with support packages. If you are not sure whether you want to leverage dedicatedfunctions, use a sandbox system to explore the new functions. You should also remember that EHPs have supportpackages of their own.

Note:

Always install SAP enhancement packages together with a support package stack. You can install the enhancementpackage 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 theenhancement 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 ifthere 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.

http://service.sap.com/instguides

http://service.sap.com/solutionmanager


©SAP AG 2009

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 usingmaintenance optimizer.

2. Use the SAP Add-On Installation Tool (transaction SAINT) and the Java Support Package Manager (JSPM) toinstall the components and support packages.

Figure 2: What you need to install SAP enhancement package 1 for Solution Manager on a system. EHPs and anyrequired support package stack are downloaded from SAP Service Marketplace and applied using transaction SAINTfor the ABAP stack and JSPM for the Java stack (asterisks indicate updated parts of the system).

SAP Enhancement Package Installation vs. UpgradeInstalling 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

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

Tools Used for the InstallationAs shown in section 2, from the point of view of the effort involved, you can treat SAP enhancement packages likesupport packages and should combine the application of both in one queue. However, there are mutual dependenciesto be taken into account. With maintenance optimizer in SAP Solution Manager, these dependencies are calculatedautomatically. SAP Solution Manager takes into account the state of the system for the SAP enhancement packageinstallation using the release/support package state and the contained software versions, plus the chosen SAPenhancement package. The result is a stack configuration file listing the objects that need to be installed in the targetsystem. The installation of the files is performed with transaction SAINT for the ABAP stack and the Java SupportPackage Manager for the Java stack:

JSPMSAP SolutionManager 7.0

<SID>……

SAP SolutionManager 7.0

<SID>……

<SID>……

SMP

SAP Solution Manager 7.0 /System Landscape Directory

- Landscape data- System Statesinput

SAINTinput

output

result

SCF

input

SPS X

……

SPS X

……

install

install

Javastack

ABAPstackEHP 1

Down-loadBasket

Figure 3: SAP enhancement package installation process: the big picture of tools and steps involved with SAPSolution Manager 7.0 SPS 15 and higher. The download stack is defined in maintenance optimizer. It is consumed bySAINT and JSPM – the latter also reads the stack configuration file (SCF) generated by maintenance optimizer, whichis needed in JSPM. All steps concerning the download of files can be automated by configuring the Software LifecycleManager (SLM).

Note:

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

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

Prerequisites for the InstallationThe 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 enhancementpackage 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

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.

PreparationsPreparing 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 therequired files.

- SP 8 and lower: Use SAP Service Marketplace + Ticket for the downloadThe 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 ofusing maintenance optimizer: SAP Service Marketplace at http://service.sap.com/swdc Download Installation andUpgrades Entry by Application Group SAP Technology Components SAP Solution Manager SAP SolutionManager 7.0 EHP 1.

- SP 9 – SP 14: Use SAP Service Marketplace + maintenance optimizer for the download with manual fileselectionChoose the target release. Then you need to use option “Select files manually” in the guided procedure ofmaintenance 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 thedownloadWith SP 15 the download definition in maintenance optimizer in SAP Solution Manager is fully functional. Werecommend 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, seeSAP 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 latestversion of the SPAM/SAINT update before you import installation packages. For more information, see also SAPNote 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 ASJava. 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 theirsubdirectories: /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 enoughdisk space. For more information, see section Requirements for Free Disk Space in the Update to SAP Solution

http://service.sap.com/swdc


©SAP AG 2009

Manager 7.0 Enhancement Package 1: Using SAINT/JSPM on SAP Service Marketplace athttp://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 changethe 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 configurationManagers 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 onestored in the user management engine (UME). You can change the password in the secure store as described inSAP Note 870445.

Downloading the Enhancement Package StackTo download SAP enhancement packages, you use maintenance optimizer of SAP Solution Manager if you are usingSAP Solution Manager 7.0 SP 9 or higher – for lower states, see the note in section “Preparations”. Starting with SP15, maintenance optimizer supports you in selecting – with SP 9 - 14 you need to use the option to manually selectfiles for download in maintenance optimizer – and downloading all required enhancement package files and supportpackages.

In addition, maintenance optimizer generates an enhancement package stack configuration file and provides it to thesoftware logistics tools for installation and upgrade using the EPS inbox of the SAP Solution Manager system. Thetools 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 athttp://help.sap.com SAP Solution Manager.

Procedure

In maintenance optimizer of SAP Solution Manager, choose the solution for which you want to downloadenhancement 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 youwant 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 packagestack unless you have already downloaded them). Files that are not selected will not be included later in thedownload.

To download the files, select whether you want to download them with the Software Lifecycle Manager (SLM) or withthe 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.


http://help.sap.com/


©SAP AG 2009

Update of an ABAP StackTo install the ABAP components of the enhancement package, you use the SAP Add-On installation Tool (transactionSAINT).

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 SoftwareLife 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 R3transprocesses 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 choosethe required configuration and confirm.

In the Add On Selection dialog box, the packages for the selected configuration are listed. Check the selection andconfirm.

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 SAPobjects but have not included any adjustment transports, or if the included adjustment transports do not cover allobjects that need adjusting, the SAP Add-On Installation Tool prompts you to perform a modification adjustmentduring 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 andprogram 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 StackTo 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 portalcontent, 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:

http://help.sap.com/nw70


©SAP AG 2009

o For JSPM SPS level 16 or higher, select the Java Support Package Manager option and update thesap.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/JSPMsoftware 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 beincluded in the target SPS. This is possible if you applied patches of the start SPS level that have been deliveredlater than the target SPS delivery date. In order not to lose these fixes, consider applying the latest patches of thetarget SPS level. If you need to include the latest patches for a particular component during the update process withthe 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 inthe 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 ofyour 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 asJ2EE Administrator and go to: Agent Administration Enable Maintenance Mode. You will get a warningmessage, 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 asJ2EE Administrator and go to: Diagnostics Administration Managed systems Agent Administration

Enable Maintenance Mode. You will get a warning message, confirming that the maintenance mode isenabled.

SP 15 – SP17:Connect to end-to-end root cause analysis (also known as diagnostics) with your web browser. Login asJ2EE 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 themaintenance mode is enabled.

Note:

When the SAP Solution Manager system is upgraded to EHP 1 and configured, the end-to-end root cause analysismaintenance 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 inas Solution Manager Administrator (by default, user SOLMAN_ADMIN). Then go to: Root Cause Analysis AgentAdministration.End-to-end root cause analysis generates self-check reports, which are available once the automatic basicconfiguration of SAP Solution Manager has been performed – see the SAP Solution Manager master guide forfurther details. These self-check reports raise a flag if the maintenance mode hasn’t been activated before the SAPSolution Manager system upgrade. In that case, activate and then deactivate the end-to-end root cause analysismaintenance 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

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 willbe 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 ofeach 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 thesystem is used in NWDI.

o REVISE: Indicates inconsistencies with the corresponding SC. The deployment cannot be performeduntil 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. JSPMchanges 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 allinstances (including dialog instances and SCS instances in a high availability environment) whose kernel directoriesDIR_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 softwaredoes not restart the instance automatically during the update

If kernel binaries of the SCS instance must be updated individually, you must do this manually whenJSPM 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 youproceed. 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 theremaining 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 notwork properly with other deployed components. Choose Show Details or examine the log files.


©SAP AG 2009

o ERROR during the deployment. View the details or examine the log files. You must correct the error tobe able to continue with the EHP installation. You can proceed as described for a deployment thatfinished with status DEPLOYED WITH WARNING. If the correction does not change the contents inthe JSPM inbox, you can resume deployment; if the correction does changes the contents in the JSPMinbox, 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 areperformed with the <sapsid>adm user as described in the aforementioned guide.

The import process is completed for the Java stack.

Further InformationFor more information on SAP enhancement packages and the SAP Enhancement Package Installer and theinstallation 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 ComponentsSAP 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 Manager7.0 Enhancement Package 1: Using SAINT/JSPM




©SAP AG 2009

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 expresspermission 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 othersoftware 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 andPowerPC are trademarks or registered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of AdobeSystems 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 registeredtrademarks 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 andimplemented 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 mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other product and service names mentioned are the trademarks of theirrespective companies. Data contained in this document serves informational purposes only. National productspecifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products andservices, 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 limitedto, 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 consequentialdamages 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 containedwithin these materials. SAP has no control over the information that you may access through the use of hot linkscontained in these materials and does not endorse your use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are notintended to be used in a productive system environment. The Code is only intended better explain and visualize thesyntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Codegiven herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if suchdamages were caused by SAP intentionally or grossly negligent.

Documents

42603024 Update Guide SAP Solution Manager 7 0 EHP 1 NEW