how to configure maintenance optimizer to use software lifecycle manager

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

© 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, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, 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.

SAP Solution Manager “How-to” Guides are intended to

simplify the product implementation. While specific

product features and procedures typically are explained in

a practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP Solution Manager.

Should you wish to receive additional information,

clarification or support, please refer to SAP Consulting.

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.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

Document History

Document Version Description

1.00 First official release of this guide

1.05 Changed Chapter 5.4: added step 4 in the procedure

1.10 (May 26, 2009) Changed Chapter 5.1: added step 7 in the procedure

1.15 (July 22, 2009) Changed Chapter 4.1: updated SLM version

Changed Chapter 4.3: added a note concerning the download via an

already established extranet connection

Changed Chapter 5.1: added step 7 in the procedure

1.20 (Oct. 26, 2009) Changed Chapter 4.1: updated SLM version

Changed Chapter 4.3: added information at the end of the chapter

Changed Chapter 5.3: added configuration information for transport

directory host being Linux/UNIX while managed system host is Microsoft

Windows NT

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Scenario ...........................................................................................................................1

2. Background Information .................................................................................................2

3. Prerequisites....................................................................................................................4

4. Configuration of Managing System ................................................................................5

4.1 Installation of Software Lifecycle Manager - SLM ......................................................5

4.2 Configuration for Secure Communication in Live Update ...........................................5

4.2.1 Set-up SAP Cryptographic Library for SLM Secure Connection .....................5

4.2.2 Generation and Import of SSL Certificate for SLM Secure Connection ..........5

4.3 Customizing Settings for Maintenance Optimizer .......................................................8

4.4 Authorization Configuration for Maintenance Optimizer ........................................... 13

4.5 S-User Assignment for Maintenance Optimizer ....................................................... 14

4.6 Common Settings for Managing and Managed Systems.......................................... 14

5. Configuration of Managed Systems ............................................................................. 15

5.1 Software Logistics Controller – SLC ........................................................................ 15

5.2 SLD Registration ..................................................................................................... 15

5.3 Configuration for Transport Directory....................................................................... 18

5.4 Support Package Manager – SPAM ........................................................................ 19

5.5 Java Support Package Manager – JSPM ................................................................ 24

6. Appendix ........................................................................................................................ 25

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.



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.



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.



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.



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

format binary.

http://help.sap.com/

http://service.sap.com/sap/support/notes/510007




October 2009 6

Figure 5: Import certificate

4. Click the Add to Certificate List pushbutton; save the change.



October 2009 7

Figure 6: Add certificate to certificate list

5. Run the ICM monitor with transaction code SMICM.

6. Choose Administration ICM Exit Soft Local (or Global); confirm.



October 2009 8

Figure 7: Restart ICM

More information: SAP Help Portal about the configuration of SAP NetWeaver Web Application Server

for supporting SSL 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 System Security System Security for SAP Web AS ABAP Only Trust

Manager Example Configuring the SAP Web AS for Supporting SSL

4.3 Customizing Settings for Maintenance Optimizer

Perform the basic Customizing for SAP Solution Manager before making maintenance optimizer-

relevant customizing settings.

Perform the Customizing for the maintenance optimizer in the managing SAP Solution Manager

system.

1. Log in to your managing SAP Solution Manager system and enter the transaction code SPRO.

2. Choose SAP Reference IMG and navigate to Change Control.

3. Perform the following Customizing activities:

Customizing Activity Name Customizing Activity Key

Configuration of Extended Maintenance Optimizer

Functions

SOLMAN_MOPZ_SLM_CONF

Multiple Software Lifecycle Manager Configuration

Assistant

SOLMAN_MOPZ_SLM_RFC

For each update of SAP Solution Manager to a new support package or enhancement package,

activate newly-delivered BC Sets. As of SAP Solution Manager 7.0 SPS 18, instead of using the




October 2009 9

Customizing activity SOLMAN_MOPZ_SLM_CONF to import newly-delivered Customizing settings, use

transaction code SOLMAN_SETUP to run the SAP Solution Manager Basic Configuration Assistant. You

can check whether the maintenance-optimizer-relevant BC Sets are activated. For more information

about the basic configuration of SAP Solution Manager, see SAP Help Portal at http://help.sap.com

SAP Solution Manager <language> SAP Solution Manager Basic Settings SAP Solution

Manager Basic Configuration.

Figure 8: SAP Solution Manager Basic Configuration Assistant




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.



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 SLM_2 for the MS_2.

Figure 10: Multiple Software Lifecycle Manager Configuration Assistant



October 2009 12

Figure 11: Software Lifecycle Manager Configuration Assistant

Note

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




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:

SAP_MAINT_OPT_ADMIN – see SAP Note 1032322

SAP_MAINT_OPT_ADD – see SAP Note 1124301

http://www.service.sap.com/…

https://smpdla.sap.com/…

https://smpdl.sap-ag.de/…






October 2009 14

3. Specify the systems to be maintained, and the activity, via the maintenance optimizer, in the

authorization object D_MOPZSYSI in role SAP_MAINT_OPT_ADMIN.

4.5 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 the maintenance optimizer system users to access SAP Service Marketplace.

More information about multiple customer numbers: SAP Note 1151450

Figure 13: Assign s-users for maintenance optimizer

4.6 Common Settings for Managing and Managed

Systems

In addition to the above configurations, the SLC, and JSPM need to be configured on the managing

SLM system.

For the managed systems, you have to check whether the Web service sapcontrol is installed with

SAP Netweaver. Only then it can be managed by the SLM system. The Web service sapcontrol is

available as of SAP Netweaver 7.00. Therefore, 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.

The SLC needs to be configured on each managed system. If the managed system contains a Java

stack, JSPM needs to be configured; if the managed system contains an ABAP stack, SPAM (together

with SAINT) needs to be configured.

These configurations are illustrated in the next section.




October 2009 15

5. Configuration of Managed Systems

Your managed system has to be based on a release higher than SAP NetWeaver 7.00, with the Web

service sapcontrol.

5.1 Software Logistics Controller – SLC

Install the latest version of the SLC. For the connection to the SLM 7.0<x>, get the latest release of

SLC 7.0<x>. For the connection to the SLM 7.1<x>, get the latest release of the SLC 7.1<x>.

To install the SLC:

1. Set up Java runtime environment with at least version 1.4.x for SLC 7.0x and 1.5.x for SLC 7.1x.

2. Download the latest Software Logistics Controller (SLC) from SAP Service Marketplace at

http://service.sap.com Downloads Download SAP Support Packages and Patches

Entry by Application Group Additional Components SL Controller SL Controller <current

release> #OS independent

3. Create the directory /usr/sap/<SID>/SYS/global/SDT. On UNIX systems, the SDT

directory owner must be the <sid>adm user, the group must be sapsys.

4. Change to the directory /usr/sap/<SID>/SYS/global/SDT.

5. Copy the SDTServer archive LUP.SAR to the SDT directory.

6. Run SAPCAR -xvf LUP.SAR with the OS user <SID>adm; on UNIX systems also run the

command chmod a+x exe/*.

7. If you install the SLC on an ABAP-only system, switch off the configuration tool: open the file

/usr/sap/<SID>/SYS/global/SDT/config/sdtserver.xml; go to section

<SecuritySettings> and change the settings to off for UseSecStore,

UseRemoteConfigManager and UseConfigManager.

8. Configure the SLC of this managed system in the Multiple Software Lifecycle Manager

Configuration Assistant. For more information, see Customizing Settings for Maintenance

Optimizer [page 12].

More information: SAP Note 1151784 (Setup of SL Controller for Live Update)

5.2 SLD Registration

Make sure you have installed the SLD on the managing system. You need to register both the ABAP

stack and the Java stack of a managed system.

1. Configure the SLD data supplier for the ABAP stack.




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.





Connect to SLD Connecting AS ABAP Systems to the SLD Setting Up the SLD Data

Supplier for Java-Based Systems

http://service.sap.com/






October 2009 16

3. Configure the SLD data supplier for systems which are neither ABAP nor Java-based.





Connect to SLD Connecting Other SAP Systems to the SLD

4. Enter the system license number:

a. Go to the managed system, enter the transaction code SLICENSE; copy the system

number, which is the later system license number for the SLD administration Web page,

from the output field.

Figure 14: Get system license number

b. Go to the SLD admin Web page (usually at http://<sldhost>:<port>/sld). Choose

Administration Content Maintenance.

c. On the Content Maintenance page, choose All Classes in the Subset dropdown list; in

the Class dropdown list, choose BC System (for the ABAP stack) or

SAP_J2EEEngineCluster (for the Java stack).




October 2009 17

Figure 15: Set system license number

d. Choose the link to your registered system to go to its maintenance page.

e. Enter the system license number. Save.

Figure 16: Set system license number

More information: SAP Note 1124583 (Maintenance Optimizer: Missing System Number error of SLM)

Also check the system number of systems in the SLD.

More information: SAP Note 1281541





October 2009 18

5.3 Configuration for Transport Directory

Both SPAM and JSPM need to access the transport directory on the host of the managing system. In

the single system update with the maintenance optimizer, the system downloads the package archives

to a central download directory. If the download directory differs from the transport directory, the

archives need to be copied there for the deployment.

You have 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 permissions for the shared folder /usr/sap.

Figure 17: Authority configuration 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.

More information: SAP Note 556734 (FAQ Transport: Setup and further information; and related

notes)

You have to perform further configuration for Linux/UNIX operating systems. You have to mount the

transport directory with the same path in the hosts of the managed systems as in the central host. ...

1. On the transport directory host, the transport directory path is /usr/sap/trans/EPS/in.




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.



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.



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.



October 2009 22

Figure 20: Configure OCS_API Web service - 1

h. Do not change the default settings, and save.



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



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.

http://service.sap.com/



October 2009 25

6. Appendix

Appendix A - Relevant Components for Issues

If any problems occur in the configuration above, and you need to send a message to SAP, use the

following components.

Component Sections

SV-SMG-MAI 4.3 Customizing Settings for Maintenance

Optimizer [page 8]

4.4 Authorization Configuration for Maintenance

Optimizer [page 13]

4.5 S-User Assignment for Maintenance Optimizer

[page 14]

BC-UPG-SLM 4.1 Installation of Software Lifecycle Manager -

SLM [page 5]

5.1 Software Logistics Controller – SLC [page 15]

5.2 SLD Registration [page 15]

5.5 Java Support Package Manager – JSPM [page

24]

BC-UPG-OCS 5.4 Support Package Manager – SPAM [page 19]

BC-SEC-SSL 4.2.1 Set-up SAP Cryptographic Library for SLM

Secure Connection [page 5]

If you have a problem in the generation of the SSL certificate with SAP NetWeaver Administrator, send a message to the component BC-JAS-SEC.

For issues that are not mentioned here, you can send a message to the component SV-SMG-MAI or

to the component of relevant SAP Notes.

Appendix B - Relevant SAP Notes

SAP Note Description

1137683

(Maintenance Optimizer: Notes for Software Lifecycle Manager)

SAP Note for configuring SLM for the

use with the maintenance optimizer

958253

(SUSE LINUX Enterprise Server 10: Installation notes)

SAP Note regarding the incorrect

encryption algorithm for the

sapcontrol Web service

There may be a problem of invalid credentials for setting up the connection between SLM and SLC

for Linux/UNIX hosts. You need to check the sapcontrol service. Follow the next steps.

1. Log in to the relevant host (of the managed or the managing system) with the operating system user <SID>adm.

2. Execute the command line sapcontrol -nr <InstanceNumber> -user <SID>adm

<password> -function OSExecute "ls" 0 0 log.txt

If you get the of invalid credentials error, see the following SAP Notes:





October 2009 26

SAP Note 877795 (Problems w/ sapstartsrv as of Release 7.00 & 6.40

patch 169)

SAP Note 927637 (Web service authentication in sapstartsrv as of

Release 7.00)

Appendix C – Update from SAP Solution Manager SPS 15-17 to SPS 18

If your SAP Solution Manager system is at support package level 15, 16, or 17, see the following

notes before you update to SPS 18. ...

1. Before applying SPS 18, finish or withdraw maintenance optimizer transactions using SLM.

Since the phases and processing of the SLM update plans have been extended in release 701,

some of your old transactions may not be available anymore.

2. If you have made the secure connection settings in previous packages, you can skip section 4.2

Configuration for Secure Communication in Live Update [page 5].

3. See section 4.3 Customizing Settings for Maintenance Optimizer [page 8] for the relevant

Customizing activities. Re-configure these activities if you already configured them in previous

SAP Solution Manager SPS levels.

Appendix D - Check SLM Web Services

For the SLM, SAP NetWeaver 7.01: ...

1. In your Web browser, go to

http://<host>:<port>/webdynpro/dispatcher/sap.com/tc~slm~ui_support/Ma

in. If you can see the SLM user interface, SLM is installed.

2. In your Web browser, go to http://<host>:<port>, choose Web Services Navigator.

Figure 23: Check SLM Web services (1)

3. Choose slmSolManServices from the available Web services.





October 2009 27


4. In the menu bar, choose Test.


5. Choose getStatus. Enter 00000000-0000-0000-0000-000000000000 in the planId field and

check the result.



October 2009 28


6. If you get the exception test.PlanException, the SLM Web services are available; if you get

another exception or no response, check whether the SLM installation was successful.

The full description of the exception test.PlanException is the following:

Retrieval of plan '00000000-0000-0000-0000-000000000000' failed.

Reason: 'SLM encountered an internal exception

(BODataManipulationException): Could not find plan on back end with

GUID "00000000-0000-0000-0000-000000000000". The reason is: The

requested object does not

exist.'</faultstring><detail><(><<)>ns1:getStatus_com.sap.slm.services

.PlanException

xmlns:pns='urn:com.sap.slm.services'xmlns:ns1='urn:slmSolManServicesWs

d/slmSolManServicesVi'><pns:msgValue>Retrieval of plan '00000000-0000-

0000-0000-000000000000' failed. Reason: 'SLM encountered an internal

exception (BODataManipulationException): Could not find plan on back

end with GUID "00000000-0000-0000-0000-000000000000". The reason is:

The requested object does not exist.

If you get other exceptions decribing The requested object does not exist, this also

indicates that the SLM Web service is available to get the plan status.



October 2009 29


www.service.sap.com/solutionmanager

how to configure maintenance optimizer to use software lifecycle manager

Documents