SAP Management Pack Release Notes - ozsoft-consulting.com · SAP Management Pack for Microsoft System Center Operations Manager Release Notes 3 Version 4.2.2 May 31, 2016 New in this

OZSoft Consulting Corporation

http://www.ozsoft-consulting.com

SAP Management Pack for Microsoft System Center Operations Manager Release Notes

SAP Management Pack for Microsoft System Center Operations Manager

Release Notes 2

About this publication These release notes provide information about the enhancements and resolved problems in the OZSoft

SAP Management Pack for Microsoft System Center Operations Manager. This information supplements

and supersedes information in the Installation, Administration and User’s Guide.

http://ozsoft-consulting.com/download/mp4sap/SAP%20MP%20for%20SCOM%20UIG.pdf


Release Notes 3

Version 4.2.2 May 31, 2016

New in this release

Zero CCMS Configuration

The new version of the Management Pack makes it possible to avoid any SAP-side CCMS configuration –

just check/keep Zero Configuration checkbox and the Management Pack will take care of including only

relevant Performance Counters and Alerts:

Should you require a more precise control - the old way is still available, just uncheck the flag and

proceed with the Monitor set configuration.

Importable Alert and Counter filters

It now possible to import Alert and Performance Counters filters supplied as a file. The Management

Pack includes best-practice alert filters bundle for filtering out CCMS Threshold Alerts available in

<Installation Folder>\import\Filter-CCMSThresholdAlerts.xml:


Release Notes 4

In the Alert Filter tab, click on Import button in the lower-right corner of the screen:

Select the file and click Open:


Release Notes 5

The imported filters will show up:

Modify if needed and Save.

Changed in this release There are no changes to the existing functionality in this release

Corrected problems There are no corrections included in this release.

Open issues and resolutions

Tracking Number Description

BMPSAP000243 SAP Host MP doesn’t load on SCOM Agent on Windows 2008 R2 and earlier due to the MP minimum supported.NET version 4.0 requirement


Release Notes 6

Installation information

SAP Management Pack installation

For complete SAP Management Pack installation information, see the Installation, Administration and

User’s Guide.

No Management Packs have been updated.

Please install the latest version of the Management Pack Connector (mp4sacom.msi).

SAP Connector will not operate unless the latest OZMP4SAP.mp is imported.




Release Notes 7

Version 4.2.1 April 19, 2016

New in this release There is no new functionality in this release

Changed in this release There are no changes to the existing functionality in this release

Corrected problems The issues listed below were reported in earlier releases of SAP Management Pack and have been corrected in this release.


BMPSAP000257 The importable CCMS Monitor file MonitorSpool.XML is missing in in the <installation folder>\SAP

BMPSAP000258 SAP Connector does not start. The following Event is produced in SAP Connector Events view: Management Pack OZMP4SAP Version 4.1.0.5 could not be found







User’s Guide.

No Management Packs have been updated.

Please install the latest version of the Management Pack Connector (mp4sacom.msi).





Release Notes 8

Version 4.2.0 March 29, 2016

New in this release

SAP Landscape Transformation (SLT) Monitoring

The Management Pack now supports SAP Landscape Transformation Monitoring.

The Management Pack takes advantage of SAP Landscape Transformation API and allows for

comprehensive replication monitoring in SCOM.

Configuration

The SLT Monitoring needs to be enabled for each SLT system. This is done in SAP Connector

configuration (SLT tab in SAP System configuration dialog):


Release Notes 9

The new SLT Configurations view lists all discovered SLT Configurations on the connected SAP systems:

Each SLT Configuration object hosts all discovered Table Replication entries.

The following SCOM Monitors are configured for SLT Configuration and SLT Table objects:

Target Object Monitor Name Description

SLT Configuration Master Job Status SLT Configuration Master Job Status

SLT Table Status Table Replication Status

SLT Table Trigger Status Table Trigger Status

SLT Table Replication Age The Age of the last Table Replication measured in seconds

SLT Table Latency Table Replication Latency measured in seconds

SLT Table Inserted Records/hour The latest inserted Records count per hour


Release Notes 10

CCMS Alert Counters

The Management Pack introduces a new facility that allows for ad hoc CCMS Alert counters.

The Alert Counters are based on a criteria definition for the incoming CCMS Alerts. When the first

matching alert is detected for an SAP System a SCOM Object is created for the Counter:


Release Notes 11

The number of matching CCMS Alerts is calculated per interval (15-default, 30, 60 … minutes) and

reported as SCOM Performance Counter

The attached Monitor enables conditional alerting and state change. The alert count calculation is taking

place before the Alert Filters and Suppression are applied.


Release Notes 12

Target Object Monitor Description

Alert Counter Alert Count Alert Count Monitor

The new Alert Counters state view lists all created Alert Counter Objects:

For Every matching CCMS Alert an event is created and associated with Alert Counter SCOM Object. You

can browse all posted CCMS alerts by right-clicking on the object and choosing Open->Event View

CCMS Spool Monitoring Integration

The CCMS Spool and Print Devices monitoring has been fully integrated into Management Pack.

When the Management Pack is configured to include Spool-related CCMS Monitors the following SCOM

objects hosted by SAP Application Server are created:

Spool Service

Spool Device(s)

The following SCOM Monitors are defined:


Spool Service Status Spool Server Status

Spool Service Errors in Spool Work Processes Number of Errors in Spool Work Processes

Spool Service Ended Spool Work Processes The number of Ended Spool Work Processes

Spool Service Wait Time Wait time in the spool service in seconds

Spool Service Work Processes Utilization Usage of the spool work processes as a percentage

Spool Service Dispatcher Queue Utilization Used area of the dispatcher queue as a percentage


Release Notes 13

Spool Service Work Processes Request Queue Utilization

Used area of the spool request queue as a percentage

Spool Service Work Processes Chronological Request Queue Utilization

Used area of the spool request queue for chronological processing as a percentage

Spool Service Request Queue Pages Number of pages in the spool request queue

Spool Service Device Cache Usage Used area of the entire device cache as a percentage

Spool Service Fixed Device Cache Usage Used area of the fixed device cache as a percentage

Spool Service In-Memory Request List Usage The usage of the List of Request stored in Shared Memory

Spool Device Messages Errors from the transfer of the output request to the host spool system

Spool Device LPQ Time Time that the output request spends in the wait queue of the output device

Spool Device Pages/min Time that the output request spends in the wait queue of the output device

The new Spool Devices state view lists all discovered Spool Devices:

Configuration

An importable CCMS Spool Monitor is included and can be found at <Installation

Folder>\SAP\MonitorSpool.XML


Release Notes 14

New Background Service Monitors

Two new Background Service Monitors have been added:


Background Service System Wide Queue Length Background Service System-wide Queue Length Monitor

Background Service System Wide Free Background WPs

System Wide Free Background Work-Processes Monitor

The new monitors are delivered in ozsoft.sap.background.mp management pack

Changed in this release

Additional SAP Authorizations

The newly added SLT functionality requires additional authorizations for the Management Pack SAP

Accounts on all relevant connected SAP Systems:

Auth Object Values Reason

S_RFC RFC_TYPE=FUGR RFC_NAME=(PWP2, RFC1, RFC2, SDDO, SDIFRUNTIME, SG00, SRFC, SYST, SYSU, SIFD, SIMG, SDNT, SALX, SXSP, SXMI, SXMB, SXBP, STUB, RFC_METADATA, PERF_TRA_DIA, RSPC_API, ECATT_EXECUTE, ECATT_LOG, /SDF/CONN_MON, ZITCONDUCTOR, SAPWL_GLOB_STAT, IUUC_REPL_API, IUUC_REPL_CONTENT_REMOTE, IUUC_REPL_GET_STATUS) ACTVT=16

RFC Calls

S_DMISS MBT_PR_ARE=* MBT_PR_LEV=PACKAGE ACTVT=03, 02

SLT Monitoring

The supplied SAP Security Role Export includes above-mentioned changes

New version of SAP .Net Connector

The latest version of SAP .Net Connector (3.0.17.0) is now used

Corrected problems There are no corrections delivered in this release.





Release Notes 15




User’s Guide.

The following Management Packs have been updated:

OZMP4SAP.mp

The following Management Packs have been added:

ozsoft.sap.alertcounters.mp

ozsoft.sap.background.mp

ozsoft.sap.spool.mp

ozsoft.sap.slt.mp

Please import these management packs.


For complete SAP Host Control Management Pack installation information, see the SAP Host Control

Management Pack Installation, Administration and User’s Guide.



http://ozsoft-consulting.com/download/mp4sap/ozsoft.sap.host.uig.pdf



Release Notes 16

Version 4.1.0 December 22, 2015

New in this release

SAP Workload Monitoring

The Management Pack now provides a highly flexible Targeted SAP Workload Monitoring.

The Management Pack takes advantage of SAP Workload Statistics collection (STATs) and allows for very

detailed and targeted Workload Monitoring. The Management Pack enables users to configure so called

‘Buckets’ that will include any recorded workloads matching the defined criteria and aggregate the

related metrics, reporting them to SCOM for Monitoring and Charting.

Importing SAP Transports

The Management Pack Workload Monitoring requires included SAP Transport to be imported on all SAP

systems where Workload Monitoring is to be enabled. The transport includes several ABAP Function

Modules that perform summarization of SAP data in order to minimize the network traffic between the

SAP and SAP Connector.

The transport ZIP file can be found in in <Installation Folder>\sap\transports\ folder. Please request your

Basis team to import the Transport.

Configuration

The Workload Monitoring configuration is performed in SAP Connector configuration screen and is SAP-

system specific (Workloads tab on SAP system configuration dialog)

In the left panel you define a Workload ‘Bucket’ which Management Pack refers as ‘SLA’. For each SLA,

in the right panel, you define one or more ‘Filters’. Each filter can specify multiple workload selection

properties: TCODE, ACCOUNT, TASKTYPE, TERMINALID, CLIENT, APPSERVER and REPORT. Each selection

property contain Regular Expression.


Release Notes 17

Saving the configuration allows SAP Management Pack to synchronize the changes with SCOM and

create the Workload Monitoring ‘SLA’ objects. During the execution all SAP Workload records matching

on of the SLAs filters will be aggregated (as average or sum depending on the type of a performance

counter) and posted into SCOM.

The Workload Monitoring view lists all defined SLA entries:

Three SCOM Monitors are configured for each ‘SLA’ Object:

Monitor Description

Average DB Request Time Average DB Processing time per Dialog Step (milliseconds)

Average Queue Time Average Queue Time per Dialog Step (milliseconds)

Average Response Time Average total Response Time per Dialog Step (milliseconds) Table 1. Workload Monitors


Release Notes 18

Additional performance counters are aggregated and collected and available for charting and

monitoring with custom monitors:

Built-in RFC Destinations Monitoring

The Management Pack now incorporates built-in RFC Destination Monitoring that does not rely on

CCMS.

Build-in RFC Destination Monitoring performs periodic RFC Pings for the configured RFC Destinations

collecting Ping Status and Latency. The ping is performed via a specialized SAP Function Module and

actually is executed on the connected SAP System and not on the SAP Connector Machine.

The ping interval is configured in Scheduling tab, field RFC Dest Ping.

RFC Destinations configuration is located in RFC Destinations tab in the SAP Configuration window:


Release Notes 19

Saving the configuration allows SAP Management Pack to synchronize the changes with SCOM and

create the RFC Destination objects.

CCMS RFC Destination Monitoring and built-in RFC Destination Monitoring can operate side by side, this

however is not recommended due to the difficulty in determining the source of availability information.

The built-in RFC Destination Monitoring reports several performance counters. Two Monitors are

supplied:

Monitor Description

Availability Ping Availability (%)

Ping Latency Average Ping Latency (milliseconds)

Requirements

RFC Destination Monitoring functionality requires the SAP system to have Solution Manager

Plug-In (ST-PI) 2008_1_700 or later installed. Please consult with your Basis team to check if ST-

PI is installed and its level using SPAM transaction.

This requirement is only relevant if you configure RFC Destinations for a particular SAP System.


Release Notes 20

SAP Security Role Export

To simplify the Security configuration SAP Management Pack now includes the SAP Security Role export

file that can be imported into you target SAP Systems and assigned to SCOM accounts. The Role export

file can be found in in <Installation Folder>\sap\profiles\BCSEN_OZSOFT.SAP. Please request your Basis

team to import the SAP Role file and assign the new Role to the SCOM SAP Account. The role includes all

required Authorizations.

Changed in this release

Additional SAP Authorizations

The newly added functionality requires additional authorizations for the Management Pack SAP

Accounts on all connected SAP Systems concerned:

Auth Object Values Reason

S_RFC RFC_TYPE=FUGR RFC_NAME=(PWP2, RFC1, RFC2, SDDO, SDIFRUNTIME, SG00, SRFC, SYST, SYSU, SIFD, SIMG, SDNT, SALX, SXSP, SXMI, SXMB, SXBP, STUB, RFC_METADATA, PERF_TRA_DIA, RSPC_API, ECATT_EXECUTE, ECATT_LOG, /SDF/CONN_MON, ZITCONDUCTOR) ACTVT=16

RFC Calls

SCOM Connection Caching

In this release SCOM Connection caching is turned ON by default. As of SCOM 2012 R2 turning off the

caching results in a significant performance penalty.

Corrected problems The issues listed below were reported in earlier releases of SAP Management Pack and have been corrected in this release.


BMPSAP000255 In the configuration utility the Save button is not enabled after the new License Key is set

BMPSAP000256 BW Process Chain Monitoring Definitions are not synchronized with SCOM resulting in no failover for Process Chain Monitoring





Release Notes 21




User’s Guide.

The following Management Packs have been updated:

OZMP4SAP.mp

The following Management Packs have been added:

ozsoft.sap.rfcdest.mp

ozsoft.sap.workloads.mp

Please import these management packs. SAP Connector will not operate unless the latest

OZMP4SAP.mp is imported.

For complete SAP Host Control Management Pack installation information, see the SAP Host Control

Management Pack Installation, Administration and User’s Guide.






Release Notes 22

Contact Information You can contact OZSoft Consulting at the following web and e-mails addresses:

Technical support: [email protected] and http://www.ozsoft-consulting.com/support

Sales and Marketing: [email protected]

You can also visit our web site at http://www.ozsoft-consulting.com for more information about OZSoft

Consulting Corporation, the SAP Performance Management Specialist

mailto:[email protected]

http://www.ozsoft-consulting.com/support

mailto:[email protected]

http://www.ozsoft-consulting.com/

Documents

SAP Management Pack Release Notes - ozsoft-consulting.com · SAP Management Pack for Microsoft System Center Operations Manager Release Notes 3 Version 4.2.2 May 31, 2016 New in this