Skip to end of metadata
Go to start of metadata

Wiki for non-SAP Monitoring with SAP Solution Manager 7.2

This is the central entry point of the non-SAP monitoring Wiki. SAP Solution Manager 7.2 for sure can be used to monitor SAP system. But it is not restricted to that and you can also monitor non-SAP systems. Once you have some experience with the monitoring of SAP system, it is not a big deal to set it up also for non-SAP systems. The intention of this wiki is to guide you through the non-SAP monitoring implementation process and to provide some how-to guides with real examples.

Monitoring non-SAP Systems with SAP Solution Manager 7.2

Why to do this?

In the ideal world the customer has a homogeneous SAP landscape and monitors everything with SAP Solution Manager. Unfortunately the real world is different and most customers have not only SAP systems but also non-SAP system. Let's take following banking scenario example to illustrate this.

The frontend applications are partially from SAP and most of the backend systems are from SAP. To exchange data between the frontend applications and the backend systems, there is a central non-SAP integration layer system in between. From a business process point of view, a process might start and end in an SAP system, but the non-SAP integration layer system is crucial for the whole process, so it definitely needs to be monitored.

You might monitor this non-SAP system with a third party monitoring but do you really want to:

  • operate several monitoring solutions?
  • maintain and train employees in several tools?

In the end, this is always an individual decision. If SAP Solution Manager is already established as a monitoring tool, and if the footprint of non-SAP applications is rather small, non-SAP monitoring in SAP Solution Manager may be a good solution.

Benefits 

Non-SAP systems can also be monitored with SAP Solution Manager. This provides you several benefits:

  • You have a single point of truth for the overall system health.
  • You need to operate only one monitoring solution.
  • The operation team only needs to learn one monitoring tool.
  • There are no license costs when using SAP Solution Manager for non-SAP monitoring (except for CA Introscope in case this is needed).
  • Seamless integration into the SAP Solution Manager System Monitoring with same look and feel as well as functionality (metric history drill down, notifications, incidents,...).

non-SAP Monitoring Implementation Process

Due to its comprehensive functionality the End-to-End Monitoring and Alerting Infrastructure (MAI) of SAP Solution Manager has reached a level of quite some complexity. Without a deep knowledge of the infrastructure you might struggle to implement monitoring for non-SAP systems. But with a clear plan and guidance the implementation is not difficult. In any case, a good understanding of the non-SAP application and its technical architecture is essential to be able to analyze the feasibility of implementing non-SAP monitoring requirements. A general guidance including some information about the implementation process is presented here.

 

Prerequisites

Before starting with the monitoring implementation for a non-SAP system, there are several prerequisites which have to be fulfilled. Otherwise you do not need to proceed with the following section because sooner or later you will run into problems.

  •  In the configuration of SAP Solution Manager (to be accessed via the SAP Fiori Launchpad, tile "Configuration - All Scenarios" in the tile group "SAP Solution Manager Configuration", or alternatively via transaction SOLMAN_SETUP)  the "System Preparation", "Infrastructure Preparation" and "Basic Configuration" need to be successfully executed. More information can be found here: SAP Solution Manager Setup
  • The "Managed System Configuration" for the Solution Manager System itself needs to be successfully executed.
  • The "System Monitoring" setup for the Solution Manager System itself needs to be successfully executed.
  • You should already have some system monitoring experience.
  • You should have a technical understanding of the Monitoring and Alerting Infrastructure (MAI).

Overview 

The following diagram provides an overview of the different activities to be done. By following this process you can setup monitoring for a non-SAP system. The sections below provide details on the individual steps, and in some cases there is a how-to guide available showing a real example.

Landscape Preparation

In addition to the general prerequisites on top there are some system specific preparations which need to be done.

Installation of Diagnostics Agent and SAP Host Agent

Most of the metrics in the non-SAP environment are collected via the Diagnostics Agent and the SAP Host Agent. Please refer to SAP Notes 1833501 and 1858920 for the installation of the Diagnostics Agent.

In case of a high available non-SAP system it might be necessary to setup the Diagnostics Agent as an "on-the-fly" agent. Please refer to "Diagnostics Agent and HA Support" wiki page for details.

Installation of Introscope Bytecode Agent (OPTIONAL)

Most of the monitoring metrics for non-SAP systems can be collected via Diagnostics Agent and SAP Host Agent. For the performance monitoring of Java and .NET based systems we rely on CA Introscope metrics. SAP Solution Manager includes a so called "Right to View" license which can be used for all applications sold by SAP. To use CA Introscope for non-SAP systems requires a "SAP Extended Diagnostics by CA" (SED) license which can be bought from SAP. Below a comparison of the "Right to View" versus the "SAP Extended Diagnostics by CA" license:

Once you have the SED you will get the full version of CA Introscope with unlocked agents and additional instrumentation for common third party middleware products. It also includes Introscope agent installation guides.

In case you already have a SED license please refer to SAP note 1280961.  

Technical System Creation

One feature of the Monitoring and Alerting Infrastructure (MAI) of Solution Manager 7.2 is its landscape awareness. This means Solution Manager knows the system landscape and maps the monitored metrics to the landscape objects, which are the so called Managed Objects (MO). The following picture provides an overview of the available MO in system monitoring:

For mainstream SAP systems, their landscape information is normally reported automatically (via various SLD data suppliers → SLD → LMDB) to SAP Solution Manager. For non-SAP systems, there is normally no automatic SLD data supplier and the landscape information needs to be maintained manually in SAP Solution Manager. This is a quite simple process and is described in the how-to guide "Creating Unspecific Cluster System".

Managed System Configuration

After the non-SAP system was created in SAP Solution Manager the Managed System Configuration needs to be done for it. The main purpose of the Managed System Configuration for non-SAP systems is the following:

  • assigning the Diagnostics Agent(s) to the non-SAP system
  • assigning the Introscope Enterprise Manager to be used for the non-SAP system
  • setup of the system related extractors and the Introscope Host Adapter (part of the Diagnostics Agent)

Like for SAP systems you just have to follow the Managed System Configuration guided procedure.

Monitoring Configuration

Up to now we just prepared everything for the real monitoring configuration which is explained in this section.

First you need to know what you want to monitor in your non-SAP system. There are four categories of metrics:

  • Availability
  • Exceptions
  • Performance 
  • Configuration

Typically, only the first three categories are used for monitoring of non-SAP systems.

Once you know what you want to monitor you need to configure the metrics and alerts in the monitoring templates. On system and instance level there are so called "generic product version" templates which are empty templates and we use them for the non-SAP purpose. On host and database level the existing templates can be used. Please note that all changes have to be maintained in custom templates as the templates delivered by SAP are not changeable. For more information about template maintenance, see here.

Finally the templates will be assigned to the non-SAP system and monitoring will be activated. More information about the configuration process for System Monitoring can be found here.

System and Instance Level Metrics

System and instance level metrics are the non-SAP system specific metrics. A good starting point is always the availability of the system and some exception related metrics. Finally also performance metrics can be configured but as soon as CA Introscope is required a "SAP Extended Diagnostics by CA" license is mandatory. In the following sub-sections some examples for the different categories are provided.

Please note that you should be familiar with the creation of custom metrics and alerts in general. See the relevant sections in the description of the System Monitoring configuration process here.

Availability Examples
  • URL Monitoring: You can check the availability of an URL based on the http status code. There are several ways to achieve this. One is the Advanced Monitoring configuration. Another one would be to create a custom metric with the data collector SAP Ping Http Generic. This is also possible using custom parameters.
  • OS Process Monitoring: You can check the existence of OS processes based on a process name pattern. An example for this is described in the how-to guide "Monitoring OS processes with MAI".
  • OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The Diagnostics Agent regularly executes a custom OS script and the result of the script can be evaluated. So this is not restricted to availability only. You can also use this for exception and performance metrics. It only depends on a custom script. How to use custom scripts is described here.
 Exception Examples
  • Log File Monitoring: You can do a text pattern search in log files, check for specific file attributes or monitor the Windows event log. Details can be found here.
  • OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The Diagnostics Agent regularly executes a custom OS script and the result of the script can be evaluated. By this you can also report exceptions. How to use custom scripts is described here.
 Performance Examples
  • Introscope Monitoring: As mentioned above you need to have a "SAP Extended Diagnostics by CA" license in case you want to use Introscope for your non-SAP system. Once Introscope is in place and you see the metrics you want to monitor in the Introscope Enterprise Manager they can be included into the monitoring in SAP Solution Manager. An example for this is described in the how-to guide "Custom Introscope Metrics". 
  • OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The OS script monitoring data provider gives you full flexibility. The Diagnostics Agent regularly executes a custom OS script and the result of the script can be evaluated. By this you can also report exceptions. How to use custom scripts is described here.

Host Level Metrics

Host level metrics can be monitored the same way as for SAP systems using the host templates for the supported operating systems.

Database Level Metrics

For the database level metrics you can also use the standard SAP database templates. But there is one additional prerequisite. The Monitoring and Alerting Infrastructure gets most of the database metrics from the DBA Cockpit of the Solution Manager. This means that the non-SAP database needs to be connected to the DBA Cockpit. In order to connect the database, depending on the database, some scripts need to be executed on the non-SAP database which create some monitoring related tables and configures the data collection into these tables. For further details check the relevant SAP notes for the DBA Cockpit connection.

Custom Reporting

Depending on the metric configuration, all metrics measured in the Monitoring and Alerting Infrastructure of Solution Manager 7.1 can be written into BW of Solution Manager. Hence a reporting can be built on top of this data. How to build custom reporting is not part of this wiki.

non-SAP Monitoring How-to Guides 

In case you are familiar with the implementation process check the non-SAP Monitoring How-to Guides page to get a quick overview of the available how-to guides. "Watch" this page to be informed once a new guide is available.


 

 

 

 

  • No labels