Skip to main content
Skip table of contents

Application Monitoring for SAP (Configure)

Features

Guideline to enable monitoring of SAP Enterprise, Web Server, Gateway and other SAP Application components. This assumes you have already deployed Germain UX - Engine for your SAP instance.

Our Recommendations: Synthetic / RPA Bots should be the first thing you ever implement for SAP (or any other application), in order to be alerted when major availability issues occur. Then everything should come next: SAP Web, Application, Gateway, Database can all be monitored with GermainUX. our 20-year experience with SAP is preconfigured in GermainUX, and any of that is easily customizable.

Configure

Essential health and Application Performance Monitoring for SAP occurs via Germain UX Engine.

Log on to Germain Workspace > left menu > Wizards > SAP

Import SAP Component Types

For new deployment, please import SAP seed data from all json files under Server Distribution/configuration/SAP by making REST calls using “REST Client” in the Germain Configuration Console. Select “merge” option while executing the REST calls. Check that the following components exist under germain.apm.monitoringConfig.components:

  • SAP Object Manager Parser

  • SAP Enterprise Manager Parser

  • SAP Crash Parser

  • SAP Crash Directory Monitor

  • SAP Log Directory Monitor

  • SAP Component Monitor (WMI)

  • SAP Component Monitor (SSH)

  • SAP HTTP Monitor

  • SAP Enterprise Configuration Monitor

  • SAP Collator

Add the SAP Server

  • Germain Workspace > Left Menu > Wizard > SAP App Server

Add credentials

Germain Workspace > Left Menu > Systems > Auth Settings > Authentications

Enter the credentials for you SAP server, usually it is SADMIN. If needed, enter the Domain, Secure Key

SAP Task level Monitoring

It is critical to enable Task level monitoring properly and inline to the below best practices. Often customers ignore those and always end up restart the whole enterprise when an issue comes up since they have no visibility as to what is causing an issue. Monitoring Tasks to this level will help avoid enterprise downtime and other errors.

  1. Adjust the below Thresholds based on what is running on your SAP environment. These values may need to be adjusted according to the SAP version, etc.

  2. Get management approval for your SLAs

  • Germain Workspace > Left Menu > Analytics > Rules > SAP-app-monitor-drl > Component Task Metrics

SAP Component (Configuration)

  • Germain Workspace > Left Menu > Wizards > Parser

Parser for SAP Log file - Germain UX

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine)

  • Fill the details as

    • Parser Component Type: SAP Object Manager Parser (Windows/Unix as applicable)

    • Monitored Application: SAP (or change if application name changed)

    • Monitored Application Component: None (or change if needed)

    • Number of instances: 1

  • Additional Configuration - Set the localized resource files for SAP log parsers

    • Set resourceFile to /com/germainsoftware/apm/localization/parser-SAP-objmgr-enu.properties

SAP Server Manager Parser (Configuration)

  • Germain Workspace > Left Menu > Wizards > Parser

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as

    • Parser Component Type: SAP Enterprise Manager Parser

    • Monitored Application: SAP (or change if application name changed)

    • Monitored Application Component: None (or change if needed)

    • Number of instances: 1

  • Click Next, Verify the details and click Submit

  • Additional Configuration - Set the localized resource files for SAP log parsers

    • Set resourceFile to /com/germainsoftware/apm/localization/parser-SAP-em-enu.properties

 Directory Manager for SAP log Files

  • Germain Workspace > Left Menu > Wizard > Directory Monitor

Directory Monitor Deployment for SAP log Files

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as

    • Directory Component Type: SAP Log Directory Monitor

    • Name – Name to the monitor, Default is SAP Log Directory Monitor

    • Monitored Server: Select the Server which is created in above steps

    • Path to Monitor: Point to the log files' location on the SAP Server; reachable from the Germain Server

    • Watch Subdirectories: no

    • Process Existing Files: yes

    • Process Empty Files: no

    • Force Polling: yes

    • Polling Interval (seconds): 300000 (**these are milliseconds **)

 

 Click Next, Verify the details and click Submit

 Directory Monitor for SAP Core Files

  • Germain Workspace > Left Menu > Wizard > Directory Monitor

 Directory Monitor for SAP Core Files - Germain UX

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as-

    • Directory Component Type: SAP Crash Directory Monitor

    • Name – Name to the monitor, Default is SAP Crash Directory Monitor

    • Monitored Server: Select the Server which is created in above stepsr

    • Path to Monitor: Point to the "crash" files' location

    • Watch Subdirectories: no

    • Process Existing Files: yes

    • Process Empty Files: no

    • Force Polling: yes

    • Polling Interval (seconds): 300000 (**these are milliseconds **)                                                                                  

Directory Monitor for SAP Gateway

  • Germain Workspace > Left Menu > Wizard > Directory Monitor

Directory Monitor for SAP Gateway - Germain UX

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as-

    • Directory Component Type: SAP Enterprise Configuration Monitor

    • Name – Name to the monitor, Default is SAP Enterprise Configuration Monitor

    • Monitored Server: Select the Server which is created in above steps

    • Path to Monitor: Point to the "siebns.dat" file's location

    • Watch Subdirectories: no

    • Process Existing Files: yes

    • Process Empty Files: no

    • Force Polling: yes

    • Polling Interval (seconds): 300000 (**these are milliseconds **)

Remote Monitor for SAP Server Performance

  • Germain Workspace > Left Menu > Wizard > Directory Monitor

Remote Monitor for SAP Server Performance

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as

    • Name: Components Status Monit

    • Monitored Server: Select the Server which is created in above steps

    • Monitored Application: SAP (or change if application name changed)

    • Credentials: Select the credentials created in above steps

    • Interval: 300

    • Local Connection for WMI?: no

    • Component Type: SAP Component Monitor (Windows|Unix)

  • Click Next, Verify the details and click Submit

  • Additional Configuration - The following configuration references have to be added to the component deployments in the config console

    • SAP Credentials [e.g. key: germain.apm.monitoringConfig.credentials, itemName: SAP Admin]

    • SAP Gateway [e.g. value: gcgSAP77]

    • SAP Server [e.g. key: germain.apm.monitoringConfig.servers, itemName: gcgSAP77]

    • SAP Enterprise [e.g. value: sba_81]

    • SAP Path [e.g. value: C:\sba811v2]

    • Excluded Components [Optional; value: can be empty, or a comma-seperated list of components names to exclude]

SAP Config Collator

  • Germain Workspace > Left Menu > System > Root Config > MonitoringConfig > SAP Config Collator

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as

    • Component Type: SAP Config Collator

    • Name: Name default is SAP Config Collator, can be changed.

  • Click Next, Verify the details and click Submit

SAP Config Collator - Germain UX

SAP HTTP and SISNAPI

  • Germain Workspace > Left Menu > System > Root Config > MonitoringConfig >  SAP HTTP Monitor

  • Select the Germain Monitoring Node ( UX ) and Engine (DefaultEngine) , Click Next

  • Fill the details as-

    • HTTP Component Type: SAP HTTP Monitor

    • Name: SAP HTTP Monitor

    • Server: Select the Server which is created in above steps

    • Application: Application to monitor

    • Scheme: HTTP

    • Port: 80 (or change if needed)

    • repeatSeconds: 300                                               

  • Click Next, Verify the details and click Submit

  • Additional Configuration - The following configuration references have to be added to the component deployments in the config console

    • For the HTTP Monitor from 4.10

  • From Germain Configuration Console, go to your monitoring node, DefaultEngine, components and SAP HTTP Monitor

    • SAP Credentials [e.g. key: germain.apm.monitoringConfig.credentials, itemName: SAP Admin]

    • SAP Component [e.g, value: component to test]

Include/Exclude SAP Components

To exclude SAP components from being monitored by Germain UX, we will need to create a reference called “ExcludedComponents” on the monitor. Follow the same logic to include one.

  • Go to you monitor and click the (plus) to the right of “References”

  • Enter the name as “ExcludedComponents” and enter the names of the components is a comma separated list as you see below.

Configuration Reference - Germain UX

KPIs

Please go here to see KPIs for SAP Component/Object Manager.

Dashboards

A number of dashboards are preconfigured for SAP, here are just a few main ones, but there might be more.

  • Go to Germain Workspace > Left Menu > Dashboards > All

  • Search for any “SAP…” dashboards, such as:
    SAP Performance
    SAP Availability

Component: Engine

Feature Availability: 2014.1 or later

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close