Anda di halaman 1dari 91

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
Plan your Solution Manager 7.2 SP5 with Maintenance Planner
• JAVA INSTANCE:
• log into Maintenance Planner and start by clicking Plan a New System. Click again on Plan.

• To generate stack file for JAVA we need to start from beginning by selecting System Type and
entering desired SID. Push the files to your download basket and download Stack XML file.

• After downloading the files you are ready to install Solution Manager 7.2 using your stack file.

ozsoft-consulting.com ITConductor.com 4
SAP Solution Manager 7.2 SP 5: ABAP Stack Installation
• Before we start what you need is to download source of SAP Solution Manager 7.2 from
https://launchpad.support.sap.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.sap.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, instead it will start a web application on port 4237 so you
can log into it with HTTPS protocol. The URL it is random generated and it will change every time you execute the
sapinst binary. In the Welcome screen, you get installation options filtered according to your stack XML file:

ozsoft-consulting.com ITConductor.com 5
SAP Solution Manager 7.2 SP 5: ABAP Stack Installation
• You can choose to automatically start the SUM after the installation is complete:

• During the upgrade, you must install the SAP notes:

Complete process. Once you complete ABAP support Pack


Stack 5 installation now its time to install JAVA stack.

ozsoft-consulting.com ITConductor.com 6
SAP Solution Manager 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. Complete process.

ozsoft-consulting.com ITConductor.com 7
Solution Manager 7.2 SP 5: Post-Installation Steps
• After the successful completion of the installation, follow the instructions provided in Post-Installation section of
the installation guide to complete the configuration. For more information, see
https://service.sap.com/instguides.
• SAP systems based on SAP NetWeaver 7.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.

• Run SGEN for your system

ozsoft-consulting.com ITConductor.com 8
Solution Manager 7.2 SP 5: recommended corrections
• Set or adjust the following profile parameters, with the specified recommended values. (SAP Note 2048519 - Profile
parameters for SAP Solution Manager 7.2)
• Ref: SAP Note 2433454 - Solution Manager
7.2 SP Stack 05: recommended corrections.
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.com ITConductor.com 9
Solution Manager 7.2 SP 5: WILY Introscope 10.1 Installation
• Ref: SAP Note 797147 - Introscope Installation for SAP Customers and 2285189 - Introscope 10.1 Release Notes for
changes and open issues
• Download installation files from SAP Service Marketplace.
• Download the third party external component package files (eula.txt and osgiPackages.v10.1.0.15.unix.tar, 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. In particular, on Unix operating systems do not use the root account to launch the installer. A common
best practice is to use the sidadm user of the Solution Manager installation to install and run the Enterprise
Manager.
• 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. Subdirectory bin of
the Enterprise Manager installation. Run ./EMCtrl.sh start
• Check http://fqdn:8081/sapdashboard/
• Users and its password:
• Admin – Admin89
• Guest – guest12

ozsoft-consulting.com ITConductor.com 10
Solution Manager 7.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.
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.com ITConductor.com 11
Solution Manager 7.2 SP 5: Install the Diagnostics Agent 7.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 - How to connect
Diagnostics Agent to Solution Manager 7.2
system

• Enter the parameters of the connection to a central System


Landscape Directory (SLD).

ozsoft-consulting.com ITConductor.com 12
Solution Manager 7.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.
• 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, and
001 for the Source Client User Masters.
• Perform this on newly installed systems and before running SOLMAN_SETUP transaction.

ozsoft-consulting.com ITConductor.com 13
Solution Manager 7.2 SP 5: SAP Note
• Pay attention to the following notes:
• 1595736 - Solution Manager: Overview on Release Information Notes
• 1680045 - Release Note for Software Provisioning Manager 1.0 (recommended: SP20)
• 2371752 - Central Note - Software Update Manager 1.0 SP20 [lmt_006]
• 2433454 - Solution Manager 7.2 SP Stack 05: recommended corrections
• 2385361 - How to connect Diagnostics Agent to Solution Manager 7.2 system
• 1833501 - Diagnostics Agent - Installer Versions
• 669669 - Update of SAP System Component Repository in SLD
• 2000132 - Configuring RFC connections to the SAPNet R/3 front end (OSS) correctly
• 797147 - Introscope Installation for SAP Customers
• 2174416 - Creation and activation of users for the Support Hub Communication
• 2359837 - "Set Up Connections to SAP" and "Support Hub Connectivity" in Solution Manager 7.2
• 2239513 - Solman_setup reports error "The configuration of RFC SAPOSS is not correct", even though SAPOSS
RFC is correctly configured

ozsoft-consulting.com ITConductor.com 14
Next – Solution Manager 7.2 SP 5: Configuration Basics
• This is the end of the installation phases of Solution Manager 7.2
SP 5
• “Solution Manager 7.2 SP 5: Monitoring Base Configuration” - is
the next section that we’ll examine.

ozsoft-consulting.com ITConductor.com 15
SAP Solution Manager 7.2 SP5

Part 2 of 4
Monitoring Base Configuration
By OZSoft Consulting for ITConductor.com
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. The first
should have no authorizations since, it could be misused. The second S-user is needed to perform the
synchronization of the service messages and system data, or to request licenses.
• Starting with Solution Manager 7.2, SAP provides a new communication channel between SAP
Solution Manager and SAP backbone system. A technical S-User is required and maintained via the
Support Portal Applications:
https://apps.support.sap.com/technical-user
This technical S-User can only be created and then activated, when being logged as a Super
Administrator.(See SAP Note 2174416 - Creation and activation of users for the Support Hub Communication )

ozsoft-consulting.com ITConductor.com 17
Mandatory Configuration
• To start with the SAP Solution Manager Configuration call transaction SOLMAN_SETUP from your productive client.
• When you start the SOLMAN_SETUP for the first time, you will be asked to activate (Web Dynpro) services, in order
to be able display this wizard in your browser screen. Confirm the popup.

• 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.com ITConductor.com 18
Mandatory Configuration: Define System Role

• Define the role and purpose of the SAP Solution Manager system, 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, please make sure you log off and Login to SAP Solution Manager with
Solman_Admin user to continue with next steps

ozsoft-consulting.com ITConductor.com 19
System Preparation: Check Prerequisites

• In this step, you check the aspects of your SAP Solution Manager installation that are relevant for configuration.
• To perform the listed manual checks, follow the documentation associated to each activity

• To perform the listed automatic check, execute the activities and check the status.

ozsoft-consulting.com ITConductor.com 20
System Preparation: Set Up Connection to SAP

• In the sub-steps of this step, you setup the connections to the SAP backbones.
• RFC Connectivity
• Support Hub Connectivity

• In this step, you ensure that SAP Solution Manager can connect to SAP Support Portal.
• Important: Every RFC connection to SAP Support Portal must use the load balancing and the related logon group.

ozsoft-consulting.com ITConductor.com 21
System Preparation: Support Hub Connectivity

• In this step, you configure the connections to the support hub channel.
• SAP introduces a new data communication channel, with SAP Solution Manager 7.2. Over time all functionalities
(including SNOTE), will migrate to use this channel.

ozsoft-consulting.com ITConductor.com 22
System Preparation: Apply Recent Corrections

• In the sub-steps of this step, your apply the latest corrections for ABAP and Java, this includes:
• Corrections for SAP Notes
• Essential ABAP Corrections
• Java Corrections
• First you apply the latest available corrections for the Note Assistant. Apply SAP note in your system – 1668882 -
Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751

ozsoft-consulting.com ITConductor.com 23
System Preparation: Apply Recent Corrections

• In the sub-step, you apply the latest essential corrections applicable to you SAP Solution Manager ABAP system.
Apply SAP note : 2353022 - SAP Solution Manager 7.2 SP05 - basic functions

• The implementation of the SAP Solution Manager Central Corrections Note, is dragging a set of other SAP notes,
containing essential corrections, as recommended by Sap.

ozsoft-consulting.com ITConductor.com 24
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. If you are unsure, check the
current support packages of the software components in your system.

ozsoft-consulting.com ITConductor.com 25
System Preparation: Maintain Technical Users

• In this step you have to create or update so called technical users, and assign the appropriate roles. During this
process, the system automatically creates users, copy specific SAP delivered roles, generate the associated role
profiles, and finally assigns the roles/profiles to the users.
• Use the Create all Users button
• Or select one by one the users you create, or for which you want to update authorization.

ozsoft-consulting.com ITConductor.com 26
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.com ITConductor.com 27
Infrastructure Preparation: Set Up Landscape Management

• In the sub-steps of this step, you describe and enable the Landscape Management, as
required by SAP Solution Manager
• First, define the connections towards all System Landscape Directory that contain data
applicable to this Solution Manager system.
• Then, specify and trigger the synchronization of the landscape Management Database, from
the relevant SLD. With the synchronization LMDB will import any up-to-date CR content, and
as well the Technical System description + CIM model.
• Finally, double check the correctness of the SAP Solution Manager ABAP and Java Technical
System description in the LMDB

ozsoft-consulting.com ITConductor.com 28
Infrastructure Preparation: SLD Connections

• Define the connections to any System Landscape Directory (SLD), being relevant for this SAP Solution Manager
• You need at least one connections with SLD role: Source for LMDB

• Choose Create New Connections, or Assign Existing HTTP


Destination from SM59.

ozsoft-consulting.com ITConductor.com 29
Infrastructure Preparation: LMDB Synchronization

• CIM model, SAP software catalog (SAP CR content), and technical system descriptions from the system landscape
is collected in the SLD (source namespace “sld/active”). It must be synchronized with the LMDB (target
namespace “active”).
• The activation starts an initial, full, automatic synchronization to import all SLD information to the LMDB, which
takes several hours.

• Choose an object server name according to the following rules:


• All SLD and LMDB systems in your landscape must have different names.
• Use a prefix reserved at SAP, if available. For more information,
see SAP Note 935245.
• Connecting to Several SLDs. The unique-path-principle for data must be
fulfilled when the LMDB is synchronized with more than one SLD system.
System landscape descriptions are always imported from all connected SLDs.
Therefore, they must not overlap. This can only be ensured if SLD systems
connected to the LMDB run in separated landscapes.

ozsoft-consulting.com ITConductor.com 30
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
Infrastructure Preparation: Set Up Java Connectivity

• In the sub-steps of this step, you set up mainly the Java connectivity by:
• Defining any Load Balancer / SAP Web Dispatcher, or the hostnames and HTTP/HTTPS ports of the SAP Solution Manager ABAP
and Java system.
• Enable the connectivity with the SAP Solution Manager Java System
• Enable the authentication of the Diagnostic Agents in the SAP Solution Manager Java System.

• In this sub-step you define, hostname and port numbers to be used to establish HTTP connections. 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. You need to temporarily
provide this information in the pop-up.

ozsoft-consulting.com ITConductor.com 32
Infrastructure Preparation: Enable Connectivity

• In this step, you check and set up the SAP Solution Manager Java system to support, for example, Web Service calls,
Java Connector RFC calls, and single sign-on for Web User Interfaces.
• 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.

ozsoft-consulting.com ITConductor.com 33
Infrastructure Preparation: Diagnostic Agent Authentication

• In this step, you configure the connections between the Diagnostics Agents and SAP Solution Manager.

• In addition, you provide a root certificate so that Diagnostic Agents can be authenticated when connecting to SAP
Solution Manager.

ozsoft-consulting.com ITConductor.com 34
Infrastructure Preparation: Set Up SAP BW

• In this section, you set up SAP Business Warehouse to be able to use it for reporting.
• Confirming to use the SAP BW part of the SAP Solution Manager System
• Maintain Users related to SAP BW activities.
• Enable the SAP BW, as foundation for SAP Solution Manager.

• This SAP Solution Manager system includes a dedicated SAP Business Information Warehouse to store, aggregate
and report collected data. In this step, you set up SAP Business Information Warehouse (BW).
• SAP recommends that you use the standard SAP Solution Manager BW environment, in the current client of the
SAP Solution Manager system. You cannot make changes later without help from SAP, as BW data is stored with
client and system-specific keys.

ozsoft-consulting.com ITConductor.com 35
Infrastructure Preparation: Maintain Users

• In this step, you create or update dialog, technical users (of type System), or BW users. You also assign roles to
them, depending on the scenario and step:
• In the System Preparation scenario, Maintain Technical Users step, you create technical users (of type System).
• In the Infrastructure Preparation scenario -> Set Up BW step -> Maintain Users step, you create BW users.
• In the Basic Configuration scenario, Create Basic Dialog Users step, you create dialog users.

• In this step, you enable the selected SAP BW, by executing the following activities:

• Use RSTCO_ADMIN transaction in the BW client, to make sure the source system activation finished successfully.
• The BI_TCO_ACTIVATION job usually requires around 15 min. in a new installation

ozsoft-consulting.com ITConductor.com 36
Infrastructure Preparation: Define CA Introscope

• In this step, you discover already installed CA Introscope Enterprise Managers (ISEM).
• Prerequisites:
• Diagnostics Agents are installed on all hosts where Enterprise Managers are operated (stand-alone, Manager of Managers, or
collectors). For more information, see SAP Note 1365123.
• The OS user that executes the Diagnostics Agent has read and write permissions for the CA Introscope installation directory
and files.

ozsoft-consulting.com ITConductor.com 37
Infrastructure Preparation: Set Up E-Mail Communication

• In this step, you set up the infrastructure that enables SAP Solution Manager to send notifications using e-mail
and text messaging (short message service, SMS), and enable e-mail encryption, manually.

• As a consequence the so called SAPConnect infrastructure is set up and the “send job” is automatically
scheduled.
• To send out notifications, 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. Since SAP_BASIS 7.31
SP2, an integrated encryption solution is available. See SAP Note 1637415.
• For more information about secure e-mail encryption, see SAP Note 149926.

ozsoft-consulting.com ITConductor.com 38
Infrastructure Preparation: Configure CRM Basis

• In this step, you configure several infrastructure components for SAP Customer Relationship Management (CRM)
that are used by the mandatory scenarios in SAP Solution Manager.
• Typically, you perform first the manual activity

• Finally, run the remaining automatic activities, by choosing Execute All.

ozsoft-consulting.com ITConductor.com 39
Infrastructure Preparation: Enable Gateway Services

• In this step, you activate SAP Gateway services (OData services), which are required to enable the SAP Solution
Manager Fiori Launchpad, SAP Fiori apps, and mobile applications. You need to activate the SAP Gateway
services for each of your scenarios. 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. If
you haven't activated them, the status of this step is red.
You find these services in this step, under Cross Scenario Configuration, in the List of Gateway Services.

ozsoft-consulting.com ITConductor.com 40
Infrastructure Preparation: 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, and the status of each step.
• After the Infrastructure Preparation you have to perform the scenario Basic Configuration

ozsoft-consulting.com ITConductor.com 41
Basic Configuration: Configure Basic Functions

• In this step, 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, EWA, Service Delivery, Default Self-Monitoring)
• Review list of import and customization
• Activation of most WebDynpro and further SAP Solution Manager Launchpad services

ozsoft-consulting.com ITConductor.com 42
Basic Configuration: Schedule Jobs

• In this step, you schedule important jobs needed by SAP Solution Manager.
• In a production system, all recommended SAP Solution Manager jobs are scheduled, including those receiving or
sending data to SAP Support Portal.
• In other systems (for development, testing etc.), you usually decide which of the SAP Solution Manager jobs that
receive or send data to SAP Support Portal are to be scheduled.

ozsoft-consulting.com ITConductor.com 43
Basic Configuration: Configure Manually

• In this step you perform manual activities in SAP Solution Manager, 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 schedule a periodic background job that creates and
updates business partners for users in the SAP Solution Manager system.
• Configuration for Rapid Content Delivery. You use this activity to configure
the Rapid Content Delivery application in SAP Solution Manager to
download content packages automatically.

• 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.com ITConductor.com 44
Basic Configuration: Configure Manually

• Delete Sessions with Corresponding Documents and Download Data. This activity helps you to reduce data
volume in SAP Solution Manager.
• Service Content Update Configuration. The Service Content Update offers a
superior method to keep the EarlyWatch Alert up-to-date. Instead of applying
ST-SER Support Packages you activate once the Service Content Update.
The SAP Solution Manager will then always retrieve the latest corrections for
the EarlyWatch Alert from SAP Service Marketplace. A prerequisite is a RFC
connection from the SAP Solution Manager to SAP Service Marketplace.
(The Service Content Updated is executed in the
job SM:SERVICE CONTENT UPDATE)

ozsoft-consulting.com ITConductor.com 45
Basic Configuration: Configure Manually

• Enable Remote HTTP Connection to Solution Manager for SAP Support. In this activity, you enable a remote HTTP
connection from SAP to the SAP Solution Manager system.
• Enable Remote R/3 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.
• SAP Solution Manager Application Log Cleanup. In this activity, you schedule the reorganization or cleanup of SAP
Solution Manager application logs. 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. This activity invalidates all server-
side caches in SAP NetWeaver user interface services.

ozsoft-consulting.com ITConductor.com 46
Basic Configuration: Create Basic Dialog Users

• In this step, you create or update dialog, technical users (of type System), or BW users.
• In a production system, you cannot create or update any user roles. These changes must be transported.
• In other systems (for development, testing, and so on), you usually create or update the user roles directly in the
system. (If the PFCG transport recording is enabled, the modifications are added to transport requests.
Otherwise, you need to add the modified roles manually to customizing transport requests.)

ozsoft-consulting.com ITConductor.com 47
Basic 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, and the status of each step.
• After the Basic Configuration you typically now start the execution of the Managed System Configuration.
• Also you should consider doing the customization of the SAP Solution Manager Launchpad (see link).

ozsoft-consulting.com ITConductor.com 48
Solution Manager 7.2 SP 5: SAP Note
• 2174416 - Creation and activation of users for the Support Hub Communication
• 1668882 - Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751
• 2353022 - SAP Solution Manager 7.2 SP05 - basic functions
• 935245 - Importance of SLD/LMDB "Object Server" parameter
• 1637415 - S/MIME integration in SAPconnect
• 149926 - Secure e-mail: Encryption, digital signature
• 2383652 - Configure NetWeaver Download Service for Rapid Content Delivery
• 1911102 - Solution Manager application logs reorganization

ozsoft-consulting.com ITConductor.com 49
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
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,
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 - How to connect
Diagnostics Agent to Solution Manager 7.2
system

• Enter the parameters of the connection to a central System


Landscape Directory (SLD).

ozsoft-consulting.com ITConductor.com 53
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
Managed System Configuration: Check Prerequisites

• The Software Prerequisites activity now relies on the RTCCTOOL running on the SAP Solution Manager system, for
checking the ST-A/PI and ST-PI versions
• Execute automatic activities first.

• Create HANA Database user.


• Note: We do not want to change this user password so make sure you run script below:
• ALTER USER MONI DISABLE PASSWORD LIFETIME;

ozsoft-consulting.com ITConductor.com 57
Managed System Configuration: Maintain RFCs

• In this step you create or delete RFC connections to the clients in managed systems, for example, client 000. For
each managed system, you should create at least a READ RFC connection to the production client.

ozsoft-consulting.com ITConductor.com 58
Managed System Configuration: Assign Diagnostics Agent

• In this step, you assign Diagnostics Agents to each server (host) on which managed systems are running.
• The “SLD Agent Candidate Management” is no longer accessible from the Managed System Configuration UIs.
• The “Auto Assign” option should be used to assign a Diagnostics Agent to a system. If auto assignments does not
work, the “Agent Admin” UI can be used for troubleshooting, before retrying “Auto Assign”

ozsoft-consulting.com ITConductor.com 59
Managed System Configuration: Enter System Parameters

• In this step, you specify the system parameters required to configure the managed system, which depend on the
type of the managed system, for example, ABAP, Java, or database systems.

ozsoft-consulting.com ITConductor.com 60
Managed System Configuration: Enter Landscape Parameters

• In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-
consuming error-handling.

ozsoft-consulting.com ITConductor.com 61
Managed System Configuration: Maintain Users

• In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-
consuming error-handling.

ozsoft-consulting.com ITConductor.com 62
Managed System Configuration: Finalize Configuration

• In this step, 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 ITConductor.com 63
Managed System Configuration: Check Configuration

• In this step, you automatically check whether the system is configured correctly, and you update the statuses in the
overview of the Managed Systems Configuration.

ozsoft-consulting.com ITConductor.com 64
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, and the status of each step.
• After this scenario is finished, you can proceed by navigating to the next scenario or by choosing a link from the
What do you want to do now? area.

ozsoft-consulting.com ITConductor.com 65
Next – Solution Manager 7.2 SP 5: System Monitoring
• This is the end of the Managed System Configuration phases of
Solution Manager 7.2 SP 5
• “Solution Manager 7.2 SP 5: System Monitoring” - is the next
section that we’ll examine that will actually monitor the
S/4HANA environment we added.

ozsoft-consulting.com ITConductor.com 66
SAP Solution Manager 7.2 SP5

Part 4 of 4
System Monitoring
By OZSoft Consulting for ITConductor.com
Solution Manager 7.2 SP 5: System Monitoring
• The Setup (Part 1), Preparation & Configuration (Part 2), and
Managed Systems Configuration (Part 3) must have been
completed successfully. If not, visit these other sections:
• Solution Manager 7.2 SAP Monitoring - Part 1 (Setup)
• Solution Manager 7.2 SAP Monitoring - Part 2 (Configuration)
• Solution Manager 7.2 SAP Monitoring - Part 3 (Managed
System Config)
• In this Part 4: We will assign the application scenario and final steps
for System Monitoring

ozsoft-consulting.com ITConductor.com 68
Solution Manager 7.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. System Monitoring includes
technical systems, DBMS and hosts.

ozsoft-consulting.com ITConductor.com 69
System Monitoring: Configure Infrastructure

• In this step, you configure the monitoring infrastructure.

• In this step, you use the automatic activities to check the prerequisites for the configuration of the System &
Application Monitoring infrastructure.

ozsoft-consulting.com ITConductor.com 70
System Monitoring: Configure Infrastructure

• In this step, you perform manual activities to configure the System and Application Monitoring infrastructure:
1. The activities are displayed in the Manual Activities table. To display the Documentation of the activities,
choose Display in the relevant row.
2. To perform the activity, choose the link in the column Navigation.
3. When you have performed the activity, change the Execution Status to Performed and choose Save.

ozsoft-consulting.com ITConductor.com 71
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
incidents (support messages) to be automatically created (in Solution Manager Support Desk) from Alerts. If you
choose Inactive, you can still create incidents manually from the alert inbox.
• Automatic Notification - 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, you can still create notifications from
the alert inbox.
• Third-Party Components - Choose Active for this dropdown list box on the Summary tab page, if you have
integrated one or more 3rd party tools to work with System & Application Monitoring.

ozsoft-consulting.com ITConductor.com 72
System Monitoring: Reporting-Settings

• In this step, the health check results of the BI-based reporting are displayed, so you can see whether the
preconditions for successfully activating the BI-based reporting are met. If no health check is finished with an
error, activate the BI content if you want to use BI-based reporting.

• If health check is finished with an error, see the SAP note 2483407 - "Cannot read the RFC destination from the BW
to the Solution Manager", error in Solution Manager 7.2

ozsoft-consulting.com ITConductor.com 73
System Monitoring: Housekeeping

• In the step "Housekeeping" you make settings for the BI and the Monitoring and Alerting Infrastructure related
housekeeping. 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 upper tray contains the settings for the BW 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. The lower tray contains the
housekeeping settings for the monitoring and alerting infrastructure. The alert store housekeeping settings
determine when an open alert is confirmed automatically and when a confirmed alert is deleted.

ozsoft-consulting.com ITConductor.com 74
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. 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. Work modes can be scheduled in the Technical Administration Workcenter under Work
Mode Management.

• As the alert consumer settings for notifications and incidents etc. also the work mode settings have the three
hierarchy levels "Global", "Template" and "Metric/Alert". Global settings are overwritten by template settings and
template settings are overwritten by metric/alert specific settings.

ozsoft-consulting.com ITConductor.com 75
System Monitoring: Update Content

• In the last step of the infrastructure configuration you update the monitoring content. The monitoring content
contains all templates that are delivered by SAP for System Monitoring and all other scenarios like PI Monitoring,
as well as data collector templates.
• The content needs to be updated after every support package implementation. It is recommended to implement
the latest version. If your monitoring is running fine, there is no need to update the content independent of the
support package implementation. If you have problems with a metric and the troubleshooting reveals that it has
an error in the definition of the content, a content update might help.

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

ozsoft-consulting.com ITConductor.com 76
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. The step is optional, you don't need to create the users to run
System Monitoring. However it might be useful to take the information provided here as template to build an
authorization concept for your Solution Manager.
• You can create two different levels of users. The L2 (Level 2) user is the more powerful user. Please check the
documentation in the column "Documentation" for the users for more information. To create all users with the
default names select the "Create all Users" button. Or create the users one by one.

ozsoft-consulting.com ITConductor.com 77
System Monitoring: Template Maintenance

• The content of System Monitoring is delivered in SAP templates which contain metrics, alerts and events used to
monitor managed objects. SAP delivers templates for a various kind of managed objects. The templates are groups
by managed object type, which can be a host, a database, a technical system or a technical instance.
• Templates are dependent on the product version of the managed object.
• A template can only be assigned if the correct product version is selected during the managed system setup of the
managed system.
• The delivered SAP templates already have meaningful settings; if you do not want to change these, you can skip
this step. If you want to make changes, we recommend that you make these changes in your own template. You
can create a template of this type by selecting the template on which you want to base your template, and
choosing the Create Custom Template button.

ozsoft-consulting.com ITConductor.com 78
System Monitoring: Define Scope

• In this step you select the managed object you want to configure for system monitoring. Without selecting a
managed object you cannot proceed to the next setup steps. You can either select technical systems, technical
scenarios, hosts, or databases.
• Before you can configure system monitoring for a managed object you have to finish the Managed System
Configuration for the object.

• Once you have selected all systems you want to set up, click the "Next" button. Make sure you are in Edit mode
when you click Next, otherwise no default templates will be assigned to the selected systems.
• In this step you can also remove monitoring from a managed object if necessary using the "Remove Monitoring"
button.

ozsoft-consulting.com ITConductor.com 79
System Monitoring: Setup Monitoring

• In this step monitoring templates will be assigned to the managed systems in scope.
• Each managed technical system consists of several managed objects of type technical instance, database and host.
• 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). For all managed objects in scope the assigned templates are
applied and activated. This is done in the background, so you can continue the configuration right away.

ozsoft-consulting.com ITConductor.com 80
System Monitoring: Complete

• The system monitoring setup is completed for the managed systems in scope.
• In this step the status of all previous system monitoring steps are displayed.

ozsoft-consulting.com ITConductor.com 81
System Monitoring: Demo
• Check System Monitoring in SOLMAN_WORKCENTER

• You can also access Solution Manager content from the Fiori Launchpad

ozsoft-consulting.com ITConductor.com 82
System Monitoring: Demo
• Click on a System’s:

• Click on a System’s Alert count:

ozsoft-consulting.com ITConductor.com 83
System Monitoring: Demo
• Click on a System’s Alert count:

• Alert Details: Shows Metric Rating

ozsoft-consulting.com ITConductor.com 84
System Monitoring: Demo
• Metric Monitoring:

ozsoft-consulting.com ITConductor.com 85
Solman 7.2 System Monitoring: Summary
• Solution Manager 7.2 System Monitoring is a project, not a simple
task, which involves:
• Planning, budget, time, resources (Solman as well as the managed
infrastructure)
• Installation of Solution Manager, upgrade, patches
• System Preparation including BW store, SLD, LMDB, Introscope, Life Cycle
Managers
• Basic Configuration: Solution Manager Diagnostics Agents, Host agents and
connectivity
• Managed Systems Configuration: discover agents, 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,
software, components, connectivity, knowledge, and team. In
return, you get automated aggregation of alerts, metrics and chart.
For historical metrics, you need to configure BI

ozsoft-consulting.com ITConductor.com 86
Solman 7.2 System Monitoring: Comparison
• In this example we set up Solman to monitor an S/4HANA
environment, total effort (60 hours – Solman Installation & Setup,
20 hours Managed System Configuration). The effort excluded
infrastructure cost and setup, and without TREX search engine

• In comparison, IT-Conductor took less than 1 hour to configure and


monitor S/4HANA using cloud-based SaaS platform, no
infrastructure required: https://www.itconductor.com/blog/cloud-
based-sap-monitoring-of-s4hana-on-azure

ozsoft-consulting.com ITConductor.com 87
SAP Monitoring as a Service
• Every customer’s Solution Manager should be monitored as a
business critical environment for optimal availability and
performance. IT-Conductor can be used in this scenario ‘How to
Monitor SAP Solution Manager’:
https://www.itconductor.com/blog/how-to-monitor-sap-solution-
manager
• Get the latest SAP Monitoring Comparison v2.0
https://www.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.com ITConductor.com 88
About OZSOFT
OZSOFT CONSULTING HEADQUARTER Email: info@ozsoft-consulting.com
20660 Stevens Creek Blvd., Suite 261 Worldwide: +1 (408) 416-2482
Cupertino, CA 95014. USA North America Toll-free: +1 (888) 876-2482
http://www.ozsoft-consulting.com

Company
> Delivering IT, with Peace of Mind! Specializing in SAP since 1996
Services
SAP on Cloud (AWS & Azure) Cloud-based Managed Services
Plan, Practice, Perform & Perfect IT
• SAP Implementation: SAP Netweaver, SAP HANA, SAP BusinessObjects architected for secure, scalable,
high-performance and availability, as well as time/cost efficiencies.
• SAP OS/DB Migration: Certified migrations using best practices to mitigate risks and minimize downtime.
Combined Upgrade and Migration support.
• Cloud Excellence Operations: IT Process Automation increases operating efficiencies, and agility best
suited for cloud services. We provide partial to fully managed services while your SAP environment runs
at AWS, using IT-Conductor for Cloud-based monitoring & automation.
Software Solutions
Full suite of SAP systems monitoring solutions for Microsoft Systems Center Operations Manager (SCOM) focus on
Availability, Alerting, and Performance Management:
• SAP Management Pack
• HANA Management Pack
• BusinessObjects Management Pack
• ASE Management Pack
About IT-Conductor
IT-CONDUCTOR HEADQUARTER Email: info@itconductor.com
20660 Stevens Creek Blvd., Suite 261 Worldwide: +1 (408) 416-2565
Cupertino, CA 95014. USA North America Toll-free: +1 (888) 666-2899
http://www.itconductor.com

Company
> Stop Guessing, 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.
IT-Conductor was officially founded in 2014 after more than 10 years of turning a big idea of automating IT into a practical
solution. The big idea is to enable customers to "Stop Guessing, and Start Managing" their enterprise IT application
environment. 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.

> 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, databases, hosts and related infrastructure
components. Templates make application discovery fast and easy to go from monitoring to managing in minutes!

___________________________________________________________________________________________________________________________________________
© 2017 IT-Conductor, Inc. and/or its affiliates. All rights reserved. IT-Conductor is a trademark of IT-Conductor, Inc. or its affiliates. This publication may
not be reproduced or distributed in any form without IT-Conductor’s prior written permission. If you are authorized to access this publication, your use
of it is subject to the Terms of Service and Copyright and Trademarks posted on itconductor.com. The information contained in this publication has
been obtained from sources believed to be reliable or from IT-Conductor’s own experience and research. IT-Conductor disclaims all warranties as to the
accuracy, completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This
publication consists of the opinions of IT-Conductor organization and should not be construed as statements of fact. The opinions expressed herein are
subject to change without notice. Although IT-Conductor may include a discussion of related legal issues, IT-Conductor does not provide legal advice or
services and its research should not be construed or used as such.
Let

itconductor.com
• Any Questions?
@itconductor
• Contact Info: info@itconductor.com
• Follow us: https://www.linkedin.com/company/it-conductor

ozsoft-consulting.com ITConductor.com 91