How to Configure Maintenance

SAP Solution ManagerHow-To Guide

How to Configure MaintenanceOptimizer to Use Software LifecycleManager to Automatically DownloadSupport Packages and SAPEnhancement Packages

Applicable Releases:

SAP Solution Manager 7.0 SPS 15 - 17

SAP Solution Manager Scenario:Change request management and change control

Version 1.05

July 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 containedherein 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 WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and servicesmentioned 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 thetrademarks 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 SAPGroup 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 suchproducts 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 notlimited 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 consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over theinformation 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 thosefeatures 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 andvisualize 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, exceptif such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode 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 onlyto be used by SAP’s Support Services and may not be

modified or altered in any way.

Document HistoryDocument Version Description

1.00 (February 2009) First official release of this guide

1.05 (July 22, 2009) Changed Chapter 4.7: added step 7 in the procedure.

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon 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 ..................................................................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 ...........................................10

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

4.6 Service Activation in Internet Communication Framework .......................................114.7 Software Logistics Controller – SLC........................................................................11

4.8 SLD Registration.....................................................................................................12

5. Appendix........................................................................................................................15

How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically DownloadSupport Packages and SAP Enhancement Packages

July 2009 1

1. ScenarioThe maintenance optimizer supports you in managing and implementing maintenance activities inyour system landscape.

The system and solution information in SAP Solution Manager, accessible via the Solution ManagerSystem Landscape transaction (SMSY), is the basis and reference for maintenance transactions. Youcan assign a solution, or one or more systems, to your maintenance transaction, for the greatestpossible flexibility. The maintenance optimizer interacts with the SAP Global Support Backbone todownload 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

ExampleThe end user MUELLERK creates a maintenance transaction (1) and assigns asolution/system to it (2). SAP Solution Manager establishes a connection to SAP GlobalSupport 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 and enhancement packages automatically using the SoftwareLifecycle Manager (SLM), with the maintenance optimizer. This use case is described in this guide.


July 2009 2

2. Background InformationSAP Solution Manager (component ST 400) SPS 15 to SPS 17, the maintenance optimizer supportsthe automatic download of support packages and enhancement packages with the Software LifecycleManager (SLM, component LIFECYCLE MGMT TOOLS 7.00). Before starting the automaticdownload, you have to perform prerequisite configurations for the managing systems and themanaged systems.

Figure 2 Deployment diagram of maintenance optimizer with Software Lifecycle Manager (SLM)

There are two ways to install the SLM and other required software logistics tools, such as, for examplethe SLD....

1. We recommend installing the SLM and the SLD together with the maintenance optimizer, on themanaging SAP Solution Manager system (see figure 3), so you only have to configure onemanaging system.


July 2009 3

Figure 3: One managing SAP Solution Manager system with maintenance optimizer, SLM, SLDand SLC supporting auto-download

2. You have two separate managing systems (see figure 4): the SAP Solution Manager systemwith 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 themanaging SAP Solution Manager system, and connects to the SLM in the other managingsystem. Except for the maintenance optimizer and the SLM, you have to set up and configurethe other required software logistics tools.

Figure 4: Two separate managing systems with maintenance optimizer, SLM, SLD and SLCsupporting auto-download

If you already have a separate managing system with the SLD, you need to configure two managingsystems, to use the already configured SLD.

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

NoteThe managed systems have to be maintained via the maintenance optimizer.Both the managing SAP Solution Manager system and the managing system with theSLM can also be managed systems, when their own components are being updated.


July 2009 4

3. PrerequisitesYou have installed SAP Solution Manager SPS 15, SP 16, or SPS 17.

There are no further prerequisites.

See Appendix B - Relevant SAP Notes [page 15] for relevant SAP Notes.


July 2009 5

4. Configuration of Managing System...

Follow the steps in this chapter to configure the required systems and tools for the automaticdownload.

4.1 Installation of Software Lifecycle Manager - SLM...

1. Install (or update to) the latest support package of the Software Lifecycle Manager (SLM), onthe managing system.More information: SAP Help Portal at http://help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) <language> SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability Software Life CycleManagement Software Lifecycle Manager

2. Check whether the SLM Web services are available, according to Appendix C - Check SLMWeb Services [page 15].

4.2 Configuration for Secure CommunicationFor the SLM, the Secure Sockets Layer (SSL) is mandatory for accessing relevant Web services andfor downloading support packages from SAP Global Support Backbone.

Follow the steps in this section.

4.2.1 Set-up SAP Cryptographic Library for SLM SecureConnection

...

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 SLMSecure 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(2004s) <language> SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Network and Transport Layer Security Transport Layer Security on the SAP J2EE EngineConfiguring 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 withformat binary.

http://help.sap.com/



July 2009 6

Figure 5: Import certificate

4. Click the Add to Certificate List pushbutton. Save the change.


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


July 2009 8

Figure 7: Restart ICM

More information: SAP Help Portal about the configuration of SAP NetWeaver Web Application Serverfor supporting SSL at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s)<language> SAP NetWeaver Library SAP NetWeaver by Key Capability Security SystemSecurity System Security for SAP Web AS ABAP Only Trust Manager ExampleConfiguring the SAP Web AS for Supporting SSL

4.3 Customizing Settings for Maintenance OptimizerComplete 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 Managersystem.

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

8. Choose SAP Reference IMG and navigate to Maintenance Optimizer (Software LifecycleManager).

9. Perform the following Customizing activities:

Customizing Activity Name Customizing Activity Key

Configuration of Extended Maintenance OptimizerFunctions

SOLMAN_MOPZ_SLM_CONF

Set-Up RFC Connection SOLMAN_MOPZ_SLM_RFC

Set-Up Logical Port SOLMAN_MOPZ_SLM_PORT



July 2009 9

Set-Up Software Lifecycle Manager SOLMAN_MOPZ_SLM_CA

The report to display the objects downloaded by the SLM (Set-Up Central Download Directory) canonly be used after the configuring the SLM.

For each update of SAP Solution Manager to a new support package or enhancement package,perform the Customizing activity SOLMAN_MOPZ_SLM_CONF to import newly-delivered Customizingsettings.

NoteIf the client role of the system is Production, change it to Customizing before you executethis Customizing activity. Change it back to Production after you have finished thisactivity. You can change the client role with transaction code SCC4.

Figure 8: Configure Customizing settings for maintenance optimizer

If you get the error message Web services for Software Lifecycle Manager notavailable, in the configuration assistant for the SLM in SAP Solution Manager, check the HTTPSconnection with Connection Test in transaction SM59.

NoteThe structure of the Customizing activities may be different from that in figure 8; you canuse CTRL+F to search for activities with the names listed above.


July 2009 10

4.4 Authorization Configuration for MaintenanceOptimizer

1. Log in to your managing SAP Solution Manager system to configure the authorizations for themaintenance optimizer.

2. Configure the following roles for maintenance optimizer system users:SAP_MAINT_OPT_ADMIN – see SAP Note 1032322SAP_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.

4.5 S-User Assignment for Maintenance Optimizer1. 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 for accessing SAP ServiceMarketplace.

More information about multiple customer numbers: SAP Note 1151450

More information about multiple s-users being assigned to one system user: SAP Note 1170592

Figure 9: Assign s-users for maintenance optimizer


July 2009 11

4.6 Service Activation in Internet CommunicationFramework

1. Go to your managing SAP Solution Manager system and enter the transaction code SICF.

2. Activate the following services in the Internet Communication Framework (ICF):

/default_host/sap/public/bc/icons

/default_host/sap/public/bc/webicons

/default_host/sap/public/bc/webdynpro

/default_host/sap/public/bc/pictograms

/default_host/sap/bc/webdynpro

/default_host/sap/bc/webdynpro/tmwflow and all its sub-nodes.

Figure 10: Activate services in ICF

4.7 Software Logistics Controller – SLC1. 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, athttp://service.sap.com Downloads Download SAP Support Packages and PatchesEntry by Application Group Additional Components SL Controller SL Controller <currentrelease> #OS independent

http://service.sap.com/


July 2009 12

3. Create the directory /usr/sap/<SID>/SYS/global/SDT. On UNIX systems, the SDTdirectory owner must be the <sid>adm user, the group must be sapsys.

4. Go 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 also run the commandchmod 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.

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

4.8 SLD RegistrationMake sure you have installed the SLD on the managing system. You need to register both the ABAPstack and the Java stack of a managed system.

1. Configure the SLD data supplier for the ABAP stack.More information: SAP Help Portal at http://help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) <language> SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability Software Life-CycleManagement System Landscape Directory Configuring Systems to Connect to SLDConnecting AS ABAP Systems to the SLD Setting Up the SLD Data Supplier for Java-BasedSystems 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 SAPNetWeaver 7.0 (2004s) <language> SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key Capability Software Life-CycleManagement System Landscape Directory Configuring Systems to Connect to SLDConnecting AS ABAP Systems to the SLD Setting Up the SLD Data Supplier for Java-BasedSystems

3. Enter the system license number:

a. Go to the managed system, enter the transaction code SLICENSE; copy the systemnumber, which is later the system license number for the SLD administration Web page,from the output field.




July 2009 13

Figure 11: Get system license number

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

c. On the Content Maintenance page, choose All Classes in the Subset dropdown list; inthe Class dropdown list, choose BC System (for the ABAP stack) orSAP_J2EEEngineCluster (for the Java stack).


July 2009 14

Figure 12: Set system license number

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

e. Enter the system license number. Save.

Figure 13: 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 SLD.More information: SAP Note 1281541


July 2009 15

5. Appendix

Appendix A - Relevant Components for IssuesIf you encounter any problems in the configuration, and you need to send a message to SAP, use thefollowing components.

Component Sections

SV-SMG-MAI 4.3 Customizing Settings for MaintenanceOptimizer [page 8]

4.4 Authorization Configuration for MaintenanceOptimizer [page 10]

4.5 S-User Assignment for Maintenance Optimizer[page 10]

4.6 Service Activation in Internet CommunicationFramework [page 11]

BC-UPG-SLM 4.1 Installation of Software Lifecycle Manager -SLM [page 5]

4.7 Software Logistics Controller – SLC [page 11]

4.8 SLD Registration [page 12]

BC-SEC-SSL 4.2.1 Set-up SAP Cryptographic Library for SLMSecure 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, orto the component of relevant SAP Notes.

Appendix B - Relevant SAP NotesSAP Note Description

1137683(Maintenance Optimizer: Notes for Software Lifecycle Manager)

SAP Note for configuring SLM for theuse with the maintenance optimizer

1154188(SLM web service authentication 700 SP14)

SAP Note for SLM Web serviceauthentication

1138247(Maintenance Optimizer: Description about the SLM Config)

SAP Note for configuration assistantfor SLM

958253(SUSE LINUX Enterprise Server 10: Installation notes)

SAP Note regarding the incorrectencryption algorithm for thesapcontrol Web service

There may be a problem of invalid credentials for setting up the connection between SLM and SLCfor Linux/UNIX hosts. Check the sapcontrol service. Follow these steps:

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


July 2009 16

2. Execute the command line sapcontrol -nr <InstanceNumber> -user <SID>adm<password> -function OSExecute "ls" 0 0 log.txtIf you get the 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 Services...

1. In your Web browser, go tohttp://<host>:<port>/webdynpro/dispatcher/sap.com/tc~slm~ui_support/Main. 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 14: Check SLM Web services (1)

3. Choose slmSolManServices from the available Web services.


July 2009 17


4. In the menu bar, choose Test.


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


July 2009 18


6. If you get the exception test.PlanException or test.ServicesException, the SLMWeb services are available; if there is no response, you might be using a lower version of theSLM. Install the latest SLM.

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 withGUID "00000000-0000-0000-0000-000000000000". The reason is: Therequested object does notexist.'</faultstring><detail><(><<)>ns1:getStatus_com.sap.slm.services.PlanExceptionxmlns:pns='urn:com.sap.slm.services'xmlns:ns1='urn:slmSolManServicesWsd/slmSolManServicesVi'><pns:msgValue>Retrieval of plan '00000000-0000-0000-0000-000000000000' failed. Reason: 'SLM encountered an internalexception (BODataManipulationException): Could not find plan on backend 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 alsoindicates that the SLM Web service is available to get the plan status.


July 2009 19


www.service.sap.com/solutionmanager

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

How to Configure Maintenance

Documents

Transcript of How to Configure Maintenance