SAP Solution Manager How-To Guide Simplified Configuration of Single System Update in Maintenance Optimizer Applicable Releases: SAP Solution Manager 7.0 Enhancement Package 1 SP23 or higher SAP Solution Manager Scenario: Implementation of SAP Solutions Version 1.00 November 2012
Copyright 2012 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 NetWeaver. 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
Typographic Conventions Type Style Example Text Description 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 Icons Icon Description Caution Note or Important Example Recommendation or Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.
Table of Contents 1. Business Scenario... 1 2. Background Information... 1 3. Prerequisites... 1 4. Single System Update Configuration... 2 4.1 Create RFC Destination... 2 4.2 Create Logical Port... 5 4.3 Maintain Technical System Details... 6 5. Appendix... 10
1. Business Scenario Maintenance Optimizer Single System Update downloads the support packages calculated by Maintenance Optimizer, and installs them, remotely, in the managed systems, centrally, from the Solution Manager system, using deployment tools such as SPAM, JSPM and/or SAINT. 2. Background Information The configuration of Maintenance Optimizer Single System Update is significantly simplified because the Maintenance Optimizer now switches the HTTPS connection with Software Lifecycle Manager to an HTTP connection. The protocol switch avoids the risky installation of crypto graphics lib on the J2EE server of Solution Manager System, and simplifies the configuration process. The switch from HTTPS to HTTP presents no security risk, because all the critical data, such as system logon credentials, service market place user and password, are no longer passed by RFC; they are now maintained directly on the J2EE server of Solution Manager system. Software Lifecycle Manager (SLM) is a Java application running on J2EE server. You can configure SLM on any Java technical system. It is not necessary to have SLM always on Solution Manager Java system even though it is typical case. In this configuration guide, we assume SLM is on Solution Manager Java system. You can adjust accordingly if your SLM is on other Java systems. 3. Prerequisites Application Enhancement. Correction Note 1709002 - MOpz: Use SLM with HTTP on the Solution Manager system. Documentation: SAP Note 1325790( BC-UPG-SLM) SAP Note 1597822( SV-SMG-MAI) How to Operate Single System Update in Maintenance Optimizer Single System Update Configuration Guide Maintenance Optimizer on Service Market Place
4. Configuring Single System Update 4.1 Create RFC Destination An HTTP RFC connection is required for the communication between Maintenance Optimizer and Software Lifecycle Manager. The RFC destination connects Maintenance Optimizer in Solution Manager ABAP with Software Lifecycle Manager in Solution Manager Java. Go to the transaction SM59, and press the New button to create a new connection. The name of the RFC connection is SLM, because Maintenance Optimizer recognizes only this name in Single System Update scenario. The connection type is G http connection to external server. The target host is the host of the Solution Manager Java server, and the service number is the port number of the http service provided by the Java server. The path prefix is slmservices/config1, the web service name in Software Lifecycle Manager.
On the Logon&Security tab, maintain the logon user and password for the Solution Manager Java server. The SSL protocol should be inactive, because we are configuring Single System Update in HTTP mode, not the traditional HTTPS mode. When you have maintained the RFC connection, test the connection by pressing the Connection Test button on the application toolbar. Update Software Lifecycle manager on the Solution Manager Java system, to the latest version, before testing the connection, by applying the newest support package of Java software component SOFTWARE LIFECYCLE MANAGEMENT. This software component is independent of all other components in the system, so this update is not harmful to any other functions in the system.
A successful test result screen looks like below.
......t www.sdn.sap.com/irj/sdn/howtoguides 4.2 Create Logical Port A logical port is required by Maintenance Optimizer, to call the web services provided by Software Lifecycle Manager. You can create it with an ABAP report delivered in SAP Note 1709002. To start the report, call transaction code SA38, enter RPT_CREATE_LP in the input box, and then press the Execute button at the top left of the application bar. The report runs in background, with no input or output. It derives its data from the created RFC destination SLM, and creates the corresponding logical port.
4.3 Maintain Technical System Details The Single System Update scenario can download and deploy support packages to technical systems. Technical system details such as system logon user, system host, etc. are needed by Software Lifecycle Manager. System details are maintained in a web configuration wizard provided by the Software Lifecycle Manager in the Solution Manager Java system. Ensure the latest support package of SOFTWARE LIFECYCLE MANAGEMENT is in the Java system. It is an independent software component, and will not harm any functions of the system. To navigate to the configuration wizard, open the initial Netweaver Application Server Java page of the Solution Manager Java System, replace the index.html at the end of the URL address, by slm, and press enter to go to the SLM configuration page.
The SLM configuration page lists any configured systems. You can create a new system entry by pressing New at the top left. When you create a new system entry, or edit a system entry in the list, you open a two-step configuration wizard. In the first step, you maintain the system data for SLM download. The data includes basic technical system information, like system ID, system host and instance number, and service market place user and password.
In the second step, you maintain the data for support package deployment, which includes operating system level user and password, SPAM/JSPM users, and the network path of the central download directory. You can press Save at the top right, to save the system configuration data in step 2.
When configuration data is saved, the system appears in the list of the initial configuration page. You can select one or more of them to validate the configuration data, by pressing Check at the top right. Check results are displayed in the middle of the page, and a detailed explanation is displayed at the right of the page.
5. Appendix www.sdn.sap.com/irj/sdn/howtoguides If you need support from SAP for the Maintenance Optimizer Single System Update feature, create a customer message on one of the following application components. For Software Lifecycle Manager BC-UPG-SLM For Maintenance Optimizer SV-SMG-MAI For ABAP support package tools BC-UPG-OCS-SPA For Java support package tools BC-UPG-OCS-SPJ