SAP Solution Manager How-To Guide How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download and Deploy Support Packages and SAP Enhancement Packages Applicable Releases: SAP Solution Manager 7.0 SPS 18 SAP Solution Manager Scenario: Change request management and change control Version 1.20 October 2009
35
Embed
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 1
1. Scenario
The maintenance optimizer supports you in managing and implementing maintenance activities in
your system landscape.
The system and solution information in SAP Solution Manager, accessible via the Solution Manager
System Landscape transaction (SMSY), is the basis and reference for maintenance transactions. You
can assign a solution, or one or more systems, to your maintenance transaction, for the greatest
possible flexibility. The maintenance optimizer interacts with the SAP Global Support Backbone to
download the support package you have selected there. To make this possible, you have to create s-
users for SAP Service Marketplace and assign them to the SAP Solution Manager end users.
Figure 1: Interaction between the maintenance optimizer and SAP Global Support Backbone
Example
The end user MUELLERK creates a maintenance transaction (1) and assigns a solution/system to it (2). SAP Solution Manager establishes a connection to SAP Global Support Backbone and displays all currently available support packages (3). The support packages selected by the user are stored in the download basket of end user S000021112 (4) and downloaded from there (5).
The maintenance optimizer leads you through the following steps for the maintenance transaction:
You can download support packages and enhancement packages automatically, and deploy them
(single system update) to the managed system using the Software Lifecycle Manager (SLM), with the
maintenance optimizer. This use case is described in this guide.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 2
2. Background Information
With SAP Solution Manager (component ST 400) SPS 15 to SPS 17, the maintenance optimizer
supports the automatic download of support packages and enhancement packages with the Software
Lifecycle Manager (SLM, component LIFECYCLE MGMT TOOLS 7.00). With SPS 18, you can also
deploy the support packages and enhancement packages in your managed system, using the single
system update function. Before starting the single system update in the maintenance optimizer, you
have to install the live update function in the SLM and perform prerequisite configuration for the
managing systems and the managed systems.
Figure 2: Deployment diagram of maintenance optimizer with Software Lifecycle Manager (SLM)
There are two ways of installing the SLM and other required software logistics tools, such as, for
example the SLD. ...
1. We recommend installing the SLM and the SLD together with the maintenance optimizer, on the
managing SAP Solution Manager system (see Figure 3), so you only have to configure one
managing system.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 3
Figure 3: One managing SAP Solution Manager system with maintenance optimizer, SLM, SLD and
SLC supporting auto-download
2. You have two separate managing systems (see Figure 4): the SAP Solution Manager system
with the maintenance optimizer, and one system where you install the SLM, the SLD content,
and the Software Logistics Controller (SLC). In this case, the maintenance optimizer is in the
managing SAP Solution Manager system, and connects to the SLM in the other managing
system.You have to set up and configure the software logistics tools required for the automatic
download, except for the maintenance optimizer and the SLM.You have to set up and configure
the tools for the single system update, in your managed system: the SLC, the SAP Add-On
Installation Tool (SAINT), the Support Package Manager (SPAM), the Java Support Package
Manager (JSPM).You also have to activate the Web service sapcontrol.
Figure 4: Two separate managing systems with maintenance optimizer, SLM, and other tools
supporting auto-download; one managed system with tools supporting single system update
If you already have a separate managing system with the SLD, you need to configure two managing
systems use the already configured SLD.
Note
An SAP Solution Manager system can connect to more than one SLM component.
Note
The managed systems have to be maintained via the maintenance optimizer. Both the managing SAP Solution Manager system and the managing system with the SLM can also be managed systems, when their own components are being updated.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 4
3. Prerequisites
You have installed SAP Solution Manager SPS 18.
You have installed the SLM, SLC and SLD in the managing system.
You have installed the SLC and the installation tool for ABAP-based systems (SPAM or SAINT) and
for Java-based systems (JSPM), in each managed system.
SAP software logistics knowledge.
See Appendix B - Relevant SAP Notes [page 25] and Appendix C – Update from SAP Solution
Manager SPS 15-17 to SPS 18 [page 26] for relevant SAP Notes.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 5
4. Configuration of Managing System ...
Follow the steps in this chapter to configure the required systems and tools for the single system
update.
4.1 Installation of Software Lifecycle Manager - SLM ...
1. Install (or update to) the support packages of the Software Lifecycle Manager (SLM) higher than
7.01 SP4 Patch 5 or release 7.11.
More information: SAP Help Portal at http://help.sap.com SAP NetWeaver SAP
NetWeaver 7.0 including Enhancement Package 1 <language> SAP NetWeaver Library
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
Software Life-Cycle Management Software Lifecycle Manager Working with the SLM
Installing Live Update
2. Check whether the SLM Web services are available according to Appendix D - Check SLM Web
Services [page 26].
4.2 Configuration for Secure Communication in Live
Update
The Secure Sockets Layer (SSL) is mandatory for accessing Web services for the component
SOFTWARE LIFECYCLE 7.01.
Follow the steps in this section.
For the component SOFTWARE LIFECYCLE 7.11, you can skip this section and directly go on
reading Customizing Settings for Maintenance Optimizer [page 8].
4.2.1 Set-up SAP Cryptographic Library for SLM Secure
Connection ...
Set up SAP Cryptographic Library on the managing SAP Solution Manager system.
More information: SAP Note 510007 (Setting-up SSL on SAP NetWeaver Application Server ABAP)
4.2.2 Generation and Import of SSL Certificate for SLM
Secure Connection
Generate the SSL certificate on the managing SLM system (server side).
More information: SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0
including Enhancement Package 1 <language> SAP NetWeaver Library SAP NetWeaver by
Key Capability Security Network and Transport Layer Security Transport Layer Security on
the SAP J2EE Engine Configuring the Use of SSL on the J2EE Engine
Trigger the import of the SSL certificate on the managing SAP Solution Manager system (client side).
1. Log in to the managing SAP Solution Manager system and run the trust manager with transaction code STRUST.
2. In the left screen area, choose SSL client (Anonymous or Standard).
3. In the right screen area, click the icon with quick info Import Certificate to import the crt file with
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 10
Figure 9: Configure Customizing settings for maintenance optimizer
Note
The structure of the Customizing activities may be different from that in figure 8; you can use CTRL+F to search for activities with the names listed above.
You can configure more than one SLM system in the Multiple Software Lifecycle Manager
Configuration Assistant. You can access the Multiple Software Lifecycle Manager Configuration
Assistant with the transaction code /n/TMWFLOW/MOPZCFG. You can acess one Software Lifecycle
Manager Configuration Assistant for each SLM system by clicking the symbol with the quick info
Config SLM in the column SLM Configuration. See Figure 9 and Figure 10.
If the managed systems are registered in different SLD systems, you have to configure them in
different SLM systems. The maintenance optimizer determines the SLM system to download and
deploy support packages and enhancement packages to the managed systems. To use the automatic
download and deployment to a managed system, you have to configure the managed system in an
SLM system.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 11
Example
A user has two different SLDs (SLD_1 and SLD_2), and a managed system MS_1 is
registered in SLD_1 while MS_2 is registered in SLD_2. The user wants to download
support packages and deploy to the two managed systems. The user has to:
1) Install two SLMs in the two SLDs, SLM_1 and SLM_2.
2) Create two entries in Multiple Sofware Lifecycle Manager Configuration Assistant.
3) Choose SLM Configuration and configure each SLM
SLM_1: Enter the system information for the SLM_1 and the MS_1.
SLM_2: Enter the system information for the SLM_2 and the MS_2.
4) Create two transactions, TA_1 and TA_2, for the two managed system MS_1 and
MS_2.
In transaction TA_1, the maintenance optimizer uses the SLM_1 to download and
deploy support packages to the MS_1; while in TA_2, the maintenance optimizer uses
The component SOFTWARE LIFECYCLE 7.01 only supports an HTTPS connection; while the SOFTWARE LIFECYCLE 7.11 only supports an HTTP connection. If the SLM check fails, check whether the HTTPS connection for the SOFTWARE LIFECYCLE 7.01 is set up correctly, by double-clicking the connection name and choosing Connection Test. For the component SOFTWARE LIFECYCLE as of release 7.0<x>, choose SessionPassword in the Communication Mode field. For the component SOFTWARE LIFECYCLE as of release 7.1<x>, choose ConfigManager in the Communication Mode field.
Note
If you want to reuse an already established extranet connection (according to SAP Note 124743) for downloading with MOPZ and SLM you must configure your proxy installed
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 13
on SAProuter to forward URLs of archives at SAP Service Marketplace to a cascadable proxy at SAP. The URLs to be forwarded are: http://www.service.sap.com/…, https://smpdla.sap.com/…, https://smpdl.sap-ag.de/… The cascadable proxy at SAP is sapservX : 8080. 'X' stands for 1 for VPN connections, 2 for Secure Network Communication (SNC), or 3 for both VPN connections and SNC.
As of SAP Solution Manager 7.0 SP 21, you need to enter the database host of managed systems to
enable the registration of different managed systems with identical SIDs in the same configuration
assistant. For more information, see Figure 12.
Figure 12: Enter database host for managed systems
Note
You need to register your managing system on which SLM is installed in the Solution
Manager System Landscape (transaction SMSY). For more information, see SAP Note
1302436
4.4 Authorization Configuration for Maintenance
Optimizer
1. Log in to your managing SAP Solution Manager system to assign the authorizations for the
maintenance optimizer.
2. Configure the following roles for maintenance optimizer system users:
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 19
2. On the host of a managed system, you have to mount the directory /usr/sap/trans/EPS/
on the transport directory host, as the local directory /usr/sap/trans/EPS/in.
You have to perform further configuration if the operating system of the transport directory host is
Linux/UNIX while the managed system host is Microsoft Windows NT. You have to mount the
transport directory with the same path in the hosts of the managed system as in the central host.
1. On the transport directory host, the transport directory path /usr/sap/trans/EPS/in needs
to be shared with a path, e.g., \\centralhost\usr.sap\trans\EPS\in.
2. On the host of the managed system, the instance profile needs to be edited (e.g.
C:/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<instance number>_<HOST>), so
that the parameter DIR_EPS_ROOT is the same as the shared path on the transport directory
host, e.g., \\centralhost\usr.sap\trans\EPS\in.
Note
In this case, mounting the network drive via Windows Explorer Tools Map Network
Drive does not work as the shared directory is mounted with the current session user
(e.g. <SID>adm) and not with the SAPService<SID> user which is used for accessing
the shared directory.
5.4 Support Package Manager – SPAM
To update ABAP stack components live, you have to manually update SPAM to the latest version,
without the SLM self-update support.
Follow the steps below to install and configure SPAM. ...
1. Log in to the managed system; run the Support Package Manager with transaction code SPAM;
update SPAM to the most up-to-date version.
2. To configure the Web service OCS_API:
a. Log in to the managed system with a user other than DDIC, in client 000.
b. Allow for changes of client-dependent objects (customizing).
c. Enter transaction code SCC4 and go to change mode.
d. Mark the entry for client 000 and choose Details to edit it.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 20
Figure 18: Set changes and transports for client-specific objects - 1
e. For Changes and Transports for Client-Specific Objects, choose Changes without
automatic recording and save.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 21
Figure 19: Set changes and transports for client-specific objects - 2
f. Run the Web service configuration with transaction code WSCONFIG. Ignore the
information message This transaction is obsolete; read the long text.
g. Enter OCS_API as service definition and variant, and choose the icon with quick info
Create.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 22
Figure 20: Configure OCS_API Web service - 1
h. Do not change the default settings, and save.
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 23
Figure 21: Configure OCS_API Web service - 2
i. Answer the question whether an external alias is to be created, with No.
j. If necessary, reset the system changeability via transaction code SCC4.
3. After the configuration of the Web service OCS_API, you can update the SPAM properties, if
required.
a. Log in to the host of the managed system, go to directory
/usr/sap/<SID>/SYS/global/SDT/plugin/SPAM/config.
b. Copy the template file SPAM.prop.template to SPAM.properties (if it does not
exist yet).
c. Edit the properties file:
Uncomment the following line: conn.type = WS.
If the Web service OCS_API does not work, continue with uncommenting the following
line: ws.port = ; and add 80<InstanceNumber> as the port.
4. Check the Web service OCS_API. Go to the wsdl (web service definition language) URL of the
Web service OCS_API:
http://<host>:80<InstanceNumber>/sap/bc/srt/rfc/sap/OCS_API?wsdl. If the
How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download
and Deploy Support Packages and SAP Enhancement Packages
October 2009 24
wsdl definitions are displayed normally, the web service is ready for use.
Figure 22: Check OCS_API Web service
5.5 Java Support Package Manager – JSPM
To update Java stack components live, you have to manually update the JSPM tool to the latest
version, without SLM self-update support. ...
1. Download JSPM from SAP Service Marketplace at http://service.sap.com SAP Support Portal
Downloads Download Support Packages and Patches.
2. Log in to the host of the managed system; run JSPM with /usr/sap/<SID>/DVEBMGS00/j2ee/JSPM/go.bat; update JSPM.
For the transport directory access configuration and Microsoft Windows NT OS-user authorization,
refer to SPAM equivalent configuration.
Note
You only need to update JSPM manually, when you use the SLM deployment for the first time. In future system updating, the maintenance optimizer automatically updates JSPM with SLM support.