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 SP 22 with Software Lifecycle Manager 7.01 SP08 ALM process: Change request management and change control Version 2.00 January 2011
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.
Transcript
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 SP 22 with Software Lifecycle Manager 7.01
Maintenance Optimizer manages and implements maintenance activities in your system landscape.
The system and solution information in the SAP Solution Manager system landscape (transaction
SMSY) is the basis and reference for maintenance transactions. You can assign one or more systems
to your maintenance transaction. Maintenance Optimizer uses the SAP Global Support Backbone to
download a support package. You have to create S-users for SAP Service Marketplace and assign
them to SAP Solution Manager end users.
Figure 1: 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).
Maintenance Optimizer leads you through the following steps in the maintenance transaction:
You can download support packages automatically, and deploy them to the managed system, using
the Software Lifecycle Manager (SLM, component SOFTWARE LIFECYCLE MANAGEMENT), with
Maintenance Optimizer (single system update). This use case is described in this guide.
www.service.sap.com/solutionmanager
2. Background Information
From SAP Solution Manager (component ST 400) SPS 22 and SLM 7.01 SP08, Maintenance
Optimizer supports the automatic download of support packages and enhancement packages, and
single system update, with SLM, for the scenarios below:
Update Type SLM
Release
Managed System
NetWeaver Release
Comment
Maintenance 7.0x 7.00 and higher ABAP stack, Java stack,
Kernel/IGS components and
TREX system auto-update
supported.
Note: SLM release 7.0x does not include 7.00. In maintenance optimizer use scenarios, only
SLM release 7.0x is now supported.
Note: Maintenance/Installation/Upgrade of add-on product versions in the above maintenance
and installation scenarios are supported.
You need to configure the managing and managed systems before a single system update.
Note
In SAP Solution Manager SPS 22, the SLM release is 7.01 SP05. SLM is a backward-
compatible Java tool; you can update it to the latest support package without changing
Solution Manager SPS.
2.1 The managing and managed system landscapes
Maintenance Optimizer can connect to multiple SLMs of different releases. The systems involved in
Maintenance Optimizer single system update can be as follows:
www.service.sap.com/solutionmanager
SAP Solution
Manager
System with
Maintenance
Optimizer
Managing
System with
Software
Lifecycle
Manager
Managing
System with
Software
Lifecycle
Manager
Managing
System with
Software
Lifecycle
Manager
Central Download Directory
Central Transport Directory
Central Transport Directory
Managed
System
Managed
System
Managed
System
Managed
System
Managed
System
A system landscape
A system landscape
Figure 2: Maintenance Optimizer with Software Lifecycle Manager (SLM)
www.service.sap.com/solutionmanager
Various tools and applications work together to support auto-download and single system update.
Assume Easy Guitar Tab Songbook you have two managing systems, the SAP Solution Manager
system with Maintenance Optimizer, and a system in which you install SLM, and the SLD content (see
Figure 3). Maintenance Optimizer is in the managing SAP Solution Manager system, and connects to
SLM in the other managing system. You need to set up and configure the software logistics tools for
the automatic download, and Maintenance Optimizer and SLM. You need to set up and configure the
tools for the single system update, in both your SLM managing system and the managed systems: the
Support Package Manager and SAP Add-On Installation Tool (SPAM/SAINT), and the Java Support
Package Manager (JSPM). The Web service sapcontrol needs to be available.
SAP Solution Manager System
Maintenance
Optimizer
Managing System with SLM Managed System
SMSY
SLM
JSPMSLD JSPM
SPAM/
SAINT
Figure 3: Two managing systems with Maintenance Optimizer, SLM, and other tools supporting auto-
download; one managed system with tools supporting single system update
Frequently, one of the managing systems with SLM is the same as the SAP Solution Manager system.
Note
An SAP Solution Manager system can connect to more than one SLM component.
Note
Maintenance Optimizer will be unavailable when importing the ST component queue. You cannot deploy SLM when updating the SAP Solution Manager system.
When you update the managing system, SLM/JSPM will be updated to the latest patches. SLM self-update may cause downtime, in which case Maintenance Optimizer may raise an exception and pause the status refresh. Resume the status refresh in this maintenance procedure (transaction) after SLM is restarts.
2.2 Configuration Sections
Before auto-download and single system update, perform the following configuration steps:
Register the system landscape: section 4.1.
Configure SLM: section 4.2-4.4.
Customize Maintenance Optimizer and configure authorization: section 4.5-4.7.
Configure logistic tools: section 0-5.3.
www.service.sap.com/solutionmanager
2.3 Update from SAP Solution Manager SPS 15-21 to
SPS 22
If your SAP Solution Manager system currently has support package stack level 15-21, see the
following notes before you update to SPS 22 or higher. ...
1. Before applying SPS 22 on the SAP Solution Manager system, finish or withdraw Maintenance
Optimizer transactions which use SLM; import the latest SPAM/SAINT.
2. If you have made the secure connection settings in previous packages, you can skip section 4.3
Configuration of Secure Connection to SLM [page 8].
3. Check section 4.4 SLM Configuration[page 12] and configure the missing items, even if you
already configured SLM in previous SAP Solution Manager SPS levels. There are enhanced
fields to be configured.
4. After applying SPS 22, for the first time, update SLM, SPAM/SAINT and JSPM to the newest
version, manually, on the managing and managed systems.
2.4 Update from SLM SP 05-07 to SP 08
If you use SLM auto-deployment, a self-update stack XML will be calculated automatically; run the
logistic tools update at the “Implement” step of the maintenance procedure. SLM will be updated to the
latest support package.
If you only use SLM auto-download, use JSPM or SDM to update SLM to SP08 or a higher SP.
www.service.sap.com/solutionmanager
3. Prerequisites
You have SAP Solution Manager SPS 22.
You have SLM and SLD in the managing systems.
You have logistic tools for ABAP-based (SPAM/SAINT) and Java-based systems (JSPM), in each
managed system.
SAP software logistics knowledge.
See Appendix B - Relevant SAP Notes [page 25] for relevant SAP Notes.
www.service.sap.com/solutionmanager
4. Configuration of Managing System ...
Follow the steps in this chapter to configure the systems and tools for the single system update.
4.1 Registration of systems in SLD and SMSY
Register both the ABAP and the Java stacks for managing and managed systems.
1. Configure the SLD data supplier for the ABAP stack.
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 System Landscape Directory Configuring Systems to
Connect to SLD Connecting AS ABAP Systems to the SLD Setting Up the SLD Data
Supplier for Java-Based Systems Global Settings default settings
2. Configure the SLD data supplier for the Java stack.
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 System Landscape Directory Configuring Systems to
Connect to SLD Connecting AS ABAP Systems to the SLD Setting Up the SLD Data
Supplier for Java-Based Systems
3. Configure the SLD data supplier for systems which are neither ABAP nor Java-based.
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 System Landscape Directory Configuring Systems to
Connect to SLD Connecting Other SAP Systems to the SLD
4. After registering systems in SLD, import the system data into SMSY.
More information: SAP Help Portal at http://help/sap.com http://help.sap.com SAP
Solution Manager Basic Settings Solution Manager System Landscape.
Note
Follow the check list to check system data in SMSY: SAP Note 1344564 (Maintenance Optimizer: Check system landscape).
Note
Check whether components JSPM are maintained in the Java system component in SMSY. If JSPM were not auto-maintained via SLD when you installed them, maintain them in Java system components of both managing and managed systems.
If you use SLM 7.01 SP08 with an early Solution Manager in which the Configuration Assistant still uses the term SLC (Software Logistic Controller), you can perform the necessary steps: SLC configuration is the previous term for technical system configuration. The SLC host is the host on which the SAPControl service runs; the SAPControl port is the port of this host. In a complex technical system located on multiple hosts, fill SAPControl host and port with the host of the central instance: for an ABAP or dual stack system, it is the ABAP central instance (type DVEBMGS); for a Java system, the Java central instance (type JC), for a Trex system, the Trex insance (type TRX).
www.service.sap.com/solutionmanager
One Technical System
Host A
Dialog
Instance
Host B
Central
Instance
DB
Figure 10: A Technical System Located on Multiple Hosts
Note
Maintenance Optimizer cannot determine the SLM connection if multiple SLMs are
configured for one system. Configure one system in only one SLM.
Note
Communication Mode
The component SOFTWARE LIFECYCLE 7.01 only supports an HTTPS connection. If the SLM check fails, check whether the HTTPS connection for the SOFTWARE LIFECYCLE 7.01 is set up correctly, by double-clicking on 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.
Note
SLM System Name
Enter the system component name of your SLM which is registered in SMSY. If the SLM is installed on a dual stack system, configure its ABAP stack part in SMSY as well, as in 4.1.
Note
Database Host
Enter the database host for each system. This enables you to configure different systems with the same SIDs for Maintenance Optimizer.
Note
Download Proxy
If you want to reuse an existing extranet connection (according to SAP Note 124743) to download with MOPZ and SLM, configure your proxy on SAProuter to forward URLs of archives in 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, where 'X' is 1 for VPN connections, 2 for Secure Network Communication (SNC), or 3 for both VPN connections and SNC.
Note
S User
The S-user is used to generate download content, and download. The license number of your SAP Solution Manager system will be sent with the S-user for consistency checking. configure the system license number in your SAP Solution Manager; and configure the
S-user consistently with this system license number. The system license number is in the field “System Number”, in the transaction /nslicense.
Note
Download Directory
Configure the central download directory in the download directory field of the SLM managing system. Configure the mounted or shared paths of the central download directory, in download directory field, for each managed system.
Ensure that user <sidadm> of the SLM managing system has write authorization for the central download directory, and user <sidadm> of the managed system has read authorization for the central download directory.
You can manage the central download directory in transaction tmwflow/mopzcfg for SLM release 7.0<x>; the previously central download directory management transaction tmwflow/mopzcd is obsolete. See chapter 5.1 for more information.
Note
SLC Port
Skip this configuration.
Note
JSPM User
If the technical system is of release 7.0x, the password needs to be the password of Software Deployment Manager (SDM); for higher releases of SLM, enter the Java account used for deployment.
Note
If you only use auto-download without auto-deployment for a managed system, you can simplify the configuration by only entering the system ID and database host of the managed system in the configuration assistant. In this case, no configuration is necessary in this managed system.
1. Log in to your managing SAP Solution Manager system, to assign the authorizations for
Maintenance Optimizer.
2. Configure the following roles for Maintenance Optimizer system users:
SAP_MAINT_OPT_ADMIN – see SAP Note 1032322
SAP_MAINT_OPT_ADD – see SAP Note 1124301
3. Specify the systems to be maintained, and the activity, via Maintenance Optimizer, in the
authorization object D_MOPZSYSI in role SAP_MAINT_OPT_ADMIN.
Note
If your SAP Solution Manager managing system is UNIX/Linux, set the parameter “install/umask” to 022. The exported stack XMLs to EPS inbox will have the authorization “-rw-r--r--”, which can be read by any users used by logistic tools.
For more information, refer to SAP Note 24869 (Files are created with incorrect authorization).
4.7 S-User Assignment for Maintenance Optimizer
1. Log in to your managing SAP Solution Manager system and enter the transaction code
AISUSER.
2. Assign S-users to Maintenance Optimizer system users, to access SAP Service Marketplace.
More information about multiple customer numbers: SAP Note 1151450
Figure 11: Assign S-Users for Maintenance Optimizer
Note
When running a Maintenance Optimizer transaction, one configured S-user can be assigned to the transaction. You can use SLM to download the automatically-calculated files; to include manually-selected files from the download basket of the S-user for SLM download, assign the S-user in SLM (see section 4.4) to this maintenance transaction.
4.8 Common Settings for Managing and Managed
Systems
In addition to the above configuration, the JSPM need to be configured on the managing SLM system.
For the managed systems, check whether the Web service sapcontrol is available with SAP
NetWeaver. Only then can it be managed by the SLM system. The web service sapcontrol is available
as of SAP NetWeaver 7.00. It is always available for the managing system, since the managing
system with SLM is always based on SAP NetWeaver 7.00 or a higher release.
If the managed system contains a Java stack, JSPM needs to be configured; if the managed system
contains an ABAP stack, SPAM/SAINT needs to be configured.
These configurations are illustrated in the next section.
www.service.sap.com/solutionmanager
5. Configuration of Managed Systems
Your managed system needs to be based on a release higher than SAP NetWeaver 7.00, with the
web service sapcontrol.
Note
As of SLM 7.01 SP08, you need not configure SLC on the managing system and
managed systems.
5.1 Configuration for Download Directory &
Transport Directory
Both SPAM and JSPM need to access the transport directory of the managed system, to get package
files.
If you use both auto-download and auto-deployment via SLM, the stack XML and downloaded
package files will be automatically processed for the system update. The support package
maintenance type, but not upgrade and installation types, are currently deployed automatically.
If you use only auto-download without auto-deployment via SLM, the stack XML is exported to the
transport directory of the SAP Solution Manager managing system and the maintenance procedure
stack file tab; the package files are downloaded into the central download directory configured in
transaction /n/tmwflow/mopzcfg. SAP recommends combining the transport directories of the
managing and managed systems and the central download directory , if they satisfy the
authorization requirements below. If not, copy the exported stack XML and package files to the
transport directory of the managed system. You may also need to copy the stack XML from the
Maintenance Optimizer procedure or the SAP Solution Manager transport directory, to the
target transport directories of managed systems.
Figure 12: The transport directory and the central download directory
www.service.sap.com/solutionmanager
Note
You can check the transport directory setting in transaction rz11. Input the parameter name DIR_EPS_ROOT. The transport directory value will be displayed. Ensure that the users on systems involved have the required authorization.
System OS Platform User Directory Access
SLM Managing System Linux/UNIX <SID>adm CDD write
Windows NT SAPService<SID> CDD write
Linux/UNIX <SID>adm TD write
Windows NT SAPService<SID> TD write
Managed System Linux/UNIX <SID>adm CDD read
Windows NT SAPService<SID> CDD read
Linux/UNIX <SID>adm TD write
Windows NT SAPService<SID> TD write
*CDD - Central Download Directory * TD – Transport Directory
You need to perform further configuration for user authorizations in the operating system, in a
Microsoft Windows NT environment:
Note
<SID> below is the system ID of the managed system. ...
1. Log in to the host of the managed system; make sure the OS user SAPService<SID> is not in
group Administrator. Otherwise, sapcontrol OSExecute will not work.
2. Log in to the host of the managed system; make sure the OS users SAPService<SID> and
<SID>adm have full authorization for the shared folder /usr/sap.
www.service.sap.com/solutionmanager
Figure 12: Authorization for Microsoft Windows NT
3. Log in to the host of the transport directory; create the OS user SAPService<SID>; set the
same password as for the OS user SAPService<SID> on the host of the managed system;
add this OS user to the group SAP_LocalAdmin. The managed system uses the equivalent OS
user on the central host, to access the transport directory.
4. More information: SAP Note 556734 (FAQ Transport: Setup and other information; and related
notes)
You need to perform further configuration if the operating system of the transport directory host is
Linux/UNIX and the managed system host is Microsoft Windows NT. 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, share the transport directory path /usr/sap/trans/EPS/in
with a path, e.g., \\centralhost\usr.sap\trans\EPS\in.
2. On the host of the managed system, edit the instance profile (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.
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
Only update JSPM manually when you use SLM deployment for the first time. In future system updates, Maintenance Optimizer automatically updates JSPM with SLM support.
Note
For a system based on NetWeaver release 7.00, update JSPM to the latest patch of a support package higher than SP21. If the JSPM is of SP level lower than SP21, and the calculated target JSPM SP is lower than SP21, the SLM deployment option will not be offered in Maintenance Optimizer transaction step “Implement”.
3. For the managing system in which SLM is located, update the JSPM configuration file
/usr/sap/<SID>/DVEBMGS<instance.number>/j2ee/JSPM/param/jspm-srv_config.txt. The
following lines need to be active, or added if missing:
/jspm/deployVersionRule = updateAll
/jspm/forceMode = true
This skips JSPM self-update if it is already up-to-date.