SAP Solution Manager 7.2 System Monitoring

SAP Solution Manager 7.2 Getting Started with Monitoring Published: 12 July 2017 In Collaboration between IT-Conductor & OZSoft Introduction This eBook is a result of a 4-parts blog series which provided an overview and explanation of major steps and considerations for Solution Manager 7.2 SP5 Installation, Configuration and SAP Monitoring of an S/4HANA scenario • Part 1: Solution Manager 7.2 SAP Monitoring (Setup) • Part 2: Solution Manager 7.2 SAP Monitoring (Base Configuration) • Part 3: Solution Manager 7.2 SAP Monitoring (Managed System Config) • Part 4: Solution Manager 7.2 SAP Monitoring (System & App Monitoring) • SAP Monitoring Summary SAP Solution Manager 7.2 SP5 Part 1 of 4 Installation By OZSoft Consulting for ITConductor.com ozsoft-consulting.com ITConductor.com 2 Plan your Solution Manager 7.2 SP5 with Maintenance Planner To install Solution Manager 7.2 SP5 we need to proceed with generation of two stack files: one for ABAP instance and one for JAVA. • ABAP INSTANCE: • log into Maintenance Planner and start by clicking Plan a New System. Click again on Plan. • Choose the right System Type (ABAP) and Solution Manager 7.2 with SP5 as a system. Push the files to your download basket and download Stack XML file. ozsoft-consulting.com ITConductor.com 3 • To generate stack file for JAVA we need to start from beginning by selecting System Type and entering desired SID.2 SP5 with Maintenance Planner • JAVA INSTANCE: • log into Maintenance Planner and start by clicking Plan a New System. Click again on Plan.com 4 . Push the files to your download basket and download Stack XML file.com ITConductor. ozsoft-consulting.Plan your Solution Manager 7.2 using your stack file. • After downloading the files you are ready to install Solution Manager 7. com 5 .com ITConductor.sap. The URL it is random generated and it will change every time you execute the sapinst binary.2 SP 5: ABAP Stack Installation • Before we start what you need is to download source of SAP Solution Manager 7.support. SAP Solution Manager 7.com/instguides Start Software Provisioning Manager with the parameter SAPINST_STACK_XML=<absolute path> • On the SP20 the SWPM won’t start the SAP GUIServer.com/#/softwarecenter • Follow the guide to install your system – especially consider the instructions for installations using a stack configuration file. Refer to the installation guide for Software Provision Manager at: https://service. instead it will start a web application on port 4237 so you can log into it with HTTPS protocol.2 from https://launchpad. In the Welcome screen. you get installation options filtered according to your stack XML file: ozsoft-consulting.sap. com ITConductor. Once you complete ABAP support Pack Stack 5 installation now its time to install JAVA stack. you must install the SAP notes: Complete process. SAP Solution Manager 7. ozsoft-consulting.2 SP 5: ABAP Stack Installation • You can choose to automatically start the SUM after the installation is complete: • During the upgrade.com 6 . com ITConductor. SAP Solution Manager 7. Complete process.com 7 .2 SP 5: JAVA Stack Installation • Start Software Provisioning Manager with the parameter SAPINST_STACK_XML=<absolute path> • Perform the installation and update procedure similar to the ABAP stack. ozsoft-consulting. • Run SGEN for your system ozsoft-consulting.com 8 . • SAP systems based on SAP NetWeaver 7.com ITConductor.com/instguides.4 or higher only: You can skip some of these post-installation steps if you have already completed them as a step in task list SAP_BASIS_SETUP_INITIAL_CONFIG when running the ABAP task manager for lifecycle management automation (transaction STC01) immediately after the installation was completed.2 SP 5: Post-Installation Steps • After the successful completion of the installation. see https://service. follow the instructions provided in Post-Installation section of the installation guide to complete the configuration. For more information.sap. Solution Manager 7. Download and apply SAP note in system We recommend to set it to ssl/client_ciphersuites = 918:PFS:HIGH More details about ciphersuites can be found in Note 510007 ozsoft-consulting. (SAP Note 2048519 .2 SP Stack 05: recommended corrections. with the specified recommended values.Profile parameters for SAP Solution Manager 7.Solution Manager 7. Solution Manager 7.com 9 .com ITConductor.2) • Ref: SAP Note 2433454 .2 SP 5: recommended corrections • Set or adjust the following profile parameters. com 10 .15. Subdirectory bin of the Enterprise Manager installation. A common best practice is to use the sidadm user of the Solution Manager installation to install and run the Enterprise Manager. In particular.1 Release Notes for changes and open issues • Download installation files from SAP Service Marketplace. • Download the third party external component package files (eula.Introscope Installation for SAP Customers and 2285189 .tar.2 SP 5: WILY Introscope 10.Introscope 10.v10.com ITConductor.txt and osgiPackages./EMCtrl. Solution Manager 7.1 Installation • Ref: SAP Note 797147 . • The installation of the Enterprise Manager by default goes to the following directories: /usr/sap/ccms/apmintroscope/ • On Unix platforms a shell script is provided to start and stop the Introscope Enterprise Manager.1.0.sh start • Check http://fqdn:8081/sapdashboard/ • Users and its password: • Admin – Admin89 • Guest – guest12 ozsoft-consulting. on Unix operating systems do not use the root account to launch the installer. Run .unix. for a UNIX system) • You should run the installer with the same user account that will be used later on for running the Enterprise Manager. com ITConductor. Solution Manager 7.com 11 . Open Functional Unit Configuration UI. • Select System Landscape Directory and click Enable Automatically • Upgrade SLD CR content & CIM model as per SAP Note: 669669 – Update of SAP System Component Repository in SLD ozsoft-consulting.2 SP 5: SLD Configuration • You can perform the initial configuration with the Configuration Wizard (CTC) in the SAP NetWeaver Administrator by calling the following URL: http://fqdn:5XX00/nwa Go to Configuration >> Scenarios >> Configuration Wizard. 2 SP 5: Install the Diagnostics Agent 7.2 system • Enter the parameters of the connection to a central System Landscape Directory (SLD). Solution Manager 7.How to connect Diagnostics Agent to Solution Manager 7.com ITConductor.com 12 .45 • Start SWPM and navigate to General Option >> Diagnostics in SAP Solution Manager >> Install – Diagnostics Agent • Specify the paths to complete DVDs or Blu-ray media such as to a mounted kernel DVD. the path to a download folder containing all software packages. or the paths to several individual download locations of software packages. Ref: SAP Note 1833501 .Diagnostics Agent - Installer Versions and 2385361 . ozsoft-consulting. and 001 for the Source Client User Masters.com 13 .com ITConductor. • Perform this on newly installed systems and before running SOLMAN_SETUP transaction.2 SP 5: Optional: Perform a client copy • You can use the SAP delivered client 001 as productive client for the SAP Solution Manager ABAP System. Solution Manager 7. ozsoft-consulting. • Alternatively create a specific productive client: • Create a new client and perform a local client copy using profile SAP_UCSV with 000 as Source Client. Creation and activation of users for the Support Hub Communication • 2359837 .Software Update Manager 1.com ITConductor.Solman_setup reports error "The configuration of RFC SAPOSS is not correct".Update of SAP System Component Repository in SLD • 2000132 .0 SP20 [lmt_006] • 2433454 .Configuring RFC connections to the SAPNet R/3 front end (OSS) correctly • 797147 .2 • 2239513 .Introscope Installation for SAP Customers • 2174416 ."Set Up Connections to SAP" and "Support Hub Connectivity" in Solution Manager 7. even though SAPOSS RFC is correctly configured ozsoft-consulting.Solution Manager: Overview on Release Information Notes • 1680045 .2 SP 5: SAP Note • Pay attention to the following notes: • 1595736 .Installer Versions • 669669 .com 14 . Solution Manager 7.2 SP Stack 05: recommended corrections • 2385361 .How to connect Diagnostics Agent to Solution Manager 7.0 (recommended: SP20) • 2371752 .2 system • 1833501 .Release Note for Software Provisioning Manager 1.Diagnostics Agent .Central Note .Solution Manager 7. 2 SP 5 • “Solution Manager 7.com 15 .2 SP 5: Configuration Basics • This is the end of the installation phases of Solution Manager 7.com ITConductor. ozsoft-consulting. Next – Solution Manager 7.2 SP 5: Monitoring Base Configuration” .is the next section that we’ll examine. SAP Solution Manager 7.com .2 SP5 Part 2 of 4 Monitoring Base Configuration By OZSoft Consulting for ITConductor. The first should have no authorizations since.Creation and activation of users for the Support Hub Communication ) ozsoft-consulting. it could be misused.sap. A technical S-User is required and maintained via the Support Portal Applications: https://apps. when being logged as a Super Administrator.com/technical-user This technical S-User can only be created and then activated.com 17 . or to request licenses. SAP provides a new communication channel between SAP Solution Manager and SAP backbone system.support.2. The second S-user is needed to perform the synchronization of the service messages and system data.(See SAP Note 2174416 . • Starting with Solution Manager 7. Prepare the Mandatory Configuration • Classical S-User are requested and maintained via the SAP Support Portal: User Management For security reasons it is recommended to maintain two S-user for SAP Solution Manager.com ITConductor. Confirm the popup. you will be asked to activate (Web Dynpro) services.com ITConductor.com 18 . Mandatory Configuration • To start with the SAP Solution Manager Configuration call transaction SOLMAN_SETUP from your productive client. • As the first execution may take some time you might get a connection timeout. • In System Preparation scenario you configure prerequisites for performing SAP Solution Manager Configuration: • Define System Role • Check Prerequisites • Set Up Connections to SAP • Apply Recent Corrections • Maintain Technical Users • Review configuration status ozsoft-consulting. in order to be able display this wizard in your browser screen. • When you start the SOLMAN_SETUP for the first time. com 19 .com ITConductor. from an IT administration point of view • For this step prefer to create SOLMAN_ADMIN user as standard or you can use any other username you want to create. • Now your system has completed the first Setp step. Mandatory Configuration: Define System Role • Define the role and purpose of the SAP Solution Manager system. please make sure you log off and Login to SAP Solution Manager with Solman_Admin user to continue with next steps ozsoft-consulting. follow the documentation associated to each activity • To perform the listed automatic check. you check the aspects of your SAP Solution Manager installation that are relevant for configuration. • To perform the listed manual checks. System Preparation: Check Prerequisites • In this step. execute the activities and check the status. ozsoft-consulting.com ITConductor.com 20 . you ensure that SAP Solution Manager can connect to SAP Support Portal.com ITConductor. • RFC Connectivity • Support Hub Connectivity • In this step. • Important: Every RFC connection to SAP Support Portal must use the load balancing and the related logon group.com 21 . System Preparation: Set Up Connection to SAP • In the sub-steps of this step. you setup the connections to the SAP backbones. ozsoft-consulting. com 22 . ozsoft-consulting.com ITConductor. you configure the connections to the support hub channel. will migrate to use this channel. with SAP Solution Manager 7.2. Over time all functionalities (including SNOTE). • SAP introduces a new data communication channel. System Preparation: Support Hub Connectivity • In this step. this includes: • Corrections for SAP Notes • Essential ABAP Corrections • Java Corrections • First you apply the latest available corrections for the Note Assistant.com 23 .750. your apply the latest corrections for ABAP and Java.com ITConductor.740. System Preparation: Apply Recent Corrections • In the sub-steps of this step. Apply SAP note in your system – 1668882 - Note Assistant: Important notes for SAP_BASIS 730.731.751 ozsoft-consulting. Apply SAP note : 2353022 .2 SP05 . containing essential corrections. you apply the latest essential corrections applicable to you SAP Solution Manager ABAP system.com 24 .com ITConductor. ozsoft-consulting. System Preparation: Apply Recent Corrections • In the sub-step. as recommended by Sap.basic functions • The implementation of the SAP Solution Manager Central Corrections Note.SAP Solution Manager 7. is dragging a set of other SAP notes. com 25 . System Preparation: Apply Recent Corrections • Finally follow the documentation to make sure to also implement the minimum patch levels required for certain Java Software Components • Each patch must correspond to the support package implemented in the system. check the current support packages of the software components in your system. ozsoft-consulting.com ITConductor. If you are unsure. System Preparation: Maintain Technical Users • In this step you have to create or update so called technical users. copy specific SAP delivered roles. or for which you want to update authorization.com 26 . generate the associated role profiles. and assign the appropriate roles. and finally assigns the roles/profiles to the users. During this process. the system automatically creates users. ozsoft-consulting.com ITConductor. • Use the Create all Users button • Or select one by one the users you create. com 27 .com ITConductor. System Preparation: Complete • The Complete step gives you an overview on all performed activities and their status • After the System Preparation you have to perform the scenario Infrastructure Preparation ozsoft-consulting. as required by SAP Solution Manager • First. double check the correctness of the SAP Solution Manager ABAP and Java Technical System description in the LMDB ozsoft-consulting. • Finally. specify and trigger the synchronization of the landscape Management Database. • Then. you describe and enable the Landscape Management.com ITConductor. With the synchronization LMDB will import any up-to-date CR content. from the relevant SLD. define the connections towards all System Landscape Directory that contain data applicable to this Solution Manager system.com 28 .Infrastructure Preparation: Set Up Landscape Management • In the sub-steps of this step. and as well the Technical System description + CIM model. ozsoft-consulting. being relevant for this SAP Solution Manager • You need at least one connections with SLD role: Source for LMDB • Choose Create New Connections. Infrastructure Preparation: SLD Connections • Define the connections to any System Landscape Directory (SLD).com 29 .com ITConductor. or Assign Existing HTTP Destination from SM59. • Connecting to Several SLDs. automatic synchronization to import all SLD information to the LMDB. The unique-path-principle for data must be fulfilled when the LMDB is synchronized with more than one SLD system. see SAP Note 935245. • The activation starts an initial. Therefore. ozsoft-consulting. full.com 30 . • Use a prefix reserved at SAP. and technical system descriptions from the system landscape is collected in the SLD (source namespace “sld/active”).com ITConductor. System landscape descriptions are always imported from all connected SLDs. It must be synchronized with the LMDB (target namespace “active”). This can only be ensured if SLD systems connected to the LMDB run in separated landscapes. For more information. Infrastructure Preparation: LMDB Synchronization • CIM model. • Choose an object server name according to the following rules: • All SLD and LMDB systems in your landscape must have different names. which takes several hours. if available. they must not overlap. SAP software catalog (SAP CR content). Infrastructure Preparation: LMDB Content Check • This step checks the systems on which SAP Solution Manager is running and whether the LMDB settings are complete. ozsoft-consulting.com ITConductor.com 31 . com ITConductor. A distinction is made between two kind of landscapes: • With Load Balancer (typically using a SAP Web Dispatcher system) • Without Load Balancer • LMDB doesn't receive fully qualified host names for the technical systems from SLD. Infrastructure Preparation: Set Up Java Connectivity • In the sub-steps of this step. ozsoft-consulting. you set up mainly the Java connectivity by: • Defining any Load Balancer / SAP Web Dispatcher. hostname and port numbers to be used to establish HTTP connections.com 32 . You need to temporarily provide this information in the pop-up. or the hostnames and HTTP/HTTPS ports of the SAP Solution Manager ABAP and Java system. • In this sub-step you define. • Enable the connectivity with the SAP Solution Manager Java System • Enable the authentication of the Diagnostic Agents in the SAP Solution Manager Java System. • JCo/RFC and Web Services calls between the SAP Solution Manager ABAP system and Java system • Checking that the Java UME uses ABAP as backend • Checking that the Java system has required software levels • Enable Single Sign-On between ABAP and Java • Turn off the Diagnostic Agent maintenance mode. Java Connector RFC calls. ozsoft-consulting. Web Service calls. for example.com ITConductor.com 33 . Infrastructure Preparation: Enable Connectivity • In this step. you check and set up the SAP Solution Manager Java system to support. and single sign-on for Web User Interfaces. you configure the connections between the Diagnostics Agents and SAP Solution Manager.com ITConductor. Infrastructure Preparation: Diagnostic Agent Authentication • In this step. ozsoft-consulting. you provide a root certificate so that Diagnostic Agents can be authenticated when connecting to SAP Solution Manager.com 34 . • In addition. com 35 . • This SAP Solution Manager system includes a dedicated SAP Business Information Warehouse to store. aggregate and report collected data. as foundation for SAP Solution Manager. • Enable the SAP BW. Infrastructure Preparation: Set Up SAP BW • In this section. you set up SAP Business Warehouse to be able to use it for reporting. you set up SAP Business Information Warehouse (BW). ozsoft-consulting. • SAP recommends that you use the standard SAP Solution Manager BW environment. In this step. as BW data is stored with client and system-specific keys. in the current client of the SAP Solution Manager system.com ITConductor. You cannot make changes later without help from SAP. • Confirming to use the SAP BW part of the SAP Solution Manager System • Maintain Users related to SAP BW activities. you enable the selected SAP BW. You also assign roles to them. you create BW users. by executing the following activities: • Use RSTCO_ADMIN transaction in the BW client. • In the Infrastructure Preparation scenario -> Set Up BW step -> Maintain Users step. you create dialog users. depending on the scenario and step: • In the System Preparation scenario. you create or update dialog. to make sure the source system activation finished successfully. Maintain Technical Users step. • The BI_TCO_ACTIVATION job usually requires around 15 min.com ITConductor. Infrastructure Preparation: Maintain Users • In this step. or BW users. Create Basic Dialog Users step. • In this step. you create technical users (of type System). technical users (of type System). • In the Basic Configuration scenario.com 36 . in a new installation ozsoft-consulting. ozsoft-consulting. • Prerequisites: • Diagnostics Agents are installed on all hosts where Enterprise Managers are operated (stand-alone. Infrastructure Preparation: Define CA Introscope • In this step. • The OS user that executes the Diagnostics Agent has read and write permissions for the CA Introscope installation directory and files. you discover already installed CA Introscope Enterprise Managers (ISEM).com 37 .com ITConductor. For more information. see SAP Note 1365123. Manager of Managers. or collectors). manually. • As a consequence the so called SAPConnect infrastructure is set up and the “send job” is automatically scheduled. • For more information about secure e-mail encryption. you set up the infrastructure that enables SAP Solution Manager to send notifications using e-mail and text messaging (short message service. ozsoft-consulting. see SAP Note 149926. • To send out notifications. SMS).31 SP2. Since SAP_BASIS 7.com ITConductor.com 38 . Infrastructure Preparation: Set Up E-Mail Communication • In this step. maintain additionally a Recipient List and Global Recipient Pool (Related Links section) • Execute the RSCONN05 report and activate the required SAPconnect secure E-mail session. an integrated encryption solution is available. and enable e-mail encryption. See SAP Note 1637415. you perform first the manual activity • Finally. Infrastructure Preparation: Configure CRM Basis • In this step. • Typically. by choosing Execute All.com ITConductor. you configure several infrastructure components for SAP Customer Relationship Management (CRM) that are used by the mandatory scenarios in SAP Solution Manager. run the remaining automatic activities. ozsoft-consulting.com 39 . in the List of Gateway Services. SAP Fiori apps. which are required to enable the SAP Solution Manager Fiori Launchpad. You find these services in this step. Infrastructure Preparation: Enable Gateway Services • In this step.com 40 .com ITConductor. the status of this step is red. you activate SAP Gateway services (OData services). If you haven't activated them. under Cross Scenario Configuration. You need to activate the SAP Gateway services for each of your scenarios. and mobile applications. ozsoft-consulting. Note: You can only work with the SAP Solution Manager Launchpad if you have activated the SAP Gateway services UI BE: Services Model Provider and OData Service for GPA document. and the status of each step.com 41 . • After the Infrastructure Preparation you have to perform the scenario Basic Configuration ozsoft-consulting. including information about the users who made the changes.com ITConductor. Infrastructure Preparation: Complete • This step provides an overview of the steps that have been performed in this scenario. com ITConductor.com 42 . EWA. Basic Configuration: Configure Basic Functions • In this step. Default Self-Monitoring) • Review list of import and customization • Activation of most WebDynpro and further SAP Solution Manager Launchpad services ozsoft-consulting. Service Delivery. you create the logical ports to enable SAP Solution Manager ABAP applications to call the Web services available on the SAP Solution Manager Java stack: • Setup of Basic Functions (RCA. • In other systems (for development. including those receiving or sending data to SAP Support Portal. ozsoft-consulting. • In a production system. testing etc.com ITConductor. all recommended SAP Solution Manager jobs are scheduled. you usually decide which of the SAP Solution Manager jobs that receive or send data to SAP Support Portal are to be scheduled. you schedule important jobs needed by SAP Solution Manager. Basic Configuration: Schedule Jobs • In this step.).com 43 . com ITConductor. you schedule a periodic background job that creates and updates business partners for users in the SAP Solution Manager system. that cannot be carried out automatically: • You enable the Rapid Content Delivery (ST-CONT) for System and Application Monitoring and Guided Procedures • You delete documents and sessions from SAP Solution Manager • You enable the SAP Service Content Updates (ST-SER) for Early Watch Alert • You setup HTTP and R/3 connections in Service Market Place to enable remote supportability • You schedule a cleanup job for application logs • Business Partner for Scenario Users. In this activity. You use this activity to configure the Rapid Content Delivery application in SAP Solution Manager to download content packages automatically.com 44 . • Configuration for Rapid Content Delivery. • Change job : AI_SDK_USER_BP_GEN to run as SOLMAN_BTC user • For more information you can look SAP note : 2383652 – Configure NetWeaver Download Service for Rapid Content Delivery ozsoft-consulting. Basic Configuration: Configure Manually • In this step you perform manual activities in SAP Solution Manager. Basic Configuration: Configure Manually • Delete Sessions with Corresponding Documents and Download Data. Instead of applying ST-SER Support Packages you activate once the Service Content Update. (The Service Content Updated is executed in the job SM:SERVICE CONTENT UPDATE) ozsoft-consulting. The Service Content Update offers a superior method to keep the EarlyWatch Alert up-to-date.com 45 . This activity helps you to reduce data volume in SAP Solution Manager. • Service Content Update Configuration. A prerequisite is a RFC connection from the SAP Solution Manager to SAP Service Marketplace.com ITConductor. The SAP Solution Manager will then always retrieve the latest corrections for the EarlyWatch Alert from SAP Service Marketplace. In this activity. you enable a remote HTTP connection from SAP to the SAP Solution Manager system. ozsoft-consulting.com 46 .com ITConductor. Basic Configuration: Configure Manually • Enable Remote HTTP Connection to Solution Manager for SAP Support. In this activity. you enable a remote R/3 connection from SAP to the customer SAP Solution Manager system. • Enable Remote R/3 Connection to Solution Manager for SAP Support. In this activity. you schedule the reorganization or cleanup of SAP Solution Manager application logs. This activity invalidates all server- side caches in SAP NetWeaver user interface services. • SAP Solution Manager Application Log Cleanup. SAP Note 1911102 describes a good practice to handle log reorganization in SAP Solution Manager. • Clear all Server-side User Interface Services for Launchpad in SAP NetWeaver. • In other systems (for development. and so on). technical users (of type System). testing. you usually create or update the user roles directly in the system. Basic Configuration: Create Basic Dialog Users • In this step. (If the PFCG transport recording is enabled.) ozsoft-consulting. the modifications are added to transport requests. • In a production system.com ITConductor.com 47 . you create or update dialog. or BW users. Otherwise. you need to add the modified roles manually to customizing transport requests. These changes must be transported. you cannot create or update any user roles. com 48 . Basic Configuration: Complete • This step provides an overview of the steps that have been performed in this scenario. ozsoft-consulting. • After the Basic Configuration you typically now start the execution of the Managed System Configuration. including information about the users who made the changes. and the status of each step. • Also you should consider doing the customization of the SAP Solution Manager Launchpad (see link).com ITConductor. Configure NetWeaver Download Service for Rapid Content Delivery • 1911102 .Importance of SLD/LMDB "Object Server" parameter • 1637415 . digital signature • 2383652 .740.S/MIME integration in SAPconnect • 149926 .2 SP 5: SAP Note • 2174416 .basic functions • 935245 .com ITConductor.751 • 2353022 .750.Solution Manager application logs reorganization ozsoft-consulting. Solution Manager 7.SAP Solution Manager 7.731.Secure e-mail: Encryption.Creation and activation of users for the Support Hub Communication • 1668882 .com 49 .Note Assistant: Important notes for SAP_BASIS 730.2 SP05 . Next – Solution Manager 7.2 SP 5: Managed Systems Configuration • This is the end of the Mandatory Configuration phases of Solution Manager 7.2 SP 5 • “Solution Manager 7.2 SP 5: Managed Systems Configuration” - is the next section that we’ll examine. ozsoft-consulting.com ITConductor.com 50 SAP Solution Manager 7.2 SP5 Part 3 of 4 Managed System Configuration By OZSoft Consulting for ITConductor.com Managed System Configuration : Register HANA system to SLD • Open URL https://<HANAServerHostname>:1129/lmsl/HDBLCM/<SID>/index.html • Login with <sid>adm user and open “Configure System Landscape Directory Registration” • Restart HANA system to push your system data in to SLD. ozsoft-consulting.com ITConductor.com 52 or the paths to several individual download locations of software packages. the path to a download folder containing all software packages.com 53 . Ref: SAP Note 1833501 .How to connect Diagnostics Agent to Solution Manager 7.Diagnostics Agent - Installer Versions and 2385361 . ozsoft-consulting.com ITConductor.2 system • Enter the parameters of the connection to a central System Landscape Directory (SLD).Managed System Configuration: Install the Diagnostics Agent • Start SWPM and navigate to General Option >> Diagnostics in SAP Solution Manager >> Install – Diagnostics Agent • Specify the paths to complete DVDs or Blu-ray media such as to a mounted kernel DVD. Install HANA client on SAP Solution Manager server • Download and extract the software to an empty directory. Open a shell and go to the directory where you unpacked the software. Call the program hdbsetup (GUI installation) or hdbinst (command-line installation). • Follow the instructions displayed by the installation tool. • For the environment of users that will use the client, including the user <sid>adm, add the installation path to the library path environment variable. (Linux: LD_LIBRARY_PATH) ozsoft-consulting.com ITConductor.com 54 Upload the Extractors for HANA 2.0 • Update Stores as per SAP note : 2403493 - Solution Manager: Enabling the Monitoring of HANA 2.0 • Upload the attached CV Template 'SAP HANA DATABASE 2.00.xml'. This template should be uploaded using the following path: Workcenter Solution Manager Administration -> Infrastructure -> Content -> Root Cause Analysis Content -> Stores. • Upload the Extractors for HANA 2.0. Please upload the attached File 'Templextr_HANA_20.csv'. This file should be uploaded using the following path: Workcenter Solution Manager Administration -> Infrastructure -> Content -> Root Cause Analysis -> Extractors. Than go to Change Mode and press the 'Expert Mode'. Only with the Expert Mode you will have the possibility to upload the attached file. • Ensure that the MAI Content is up-to-date. It is available with: • Solution Manager 7.1: ST_CONT 100 SP 28 • Solution Manager 7.2: ST_CONT 200 SP 9 ozsoft-consulting.com ITConductor.com 55 Managed System Configuration: Assign Product • Run transaction SOLMAN_SETUP and select system: • Both systems are configured together. • Set Diagnostics-relevance with Automatic settings ozsoft-consulting.com ITConductor.com 56 • Note: We do not want to change this user password so make sure you run script below: • ALTER USER MONI DISABLE PASSWORD LIFETIME. Managed System Configuration: Check Prerequisites • The Software Prerequisites activity now relies on the RTCCTOOL running on the SAP Solution Manager system.com 57 .com ITConductor. • Create HANA Database user. for checking the ST-A/PI and ST-PI versions • Execute automatic activities first. ozsoft-consulting. for example.com ITConductor. For each managed system.com 58 . Managed System Configuration: Maintain RFCs • In this step you create or delete RFC connections to the clients in managed systems. client 000. you should create at least a READ RFC connection to the production client. ozsoft-consulting. you assign Diagnostics Agents to each server (host) on which managed systems are running.com ITConductor. If auto assignments does not work. • The “Auto Assign” option should be used to assign a Diagnostics Agent to a system. the “Agent Admin” UI can be used for troubleshooting. • The “SLD Agent Candidate Management” is no longer accessible from the Managed System Configuration UIs. before retrying “Auto Assign” ozsoft-consulting. Managed System Configuration: Assign Diagnostics Agent • In this step.com 59 . ozsoft-consulting. Java. you specify the system parameters required to configure the managed system. ABAP. Managed System Configuration: Enter System Parameters • In this step. which depend on the type of the managed system.com ITConductor. or database systems.com 60 . for example. com ITConductor. to avoid time- consuming error-handling.com 61 . you can verify and add landscape parameters.Managed System Configuration: Enter Landscape Parameters • In this step. ozsoft-consulting. Verify the landscape parameters carefully. com ITConductor. to avoid time- consuming error-handling. Verify the landscape parameters carefully. Managed System Configuration: Maintain Users • In this step. ozsoft-consulting.com 62 . you can verify and add landscape parameters. you use the automatic activities to configure the technical system and the client that you have selected in step 3 Select Monitored Systems and step 4 Select Client. ozsoft-consulting.com 63 . Managed System Configuration: Finalize Configuration • In this step.com ITConductor. Managed System Configuration: Check Configuration • In this step. ozsoft-consulting.com 64 .com ITConductor. you automatically check whether the system is configured correctly. and you update the statuses in the overview of the Managed Systems Configuration. com ITConductor. ozsoft-consulting. • After this scenario is finished.com 65 . and the status of each step. you can proceed by navigating to the next scenario or by choosing a link from the What do you want to do now? area. Managed System Configuration: Complete • This step provides an overview of the steps that have been performed in this scenario. including information about the users who made the changes. ozsoft-consulting.2 SP 5: System Monitoring” .2 SP 5 • “Solution Manager 7.is the next section that we’ll examine that will actually monitor the S/4HANA environment we added.com 66 .2 SP 5: System Monitoring • This is the end of the Managed System Configuration phases of Solution Manager 7.com ITConductor. Next – Solution Manager 7. SAP Solution Manager 7.com .2 SP5 Part 4 of 4 System Monitoring By OZSoft Consulting for ITConductor. 2 SP 5: System Monitoring • The Setup (Part 1).com 68 .com ITConductor. and Managed Systems Configuration (Part 3) must have been completed successfully. Solution Manager 7.Part 2 (Configuration) • Solution Manager 7.Part 3 (Managed System Config) • In this Part 4: We will assign the application scenario and final steps for System Monitoring ozsoft-consulting.2 SAP Monitoring . Preparation & Configuration (Part 2). visit these other sections: • Solution Manager 7.2 SAP Monitoring .Part 1 (Setup) • Solution Manager 7.2 SAP Monitoring . If not. com ITConductor.2 SP 5: System Monitoring • Run transaction SOLMAN_SETUP: Application Operations -> System Monitoring • This step is the entry point and overview page of the system monitoring configuration. ozsoft-consulting. System Monitoring includes technical systems.com 69 . Solution Manager 7. DBMS and hosts. com ITConductor. you configure the monitoring infrastructure. • In this step. System Monitoring: Configure Infrastructure • In this step.com 70 . you use the automatic activities to check the prerequisites for the configuration of the System & Application Monitoring infrastructure. ozsoft-consulting. you perform manual activities to configure the System and Application Monitoring infrastructure: 1. ozsoft-consulting. 2. To perform the activity.com ITConductor. change the Execution Status to Performed and choose Save. System Monitoring: Configure Infrastructure • In this step. When you have performed the activity. To display the Documentation of the activities.com 71 . choose the link in the column Navigation. The activities are displayed in the Manual Activities table. choose Display in the relevant row. 3. you can still create incidents manually from the alert inbox.Choose Active for this dropdown list box on the Summary tab page. • Automatic Notification . ozsoft-consulting.com 72 . you can still create notifications from the alert inbox. • Third-Party Components . if you want incidents (support messages) to be automatically created (in Solution Manager Support Desk) from Alerts.com ITConductor. If you choose Inactive. if you have integrated one or more 3rd party tools to work with System & Application Monitoring.Choose Active for this dropdown list box on the Summary tab page. System Monitoring: Default Settings • In this step you can enable or disable the following functions for the System & Application Monitoring: • Automatic Incident Creation .Choose Active for this dropdown list box on the Summary tab page. if you want alerts to automatically send notifications as e-mails or SMS. If you choose Inactive. System Monitoring: Reporting-Settings • In this step. activate the BI content if you want to use BI-based reporting. so you can see whether the preconditions for successfully activating the BI-based reporting are met.com 73 . • If health check is finished with an error. error in Solution Manager 7."Cannot read the RFC destination from the BW to the Solution Manager".2 ozsoft-consulting. the health check results of the BI-based reporting are displayed. see the SAP note 2483407 .com ITConductor. If no health check is finished with an error. • The upper tray contains the settings for the BW housekeeping. System Monitoring: Housekeeping • In the step "Housekeeping" you make settings for the BI and the Monitoring and Alerting Infrastructure related housekeeping. Per default minute interval data are kept for 19 days and then aggregated to hourly data which are then kept for 31 days and so on.com ITConductor. The alert store housekeeping settings determine when an open alert is confirmed automatically and when a confirmed alert is deleted.com 74 . ozsoft-consulting. It is recommended to leave the default settings und just save in this step. Please be sure you really know what you are doing when you change settings here. as these settings have an influence on the data growth in Solution Manager and hence changes here can lead to huge data growth if not considered carefully. The lower tray contains the housekeeping settings for the monitoring and alerting infrastructure. Global settings are overwritten by template settings and template settings are overwritten by metric/alert specific settings. ozsoft-consulting.com ITConductor. also the work mode settings have the three hierarchy levels "Global". "Template" and "Metric/Alert". The monitoring can be paused depending on the work mode a system is in and you can even have different thresholds depending on the work mode. This way you avoid getting alerts if you system is in a planned downtime. • As the alert consumer settings for notifications and incidents etc. System Monitoring: Workmode Settings • In the step "Workmode Settings" you can change the global settings for the handling of the alerting if work modes are configured for a system.com 75 . Work modes can be scheduled in the Technical Administration Workcenter under Work Mode Management. as well as data collector templates. It is recommended to implement the latest version. a content update might help. If your monitoring is running fine.com 76 .com ITConductor. there is no need to update the content independent of the support package implementation. • If new content is found then you will see it in this step indicated by a "Yes" for New Content Available and also the "Update" button will be activated. The monitoring content contains all templates that are delivered by SAP for System Monitoring and all other scenarios like PI Monitoring. ozsoft-consulting. If you have problems with a metric and the troubleshooting reveals that it has an error in the definition of the content. • The content needs to be updated after every support package implementation. System Monitoring: Update Content • In the last step of the infrastructure configuration you update the monitoring content. • You can create two different levels of users. Or create the users one by one. However it might be useful to take the information provided here as template to build an authorization concept for your Solution Manager.com ITConductor. Please check the documentation in the column "Documentation" for the users for more information. ozsoft-consulting. The L2 (Level 2) user is the more powerful user. The step is optional. System Monitoring: Standard Users • In the step "Standard Users" you can create users in SAP Solution Manager that have the exact right amount of authorizations to perform System Monitoring. you don't need to create the users to run System Monitoring. To create all users with the default names select the "Create all Users" button.com 77 . • The delivered SAP templates already have meaningful settings. You can create a template of this type by selecting the template on which you want to base your template.com 78 . a database. which can be a host. a technical system or a technical instance. you can skip this step. ozsoft-consulting. System Monitoring: Template Maintenance • The content of System Monitoring is delivered in SAP templates which contain metrics. and choosing the Create Custom Template button. alerts and events used to monitor managed objects.com ITConductor. SAP delivers templates for a various kind of managed objects. The templates are groups by managed object type. • Templates are dependent on the product version of the managed object. if you do not want to change these. If you want to make changes. we recommend that you make these changes in your own template. • A template can only be assigned if the correct product version is selected during the managed system setup of the managed system. or databases. • Once you have selected all systems you want to set up. • Before you can configure system monitoring for a managed object you have to finish the Managed System Configuration for the object. • In this step you can also remove monitoring from a managed object if necessary using the "Remove Monitoring" button.com ITConductor. click the "Next" button. otherwise no default templates will be assigned to the selected systems. technical scenarios. You can either select technical systems. Without selecting a managed object you cannot proceed to the next setup steps. ozsoft-consulting. Make sure you are in Edit mode when you click Next. hosts. System Monitoring: Define Scope • In this step you select the managed object you want to configure for system monitoring.com 79 . so you can continue the configuration right away. This is done in the background.com ITConductor. For all managed objects in scope the assigned templates are applied and activated. • Each managed technical system consists of several managed objects of type technical instance. System Monitoring: Setup Monitoring • In this step monitoring templates will be assigned to the managed systems in scope. • Managed objects can have one template per installed product. • Choose the Apply and Activate button to apply and activate the assigned templates (you can display or change the default templates in step Template Maintenance). database and host.com 80 . ozsoft-consulting. ozsoft-consulting. • In this step the status of all previous system monitoring steps are displayed. System Monitoring: Complete • The system monitoring setup is completed for the managed systems in scope.com ITConductor.com 81 . com ITConductor.com 82 . System Monitoring: Demo • Check System Monitoring in SOLMAN_WORKCENTER • You can also access Solution Manager content from the Fiori Launchpad ozsoft-consulting. System Monitoring: Demo • Click on a System’s: • Click on a System’s Alert count: ozsoft-consulting.com 83 .com ITConductor. com ITConductor.com 84 . System Monitoring: Demo • Click on a System’s Alert count: • Alert Details: Shows Metric Rating ozsoft-consulting. com ITConductor. System Monitoring: Demo • Metric Monitoring: ozsoft-consulting.com 85 . you get automated aggregation of alerts. knowledge. upgrade. connectivity. components. LMDB. Host agents and connectivity • Managed Systems Configuration: discover agents. which involves: • Planning.2 System Monitoring is a project. assign products • System Monitoring: scope of systems and report • Search Engine: TREX installation is needed for non-HANA databases • Solman is a mission-critical enterprise application with full IT landscape which requires dedicated management of: systems. In return. For historical metrics. and team. patches • System Preparation including BW store. budget.com 86 . Solman 7. metrics and chart. time. you need to configure BI ozsoft-consulting. software. Life Cycle Managers • Basic Configuration: Solution Manager Diagnostics Agents. Introscope. resources (Solman as well as the managed infrastructure) • Installation of Solution Manager. not a simple task. SLD.com ITConductor.2 System Monitoring: Summary • Solution Manager 7. com 87 .com ITConductor. 20 hours Managed System Configuration).2 System Monitoring: Comparison • In this example we set up Solman to monitor an S/4HANA environment. Solman 7.com/blog/cloud- based-sap-monitoring-of-s4hana-on-azure ozsoft-consulting. total effort (60 hours – Solman Installation & Setup. IT-Conductor took less than 1 hour to configure and monitor S/4HANA using cloud-based SaaS platform.itconductor. no infrastructure required: https://www. The effort excluded infrastructure cost and setup. and without TREX search engine • In comparison. 0 https://www.itconductor.com/blog/how-to-monitor-sap-solution- manager • Get the latest SAP Monitoring Comparison v2. IT-Conductor can be used in this scenario ‘How to Monitor SAP Solution Manager’: https://www. SAP Monitoring as a Service • Every customer’s Solution Manager should be monitored as a business critical environment for optimal availability and performance.com 88 .itconductor.com ITConductor.com/blog/sap-monitoring-tools-video- overview • What if you just need help with SAP Basis and/or Solution Manager? Engage OZSOFT’s 20+ years experienced global SAP Basis services ozsoft-consulting. Software Solutions Full suite of SAP systems monitoring solutions for Microsoft Systems Center Operations Manager (SCOM) focus on Availability. using IT-Conductor for Cloud-based monitoring & automation. SAP BusinessObjects architected for secure. • Cloud Excellence Operations: IT Process Automation increases operating efficiencies. scalable. Perform & Perfect IT • SAP Implementation: SAP Netweaver. as well as time/cost efficiencies. CA 95014.com Company > Delivering IT. and Performance Management: • SAP Management Pack • HANA Management Pack • BusinessObjects Management Pack • ASE Management Pack .com 20660 Stevens Creek Blvd. USA North America Toll-free: +1 (888) 876-2482 http://www. • SAP OS/DB Migration: Certified migrations using best practices to mitigate risks and minimize downtime.ozsoft-consulting. Practice.About OZSOFT OZSOFT CONSULTING HEADQUARTER Email: info@ozsoft-consulting. high-performance and availability. with Peace of Mind! Specializing in SAP since 1996 Services SAP on Cloud (AWS & Azure) Cloud-based Managed Services Plan. Alerting. Combined Upgrade and Migration support.. and agility best suited for cloud services. Suite 261 Worldwide: +1 (408) 416-2482 Cupertino. We provide partial to fully managed services while your SAP environment runs at AWS. SAP HANA. IT-Conductor does not provide legal advice or services and its research should not be construed or used as such. Inc. Although IT-Conductor may include a discussion of related legal issues. > Monitor SAP WITHOUT Installation! The power of IT-Conductor lies in it's ease of access through a cloud platform to simply hook up to your environment via a secured connection and start agentlessly monitor and manage the applications. and/or its affiliates. hosts and related infrastructure components. It's all about the integrated ability to collect vast amount of application and supporting infrastructure instrumentation data into standardized and time-synchronized intelligence that can be action upon. .itconductor. Templates make application discovery fast and easy to go from monitoring to managing in minutes! ___________________________________________________________________________________________________________________________________________ © 2017 IT-Conductor. The big idea is to enable customers to "Stop Guessing. completeness or adequacy of such information and shall have no liability for errors.. and Start Managing" their enterprise IT application environment. This publication may not be reproduced or distributed in any form without IT-Conductor’s prior written permission.com. your use of it is subject to the Terms of Service and Copyright and Trademarks posted on itconductor. This publication consists of the opinions of IT-Conductor organization and should not be construed as statements of fact. omissions or inadequacies in such information. IT-Conductor is a trademark of IT-Conductor.com 20660 Stevens Creek Blvd. IT-Conductor was officially founded in 2014 after more than 10 years of turning a big idea of automating IT into a practical solution. Inc. Start Managing! IT-Conductor is the AMMO you need to: • Automate • Monitor • Manage & • Optimize your SAP Performance & Operations including Performance Testing/Tuning as a Service. USA North America Toll-free: +1 (888) 666-2899 http://www. or its affiliates. All rights reserved. If you are authorized to access this publication. Suite 261 Worldwide: +1 (408) 416-2565 Cupertino. IT-Conductor disclaims all warranties as to the accuracy. databases. CA 95014.About IT-Conductor IT-CONDUCTOR HEADQUARTER Email: info@itconductor. The opinions expressed herein are subject to change without notice. The information contained in this publication has been obtained from sources believed to be reliable or from IT-Conductor’s own experience and research.com Company > Stop Guessing. Let itconductor.linkedin.com ITConductor.com 91 .com/company/it-conductor ozsoft-consulting.com • Any Questions? @itconductor • Contact Info: [email protected] • Follow us: https://www.