sap_basis (SAP Basis Monitoring) Release Notes

The SAP Basis Monitoring (sap_basis) probe monitors the health and performance of the SAP landscape. This probe helps enterprises monitor their mission-critical SAP applications. The sap_basis probe can monitor the SAP instances, database instances, and file systems that are the main components of a SAP Basis deployment. Refer to  to understand the monitoring capabilities of the probe.
uimpga-ga
sap_basis_RN
The SAP Basis Monitoring (sap_basis) probe monitors the health and performance of the SAP landscape. This probe helps enterprises monitor their mission-critical SAP applications. The sap_basis probe can monitor the SAP instances, database instances, and file systems that are the main components of a SAP Basis deployment. Refer to sap_basis Metrics to understand the monitoring capabilities of the probe.
The probe allows Basis administrators to obtain a holistic view of their SAP Basis environment and helps them detect problems before they affect end-users. By using this probe, the Basis team can monitor the performance of their applications from a single console, see alerts when issues arise, diagnose and troubleshoot problems, track trends, and plan using the graphs and charts in Unified Service Manager.
You can define QoS and alarms to be generated when specified thresholds are breached or when the SAP Server is unavailable. You can also configure the factory templates to monitor SAP ABAP, SAP HANA, SAP PI, SAP NetWeaver and SAP BOBJ and use out of the box dashboards to view the state of these SAP products.
Contents
Revision History
This section describes the history of the revisions for this probe.
Version
Description
State
Date
2.06
What's New:
  • Added New Metrics for Inbound & Outbound Queues and Enqueue Management.
GA
December 2019
2.02
What's New:
  • Added support to monitor SAP HANA Platform 2.0.
GA
April 2019
2.01
What's New:
  • Added support to login to the SAP system through Logon Groups.
  • Added support for Custom SAP Control (Netweaver) Monitoring. For more information, see sap_basis IM Configuration.
  • Added support for SAP NetWeaver Process Orchestration (SAP PO).
  • Added support to monitor:
    • SAP HANA on HEC (HANA Enterprise Cloud by SAP) based deployments.
    • HANA database as a standalone resource.
    • SAP BusinessObjects BI (SAP BOBJ)
  • Introduced new SAP Dashboard to monitor the SAP objects. For more information, see SAP CABI for CA UIM Dashboards.
Fixed Defects:
  • The probe retrieved NULL values for some metrics while creating a SAP NetWeaver (PI/PO) profile.
    Support case number 750286
  • Added support to monitor SAP NetWeaver deployments version 7.21.
    Support case number 751434
GA
September 2017
1.40
What's New:
  • Added support to monitor the RFC connection status in SM59.
  • Added support to calculate the count of ABAP runtime errors in ST22.
  • Added support to retrieve the number of waiting emails in CCMS.
  • Enhanced support for SAP NetWeaver monitoring.
  • Added support for Java JRE 8.
Fixed Defects:
  • The probe did not display some metrics when the SID was entered in lower case while creating a SAP ABAP profile.
    Support case number 533051
GA
January 2017
1.31
What's New:
    • QoS source and target are updated to support the SAP CABI dashboard.
    • Added the QOS_SAP_LICENSE_EXPIRY_DAYS and QOS_SAP_VM_MAX_GC_RATE messages in existing templates for SAP ABAP and SAP HANA.
GA
September 2016
1.30
What's New:
    • Added support for SAP NetWeaver Process Integration (SAP PI).
    • Added support for Linux platform.
    • Enhanced the factory templates to include monitors for the SAP CABI dashboard.
Note
: The probe upgrade from version 1.2 to version 1.3 is not supported.
Beta
August 2016
1.20
What's New:
    • Added support to monitor SAP HANA database on-premise deployments.
    • Added support to monitor SAP NetWeaver deployments.
    • Added support to monitor fifteen SAP events. See sap_basis IM Configuration for details.
    • Added support to monitor the following SAP components:
      • Availability of
        SAP License Status
        and
        Ended Work Processes
      • SAP ICM service
      • P ackets In
        and
        Packets Out
        in SAP OS Collector.
Note
: The probe upgrade from version 1.0 to version 1.2 is not supported.
GA
August 2016
1.00
What's New:
    • First release of the probe.
    • The probe is supported only on Windows platform through the Infrastructure Manager GUI.
    • The probe can be deployed only on English locale.
Beta
May 2016
Probe Specific Hardware Requirements
The sap_basis probe is installed on systems with the following minimum resources:
  • Memory: 4 GB of RAM. The OOB configuration of the probe requires 256 MB of RAM.
  • CPU: 3-GHz dual-core processor; 32-bit or 64-bit
Probe Specific Software Requirements
The sap_basis probe requires the following software environment:
  • CA Unified Infrastructure Management 8.31 or later
  • Robot 7.8 or later (recommended)
  • Java JRE version 7 or later
  • Install ci_defn_pack version 1.25 or later on the primary hub robot (with nis_server probe) to view the metrics on the USM portal. Restart nis_server after you deploy ci_defn_pack.
  • Install the Wasp Language Pack version 8.45 or later to view the correct Metric Names on the USM portal. Restart the
    wasp
    probe after you deploy the
    wasp_language_pack
    .
  • .Net Framework 3.5
  • Unified Dashboard 3.08 (for sap_basis 1.30 and later)
For more information about upgrading Unified Dashboard, see Unified Dashboards.
Supported Platforms
The sap_basis probe is certified on the SAP ERP Central Component (ECC) 6.0 version. You can also use the probe with the following SAP versions:
Supported SAP Versions
Supported NetWeaver Versions
Supported Databases
Supported Platforms
  • SAP R/3 Enterprise Edition 4.0B
  • SAP R/3 Enterprise Edition 4.3
  • SAP R/3 Enterprise Edition 4.5B
  • SAP R/3 Enterprise Edition 4.6C
  • SAP R/3 Enterprise Edition 4.6F
  • SAP R/3 Enterprise Edition 4.7
  • SAP ERP Central Component (ECC) 5.0
  • SAP NetWeaver AS ABAP (7.1/7.2)
  • SAP SCM (2007/4.0/4.1/5.0)
  • SAP SRM (3.0/4.0/5.0/6.0/7.0)
  • SAP CRM (2007/3.0/3.1/4.0/5.0/7.0)
  • SAP BW (2.0B/2.1C/3.0A/3.0B/3.1)
  • SAP BusinessObjects BI (BOBJ) 4.1
SAP NetWeaver 7.4
Oracle
  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016
SAP NetWeaver PI 7.40 SP5
DB2
Red Hat Enterprise Linux 7.2
SAP NetWeaver PO 7.50
SAP HANA 1.0 SP6
SAP NetWeaver 7.21
Access Requirements for SAP System User
For (ABAP) and (ABAP + Java Stack) only
If the user does not have a
SAP_ALL
profile, a role is required to be created in the SAP system with the following access:
Technical Name
Value
Authorization Object Name
S_RFC
Activity
ACTVT
*
Name of RFC to be protected
RFC_NAME
*
Type of RFC to be protected
RFC_TYPE
*
Authorization Object Name
S_RZL_ADM
Activity
ACTVT
03 (Display)
Authorization Object Name
S_XMI_LOG
Activity
XMILOGACC
*
Authorization Object Name
S_XMI_LOG
XMI logging: Company name
EXTCOMPANY
*
XMI logging: Program name
EXTPRODUCT
*
Interface ID (for example, XBP)
INTERFACE
*
Authorization Object Name
S_APPL_LOG
Activity
ACTVT
03 (Display)
Application log: Object name
ALG_OBJECT
*
Application Log: Subobject
ALG_SUBOBJ
*
Authorization Object Name
S_IDOCCTRL
Activity
ACTVT
03 (Display)
Transaction Code
EDI_TC
OYSP, WE05, WE07-WE08, WE12, WE14-WE19, WE40-WE47, WE55-WE57, WELI
Authorization Object Name
S_IDOCMONI
Activity
ACTVT
03 (Display)
Direction for IDoc
EDI_DIR
*
Message Type
EDI_MES
*
Partner number
EDI_PRN
*
Partner Type
EDI_PRT
*
Transaction Code
EDI_TCD
WE02, WE05, WE07, WE09-WE10, WE19
Authorization Object Name
S_IDOCPART
Activity
ACTVT
03 (Display)
Partner number
EDI_PRN
*
Partner Type
EDI_PRT
*
Transaction Code
EDI_TCD
WE20
Authorization Object Name
S_IDOCPART
Activity
ACTVT
03 (Display)
Port type
EDI_POR
*
Transaction Code
EDI_TCD
WE21
Upgrade Considerations
This section lists the upgrade considerations for the sap_basis probe.
  • Upgrade from previous versions to 1.30 is not supported.
  • (For SAP NetWeaver only)
    Upgrade from version 1.31 to 1.40 is supported only if the JMX user has the same credentials as SAP Control Web Services. The user is also required to delete the existing resource and recreate it with valid SAP Control Web Service credentials.
Subsystem ID Considerations
Alarms are classified by subsystem IDs. Each subsystem ID identifies the name of a system component. You must add additional subsystem IDs to view alarm data for the sap_basis probe in USM.
The following subsystem IDs must be added to nas if you use nas 8.4 or earlier:
Key Name
Value
2.25
Sap
Follow these steps:
  1. Open
    Raw Configure
    for the nas probe.
  2. Click
    Subsystems
    .
  3. Add the new key name and value.
  4. Repeat this process for all of the required subsystem IDs.
Known Issues
The following known issue exists with the probe:
Issue:
The probe sends an additional non-responding and clear alarm from the Robot where it is deployed.
For example, if the resource of the probe is BOBJ1, and it is deployed on the Robot: ROBO1, the probe, in addition to sending the non-responding and clear alarm from BOBJ1, also sends an alarm from ROBO1.
Solution:
There is no workaround at this time.
Troubleshooting
Following are some troubleshooting issues for the sap_basis probe.
I cannot see graphs on the Unified Service Management (USM) portal
Solution:
Restart your data engine and the discovery server.
My resource binds with incorrect HANA database
Symptom:
While creating a new resource for the HANA database, I can bind the ABAP resource with incorrect HANA database.
Solution:
The probe can monitor both bound and unbound HANA databases. CA recommends you to monitor the HANA database associated to your SAP ABAP resource.
Multi-Tenancy Issue
Symptom:
The probe is unable to identify QoS information generated for different SAP servers that have the same
hostname
or
SID
or
System Number
. The probe merges this QoS information
even if the probe is deployed on different hubs or robots.
Solution:
If you are using the sap_basis probe in a multi-tenant environment, add the following key using the raw configuration interface of the probe and set its value as
true
.
  • multi_tenant_source
This enables the probe to identify the source and thus it creates different entries for different robots. Thus, you get the required source, target and QoS combination.