PUBLIC Setup 4.6 Systems for MAI

Solution Manager 7.1 Document Version: 1.1 2013-06-27

Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example EXAMPLE Example Example <Example> Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. 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. EXAM PLE Keys on the keyboard, for example, F2 or EN TER. 2 2012 SAP AG. All rights reserved. Typographic Conventions

Document History Version Date Change 1.0 <2012-11-30> Initial Creation 1.1 <2013-06-27> Removed unnecessary step in Configure Automatically setup activity Document History 2012 SAP AG. All rights reserved. 3

Introduction... 5 1 System Preparation... 6 1.1 Check the Software versions.... 6 1.2 Instance Status support... 6 1.3 Diagnostics and SAP HostAgent :... 6 1.4 Create the required user on the Managed system.... 6 1.5 Create the Read RFC... 7 2 Manual system creation in LMDB... 8 2.1 Check Outside Discovery status.... 8 2.2 Create the technical system: The Technical System Editor... 8 2.2.1 Create the system... 8 2.2.2 Assign the software... 8 2.2.3 Assign the System database... 9 2.2.4 Create the Technical Instance... 9 2.2.5 Create the ABAP Clients... 9 3 Managed system Setup... 10 3.1 Step 1: Assign Product... 10 3.2 Step 2: Check Prerequisites... 10 3.3 Connect managed system... 10 3.4 Assign the Diagnostics Agent.... 10 3.5 Skip Enter System Parameters... 10 3.6 Enter Landscape Parameters... 10 3.7 Skip "Create Users" step... 11 3.8 Configure Automatically... 11 4 System Monitoring Setup... 12 4.1 Update the Template Content... 12 4.2 Check the templates... 12 4.3 Perform the System Monitoring setup... 12 4.4 Start the system monitoring application... 12 5 Customization and Troubleshooting... 13 4 2012 SAP AG. All rights reserved.

Introduction In SAP Solution manager 7.0, 4.6 systems were supported in terms of monitoring using central CCMS. SAP Solution Manger 7.1 introduced a new framework of Monitoring and Alerting but 4.6 systems were too old and could not be supported. These systems are still heavily used by customers and hence also require monitoring and alerting capabilities. With SAP Solution Manager SP 7, these systems are now supported but the setup requires specific manual setup steps that are described in this document. 2012 SAP AG. All rights reserved. 5

1 System Preparation 1.1 Check the Software versions. Solution Manager must be of version 7.10 SP7 or higher. In order to collect the metrics, the managed system must have the ST-PI component of version SP7 or higher. 1.2 Instance Status support In order to get the instance status, you need to implement note 1285185 -> Appendix A1. This step is optional but allows you to be notified about your instance status. 1.3 Diagnostics and SAP HostAgent : The diagnostics agent with the SAP host agent are required to collect specific os data metrics and enables Outside Discovery that eases the host creation in LMDB. You have to make sure that the SAPHost Agent is of version 90 or higher and that it is rightly configured. You'll find all the details in the SAP Solution Manager Configuration workcenter: follow System Preparation step "Prepare Landscape Description Prepare Outside Discovery. Make sure you also have agents installed on the Database server to get the host in LMDB. 1.4 Create the required user on the Managed system. To get metrics from the managed system, solution manager will use a remote function call on the managed system. To make this possible, you need to create a specific user with some minimum rights. To do so : Create user SM_<SOLMAN_SID> on the managed system. Assign authorization o Object S_RFC o RFC_TYPE FUGR o /SDF/E2E_EFWKE_COLLECTORS2 6 2012 SAP AG. All rights reserved.

1.5 Create the Read RFC From the solution manager stack, start transaction SM59 then create an ABAP connection named SM_<managed_SID>CLNT<ABAP_CLIENT>_READ (i.e. SM_PRDCLNT200_READ for system PRD on client 200). Enter the logon details with user created step 1.4. 2012 SAP AG. All rights reserved. 7

2 Manual system creation in LMDB 2.1 Check Outside Discovery status. Start the Landscape Browser application from the SAP Solution Manager Administration workcenter (related links) then click on the Host view. Search for your hosts on which your system is installed on. Make sure it already exists then click on the host status light on the right. In case you cannot see your host or if the host status is different from green check SAP note (1611483 - SolutionManager7.1 - Outside Discovery common errors). 2.2 Create the technical system: The Technical System Editor 4.6 system are too old to benefit from the SLD data providers so a manual creation is required here. You may find instructions on how to create to use the Technical System Editor from SAP note 1669650 - LMDB concept & troubleshooting in the LMDB setup guide. If your system is already existing in LMDB you can skip step 2.2.1 2.2.1 Create the system From SAP Solution manager Administration workcenter as a solman_admin user, navigate to view Landscape Technical Systems then click on System Operations Create Technical system. Enter the system type ABAP then click on Next Enter the system Id, installation number and database host Name then click on Next Next screen should display the Extended System. It must be the same as the SID then click on Next Save 2.2.2 Assign the software In the technical System Editor, select your system then display the software section. Make sure you have at least the SAP R/3 4.6C: R/3 Server installed and marked as diagnostics relevant. Assign the newly created product instance to the corresponding Product System using the button Assign to Product System. Create it if needed 8 2012 SAP AG. All rights reserved.

2.2.3 Assign the System database Select the Assign Database then click on the Assign System Database. Select the corresponding database in the F4 help and click ok. 2.2.4 Create the Technical Instance Select Technical Instances then click on Add. Choose the host from the F4 help and the instance number. Enter the working directory (i.e. \usr\sap\<sid>\dvebmgs<nb>\work) Check (eventually) the Central Application Application Server check box Repeat for all other instances. 2.2.5 Create the ABAP Clients. Drill in the ABAP Clients then click on add for each client in your managed system. Enter a Logical System name and eventually enter a "Role in development Landscape" in the matching column. 2012 SAP AG. All rights reserved. 9

3 Managed system Setup Start transaction solman_setup from your SAP Solution manager with a solman_admin user. Select Managed Systems Configuration then select your managed system and click on Configure System. 3.1 Step 1: Assign Product This step should be green if you correctly followed step 2.2.2. You might need to check the Diag. Rel. checkbox 3.2 Step 2: Check Prerequisites Prerequisites 3.3 Connect managed system Enter as the RFC read Access the destination created step 1.5 Create the Read RFC 3.4 Assign the Diagnostics Agent. Assign the diagnostic agent installed on the Managed system 3.5 Skip Enter System Parameters 3.6 Enter Landscape Parameters Make sure the installation paths are the right ones. 10 2012 SAP AG. All rights reserved.

4 System Monitoring Setup 4.1 Update the Template Content In case this is the first system monitoring setup you are performing, you need to first execute the steps 1 to 3. Especially make sure that the applied content is up to date and matches your Solution Manager SP. 4.2 Check the templates In step 4 Template Maintenance, make sure that there is the SAP ABAP 4.6C template in the Technical Instance and the Technical System trees. If not it is more likely that your Template content is not up to date or your Solution Manager is of version 7.10 SP6 or lower. 4.3 Perform the System Monitoring setup Select your managed 4.6 system in the Technical Systems tab and then select next. Make sure the SAP ABAP Basis 4.6C is part of the Installed Products. If not, check the managed system setup again. Click on Assign Templates on all the needed Managed Object Name especially the system and the instances and choose the default SAP ABAP 4.6 template. Click on Apply and activate. Click on next Eventually activate Reporting functionality. (details are described in the Solution Manager Help) Click on next and see the setup results. 4.4 Start the system monitoring application Once you performed the setup, it might take some minutes before you get results. After some time, start the Technical Monitoring workcenter, opens System Monitoring view, select your system and then start the System monitoring 12 2012 SAP AG. All rights reserved.

5 Customization and Troubleshooting SAP delivers best practices template as standard content that should fit most of your needs. For any customization requirements or to trouble shoot eventual missing metrics., please navigate to the SAP Technical Operations WIKI available here http://wiki.sdn.sap.com/wiki/display/techops/home 2012 SAP AG. All rights reserved. 13

www.sap.com/contactsap

Material Number 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System ads, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, xapps, xapp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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.