configure maint opt sps22 [1]

8/6/2019 Configure Maint Opt SPS22 [1]

http://slidepdf.com/reader/full/configure-maint-opt-sps22-1 1/38

SAP Solut ion Mana ger

How -To Guide

How t o Conf igure Main tenanc e

Opt im izer to Use Sof t w are Li fecyc le

Manager t o Autom at ic a l l y Dow nload

and Deploy Support Pac k ages and

SAP Enhanc em ent Pac k ages

Appl icable Releases:

SAP Solut ion Ma nager 7.0 SP 22

ALM proc ess:

Change request managem ent and change contr o l

Version 1.05

Oct ober 2010



© Copyright 2010 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 withrespect 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 forerrors 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 H is to ry

Document Version Description

1.00 First official release of this guide

1.05 Changed Chapter 4.4: added a note regarding S-User and update of the

SLM configuation information

Changed Chapter 5.2: update configuration information for transport

directory



Typographic Convent ions

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

CautionNote or Important

Example

Recommendation or Tip



How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download

and Deploy Support Packages and SAP Enhancement Packages

October 2010 1

Contents

1. Scenario ...........................................................................................................................2

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

2.1 The managing and managed system landscapes ......................................................3

2.2 Configuration Sections ..............................................................................................5

2.3 Update from SAP Solution Manager SPS 15-21 to SPS 22 .......................................5

3. Prerequisites....................................................................................................................7

4. Configuration of Managing System ................................................................................8

4.1 Registration of systems in SLD and SMSY ................................................................8

4.2 Installation of Software Lifecycle Manager - SLM ......................................................94.3 Configuration for Secure Connection to SLM .............................................................9

4.3.1 Setting up SAP Cryptographic Library for SLM Secure Connection ...............9

4.3.2 Generation and Import of SSL Certificate for SLM Secure Connection ..........9

4.4 SLM Configuration .................................................................................................. 12

4.5 Customizing Settings for Maintenance Optimizer..................................................... 17

4.6 Authorization Configuration for Maintenance Optimizer ........................................... 18

4.7 S-User Assignment for Maintenance Optimizer ....................................................... 19

4.8 Common Settings for Managing and Managed Systems.......................................... 19

5. Configuration of Managed Systems ............................................................................. 20

5.1 Software Logistics Controller – SLC ........................................................................ 20

5.2 Configuration for Transport Directory....................................................................... 20

5.3 Support Package Manager – SPAM ........................................................................ 23

5.4 Java Support Package Manager – JSPM ................................................................ 28

6. Appendix........................................................................................................................ 29





October 2010 2

1. Sc enar ioThe maintenance optimizer helps you to manage and implement 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 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 asolution/system to it (2). SAP Solution Manager establishes a connection to SAP Global

Support Backbone and displays all currently available support packages (3). The supportpackages selected by the user are stored in the download basket of end userS000021112 (4) and downloaded from there (5).

The maintenance optimizer leads you through the following steps for the maintenance transaction:

You can download support 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 2010 3

2. Bac k ground Inform at ionWith SAP Solution Manager (component ST 400) SPS 22, the Maintenance Optimizer supports the

automatic download of support packages and enhancement packages. At the same time, theMaintenance Optimizer supports single system update, with the Software Lifecycle Manager (SLM,

component SOFTWARE LIFECYCLE MANAGEMENT), for the scenarios below:

Update Type SLM

Release

Managed System

NetWeaver Release

Comment

Maintenance 7.0x 7.00 Kernel and IGS components auto-

update not supported.

7.01 Kernel and IGS components auto-

update not supported.

7.02 Kernel and IGS components 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. For SLM 7.01, the minimum required release is 7.01

SP05 patch 2.

Note: Maintenance/Installation/Upgrade of add-on product versions in the above maintenance

and installation scenarios, is supported.

Note: If kernel auto-update is not supported by SLM, you need to update kernels before

deploying other packages via SLM.

Before a single system update, you need to configure the managing and managed systems.

2 .1 T he manag ing and managed system l andscapes

The Maintenance Optimizer can connect to multiple SLMs of different releases. The systems involved

in the maintenance optimizer single system update can be as follows:





October 2010 4

Figure 2: Deployment of Maintenance Optimizer with Software Lifecycle Manager (SLM)





October 2010 5

Various tools and applications work together to support auto-download and single system update.

Suppose you have two managing systems (see Figure 3Figure 3): the SAP Solution Manager system

with the Maintenance Optimizer, and a system in which you install the SLM, the SLD content, and the

Software Logistics Controller (SLC). In this case, the Maintenance Optimizer is in the managing SAPSolution Manager system, and connects to the SLM in the other managing system. You need to set up

and configure the software logistics tools for the automatic download, in addition to the maintenance

optimizer and the SLM. You need to set up and configure the tools for the single system update, in

both your SLM managing system and managed systems: the SLC, the Support Package Manager and

SAP Add-On Installation Tool (SPAM/SAINT), and the Java Support Package Manager (JSPM). You

also need to activate the Web service sapcontrol .

Figure 3: Two separate 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 system with SAP Solution

Manager.

Note

An SAP Solution Manager system can connect to more than one SLM component.

Note

The managed systems need to be maintained via the Maintenance Optimizer.The managing SAP Solution Manager system and the managing system with the SLMcan also be managed systems, when their own components are being updated.

2.2 Co nf igu ra t ion Sec t i ons

Before using the auto-download and single system update functions, you need to perform the

configuration steps below:

Register the system landscape: section 4.1.

Configure SLM: section 4.2-4.4.

Customize the Maintenance Optimizer and configure authorization: section 4.5-4.7.

Configure logistic tools: section 04.8-5.4.

2 .3 Upda te f rom SAP So lut i on Manager SPS 15 -21 to

SPS 22

If your SAP Solution Manager system is currently at 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 the

Maintenance Optimizer transactions which are using SLM; import the latest SPAM/SAINT.





October 2010 6

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

Configuration for Secure Connection to SLM Configuration for Secure Communication in Live

Update [page 8 ].

3. Check section 4.4 SLM ConfigurationSLM Configuration [page 1211] and configure the missingitems, 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, you need to update SLM, SLC, SPAM/SAINT and

JSPM to the newest version, manually, on other managing and managed systems.

Formatt(United St





October 2010 7

3. Prerequis i t esYou have installed SAP Solution Manager SPS 22.

You have installed the SLM, SLC and SLD in the managing systems.

You have installed the SLC and the installation tool for ABAP-based systems (SPAM/SAINT) and for

Java-based systems (JSPM), in each managed system.

SAP software logistics knowledge.

See Appendix B - Relevant SAP NotesAppendix B - Relevant SAP Notes [page 2927 ] for relevant

SAP Notes.

Formatt

Times NeStates)





October 2010 8

4 . Conf igur at i on o f Manag ing Sy stem...

Follow the steps in this chapter to configure the required systems and tools for the single system

update.

4 .1 Regi st r a t i on o f systems i n SLD and SMSYYou need to register both the ABAP stack and the Java stack 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.




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.



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

Note

Check the system numbers of systems in the SLD.More information: SAP Note 1281541 (Wrong SLD system number causes error in SLMplan execution).

4. After registering systems in SLD, you need to 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 (MaintenanceOptimizer: Check system landscape).

Note

Check whether components SLC and JSPM are maintained in the Java systemcomponent in SMSY. If SLC and, JSPM were not auto-maintained via SLD, while youinstalled them, you need to maintain them in Java system components of both managingand managed systems.

http://help.sap.com/












October 2010 9

4 .2 Ins tal la t i on o f So ftw a re L ifecyc le M anager - SLM...

1. Install (or update to) the Software Lifecycle Manager (SLM) to the latest available patch of thesupport package equal to or higher than 7.01 SP5 patch 2.




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 C - Check SLM Web

ServicesAppendix C - Check SLM Web Services [page 3028 ].

4 .3 Conf igur at i on fo r Secu r e Connec t i on t o SLMThe Secure Sockets Layer (SSL) is mandatory for accessing Web services for the component

SOFTWARE LIFECYCLE 7.01.

Follow the steps in this section.

4 .3 .1 Se t t i ng up SAP Cryptog raph i c L i bra ry f o r SLM Secure

Connect ion...

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 .3 .2 Genera t i on and Impor t of SSL Cer t i f ica t e fo r SLMSec ure Connec t ion

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 withtransaction 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 .

Formatt

Times NeStates)









October 2010 10

Figure 4: Import certificate

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





October 2010 11

Figure 5: 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 2010 12

Figure 6: 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.4 SL M Co nf ig urat ion

To use the automatic download and deployment to a managed system, you need to configure the

managed system in an SLM system. You can access the Multiple Software Lifecycle Manager

Configuration Assistant with the transaction code /n/TMWFLOW/MOPZCFG, in the SAP Solution

Manager system. You can configure more than one SLM in the Multiple Software Lifecycle Manager Configuration Assistant .

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.

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 with these two SLDs, SLM_1 and SLM_2.

2) Create two SLM connection entries in Multiple Software Lifecycle ManagerConfiguration Assistant.







October 2010 13

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 7: Multiple Software Lifecycle Manager Configuration Assistant





October 2010 14

Figure 8: Software Lifecycle Manager Configuration Assistant





October 2010 16

Note

Download Proxy.

If you want to reuse an existing extranet connection (according to SAP Note 124743) to

download with MOPZ and SLM, you must configure your proxy on SAProuter to forwardURLs of archives at SAP Service Marketplace to a cascadable proxy at SAP. The URLsto 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' is1 for VPN connections, 2 for Secure Network Communication (SNC), or 3 for both VPNconnections and SNC.

Note

S User.

The S-user is used for generating download content and downloading. Besides, thesystem license number of your SAP Solution Manager system will be sent together withthe S-user for consistency checking. You need to configure the system license number inyour SAP Solution Manager and configure the S-user consistent with this system license

number here. To check the configured system license number, open transaction /nslicense, see the field “System Number”.

Note

Download Directory.

You need to configure the central download directory in the download directory field forthe SLM managing system. You need to configure the mounted or shared paths of thecentral download directory, in download directory field, for each managed system.

You need to ensure that: user <sidadm> of the SLM managing system has writeauthorization to the central download directory; user <sidadm> of the managed systemneeds read authorization to the central download directory.

You can manage the central download directory in transaction /n/tmwflow/mopzcfg for

SLM of release 7.0<x>; the previously-delivered central download directory managementtransaction /n/tmwflow/mopzcd is obsolete.

Note

SLC Port.

If the system is installed with product version SAP NETWEAVER CE, you need toconfigure its SLC port as 6240.

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

https://smpdla.sap.com/

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

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

https://smpdla.sap.com/

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





October 2010 17

Figure 10 Software Lifecycle Manager Configuration Assistant – Simplified Configuration for

Download Only Purpose (as from ST 400 SP25)

Note

If you only need to use auto-download without auto-deployment for some managedsystem, you can simplify the configuration much with only inputting system ID anddatabase host of the managed system in the configuration assistant. In this case, there is

no configuration necessary inside this managed system.

4 .5 Cus tomizing Se t t i ngs for Maintenance Op t im ize r Perform the basic Customizing for SAP Solution Manager before making Maintenance Optimizer-

relevant customizing settings. For each update of SAP Solution Manager to a new support package or

enhancement package, activate any newly-delivered BC Sets.

Run the SAP Solution Manager Basic Configuration Assistant, with transaction code SOLMAN_SETUP.

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 .







October 2010 18

Figure 10: SAP Solution Manager Basic Configuration Assistant

4 .6 A utho ri za t ion Conf igur at i on f or M a in tenance

Opt imizer

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

3. Specify the systems to be maintained, and the activity, via the Maintenance Optimizer, in theauthorization object D_MOPZSYSI in role SAP_MAINT_OPT_ADMIN.

Note

If your SAP Solution Manager managing system is a UNIX/Linux one, you need to setthe parameter “install/umask” to 022. With this, the exported stack XMLs to EPS inboxwill have the permission of “-rw-r--r--”, which can be read by any users used by logistictools.

For more information, refer to SAP Note 24869 (Files are created with incorrectpermissions).





October 2010 19

4 .7 S-User Ass ignmen t for Ma in tenance Op t im ize r

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 11: Assign S-Users for Maintenance Optimizer

4 .8 Common Se t t i ngs fo r Manag ing and Managed

Systems

In addition to the above configuration, 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 can it be managed by the SLM system. The Web service sapcontrol is

available as of SAP Netweaver 7.00.It is therefore 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/SAINT

needs to be configured.

These configurations are illustrated in the next section.





October 2010 20

5 . Conf igur at i on o f Managed Sy stem sYour managed system needs to be based on a release higher than SAP NetWeaver 7.00, with the

Web service sapcontrol .

5 .1 So ftw a re Log is t ic s Con t r ol le r – SLC

For the managed system which is of SAP NetWeaver release 7.0x, install the latest patch of SLC 700;

For the managed system which is of SAP NetWeaver release 7.1x, 7.2x or 7.3x, install the latest patch

of SLC 720. The requisite lowest patch of SLC 700 for Maintenance Optimizer SP22 is patch 21; the

requisite lowest patch of SLC for Maintenance Optimizer SP22 is patch 1.

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 4.4 SLM Configuration [page 8 ].

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

5 .2 Conf igur at i on fo r T ransport Di rec to r y

Both SPAM and JSPM need to access the transport directory of the managed system to get package

files.

In case that you use both auto-download and system update via SLM, the stack XML and downloaded

package files will be automatically processed for the system update.

In case that you use only auto-download without system update via SLM, the stack XML is exported to

the transport directory of SAP Solution Manager managing system; the package files are downloaded

in the central download directory configured in transaction /n/tmwflow/mopzcfg. SAP recommends to

unify the transport directories of the managing and manged systems and the central download

directory as the same one, which needs to satisfy the authorization requirements below. If not, you

need to copy the exported stack XML and package files to the transport directory of the managed

system.

http://service.sap.com/






October 2010 21

Figure 12: The transport directory and the central download directory

NoteYou can check the transport directory setting via transaction /nrz11. Input the parametername DIR_EPS_ROOT, the transport directory value will be displayed. You need toensure that users on involved systems have the correct authorizations.

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





October 2010 22

Figure 12: 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)

4.

You have 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. 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 .

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.





October 2010 24

Figure 13: 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 2010 25

Figure 14: Set changes and transports for client-specific objects - 2

f. Run the Web service configuration with transaction code WSCONFIG. Ignore theinformation 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 2010 27

Figure 16: 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 codeSCC4.

3. After the configuration of the Web service OCS_API , you can update the SPAM properties, ifrequired.

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 yet

exist).

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 followingline: 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 with your SAP system user:http://<host>:80<InstanceNumber>/sap/bc/srt/rfc/sap/OCS_API?wsdl . If the





October 2010 28

wsdl definitions are displayed normally, the web service is ready for use.

Figure 17: Check OCS_API Web service

5 .4 Java Suppo rt P ackage Manage r – JSPM

To update Java stack components via SLM, for the first time, you need 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 equivalent SPAM configuration.

Note

You only need to update JSPM manually when you use the SLM deployment for the firsttime. In future system updating, the maintenance optimizer automatically updates JSPMwith SLM support.

Note

For a system based on Netweaver release 7.00, you need to update JSPM to the latestpatch of a support package higher than SP21.







October 2010 29

6. Appendix

Appendix A - Relevant Components for IssuesIf 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.5 Customizing Settings for Maintenance

OptimizerCustomizing Settings for Maintenance

Optimizer [page 1715 ]

4.6 Authorization Configuration for Maintenance

OptimizerAuthorization Configuration for

Maintenance Optimizer [page 1818 ]

4.7 S-User Assignment for Maintenance

OptimizerS-User Assignment for Maintenance

Optimizer [page 1919 ]

BC-UPG-SLM 4.1 Registration of systems in SLD and SMSY

(the registration in SLD)

4.2 Installation of Software Lifecycle Manager -

SLMInstallation of Software Lifecycle Manager -

SLM [page 9 ]

4.4 SLM Configuration

5.1 Software Logistics Controller – SLCSoftware

Logistics Controller – SLC [page20]

5.4 Java Support Package Manager – JSPMJava

Support Package Manager – JSPM [page 28 ]

BC-UPG-OCS 5.3 Support Package Manager – SPAMSupport

Package Manager – SPAM [page23 ]

BC-SEC-SSL 4.3.1 Setting up SAP Cryptographic Library for

SLM Secure ConnectionSet-up SAP Cryptographic

Library for SLM Secure Connection [page 9 ]

If you have a problem in the generation of the SSL certificate with SAP Netweaver Administrator, senda 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

1306446

(Maintenance Optimizer: Notes for Single System Update)

Collective SAP Note for auto-

download and single system update

scenarios.

Formatt

(United St

Formatt

Times NeStates)

Formatt

Times NeStates)

Formatt

Times NeStates)

Formatt

Times NeStates)

Formatt

Times Ne

Formatt

Times Ne

Formatt

Times NeStates)





October 2010 30

1151732

(SLM/SLC Configuration Trouble Shooting Guide)

SAP Note for trouble shooting in SLM

configuration.

1325790(SLM 7.0x - Troubleshooting note)

SAP Note for trouble shooting in SLMexecution, including the manual

actions list updated frequently.

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 to set-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 systemuser <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:

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 - Check SLM Web Service sFor the SLM, SAP NetWeaver 7.01:...

1. In your Web browser, go tohttp://<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 18: Check SLM Web services (1)





October 2010 31

3. Choose slmSolManServices from the available Web services.


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 2010 32


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 internalexception (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.



w w w . s e r v i c e . s a p . c o m / s o l u t i o n m a n a g e r

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

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

configure maint opt sps22 [1]

Documents