omi management pack for sap -1.00 - user guide ep_perf 153 icmstat_perf 155 jobrep_perf 156...

OMi Management Pack for SAPSoftware Version: 1.00

Operations Manager i for Linux and Windows® operating systems

User Guide

Document Release Date: June 2017 Software Release Date: May 2014

Legal Notices

WarrantyThe only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothingherein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights LegendConfidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commerciallicense.

Copyright Notice© 2014 - 2017 Hewlett Packard Enterprise Development LP

Trademark NoticesAdobe® is a trademark of Adobe Systems Incorporated.

Microsoft® andWindows® are U.S. registered trademarks of theMicrosoft group of companies.

UNIX® is a registered trademark of TheOpenGroup.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

Documentation UpdatesTo check for recent updates or to verify that you are using themost recent edition of a document, go to: https://softwaresupport.hpe.com/.

This site requires that you register for an HPE Passport and to sign in. To register for an HPE Passport ID, click Register on the HPE Software Support site or click Create anAccount on the HPE Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HPE sales representative for details.

SupportVisit the HPE Software Support site at: https://softwaresupport.hpe.com/.

Most of the support areas require that you register as an HPE Passport user and to sign in. Many also require a support contract. To register for an HPE Passport ID, clickRegister on the HPE Support site or click Create an Account on the HPE Passport login page.

To findmore information about access levels, go to: https://softwaresupport.hpe.com/web/softwaresupport/access-levels.

HPE Software Solutions Now accesses the Solution and Integration Portal website. This site enables you to explore HPE product solutions tomeet your business needs,includes a full list of integrations between HPE products, as well as a listing of ITIL processes. The URL for this website is https://softwaresupport.hpe.com/km/KM01702731.

User Guide

HPE OMi Management Pack for SAP (1.00) of 308

https://softwaresupport.hpe.com/

https://softwaresupport.hpe.com/

https://softwaresupport.hpe.com/web/softwaresupport/access-levels

https://softwaresupport.hpe.com/km/KM01702731

Contents

Chapter 1: OMi Management Pack for SAP 10Chapter 2: Getting Started 11

Task 1: Adding Remote Managed Node to BSM 9.2x or OMi 10.xConsole 11Task 2: Enabling the Enrichment Rules 11Task 3: Deploying the SAP Discovery Aspect 12Task 4: Configuring SAP Node for ABAP Application Server Monitoring 17Task 5: Deploying SAP ABAP Configuration Aspect 18Data Collection 19Task 6: Identifying and Deploying an SAP Management Template 20Task 7: Deploying SAP Aspects 22Task 8: Configuring SAP ABAP Monitoring Templates 26Monitoring SAP Environment 27

Chapter 3: Components 31SAP Management Templates 31Overview of SAP Management Templates 32

Tasks 33Essential SAP ABAP Management Template 35Extensive SAP ABAP Management Template 36Essential SAP J2EE Management Template 37

User Interface Reference 38Extensive SAP J2EE Management Template 38

User Interface Reference 39SAP Aspects 39Types of SAP Aspects 40

Tasks 40SAP ABAP Aspects 42

User Interface Reference 42SAP ABAP Batch Job Health 43SAP ABAP Base 43SAP ABAP Configuration 43

User Guide


SAP ABAP Correction and Transport System Status 44SAP ABAP Discovery 44SAP ABAP Dump Status 44SAP ABAP Idoc Status 44SAP ABAP Lock Status 45SAP ABAP Performance Monitor 45SAP ABAP Processes and Dispatcher Status 45SAP ABAP RFC Destination Status 46SAP ABAP Remote Configuration 46SAP ABAP Security Status 46SAP ABAP Spool Health 47SAP ABAP System Change Option Status 47SAP ABAP Transport Status 47SAP ABAP Update Tasks Health 48SAP ABAP User Health 48SAP ABAP Work Process Health 48SAP CCMS Integration 49SAP System Health 49SAP Temporary Sequential File Monitoring 49

SAP J2EE Aspects 50User Interface Reference 50

SAP J2EE Base 50SAP J2EE Application Thread Pool Performance 51SAP J2EE Cluster Manager - Message Server CommunicationLayer Performance 54SAP J2EE Cluster Manager - Session Communication LayerPerformance 60SAP J2EE Configuration 62SAP J2EE Configuration Manager and Class LoaderPerformance 63SAP J2EE Connections Manipulator Performance 63SAP J2EE Connector Service Performance 64SAP J2EE Discovery 77SAP J2EE EJB Performance 77SAP J2EE Http Provider Performance 80

User Guide


SAP J2EE JMS Performance 81SAP J2EE JMX Adapter Performance 82SAP J2EE JNDI Registry Status 82SAP J2EE Log Configurator Performance 83SAP J2EE Memory Status 83SAP J2EE P4 and IIOP Provider Performance 84SAP J2EE Ports Manager Performance 84SAP J2EE Sessions Manager Performance 85SAP J2EE System Thread Pool Performance 87SAP J2EE Transaction Status 89SAP J2EE Web Container Performance 90SAP J2EE Web Services Performance 91SAP JARM Requests Performance 92

SAP ABAP Monitoring Templates 93Remote Monitoring with SAP ABAP Monitoring Templates 94

Specifying Individual Remote Servers to Monitor 95SAPABAP_BatJobMon 95

Alert Types 96Configuring Job-Report Monitor Alert Types 98

SAPABAP_CCMSIntegrationMon 105SAPABAP_CTSMon 113

Monitor Type 114Alert Types 114File Locations 114Environment Variables 115Command-Line Parameters 115Remote Monitoring 115Configuring SAPABAP_CTSMon Monitoring Template AlertTypes 115REQUEST_CREATED 116REQUEST_RELEASED 117TASK_CREATED 119TASK_RELEASED 120OBJECT_USED 121OBJECT_RELEASED 122

User Guide


SAPABAP_DispMon 124Prerequisites 124Checking the snapshot option 125File Locations 125Integrating SAPABAP_DispMon Monitoring Template with OMiMP for SAP Monitors 126SAPABAP_DispMon Monitoring Template Configuration 127

SAPABAP_DmpMon 129Monitor Type 130Alert Types 130File Locations 130Environment Variables 130Command-Line Parameters 131Remote Monitoring 131ABAP4_ERROR_EXIST 131

SAPABAP_IdocStatusMon 132Monitor Type 132Alert Types 132File Locations 132Environment Variables 133Command-Line Parameters 133Remote Monitoring 133Configuring SAPABAP_IdocStatusMon Monitoring TemplateAlert Types 133IDOC_CURRENT_STATUS 133Checking the iDOC Status 136

SAPABAP_LckChkMon 140OLD_LOCKS 141

SAPABAP_PerfMon 142Overview 142Configuring the SAPABAP_PerfMon Monitoring Template 143Managing the OMi MP for SAP R/3 Performance Agent 147OMi MP for SAP Performance Monitors 149DBINFO_PERF 151DOCSTAT_PERF 152

User Guide


EP_PERF 153ICMSTAT_PERF 155JOBREP_PERF 156SAPBUFFER_PERF 157SPOOL_PERF 160SYSUP_PERF 162UPDATE_PERF 162STATRECS_PERF 163USER_PERF 164WLSUM_PERF 164WP_PERF 166Removing the OMi MP for SAP R/3 Performance Agent 168

SAPABAP_ProcMon 170File Locations 170Environment Variables 170Monitoring Conditions 171Sample Configuration 171

SAPABAP_RFCDestMon 174CHECK 174Environment Variables 175Command-Line Parameters 175Remote Monitoring 175Configuring RFC-destination Alert Types 175CHECK 176

SAPABAP_SecMon 177File Locations 177Alert Types 178SAP_PARAMETERS 178DEFAULT_USERS 180PRIVILEGED_USERS 181Remote Monitoring using SAPABAP_SecMon MonitoringTemplate 182

SAPABAP_SplMon 184Configuring Alert Types 185SPOOL_ENTRIES_RANGE 185

User Guide


SPOOL_ERROR_RANGE 186PRINT_ERROR_EXISTS 187

SAPABAP_StatRecMon 187SAPABAP_StatusMon 188

Environment Variables 189History File 190

Configuring SAPABAP_StatusMon Monitoring Template 191Establishing the SAP Status 192Monitoring SAP Remotely 193

SAPABAP_SysChgOptMon 194Configuring SAPABAP_SysChgOptMon Monitoring TemplateAlert Types 196CHANGE_OPT 196

SAPABAP_TraceMon 200SAPABAP_TransMon 203

Configuring Transport-Monitor Alert Types 205TRANS 205REPAIR 208RFCONNECT 209TPTEST 210

SAPABAP_UpdProcMon 211Configuring Update-Monitor Alert Types 212

SAPABAP_UsrMon 213USER_LOGGEDIN_MAX 214

SAPABAP_WPMon 216Configuring Work-Process Monitor Alert Types 218WP_AVAILABLE 218WP_IDLE 221WP_CHECK_CONFIGURED 224WP_STATUS 225

TempSeqFileMon 226Monitoring the TemSe file 226

Customizing SAP ABAP Monitoring Templates 227SAP ABAP Monitoring Templates, Monitoring TemplateConfiguration Files, and History Files 227

User Guide


Keywords and Parameters 231Query Conditions for Monitoring Templates 234Configuration Fields in ABAP Monitoring Templates 236Environment Variables 236Command-Line Parameters 237

SAP Parameters 237Types of Parameters 237Configuring ABAP Monitoring Template Parameters 240

Run-time Service Model (RTSM) Views 243Event Type Indicators (ETIs) 246Health Indicators (HIs) 248Configuration Items and Configuration Item Types 251Topology Based Event Correlation (TBEC) Rules 252Tools 257

Chapter 4: Creating SAP Management Templates 264Editing SAP Management Templates 266

Editing Parameters 266Editing Aspects 267

Chapter 5: Deployment Scenarios 269Chapter 6: Troubleshooting 284Appendix: Metrics and Datasources 298

SAP ABAP Application Server 298SAP J2EE Application Server 307

Send documentation feedback 308

User Guide


Chapter 1: OMi Management Pack for SAPTheOMi Management Pack for SAP (OMi MP for SAP) works with Operations Manager i (OMi) andenables you tomonitor primary and advanced components of your SAP environment and the underlyinginfrastructure.

It includes Health Indicators (HIs) and Event Type Indicators (ETIs) that analyze the events that occurin your SAP Configuration Items (CIs) and report the health status of the SAP environment. It alsoincludes two sets of out of the box Management Templates for monitoring the availability, health, andperformance of ABAP and Java Application Servers in your SAP landscape. TheseManagementTemplates consists of a two separate sets of Aspects which enable easy monitoring of both ABAP andJava Application Servers in your SAP landscape.TheManagement Templates can be deployed byadministrators for monitoring your SAP landscape. TheManagement Templates can also be easilycustomized by Subject Matter Experts (SMEs) and developers to suit different monitoringrequirements.

The SAP ABAP Monitoring Templates features RemoteMonitoring which extends the scope ofmonitoring ABAP Application Servers by enabling you tomonitor SAP ABAP Application Servers onnodes which does not haveOperations Agent installed. You can set up and perform the remotemonitoring of ABAP Application Servers from an SAP CI, where Operations Agent is installed andOMiMP for SAP Management Templates are deployed.

TheOMi MP for SAP includes the following artifacts for monitoring your SAP environment:

l Two separate sets of Management Templates for ABAP and Java Application Servers

l Separate Aspects for ABAP and Java Application Servers

l ABAP Monitoring Templates

l J2EE Policy Templates

l Instrumentation

OMi MP for SAP works with OMi and provides the following salient features:

l Ready-to-deploy, management solutions to suit different monitoring requirements

l Separate set of Management Templates and Aspects covering ABAP and Java Application Serversfor creating customized solutions

l RemoteMonitoring solution for ABAP Application Servers


Chapter 2: Getting StartedYouwant to monitor a business critical SAP environment comprising of ABAP and Java ApplicationServer instances.

Your SAP environment can have either ABAP, Java or both Application Server instances. You want tocheck the availability and performance of either ABAP, Java or both Application Servers and alsomonitor the basic functionality of your SAP Environment.

Task 1: Adding Remote Managed Node to BSM 9.2x

or OMi 10.x Console

Before you beginmonitoring, follow these steps to add the nodes.

1. Open theMonitored Nodes pane from Administration:

On BSM 9.2x, click Admin > Operations Management > Setup > Monitored Nodes.

OnOMi 10.x, click Administration > Setup and Maintenance > Monitored Nodes.

2. In the Node Views pane, click Predefined Node Filter > Monitored Nodes and then clickand then select the required OS type. The Create New Monitored Nodes dialog box appears.

3. Specify the Primary DNS Name, IP address, Operating System, and Processor Architecture ofthe node and click OK.

Task 2: Enabling the Enrichment Rules

Youmust enable the following enrichment rules to populate the SAP CI’s display label with additionalinformation about container or the hostname:

l SoftwareElementDisplayLabelForNewHost

l SoftwareElementDisplayLabelForExistingHost

l SoftwareElementDisplayLabelPopulator

To enable the Enrichment rules, follow these steps:


1. Open the Enrichment manager pane:

On BSM 9.2x, click Admin > RTSM Administration > Modeling > Enrichment manager.

OnOMi 10.x, click Administration > RTSM Administration > Modeling > Enrichmentmanager.

2. In the Enrichment Rules pane, select SoftwareElementDisplayLabelForNewHost from the list.

3. Right-click and select Properties.

The Enrichment Rule Properties window appears.

4. Click Next.

5. Select Rule is Active.

6. Click Finish.

7. In the Enrichment Rules pane, click Save to save the changes.

8. Select SoftwareElementDisplayLabelForExistingHost and repeat steps 3 to 7.

9. Select SoftwareElementDisplayLabelPopulator and repeat steps 3 to 7.

Task 3: Deploying the SAP Discovery Aspect

To discover the SAP CI on the added SAP managed nodes, youmust deploy the SAP Discoveryaspect. OMi MP for SAP has two separate set of Discovery aspects for ABAP and J2EE ApplicationServer. You can deploy the Discovery aspect depending on the type of CI you want to discover.

Deploying SAP J2EE Discovery Aspect

To discover the J2EE Applications Servers in your SAP Landscape, follow these steps:

1. Open theManagement Templates & Aspects pane:

On BSM 9.2x, click Admin > Operations Management > Monitoring > ManagementTemplates & Aspects.

OnOMi 10.x, click Administration > Monitoring > Management Templates & Aspects.

2. In the Configuration Folders pane:

Configuration Folders > ERP Management > SAP NetWeaver Application Server >JAVA Aspects

User GuideChapter 2: Getting Started


3. In the JAVA Aspects folder, select theSAP J2EE DiscoveryAspect, and then click to open

the Assign and Deploy Wizard.

4. In theConfiguration Item tab, select the SAP managed node to which you want to deploy theSAP J2EE Discovery Aspect.

5. Click Next to go toRequired Parameters tab.

6. Click Next to go toAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x.

Note: In theAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x, youcan override the default values of any parameter. You can specify a value for each parameterat theManagement Template level. By default, parameters defined as expert parameters are

not shown. To view expert parameters, click Show Expert Parameters.

7. Click Next.

8. (Optional). If you do not want to enable the assignment immediately, Enable AssignedObjects OnBSM 9.2x or OnOMi 10.x Enable Assignment(s) check box

On BSM 9.2x, clear theEnable Assigned Objects check box.

OnOMi 10.x, clear theEnable Assignment(s) check box.

You can then enable the assignment later using the Assignments & Tuning pane.

9. Click Finish.

Deploying SAP ABAP Discovery Aspect

To discover the SAP ABAP Applications Servers in your SAP Landscape, follow these steps:





Configuration Folders > ERP Management > SAP NetWeaver Application Server > ABAPAspects

3. In the ABAP Aspects folder, select theSAP ABAP DiscoveryAspect, and then click to open

the Assign and Deploy Wizard.

4. In theConfiguration Item tab, click the SAP managed node to which you want to deploy the



SAP ABAP Discovery Aspect.

5. Click Next to go toRequired Parameters tab.

6. Click Next to go toAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x.



7. Click Next.

8. (Optional). If you do not want to enable the assignment immediately, .




9. Click Finish.

Deploying SAP ABAP Remote Configuration Aspect

If you want to monitor SAP ABAP Application Servers on nodes which do not haveOperations Agent(OA) installed, you can deploy SAP ABAP Remote Configuration Aspect.

To deploy SAP ABAP Remote Configuration Aspect, follow these steps:






3. In the ABAP Aspects folder, select theSAP ABAP Remote Configuration Aspect, and thenclick to open the Assign and Deploy Wizard.

4. In theConfiguration Item tab, click the SAP managed node you want to use as themonitoringhost (where the Agent is installed) and then click Next.

5. In theRequired Parameters tab, youmust specify the details about the remote SAP Central



Instance node that you want to monitor using OMi MP for SAP.

a. Select theSAP ABAP Application Server Instance with HostName and SID parameter

in the list, and then click . The Edit Parameter: SAP ABAP Application Server Instance

number with HostName and SID dialog box opens.

b. Specify theSAP ABAP Application Server Central Instance along with Host Name andSID of Remote SAP ABAP Application Server as shown in the following example:

Example:

testnode.hpe.com_T01_00

Here testnode.hpe.comis the fully qualified SAP Remote Host Name, T01is the SID for SAP Remote Host and 00is the SAP Instance number.

c. Click OK.

d. Select theSAP ABAP Application Server Client parameter in the list, and then click .

The Edit Parameter: SAP ABAP Application Server Client opens.

e. Click Value, specify the client number of remote SAP ABAP Application Server, and thenclick OK.

6. Click Next to go toAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x. To

change the default values of the parameters, you can select the parameter and then click . The

Edit Parameter dialog box opens. Click Value, specify the value, and then click OK. For example,you can change the default username and password for the Remote SAP ABAP ApplicationServer from the Edit Instance Parameter pane. You can also addmultiple Remote Host that youwant to monitor from the Edit Instance Parameter pane.

To add SAP Remote nodes from within the Edit Instance Parameter pane, follow these steps:

a. In the Instance Values pane, click . The Edit Parameter dialog box opens.

b. Specify the SAP ABAP Application Server Instance along with Host Name and SID ofRemote SAP ABAP Application Server as shown in the following example:

Example:


Here testnode.hpe.com is the fully qualified SAP Remote Host Name, T01 is the SID forSAP Remote Host and 00 is the SAP Instance number.



OMi MP for SAP enables you to provide the Remote SAP ABAP Application Servercredentials in the following combinations:

i. Remote Host Name (fully qualified) Single SAP SID andMultiple ABAP ApplicationServer Instance.

Example:




ii. Remote Host Name (fully qualified) Multiple SAP SID and ABAP Application ServerInstance.

Example:




iii. Multiple Remote Host Name (fully qualified) with SAP SID and ABAP ApplicationServer Instance.

Example:


testnode01.hpe.com_T01_00

testnode02.hpe.com_T01.3_00


not shown. To show expert parameters, click Show Expert Parameters.

7. Click Next.





9. Click Finish.



Note:After deploying SAP Discovery Aspect, youmust verify if the SAP CIs are populated in theBSM 9.2x or OMi 10.x console. To view discovered CIs:

1. Open the Events Perspective pane:

On BSM 9.2x, click Applications > Operations Management > Event Perspective.

OnOMi 10.x, clickWorkspaces > Operations Console > Event Perspective.

2. Select SAP_Deployment view. The SAP CIs are populated in the Browse Views.

3. Select SAP_ABAP_Deployment andSAP_J2EE_Deployment view to visualize therespective SAP Application Server CIs.

Task 4: Configuring SAP Node for ABAP Application

Server Monitoring

Youmust complete the following tasks to enable the OMi MP for SAP for monitoring SAP ABAPApplication Server:

1. Apply OMi MP for SAP Transport

Youmust copy the OMi MP for SAP transport files from instrumentation folder to the SAPtransport directories on each SAP NetWeaver central instance and apply them.

2. Configure SAP User for OMi

Youmust set up an SAP User for OMi so that OMi MP for SAP can log on to SAP whenever OMiMP for SAP applications, monitors, or actions need access to SAP.

3. Copy lib files to Instrumentation folder

Youmust copy the SAP RFC library files to the instrumentation folder on the SAP managed node.

4. For Solaris managed node, configure LD_LIBRARY_PATH to 32-bit libgcc_s.so path

Youmust configure LD_LIBRARY_PATH to 32-bit libgcc_s.so path, if you aremonitoring aSolaris managed node.

For more information about Configuring SAP Node for ABAP Application Server Monitoring, seeOMiMP for SAP Installation Guide.



Task 5: Deploying SAP ABAP Configuration Aspect

Note:Youmust deploy SAP ABAP Configuration Aspect before deploying SAP ABAPManagement Templates.

To deploy SAP ABAP Configuration Aspect on SAP ABAP Application Server, follow these steps:





Configuration Folders > ERP Management > SAP NetWeaver Application Server > SAPABAP Aspects

3. In the ABAP Aspects folder, select theSAP ABAP Configuration Aspect, and then click to

open the Assign and Deploy Wizard.

4. In theConfiguration Item tab, click the SAP ABAP Application Server Central Instance you wantto deploy the SAP Aspects. For more information about SAP ABAP Aspects that supports SAPCentral Instance and Application Server, seeOMi MP for SAP ABAP Monitoring TemplateConfiguration Files table in Deployment Scenarios.

Note:Youmust not select the SAP ABAP Application Server configured as part ofSAP ABAP Remote Configuration Aspect. For more information "DeployingSAP ABAP Remote Configuration Aspect ".

5. Click Next. TheRequired Parameters tab opens.

6. Select SAP ABAP Application Server Client parameter and click .

The Edit Parameter: SAP ABAP Application Server Client opens.

7. Click Value, specify the value, and then click OK.

8. Click Next to go toAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x.You can edit the default values for parameters inAll Parameters tab.



Note: To change the default values of Mandatory Parameter for SAP ABAP Application

Server, you can select the parameter and then click . The Edit Parameter dialog box

opens. Click Value, specify the value, and then click OK.

9. Click Next.





11. Click Finish.

Data Collection

Frequency (polling interval) at which each Aspect must bemonitored is predefined with a default valuein a specific frequency parameter. Frequency parameter is an expert parameter that is defined for eachof themetrics regardless of whether they are for generating events or not.

Following are the four predefined frequency parameters:

Parameter Frequency

Very High 5mins

High 15mins

Medium 1 hour

Low 24 hours

After Management Templates and Aspects are deployed, collector is triggered based on the predefinedfrequency parameter in a specific Aspect. You canmodify the default value of the parameter atfollowing two levels:

l During deployment of theManagement Template or Aspects using theManagement Templates &Aspects pane.

l After deployment using the Assignments & Tuning pane.

For more information about how tomodify the parameter values, see Types of Parameters.



Task 6: Identifying and Deploying an

SAP Management Template

Note:Youmust deploy the SAP Discovery Aspect even if the CIs are already populated by anyother source such as SiteScope, DDM, and so on. For more information, see "Task 3: Deployingthe SAP Discovery Aspect".

OMi MP for SAP contains two separate set of Management Templates and Aspects for monitoring theABAP and J2EE Application Servers in your SAP Landscape. TheOMi MP for SAP also contains a setof SAP ABAP Monitoring Templates which you can configure to run at regular intervals to collectinformation regarding various functionality of ABAP Application Servers in your SAP Environment. Formore information about ABAP Monitoring Templates, see "RemoteMonitoring with SAP ABAPMonitoring Templates ".

Deploying an SAP Management Template

Youmust identify the SAP Management Template suitable for your SAP environment beforedeployment by following these recommendations:

l Formonitoring the basic functionality of SAP ABAP Application Server that comprises any of thesecomponents - health, dump status, batch job health, transport, user health, processes anddispatcher, work processes, security, and RFC destinations, you can deploy EssentialSAP ABAP Management Template.

l For in-depth and detailedmonitoring of SAP ABAP Application Server environments, you candeploy Extensive SAP ABAP Management Template.

l Formonitoring the basic functionality of SAP J2EE Application Server that comprises any of thesecomponents - SAP J2EE requests, system and application thread pool, memory, and transactionstatus, you can deploy Essential SAP J2EE Management Template.

l For in-depth and detailedmonitoring of SAP J2EE Application Server environments, you can deployExtensive SAP J2EE Management Template.

To deploy OMi MP for SAP Management Templates, follow these steps:







For ABAP Application Server:

Configuration Folders > ERP Management > SAP NetWeaver Application Server > ABAPManagement Templates

For J2EE Application Server:

Configuration Folders > ERP Management > SAP NetWeaver Application Server > JAVAManagement Templates

3. In theSAP Management Templates folder, click theManagement Template that you want todeploy, and then click . The Assign and Deploy wizard opens.

4. In theConfiguration Item tab, click the SAP system or SID to which you want to assign theManagement Template, and then click Next. You can select multiple items by holding down theCtrl orShift key while selecting them.

5. In theRequired Parameters tab, youmust specify themandatory parameters.

For J2EE:

a. Select the Java Installation Directory parameter in the list, and then click the . The Edit

Parameter: Java Installation Directory dialog box opens.

b. Click Value, specify the value, and then click OK.

c. Select theSAP J2EE Application Server Instance User Name parameter in the list, and

then click the . The Edit Parameter: SAP J2EE Application Server Instance User Name

dialog box opens.

d. Click Value, specify the value, and then click OK.

e. Select theSAP J2EE Application Server Instance Password parameter in the list, and

then click the . The Edit Parameter: SAP J2EE Application Server Instance Password

dialog box opens.

f. Click Value, specify the value, and then click OK.

For ABAP:



Edit Parameter dialog box opens. Click Value, specify the value, and then click OK.



Note: In theAll Parameters tab on BSM 9.2x orParameter Summary tab onOMi 10.x, youcan override the default values of a parameter. You can specify a value for each parameter attheManagement Template level. By default, parameters defined as expert parameters are not

shown. To show expert parameters, click Show Expert Parameters.

7. Click Next.

8. (Optional). If you do not want to enable the assignment immediately, clear the Enable AssignedObjectsEnable Assignment(s) check box.




9. Click Finish.

Note: The username given during the deployment of aManagement Templatemust haverequired privileges for OMi MP for SAP to collect data. You can create separate user forABAP and J2EE Application Servers. You can also create a single SAP user with necessaryprivileges to collect data from ABAP and J2EE Application Servers.

Note:Data logging is disabled by default for SAP ABAP Application Server. Youmust run theSAP ABAP Application Server - Start Performance Agent tool to enableSAP ABAP data logging.

Task 7: Deploying SAP Aspects

If you are usingMonitoring Automation for Servers license, youmust deploy the OMi MP for SAPAspects to the SAP CIs.

Note:Youmust deploy the SAP Discovery Aspect even if the CIs are already populated by anyother source such as SiteScope, DDM, and so on. For more information, see "Task 3: Deployingthe SAP Discovery Aspect".

Note:Youmust deploy SAP ABAP Configuration Aspect before deploying otherSAP ABAP Aspects.

Deploying SAP ABAP Configuration Aspect on SAP Managed Nodes

To deploy SAP ABAP Configuration Aspect on SAP managed nodes, follow these steps:








3. In the SAP ABAP Aspects folder, select theSAP ABAP Configuration Aspect, and then clickAssign and Deploy Item to open the Assign and Deploy Wizard.

4. In theConfiguration Item tab, click the appropriate SAP managed node to which you want todeploy the SAP ABAP Configuration Aspect. Click Next to accept the CIs and go toRequiredParameters.


a. Select theSAP ABAP Application Server Instance Name parameter and click . The

Edit Parameter dialog box opens.

b. In the Edit Instance Parameter pane, select theSAP ABAP Application Server Instance

Name parameter and click . The Edit Parameter dialog box opens.

c. Click Value, specify the value in the following format:

ShortHostName_SAPSID_SAPInstNum_ABAP

Example:

TestNode_W09_00_ABAP

d. Click OK.

e. Select theSAP ABAP Application Server Client parameter in the list, and then click .

The Edit Parameter: SAP ABAP Application Server Client dialog box opens.

f. Click Value, specify the SAP ABAP server client number, and then click OK.

Example:

001

g. Select theSAP ABAP Application Server Instance Number parameter and click . The

Edit Parameter dialog box opens.



h. Click Value, specify the SAP ABAP server instance number, and then click OK.

Example:

00

i. Select theSAP ABAP Host Name parameter and click .

The Edit Parameter dialog box opens.

j. Click Value, specify the SAP managed node name (fully qualified) within parenthesis.

Example:

(TestNode.hpe.com)

k. Click OK.




7. Click Finish.

Deploying OMi MP for SAP Aspects

To deploy OMi MP for SAP Aspects on SAP Managed Nodes, follow these steps:





For ABAP Application Server:


For J2EE Application Server:

Configuration Folders > ERP Management > SAP NetWeaver Application Server >JAVA Aspects

3. In the specific SAP Aspects folder, select the SAP Aspect you want to deploy, and then click

Assign and Deploy Item to open the Assign and Deploy Wizard.



4. In theConfiguration Item tab, click the appropriate SAP managed node to which you want todeploy the SAP Aspect. You can select multiple items by holding down theCtrl orShift key whileselecting them. Click Next to accept the CIs and go toRequired Parameters.


For J2EE:

a. Select the Java Installation Directory parameter in the list, and then click . The Edit

Parameter: Java Installation Directory dialog box opens.

b. Click Value, specify the value, and then click OK.

c. Select theSAP J2EE Application Server Instance User Name parameter in the list, and

then click . The Edit Parameter: SAP J2EE Application Server Instance User Name dialog

box opens.

d. Click Value, specify the value, and then click OK.

e. Select theSAP J2EE Application Server Instance Password parameter in the list, and

then click . The Edit Parameter: SAP J2EE Application Server Instance Password dialog

box opens.

f. Click Value, specify the value, and then click OK.

For ABAP:






For J2EE:

To change the default values of SAP J2EE Application Server Instance Name parameter, you can

select the parameter and then click . The Edit Parameter dialog box opens. Click Value,specify the value, and then click OK.

For ABAP:



To change the default values of Mandatory Parameter for SAP ABAP Application Server, you can

select the parameter and then click . The Edit Parameter dialog box opens. Click Value,specify the value, and then click OK.

7. Click Next.





9. Click Finish.

Task 8: Configuring SAP ABAP Monitoring

Templates

TheOMi MP for SAP contains SAP ABAP Monitoring Templates which enables you tomonitor specificfunctionality of SAP ABAP Application Server. A set of SAP ABAP Monitoring Templates providedwith OMi MP for SAP contains out-of-the-box configuration which enables deployment without anymanual configuration. OMi MP for SAP enables you to configure SAP ABAP Monitoring Template formonitoring functionality specific to your SAP environment.

The SAP ABAP Monitoring Templates with out-of-the-box configuration are listed in the following table:

SAPABAP Monitoring Template Description

SAPABAP_CCMSIntegrationMon SAP ABAP Monitoring Template for monitoring the output ofSAP CCMS monitoring infrastructure.

SAPABAP_DispMon SAP ABAP Monitoring Template for monitoring the size,content and status of various queues for different types of SAPwork processes.

SAPABAP_DumpMon SAP ABAP Monitoring Template for monitoring the runtimeerrors that occur on the SAP ABAP system.

SAPABAP_LckChkMon SAP ABAP Monitoring Template for monitoring the Enqueueprocess whichmanages the SAP ABAP logical locks fordifferent SAP transactions and SAP reports.

SAPABAP_Perfmon SAP ABAP Monitoring Template for collecting the SAP



Performancemetrics from different OMi MP for SAPPerformancemonitors.

SAPABAP_SplMon SAP ABAP Monitoring Template for monitoring the number ofSAP ABAP Spooler entries, error generating spool requests,erroneous spooler entries in the print requests.

SAPABAP_StatusMon SAP ABAP Monitoring Template for monitoring the SAP ABAPApplication Server Availability Status.

SAPABAP_TraceMon SAP ABAP Monitoring Template for monitoring all the SAPTrace and Log files for "ERROR".

SAPABAP_TransMon SAP ABAP Monitoring Template for monitoring thesuccessfully imported/exported SAP ABAP transports, failedimports/exports, availability of confirmed/unconfirmed repairsand connections/tptests to the configured systems.

SAPABAP_UpdProcMon SAP ABAP Monitoring Template for monitoring the differentconditions of SAP ABAP update processes like inactive Statusand errors.

SAPABAP_WPMon SAP ABAP Monitoring Template for monitoring the runningwork processes, waiting work process, checking the variousstatus of work process such as Debug, Private or No Restart.

For more information about configuring SAP ABAP Monitoring Templates, see "SAP ABAP MonitoringTemplates".

Monitoring SAP Environment

After you deploy Management Template and Aspects, you can analyze the status of events from thefollowing perspectives:

l Event Perspective

l Health Perspective

l Performance Perspective

Event Perspective

The Event Perspective provides complete information of events from an Event Perspective. In theEvent Perspective, you can view the event information of SAP Application Server CIs that aremonitored by OMi MP for SAP.

To view the Event Perspective of SAP Application Server CIs, follow these steps:



1. Open the Event Perspective pane:

On BSM 9.2x, click Applications > Operations Management > Event Perspective.

OnOMi 10.x, clickWorkspaces > Operations Console > Event Perspective.

The View Explorer pane appears.

2. In theBrowse Views tab, select SAP_Deployment orSAP_ABAP_Deployment orSAP_J2EE_Deployment view that contains the respective SAP Application Server CIs for which youwant to view the events. Alternatively, you can useSearch tab to find Application Server CI.

3. Click the SAP Application Server CI for which you want to view the Event Perspective. The list ofevents for the selected SAP Application Server CI appears on the Event Browser pane.

When you click an event from the Event Browser, the Event Details pane opens where you canview following details:

o General - Displays the detailed information about the selected event such as Severity,Lifecycle State, Priority, Related CIs and so on.

o Additional Info - Displays more detailed information about the attributes of the selected event.

o Source Info - Displays an overview of the information available about the source of theselected event.

o Actions - Displays the list of actions available for a selected event. There are two types ofpossible actions: User Action and Automatic Action.

o Annotations - Displays a list of the annotations attached to the selected event.

o Custom Attributes - Displays a list of the attributes that either an administrator or aresponsible user manually configured and added to the selected event.

o Related Events - Displays an overview of all the events that are related to the event selectedin the Event Browser.

o History - Displays the history of the selected event.

o Resolver Hints - Displays the information used to identify the node and CI associated with anevent.

o Instructions - Displays instruction information designed to help operators handle theassociated event.

o Forwarding - Displays the transfer of ownership details if any, for the events.

Note: Formore information about Managing Events, see theOperations Manager i ConceptsGuide.

Health Perspective



The Health Perspective provides a high-level view of the overall health information of the related CIs inthe context of events. In the Health Perspective, you can view the health information of the SAPApplication Server CIs that aremonitored by OMi MP for SAP.

To view the Health Perspective of SAP Application Server CIs, follow these steps:

1. Open the Health Perspective pane:

On BSM 9.2x, click Applications > Operations Management > Health Perspective.

OnOMi 10.x, clickWorkspaces > Operations Console > Health Perspective.


2. In theBrowse Views tab, select SAP_Deployment orSAP_ABAP_Deployment orSAP_J2EE_Deployment view that contains the respective SAP Application Server CIs for which youwant to view the health related events. Alternatively, you can useSearch tab to find a SAPApplication Server CI.

3. Click the SAP Application Server CI for which you want to view the Health Perspective. The list ofhealth related events for the selected SAP Application Server CI appears on the Event Browserpane.

When you click an event from the Event Browser pane, the following panes appear:

o Health Top View - Displays the health top view of the selected event.

o Health Indicators - Displays the Key Performance Indicators (KPIs) and HIs related to the CIthat you select from the Health Top View pane.

o Actions - Displays the list of actions available for a selected event.

Note: Formore information about Managing Events, see theOperations Manager i ConceptsGuide.

Performance Perspective

Performance Perspective enables you to populate graphs from existing graph templates. You can alsoplot customized graphs by selecting the requiredmetrics for a selected CI.

To view the Performance Perspective of SAP Application Server CIs using graphs, follow these steps:

1. Open the Performance Perspective pane:

On BSM 9.2x, click Applications > Operations Management > Performance Perspective.

OnOMi 10.x, clickWorkspaces > Operations Console > Performance Perspective.




2. In theBrowse Views tab, select SAP_Deployment orSAP_ABAP_Deployment orSAP_J2EE_Deployment view. The performance pane appears, which lists the default graphs availablefor the respective views.

3. Click the graph you want to plot from theGraphs tab, and then click Draw Graphs. Theselected graph is plotted on the right pane.



Chapter 3: ComponentsTheOMi MP for SAP includes the following components for monitoring your SAP environment:

l SAP Management Templates

l SAP Aspects

l SAP ABAP Monitoring Templates

l SAP Parameters

l Run-time ServiceModel (RTSM) Views

l Event Type Indicators (ETIs)

l Health Indicators (HIs)

l Configuration Items (CIs) and Configuration Item Types (CITs)

l Topology Based Event Correlation (TBEC) Rules

l Tools

SAP Management Templates

The SAP Management Templates provide a completemanagement solution for monitoring the healthand performance of different systems and applications in your SAP landscape.

By default, OMi MP for SAP comprises two sets of SAP Management Templates with predefinedsettings tomonitor ABAP and Java application servers in the environment. You can deploy the SAPManagement Templates with the default parameters and seamlessly monitor the systems in yourenvironment. These SAP Management Templates comprises several Aspects which enables you tomonitor the ABAP and Java Application Servers.

Based on themonitoring requirements, you can also customize the SAP Management Templates orcreate SAP Management Templates tomonitor the systems in your environment.


Overview of SAP Management Templates

OMi MP for SAP comprises the following two sets of Management Templates tomonitor ABAP andJava stacks in your SAP environment:

SAP ABAP Monitoring

OMi MP for SAP contains the followingManagement Templates for monitoring ABAP applicationserver:

l "Essential SAP ABAP Management Template"

l "Extensive SAP ABAP Management Template"

SAP J2EE Monitoring

OMi MP for SAP contains the followingManagement Templates for monitoring Java application server:

l "Essential SAP J2EE Management Template "

l "Extensive SAP J2EE Management Template"

How to Access Management Templates

1. For ABAP Application Server:



2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >ABAP Management Templates.

3. For J2EE Application Server:



4. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >JAVA Management Templates.

User GuideChapter 3: Components


Tasks

You can perform the following tasks onOMi MP for SAP Management Template:

How to Deploy OMi MP for SAP Management Templates

Formore information, see Task 6: Identifying and Deploying a SAP Management Template.

How to Automatically Assign OMi MP for SAP Management Templates and OMi MP for SAPAspects

To automatically assign OMi MP for SAP Management Templates or Aspects, follow these steps:

1. Open the Automatic Assignment Rules:

On BSM 9.2x, click Admin > Operations Management > Monitoring > AutomaticAssignment Rules.

OnOMi 10.x, click Administration > Monitoring > Automatic Assignment Rules.

Automatic Assignment Rules consists of Auto-Assignment Rules pane at the top and Parameterspane at the bottom.

2. In theAuto-Assignment Rules pane, click New Assignment and select the appropriateoption. The Create Auto-Assignment Rule wizard opens.

3. In theSelect Target View tab, select the view for which you want to create the automaticassignment rule, and then click Next.

4. In theSelect Item to Assign tab, click theManagement Template or an Aspect that you want toautomatically assign to all the CIs, and then click Next.

The latest version of theManagement Template or Aspect that you want to assign is selected bydefault. Click Next.

5. In theRequired Parameters tab, click Next.

Note: There are no parameters that require editing for this assignment.

6. (Optional). In theAll Parameters on BSM 9.2x orParameter Summary tab onOMi 10.x, you canchange the default value of parameters by following these steps:

a. To edit a parameter, double-click it or select it from the list and click Edit. The EditParameter dialog box opens.

b. Change the default value and click OK.



7. Click Next.

8. (Optional). In theConfigure Option tab, clear theActivate Auto- Assignment Rule check box ifyou do not want to activate the assignment rule immediately. You can activate automaticassignment rules later using the Automatic Assignment Rules pane at Administration >Monitoring > Automatic Assignment Rules.

9. Click Finish to save the changes. The assignment rule is added to the list of auto-assignmentrules.

An assignment may trigger an event to be sent to OMi if one of the following situations applies:

l A deployment job fails.

l An auto-assignment fails.

l An auto-assignment succeeds.

You can check if the automatic assignment rule successfully created the expected assignments byfollowing these steps:

1. Open the Assignments & Tuning pane:

On BSM 9.2x, click Admin > Operations Management > Assignments & Tuning.

OnOMi 10.x, click Administration > Monitoring > Assignments & Tuning.

2. In theBrowse Views tab, select the view you identified while creating your automatic assignmentrule.

3. Expand the view, and select a node that corresponds to the root CI type of the assigned item.Assignments created as a result of Automatic Assignment Rules are shown in the list ofassignments at the top of the right pane, and have the value Auto-Assignment in the columnAssigned By.

You can consider the following options for tuning the assignment:

l Use the Auto-Assignment Rules pane to tune the parameter values for all assignments triggered bythe automatic assignment rule.

l Use the Assignments pane to tune, redeploy, delete, and enable or disable individual assignments.

How to display an Inventory Report for OMi MP for SAP Management Template

The Inventory Report displays theManagement Templates, Aspects, and Policy Templates that areavailable on a server. To display an Inventory Report for OMi MP for SAP Management Template,follow these steps:



1. Select theManagement Template for which you want to create the report for.

2. Click Generate Inventory Report in the Configuration Folders pane.

The report displays theManagement Templates, Aspects, and Policy Templates that are availableon the server.

You can display additional types of reports from the Assignments & Tuning pane.

Essential SAP ABAP Management Template

The Essential SAP ABAP Management Templatemonitors the SAP ABAP systems in yourSAP Landscape. You canmonitor the health and availability of the following system:

SAP ABAP Application Server

How to Access Essential SAP ABAP Management Template

1. Open theManagement Templates & Aspects pane:On BSM 9.2x, click Admin > Operations Management > Monitoring > ManagementTemplates & Aspects.


2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >ABAP Management Templates > Essential SAP ABAP Management Template.

User Interface Reference

Management Template - General

Provides an overview of the attributes of theManagement Template.

UI Element Description

Name Name of ABAP Management Template

Description The description of theManagement Template.

ID A unique Identifier for the GUID version.

Version ID A unique identifier for this version of theManagement Template.

Version The current version of theManagement Template. In this instance, the version of theManagement Template is 1.0.

Change The text that describes what is new ormodified in this version of theManagement




Log Template.

Management Template - Topology View

Provides an overview of the CI type you want to assign to theManagement Template.

UIElement Description

TopologyView

Essential SAP ABAP Management Template uses SAP_ABAP_Deployment forTopology View. It contains the CI types that you want to manage using theManagement Template.

CI Type The type of CIs managed by Essential SAP ABAP Management Template. This is thetype of CI to which theManagement Template can be assigned. The Essential SAPABAP Management Template contains SAP System CI Types.

Extensive SAP ABAP Management Template

The Extensive SAP ABAP Management Templatemonitors the SAP ABAP systems in yourSAP Environment. You canmonitor the health and availability of the following system:


How to Access Extensive SAP ABAP Management Template



2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >ABAP Management Templates > Extensive SAP ABAP Management Template.





Name Name of ABAP Management Template




Description The description of theManagement Template.

ID A unique Identifier for the GUID version.

Version ID A unique identifier for this version of theManagement Template.

Version The current version of theManagement Template. In this instance, the version of theManagement Template is 1.0.

ChangeLog

The text that describes what is new ormodified in this version of theManagementTemplate.




TopologyView



Essential SAP J2EE Management Template

The Essential SAP J2EE Management Templatemonitors the SAP J2EE requests, system andapplication thread pool, memory, and transaction status. You canmonitor the health and availability ofthe SAP J2EE Application Server.

How to Access the Essential SAP J2EE Management Template



2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >JAVA Management Templates > Essential SAP J2EE Management Template.







TopologyView






TopologyView

SAP_Deployment is the topology view for Essential SAP J2EE ManagementTemplate. It contains the CI types that you want to manage using theManagementTemplate.

CI Type The type of CIs managed by Essential SAP J2EE Management Template. This is thetype of CI to which theManagement Template can be assigned. The Essential SAPJ2EE Management Template contains SAP System CI Types.

Extensive SAP J2EE Management Template

The Extensive SAP J2EE Management Templatemonitors the SAP J2EE application serveravailability, SAP J2EE requests, system and application thread pool, memory, transaction, ports,JMX, EJB, sessions, and connector services.

You canmonitor the health and availability of SAP J2EE Application Server.

How to Access the Extensive SAP J2EE Management Template




OnBSM 9.2x, click Admin > Operations Management > Monitoring > ManagementTemplates & Aspects.


2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >JAVA Management Templates > Extensive SAP J2EE Management Template.





TopologyView






TopologyView

SAP_Deployment is the topology view for Essential SAP J2EE ManagementTemplate. It contains the CI types that you want to manage using theManagementTemplate.

CI Type The type of CIs managed by Essential SAP J2EE Management Template. This is thetype of CI to which theManagement Template can be assigned. The Essential SAPJ2EE Management Template contains SAP System CI Types.

SAP Aspects

SAP Aspects are used tomonitor specific functionality of the applications and systems operating inyour SAP Landscape. The systems can be individual or clustered systems. Each SAP Aspect



comprises policy templates, instrumentation, and parameters which enables you tomonitor the healthand performance of SAP systems. Each Aspect provides the ability to monitor a configured applicationserver CI.

Types of SAP Aspects

OMi MP for SAP comprises the following two sets of Aspects to monitor ABAP and Java stacks inyour SAP environment:

l SAP ABAP Monitoring - "SAP ABAP Aspects"

l SAP J2EE Monitoring - SAP J2EE Aspects

How to Access SAP Aspects



2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server.

Tasks

This section provides information about the following tasks:

How to deploy OMi MP for SAP Aspect

Formore information about deploying OMi MP for SAP, see Task 7: Deploying SAP Aspects.

How to Create OMi MP for SAP Aspect




2. Click Configuration Folders > ERP Management > SAP NetWeaver Application Server >ABAP Aspects.



3. In theManagement Templates & Aspects pane, click , and then click Create Aspect. TheAdd New Aspect dialog box opens.

4. In theGeneral tab, specify a Name for the new Aspect, and then click Next.

5. In theCI Types tab, select one or more CITs from Available CI Types pane to associate with the

Aspect and click to add them to the Assigned CI Types pane, and then click Next.

Note:You can useCTRL orSHIFT key to select multiple CITs.

6. In the Instrumentation tab, click Add Instrumentation to add instrumentation categories tothe Aspect. The Add Instrumentation window opens which lists the instrumentation that you wantto add. Select the instrumentation and click OK. Click Next.

Note:You can add instrumentation based on your requirement. You can skip the step if youdo not want to add instrumentation to the Aspect.

7. (Optional). In theAspects tab, click Add Existing Aspect. The Add Existing dialog box openswhich enables you to select an existing Aspect that you want to add within an Aspect. Click anAspect and then click OK. You can useCTRL orSHIFT key to select multiple Aspects. ClickNext.

Note: If you are adding existing Aspects within an Aspect, ensure at least one of the CITs ofthe Aspect that you addmust be a CIT or a parent CIT of the existing Aspect.

8. (Optional). In thePolicy Template tab, click Add Policy Templates on BSM 9.2x orAddPolicy Templates From List onOMi 10.x. The Add New Policy Templates From List to Aspectdialog box on BSM 9.2x or Add New Policy Templates dialog box onOMi 10.xopens.Select thePolicy Templates that you want to add and click OK.

9. If suitable Policy Templates do not exist, follow these steps to add a new Policy Template:

a. Click , and then click Add New Policy Template to create a Policy Template. TheSelect Type for New Policy Template dialog box opens.

b. Select theMeasurement Threshold Policy Template type from the Type drop-down list andclick OK. The Policy Related Information dialog box opens.

c. In the Policy Related Information dialog box, specify a unique policy name and click OK. Anew Policy Template is added.

10. Click Next.

11. In theParameters tab, you see a list of parameters from the Policy Templates that you added to



this Aspect.

To edit parameters:

a. Double-click the parameter or select the parameter from the list and click Edit. The EditParameter dialog box opens.

b. Modify the default parameter value and click OK.

12. In the Add New Aspect dialog box, click Finish to save the aspect. The new aspect appears in theManagement Templates & Aspects pane.

How to Deploy OMi MP for SAP Aspects

Formore information, see Task 7: Deploying SAP Aspects.

SAP ABAP Aspects

SAP ABAP Aspects are used tomonitor the ABAP applications and system operating in your SAPenvironment. These systems can be individual or clustered systems. Each SAP ABAP Aspectcomprises of policy templates, instrumentation, and parameters for monitoring the health andperformance of the SAP systems. Each Aspect provides the ability to monitor a Computer CI.


General Provides an overview of the general attributes of the SAP Aspects.

CI Type The type of configuration items that the Aspect can be assigned to. This is thetype of CI to which theManagement Template can be assigned. The SAPAspects contain Computer and SAP ABAP Application Server CI types.

Instrumentation Provides a single package which contains the binaries for discovery, collection,and data logging.

Aspects Provides an overview of any Aspects that the SAP Aspect contains. You canexpand each item in the list to seemore details about the nested Aspect. TheSAP ABAP Base Aspect is part of all the other Aspects.

PolicyTemplates

Provides an overview of the policy templates that the SAP Aspect contain. Youcan expand each item in the list to seemore details about the policy template.

TheOMi MP for SAP contains the following aspects for monitoring ABAP Application Server:



SAP ABAP Batch Job Health

Monitors the status and collects performance of batch jobs running on the SAP system.

CI TypePolicyTemplate Indicator Description

PolicyType

SapAbapApplicationServer SAPABAP_BatJobMon

NA Configuration file for monitoringthe SAP ABAP Batch jobs thatare exceeding the defined timeinterval, closed before thedefined time interval, and notstarted at the scheduled time.

SAPABAPMonitoringTemplate

SAP ABAP Base

Base Aspect for Monitoring SAP ABAP Landscapes contains Configuration, Scheduler, and Logger.


PolicyType

SapAbapApplicationServer SAPABAP_High

NA Runs the SAP ABAPcollector/analyzer every 15min with favorites metrics

ScheduledTask

SapAbapApplicationServer SAPABAP_Messages

NA SAP MP message template formessage interception.

OpenMessageInterface

SapAbapApplicationServer SAPABAP_Low

NA Runs the SAP ABAPcollector/analyzer Lowschedule

ScheduledTask

SapAbapApplicationServer SAPABAP_Medium

NA Runs the SAP ABAPcollector/analyzer everyMEDIUM schedule

ScheduledTask

SapAbapApplicationServer SAPABAP_VeryHigh

NA Runs the SAP ABAPcollector/analyzer everyVERYHIGH schedule

ScheduledTask

SAP ABAP Configuration

Collects configuration information for SAP ABAP application server CIs.



CI Type Policy Template Indicator DescriptionPolicyType

SapAbapApplicationServer SAPABAP_Configuration

NA SAP ABAPConfiguration Details.

ConfigFile

SAP ABAP Correction and Transport System Status

Monitors the various parameters of SAP Correction and Transport System.


PolicyType

SapAbapApplicationServer SAPABAP_CTSMon

NA Configuration file for monitoringthe SAP Correction andTransport System for differenttransport requests, tasks, andobjects.


SAP ABAP Discovery

Discovers the various ABAP instances in the SAP landscape.

CI Type Policy Template Indicator Description Policy Type

Computer SAPABAP_Discovery

NA SAP ABAP discoverypolicy.

Service Auto-Discovery

SAP ABAP Dump Status

Monitors the runtime errors on the SAP ABAP environment.


PolicyType

SapAbapApplicationServer SAPABAP_DmpMon

NA Configuration file formonitoring the runtime errorsthat occur on the SAP ABAPsystem.


SAP ABAP Idoc Status

Monitors the status of Inbound andOutbound Idocs.




PolicyType

SapAbapApplicationServer SAPABAP_IdocStatusMon

NA Configuration file formonitoring the currentstatus of different Idocs onthe SAP ABAP system.


SAP ABAP Lock Status

Monitors the database locks on the SAP system.


PolicyType

SapAbapApplicationServer SAPABAP_LckChkMon

NA Configuration file for monitoringthe Enqueue process whichmanages the SAP ABAPlogical locks for different SAPtransactions and SAP reports.


SAP ABAP Performance Monitor

Collects the SAP performancemetrics with respect to Oracle database, document statistics,enterprise portal, ICM statistics, batch jobs, buffer, memory, spools, update jobs, users, statisticalrecords, workload statistics, and work processes.


PolicyType

SapAbapApplicationServer SAPABAP_StatRecMon

NA Configuration file for specifyingthe SAP transactions for SAPABAP statistical recordsperformancemonitor.


SapAbapApplicationServer SAPABAP_PerfMon

NA Configuration file for collectingthe SAP Performancemetricsfrom different SAP MPperformancemonitors.


SAP ABAP Processes and Dispatcher Status

Monitors the status of various SAP work processes and the ABAP dispatcher.




PolicyType

SapAbapApplicationServer SAPABAP_ProcMon

NA Configuration file for monitoringthe number of SAP ABAPprocesses.


SapAbapApplicationServer SAPABAP_DispMon

NA Configuration file for monitoringthe size, content and status ofvarious queues for differenttypes of SAP work processes.


SAP ABAP RFC Destination Status

Monitors the failed SAP RFC destinations.


PolicyType

SapAbapApplicationServer SAPABAP_RFCDestMon

NA Configuration file formonitoring the failed SAPRFC destinations based onthe connection type andname of the SAP RFCdestinations.


SAP ABAP Remote Configuration

Configuration input for SAP ABAP remotely monitored nodes.


Computer SAPABAP_RemoteDiscovery

NA Discovers SAP ABAP Remote Nodesalong with SAP System and Instancenumber

ServiceAuto-Discovery

Computer SAPABAP_RemoteConfiguration

NA SAP ABAP Remote ConfigurationDetails.

ConfigFile

SAP ABAP Security Status

Monitors the security status of important SAP users, SAP system parameters and security events.




PolicyType

SapAbapApplicationServer SAPABAP_SecMon

NA Configuration file for monitoringthe SAP ABAP Securityparameters like the privilegesand authorizations of importantSAP users, parameters thataffect the overall SAP.


SAP ABAP Spool Health

Monitors the status of various spool requests in the SAP system.


PolicyType

SapAbapApplicationServer SAPABAP_SplMon

NA Configuration file for monitoringthe number of SAP ABAPspooler entries, error generatingspool requests, and erroneousspooler entries in the printrequests.


SAP ABAP System Change Option Status

Monitors the SAP system change option.


PolicyType

SapAbapApplicationServer SAPABAP_SysChgOptMon

NA Configuration file formonitoring the SAP ABAPSystem Change optionsbased on the global editStatus flag, namespaces,and software components.


SAP ABAP Transport Status

Monitors the status of imports/exports of the transports on the SAP system.




PolicyType

SapAbapApplicationServer SAPABAP_TransMon

NA Configuration file for monitoringthe successfullyimported/exported SAP ABAPtransports, failedimports/exports, availability ofconfirmed/unconfirmed repairsand connections/tptests to theconfigured systems.


SAP ABAP Update Tasks Health

Monitors the status of update tasks running on the SAP system.


PolicyType

SapAbapApplicationServer SAPABAP_UpdProcMon

NA Configuration file formonitoring the differentconditions of SAP ABAPUpdate processes likeinactive Status and errors.


SAP ABAP User Health

Monitors the status of logged-in users.

CI TypePolicyTemplate Indicator Description Policy Type

SapAbapApplicationServer SAPABAP_UsrMon

NA Configuration file formonitoring the SAP ABAPlogged-in Users.

SAP ABAPMonitoringTemplate

SAP ABAP Work Process Health

Monitors the status of the SAP work processes.


PolicyType

SapAbapApplicationServer SAPABAP_ NA Configuration file for monitoring SAP




PolicyType

WPMon the running work processes,waiting work process, checkingthe various Status of workprocess like Debug/Private/NoRestart.

ABAPMonitoringTemplate

SAP CCMS Integration

Monitors the output of SAP CCMS monitor sets.


SapAbapApplicationServer SAPABAP_CCMSIntegrationMon

NA Configuration file formonitoring the outputof SAP CCMSmonitoringinfrastructure.


SAP System Health

Monitors the SAP System availability status and trace file/log file status.


PolicyType

SapAbapApplicationServer SAPABAP_TraceMon

NA Configuration file formonitoring all the SAP Traceand Log files for "ERROR".


SapAbapApplicationServer SAPABAP_StatusMon

NA Configuration file formonitoring the SAP ABAPApplication Server AvailabilityStatus.


SAP Temporary Sequential File Monitoring

Monitors the inconsistencies of the temporary Sequential objects.




SapAbapApplicationServer SAPABAP_TempSeqFileMon

NA Configuration file formonitoring theinconsistencies found inthe SAP ABAP temporarysequential objects.


SAP J2EE Aspects

SAP J2EE Aspects are used tomonitor the Java applications and system operating in your SAPLandscape. The systems can be individual or clustered systems. Each SAP J2EE Aspect comprisesof policy templates, instrumentation, and parameters for monitoring the health and performance of theSAP systems. Each Aspect enables you tomonitor a Computer CI.


General Provides an overview of the general attributes of the SAP Aspects.

CI Type The type of configuration items that the Aspect can be assigned to. This is thetype of CI to which theManagement Template can be assigned. The SAPAspects contain the Computer and SAP J2EE Application Server CI types.

Instrumentation Provides a package which contains the binaries for discovery, collection, anddata logging.

Aspects Provides an overview of SAP Aspects. You can expand each item in the list toseemore details about an Aspect. The SAP J2EE Base Aspect is part of all theother Aspects.

PolicyTemplates

Provides an overview of the policy templates that the SAP Aspect contains. Youcan expand each item in the list to seemore details about the policy template.

TheOMi MP for SAP contains the following aspects for monitoring J2EE Application Server:

SAP J2EE Base

Base Aspect for monitoring SAP Landscapes and contains configuration, scheduler, and logger.




PolicyType

SapJ2eeApplicationServer SAPJ2EE_VeryHigh

NA Runs the SAP J2EEcollector/analyzer everyVERYHIGH schedule

ScheduledTask

SapJ2eeApplicationServer SAPJ2EE_Low

NA Runs the SAP J2EEcollector/analyzer Lowschedule

ScheduledTask

SapJ2eeApplicationServer SAPJ2EE_Medium

NA Runs the SAP J2EEcollector/analyzer everyMEDIUM schedule

ScheduledTask

SapJ2eeApplicationServer SAPJ2EE_High

NA Runs the SAP J2EEcollector/analyzer every 15minwith favorites metrics

ScheduledTask

SapJ2eeApplicationServer SAPJ2EE_Messages

NA SAP MP message template formessage interception.

OpenMessageInterface

SapJ2eeApplicationServer SAPJ2EE_NWStatus

NA Status and availability of SAPJ2EE Application Server.

ScheduledTask

SAP J2EE Application Thread Pool Performance

Monitors the performance of application thread pools of the SAP J2EE system. This Aspect supportsdifferent metrics depending on the SAP versions.

CI Type

PolicyTemplate Indicator

Description

PolicyType

SapJ2eeApplicationServer

SAPJ2EE_0226

NA MinThreadPool Size.

ConfigFile


SAPJ2EE_0219

ApplicationThreadPoolUtilization:High /ApplicationThreadPoolUtilization:Normal

Application Threadspool -Threadpoolusage rate

MeasurementThreshold


SAPJ2EE_0229

NA WaitingTasks

ConfigFile



CI Type


Description

PolicyType

QueueOverflow.


SAPJ2EE_0031

NA MaximumApplication threadspool size.

ConfigFile


SAPJ2EE_0227


Application Threadspool -Threadpoolcapacityrate



SAPJ2EE_0221

NA ActiveThreadsCount.

ConfigFile


SAPJ2EE_0034

NA ActiveApplication threadspool size.

ConfigFile


SAPJ2EE_0033

NA CurrentApplication threadspool size.

ConfigFile


SAPJ2EE_0036

NA Waitingtasksqueuesize in theApplication threadspool.

ConfigFile


SAPJ2EE_0032

NA InitialApplication threadspool size.

ConfigFile


SAPJ2EE_0223

NA InitialThreadPool Size.

ConfigFile



CI Type


Description

PolicyType


SAPJ2EE_0225

NA MaxWaitingTasksQueueSize.

ConfigFile


SAPJ2EE_0220


Application Threadspool -Waitingtasksusage rate



SAPJ2EE_0228

NA WaitingTasksCount.

ConfigFile


SAPJ2EE_0222

NA CurrentThreadPool Size.

ConfigFile


SAPJ2EE_0224

NA MaxThreadPool Size.

ConfigFile


SAPJ2EE_0218


Application threadspool -Usagerate



SAPJ2EE_0030

NA MinimumApplication threadspool size.

ConfigFile


SAPJ2EE_0035

NA Waitingtaskscount intheApplication threadspool.

ConfigFile


SAPJ2EE_0037

NA Waitingtasks

ConfigFile



CI Type


Description

PolicyType

queueoverflowin theApplication threadspool.

SAP J2EE Cluster Manager - Message Server Communication LayerPerformance

Monitors themessage server communication layer in the cluster manager. This Aspect supportsdifferent metrics depending on the SAP versions.


SapJ2eeApplicationServer SAPJ2EE_0066

NA Total number of bytesreceived from theconfigurationManagerthroughmessage servercommunication layer



NA Averagemessageprocessing time



NA Total number of bytesreceived from deploy servicethrough themessage servercommunication layer



NA Total number of bytes sentfrom the cachemanagerthroughmessage servercommunication layer



NA Total number of bytes sentfrom the servlet JSP servicethrough themessage servercommunication layer



NA Current message contextpool size of the J2EE cluster






NA Total number of bytes sentfrom Telnet service throughthemessage servercommunication layer



NA Total number of bytesreceived from the IIOP portthrough themessage servercommunication layer



NA Total number of bytes sentfrom JMS provider throughthemessage servercommunication layer



NA Total number of bytesreceived from the internalconnection of the servicemanager through themessage servercommunication layer



NA Total number of bytes sentfrom the IIOP port throughthemessage servercommunication layer



NA Total number of bytesreceived from webDYNPROservice through themessageserver communication layer



NA Total number of bytes sentfrom connector servicethrough themessage servercommunication layer



NA Total number of bytesreceived from the webservices through themessage servercommunication layer



NA Total number of bytesreceived from the P4 portthrough themessage servercommunication layer






NA Total number of bytesreceived from the specifiedservice through themessageserver communication layer



NA Total number of bytes sentfrom the internal connectionof the servicemanagerthrough themessage servercommunication layer



NA Total number of bytesreceived from JMX servicethrough themessage servercommunication layer



NA Total number of bytes sentfrom the shell servicethrough themessage servercommunication layer



NA Total number of bytesreceived from JMXnotification service throughthemessage servercommunication layer



NA Total number of bytesreceived from securityservice through themessageserver communication layer



NA Total number of bytesreceived from connectorservice through themessageserver communication layer



NA Total number of bytes sentfrom JMX notification servicethrough themessage servercommunication layer



NA Total number of bytesreceived from JMS providerthrough themessage servercommunication layer






NA Total number of bytes sentfrom naming service throughthemessage servercommunication layer



NA Total number of bytesreceived from the SAPsecurity core usermanagement engine servicethrough themessage servercommunication layer



NA Total number of bytesreceived from the Deploydistributor of the servicemanager throughmessageserver communication layer



NA Total number of bytesreceived from the servletJSP service through themessage servercommunication layer



NA Total number of bytesreceived from HTTP portthrough themessage servercommunication layer



NA Total number of bytesreceived from the SLDservice through themessageserver communication layer



NA Total number of bytes sentfrom the deploy distributor ofthe servicemanager throughmessage servercommunication layer



NA Total number of bytes sentfrom HTTP port through themessage servercommunication layer



NA Total number of bytesreceived from the log





configurator through themessage servercommunication layer


NA Total number of bytesreceived from the RFCengine service through themessage servercommunication layer



NA Total number of bytes sentfrom the log configuratorthrough themessage servercommunication layer



NA Total number of bytes sentfrom the P4 port through themessage servercommunication layer



NA Total number of bytes sentfrom the ConfigurationManager throughmessageserver communication layer



NA Total number of bytesreceived from the applicationtracing service through themessage servercommunication layer



NA Total number of bytes sentfrom security service throughthemessage servercommunication layer



NA Total number of bytes sentfrom deploy service throughthemessage servercommunication layer



NA Total number of bytes sentfrom the web servicesthrough themessage servercommunication layer


SapJ2eeApplicationServer SAPJ2EE_ NA Total number of bytes sent Measurement




0061 from webDYNPRO servicethrough themessage servercommunication layer

Threshold


NA Total number of bytes sentfrom the sap security coreuser management engineservice through themessageserver communication layer



NA Total number of bytesreceived from the cachemanager throughmessageserver communication layer



NA Total number of bytes sentfrom JMX service throughthemessage servercommunication layer



NA Total number of bytes sentfrom the specified servicethrough themessage servercommunication layer



NA Total number of bytes sentfrom the SLD service throughthemessage servercommunication layer



NA Total number of bytesreceived from thePRTBRIDGE servicethrough themessage servercommunication layer



NA Total number of bytesreceived from namingservice through themessageserver communication layer



NA Total number of bytesreceived from the shellservice through themessageserver communication layer


SapJ2eeApplicationServer SAPJ2EE_ NA Total number of bytes Measurement




0077 received from telnet servicethrough themessage servercommunication layer

Threshold


NA Total number of bytes sentfrom the PRTBRIDGEservice through themessageserver communication layer



NA Total number of bytes sentfrom the application tracingservice through themessageserver communication layer



NA Averagemessage contextprocess time of the J2EEcluster



NA Total number of bytes sentfrom the RFC engine servicethrough themessage servercommunication layer


SAP J2EE Cluster Manager - Session Communication Layer Performance

Monitors the session communication layer in the cluster manager. This Aspect supports differentmetrics depending on the SAP versions.



NA Total number of bytes sentfrom the IIOP servicethrough the sessioncommunication layer



NA Current size of the HTTPmessage queue in thesession communication layer



NA Total number of bytes sentfrom the JMS providerservice through the sessioncommunication layer






NA Total number of bytes sentfrom the HTTP servicethrough the sessioncommunication layer



NA Total number of bytesreceived from the JMSprovider service through thesession communication layer



NA Current size of the JMSprovider message queue inthe session communicationlayer



NA Total number of bytesreceived from the telnetservice through the sessioncommunication layer



NA Total number of bytesreceived from the HTTPservice through the sessioncommunication layer



NA Average session processingtime



NA Current size of the telnetmessage queue in thesession communication layer



NA Total number of bytes sentfrom the telnet servicethrough the sessioncommunication layer



NA Total number of bytes sentfrom the web servicesthrough the sessioncommunication layer



NA Current size of the internalmessage queue in thesession communication layer



NA Maximum session queuesize






NA Total number of bytes sentfrom the P4 port servicethrough the sessioncommunication layer



NA Current size of the P4message queue in thesession communication layer



NA Current size of the webservices message queue inthe session communicationlayer



NA Total number of bytesreceived from the internalservice through the sessioncommunication layer



NA Total number of bytes sentfrom the internal servicethrough the sessioncommunication layer



NA Current size of the IIOPmessage queue in thesession communication layer



NA Total number of bytesreceived from the IIOPservice through the sessioncommunication layer



NA Total number of bytesreceived from the P4 portservice through the sessioncommunication layer



NA Total number of bytesreceived from the webservices through the sessioncommunication layer


SAP J2EE Configuration

Collects configuration for J2EE application server CIs.




SapJ2eeApplicationServer SAPJ2EE_Configuration

NA SAP J2EE ConfigurationDetails.

ConfigFile

SAP J2EE Configuration Manager and Class Loader Performance

Monitors the cache hit rate and commit duration parameters of the configurationManager and Classloader count.



NA Commitduration



CacheHitRate:High /CacheHitRate:Normal

Configurationmanager -Cache hit rate



NA Configurationmanager -CommitDuration



NA Class loadercount



CacheHitRate:High /CacheHitRate:Normal,CacheHitRate:High /CacheHitRate:Normal

Cache hit rate MeasurementThreshold


NA Class loadercount


SAP J2EE Connections Manipulator Performance

Monitors the number of connections for different ports in the connectionmanipulator. This Aspectsupports only SAP version 7.0 and SAP 7.0x.


SapJ2eeApplicationServer SAPJ2EE_ NA Maximum possible ConfigFile




0021 connections in theconnections manipulator(dispatcher).


NA P4 connections count ofconnections manipulator(dispatcher).

ConfigFile


NA IIOP connections count ofconnections manipulator(dispatcher).

ConfigFile


NA Free connections in the poolof connections manipulator(dispatcher).

ConfigFile


NA Total connections count ofconnections manipulator(dispatcher)



NA Telnet connections count ofconnections manipulator(dispatcher).

ConfigFile


NA HTTP connections count ofconnections manipulator(dispatcher).

ConfigFile


NA JMS connections count ofconnections manipulator(dispatcher).

ConfigFile


NA Other connections count ofconnections manipulator(dispatcher).

ConfigFile

SAP J2EE Connector Service Performance

Monitors themanaged connections for different resource adapters.This Aspect supports only SAPversion 7.0 and SAP 7.0x.



NA Number of freemanagedconnections from ADS





resource adapter


NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_FO resourceadapter



NA Number of usedmanagedconnections from SAP/CAF_EUP_ER resource adapter



NA Number of usedmanagedconnections from SAP/BC_SLM resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SDK_SAPQ resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/CAF_EUP_ERresource adapter



NA Number of usedmanagedconnections fromSAPSR3DB resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SDK_XMLA resourceadapter



NA Number of freemanagedconnections from SAP/CAF_RT resource adapter



NA Number of freemanagedconnections from SDK_SAPQ resource adapter


SapJ2eeApplicationServer SAPJ2EE_ NA Number of freemanaged Measurement




2092 connections from SAP/BC_SLM resource adapter

Threshold


NA Number of clients waiting forpooledmanaged connectionsfor SDK_SAPQ resourceadapter



NA Number of freemanagedconnections from SAP/BC_MIGSERVICE resourceadapter



NA Number of freemanagedconnections from SAP/EP_PRT resource adapter



NA Number of usedmanagedconnections from SDK_SAPQ resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_SLM resourceadapter



NA Number of freemanagedconnections fromSAP/LOCAL_MAINFRAME_POOLresource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe ADS resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_JDO resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/CAF_RT resource





adapter


NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_UDDI resourceadapter



NA Number of usedmanagedconnections from SAP/BC_UDDI resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SDK_CAF resourceadapter



NA Number of usedmanagedconnections fromSAP/CAF/EUP_GP/MAIL_CF resource adapter



NA Number of freemanagedconnections from SAP/BC_UME resource adapter



NA Number of usedmanagedconnections from SAP/BC_JDO resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/EP_PRT resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SDK_ODBO resourceadapter



NA Number of usedmanagedconnections from SDK_XMLA resource adapter



NA Number of freemanagedconnections from SAP/BC_XMLA resource adapter






NA Number of freemanagedconnections from SDK_JDBC resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAPSR3DB resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_MIGSERVICEresource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_SLM resourceadapter



NA Number of freemanagedconnections from SAP/BC_JDO resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_WDRRresource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_WDRRresource adapter



NA Number of freemanagedconnections from SAP/BW_MMR resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/CAF_RT resourceadapter


SapJ2eeApplicationServer SAPJ2EE_ NA Number of clients waiting for Measurement




2034 pooledmanaged connectionsfor SAP/CAF_EUP_GPresource adapter

Threshold


NA Number of clients waiting forpooledmanaged connectionsfor SDK_ODBO resourceadapter



NA Number of usedmanagedconnections from SAP/EP_DQE resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/CAF/EUP_GP/MAIL_CF resourceadapter



NA Number of usedmanagedconnections from SAP/BC_UME resource adapter



NA Number of freemanagedconnections fromSAP/CAF/EUP_GP/MAIL_CF resource adapter



NA Number of usedmanagedconnections from SAP/BC_ADM resource adapter



NA Number of usedmanagedconnections from SAP/EP_PRT resource adapter



NA Number of usedmanagedconnections from SAP/BC_JMS resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/LOCAL_MAINFRAME_POOLresource adapter


SapJ2eeApplicationServer SAPJ2EE_ NA Number of freemanaged Measurement




2108 connections from SAP/BC_UDDI resource adapter

Threshold


NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_FO resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_UME resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/EP_DQE resourceadapter



NA Number of usedmanagedconnections from UTDBresource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/CAF_EUP_GPresource adapter



NA Number of freemanagedconnections from SDK_XMLA resource adapter



NA Number of freemanagedconnections from SAP/BC_WDRR resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/EP_PCD resourceadapter



NA Number of freemanagedconnections from SAP/BC_SLD resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_MON resource





adapter


NA Number of usedmanagedconnections from SAP/BC_MON resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BW_MMR resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_UME resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_SLD resourceadapter



NA Number of usedmanagedconnections fromSAP/LOCAL_MAINFRAME_POOLresource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/LOCAL_MAINFRAME_POOLresource adapter



NA Number of usedmanagedconnections from SDK_JDBC resource adapter



NA Number of usedmanagedconnections from SDK_CAFresource adapter



NA Number of freemanagedconnections from SAP/EP_DQE resource adapter






NA Number of clients waiting forpooledmanaged connectionsfor SDK_JDBC resourceadapter



NA Number of freemanagedconnections fromSAPSR3DB resourceadapter



NA Number of usedmanagedconnections from SAP/BC_MIGSERVICE resourceadapter



NA Number of freemanagedconnections from SAP/CAF_EUP_ER resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/EP_DQE resourceadapter



NA Number of usedmanagedconnections from SAP/BC_WDRR resource adapter



NA Number of freemanagedconnections from SAP/CAF_EUP_GP resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/CAF_EUP_ERresource adapter



NA Number of freemanagedconnections from SAP/CAF_BW_RT resource adapter



NA Number of usedmanagedconnections from SAP/CAF_RT resource adapter



NA Number of freemanagedconnections from SDK_CAF





resource adapter


NA Number of freemanagedconnections from SAP/EP_PCD resource adapter



NA Number of freemanagedconnections from UTDBresource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_JMS resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SDK_CAF resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_SLD resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_JMS resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/CAF/EUP_GP/MAIL_CF resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_JDO resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BW_MMR resource





adapter


NA Maximum number ofmanaged connectionssimultaneously opened fromthe UTDB resource adapter



NA Number of freemanagedconnections from SDK_ODBO resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SDK_XMLA resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SDK_JDBC resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_MIGSERVICEresource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_MON resourceadapter



NA Number of freemanagedconnections from SAP/BC_JMS resource adapter



NA Number of freemanagedconnections from SAP/BC_FO resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/EP_PRT resourceadapter



NA Number of freemanagedconnections from SAP/BC_





ADM resource adapter


NA Number of clients waiting forpooledmanaged connectionsfor ADS resource adapter



NA Number of usedmanagedconnections from SAP/BC_XMLA resource adapter



NA Number of usedmanagedconnections from SAP/BC_FO resource adapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/BC_XMLA resourceadapter



NA Number of usedmanagedconnections from SAP/BW_MMR resource adapter



NA Number of usedmanagedconnections from SAP/CAF_EUP_GP resource adapter



NA Number of usedmanagedconnections from SAP/BC_SLD resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_XMLA resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor SAPSR3DB resourceadapter



NA Maximum number ofmanaged connectionssimultaneously opened fromthe SAP/EP_PCD resourceadapter






NA Number of usedmanagedconnections from SAP/EP_PCD resource adapter



NA Number of usedmanagedconnections from SDK_ODBO resource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/CAF_BW_RTresource adapter



NA Number of clients waiting forpooledmanaged connectionsfor SAP/BC_ADM resourceadapter



NA Number of clients waiting forpooledmanaged connectionsfor UTDB resource adapter



NA Number of usedmanagedconnections from SAP/CAF_BW_RT resource adapter



NA Number of freemanagedconnections from SAP/BC_MON resource adapter



NA Maximum Number ofmanaged connectionssimultaneously opened fromthe SAP/BC_UDDI resourceadapter



NA Number of usedmanagedconnections from ADSresource adapter



NA Maximum Number ofmanaged connectionssimultaneously opened fromthe SAP/CAF_BW_RTresource adapter



NA Maximum Number ofmanaged connections





simultaneously opened fromthe SAP/BC_ADM resourceadapter

SAP J2EE Discovery

Discovers the various JAVA instances in the SAP landscape.

CI Type Policy Template Indicator Description Policy Type

Computer SAPJ2EE_Discovery

NA SAPMP J2EE Discoverypolicy.

Service Auto-Discovery

SAP J2EE EJB Performance

Monitors the performance of the session statefull beans, stateless beans , message driven beans andentity beans. This Aspect supports only SAP version 7.0 and SAP 7.0x.



NA Initial number of beaninstances that will be createdin the pool



NA Number of bean instancesthat this pool can hold



NA Number of bean instancesprovided by this pool, whichare currently used by theapplication or are stored inthe pool



NA Number of times a beaninstance has been activated



NA Number of times a beaninstance has beenpassivated



NA Number of times a beaninstance has been





passivated


NA Number of times a bean hasbeen created



NA The number by which thetotal number of instances inthe pool will be incrementedeach time a new instance isrequested and there are noidle instances in the pool.The value of this elementmust be positive.



NA Number of bean instancesprovided by this pool, whichare currently used by theapplication or are stored inthe pool.



NA Number of bean instancesprovided by this pool whichare currently used by thisapplication.



NA Number of bean sessionsthat are currently passivated



NA Number of bean instancesprovided by this pool whichare currently used by thisapplication



NA Number of times a beaninstance has been activated



NA The time in seconds afterwhich an idle active sessionis passivated








SapJ2eeApplicationServer SAPJ2EE_ NA Number of times a bean and Measurement




2163 its session has beenremoved

Threshold


NA Number of times a bean andits session has beenremoved



NA Number of bean instancesthat this pool can hold






NA The period in seconds sincethe bean's passivation, afterwhich the EJB containerclears the session bean'sinstance from the swap anddestroys the session.



NA Number of bean instancesthat this pool can hold.



NA Number of bean instancesprovided by this pool whichare currently used by thisapplication.



NA Number of bean instancesprovided by this pool, whichare currently used by theapplication or are stored inthe pool.






NA Number of completedsessions



NA Number of active beansessions


















NA Number of times a bean hasbeen created.


SAP J2EE Http Provider Performance

Monitors the performance of requests in the HTTP provider. This Aspect supports different metricsdepending on the SAP versions.



NA Number of skipping requestsof the open connections inthe HTTP provider



NA All Requests Count. ConfigFile


NA HTTP provider - Activethreads count



NA Average request responsetime of the HTTP provider






NA Total number of all requestsin the HTTP provider.

ConfigFile


NA Total count of requests in theHTTP provider.

ConfigFile


NA HTTP provider - Threads in-process rate



NA Number of reading requestsof the open connections inthe HTTP provider



NA Total count of the openconnections of the HTTPprovider



NA Number of reading responseof the open connections inthe HTTP provider



NA Average rate of requests perconnection in the HTTPprovider



NA Number of Keep Alivewaiting connections of theHTTP provider


SAP J2EE JMS Performance

Monitors the JMS session container. This Aspect supports versions starting from SAP 7.1



NA JMS Session container -Connections count



NA JMS Session container -Consumer count



NA JMS Session container -Producers count




SAP J2EE JMX Adapter Performance

Monitors the JMX Adapter protocol.This Aspect supports different metrics depending on the SAPversions.



NA JMX Adapter - Local MBeanRepository size of JMXAdapter



NA Maximum entries in the JMXAdapter cache



NA JMX Adapter - Cluster widenotification listeners



NA Active threads in thenotification queue of JMXAdapter



NA Current entries in the JMXAdapter cache



NA Replaced entries in the JMXAdapter cache



NA Cache hit rate of the JMXAdapter



NA Notification queue size of theJMX Adapter


SAP J2EE JNDI Registry Status

Monitors the JNDI registry.This Aspect supports versions starting from SAP 7.1.



NA JNDI Registry - ByteArray Cache size



NA JNDI Registry - Boundobjects count




SAP J2EE Log Configurator Performance

Monitors the log file size and status of themessages in the log configurator. This Aspect supportsdifferent metrics depending on the SAP versions.



NA Number of error messages inthe Log Configurator.

ConfigFile


NA Number of all loggedmessages in the LogConfigurator.

ConfigFile


NA Total log file size in the LogConfigurator



NA Log Configurator - Total logfile size



NA Number of fatal messages inthe Log Configurator.

ConfigFile


NA Number of warningmessages in the LogConfigurator.

ConfigFile

SAP J2EE Memory Status

Monitors the status of J2EE memory and time out parameter of SAP system. This Aspect supportsdifferent metrics depending on the SAP versions.



NA UsedMemory. ConfigFile


NA AllocatedMemory. ConfigFile


NA Usedmemory. ConfigFile


NA Available Memory. ConfigFile





NA AllocatedMemory. ConfigFile


NA Timeout - Estimatedfrequency per minute



NA Available Memory. ConfigFile

SAP J2EE P4 and IIOP Provider Performance

Monitors the performance of P4 and IIOP service providers. This Aspect supports different metricsdepending on the SAP versions.



NA IIOP Provider - Threadusage rate



NA P4 provider - Failedrequests count



NA P4 provider - Threadusage rate



NA RequestsCount. ConfigFile


NA Number of requests in theP4 provider.

ConfigFile

SAP J2EE Ports Manager Performance

Monitors the accepting threads usage for different ports. This Aspect supports only SAP version 7.0and SAP 7.0x.


PolicyType


NA Accepting threads usage rate ofP4 port.

ConfigFile

SapJ2eeApplicationServer SAPJ2EE_ NA Accepting threads usage rate of ConfigFile




PolicyType

0006 IIOP (SSL) port.


NA Accepting threads usage rate ofJMS provider.

ConfigFile


NA Accepting threads usage rate ofP4 (SSL) port.

ConfigFile


NA Accepting threads usage rate ofIIOP port.

ConfigFile


NA Accepting threads usage rate ofHTTP port.

ConfigFile


NA Accepting threads usage rate ofTelnet.

ConfigFile


NA Accepting threads usage rate ofHTTP (SSL) port.

ConfigFile


NA Accepting threads usage rate ofP4 (HTTP Tunneling) port.

ConfigFile

SAP J2EE Sessions Manager Performance

Monitors the status and performance of sessions and session aggregated data. This Aspect supportsdifferent metrics depending on the SAP versions.

CI Type


Description

PolicyType


SAPJ2EE_2232

UnsuccessfulLogonAttemptsRate:High /UnsuccessfulLogonAttemptsRate:Normal

Security -Unsuccessful logonattempts



SAPJ2EE_2182

NA Number oftimed outsessions inthesecurityserver.

ConfigFile


SAPJ2EE_0204

NA Sessionsmanager -

Measurement



CI Type


Description

PolicyType

Active websessionscount

Threshold


SAPJ2EE_2184

NA Number oflogged offsessions inthesecurityserver.

ConfigFile


SAPJ2EE_0202

NA OpenedWebSessionsCount.

ConfigFile


SAPJ2EE_2180

NA Number ofactivesessions inthesecurityserver.

ConfigFile


SAPJ2EE_2183

NA Number ofinvalidsessions inthesecurityserver.

ConfigFile


SAPJ2EE_2181

NA Totalnumber ofsessions inthesecurityserver.

ConfigFile


SAPJ2EE_0205

NA Sessionsmanager -Number oflogged inusers



SAPJ2EE_0201

NA Openedsecuritysessions

ConfigFile



CI Type


Description

PolicyType

count.


SAPJ2EE_0203

NA OpenedEJBsessionscount.

ConfigFile

SAP J2EE System Thread Pool Performance

Monitors the performance of Java Application Response timeMeasurement requests.

CI TypePolicyTemplate Indicator

Description

PolicyType


SAPJ2EE_0215

SystemThreadPoolUtilization:High /SystemThreadPoolUtilization:Normal

SystemThreadspool -Threadpoolcapacityrate



SAPJ2EE_0024

NA InitialSystemthreadspool size.

ConfigFile


SAPJ2EE_0027

NA Waitingtaskscount intheSystemthreadspool.

ConfigFile


SAPJ2EE_0028

NA Waitingtasksqueue sizein theSystemthreadspool.

ConfigFile

SapJ2eeApplicationSer SAPJ2E NA Current ConfigFile




Description

PolicyType

ver E_0025 Systemthreadspool size.


SAPJ2EE_0214

NA MinThreadPool Size.

ConfigFile


SAPJ2EE_0022

NA MinimumSystemthreadspool size.

ConfigFile


SAPJ2EE_0208

NA SystemThreadspool -Waitingtasksusage rate



SAPJ2EE_0206

SystemThreadPoolUtilization:High /SystemThreadPoolUtilization:Normal

SystemThreadspool -Usage rate



SAPJ2EE_0207

NA SystemThreadspool -Threadpool usagerate



SAPJ2EE_0211

NA InitialThreadPool Size.

ConfigFile


SAPJ2EE_0023

NA MaximumSystemthreadspool size.

ConfigFile


SAPJ2EE_0029

NA Waitingtasksqueueoverflow intheSystem

ConfigFile




Description

PolicyType

threadspool.


SAPJ2EE_0209

NA ActiveThreadsCount.

ConfigFile


SAPJ2EE_0026

NA Activethreadcount intheSystemthreadspool.

ConfigFile


SAPJ2EE_0212

NA MaxThreadPool Size.

ConfigFile


SAPJ2EE_0213

NA MaxWaitingTasksQueueSize.

ConfigFile


SAPJ2EE_0217

NA WaitingTasksQueueOverflow.

ConfigFile


SAPJ2EE_0210

NA CurrentThreadPool Size.

ConfigFile


SAPJ2EE_0216

NA WaitingTasksCount.

ConfigFile

SAP J2EE Transaction Status

Monitors the status of different types of transactions.This Aspect supports versions starting from SAP7.1.



CI Type

PolicyTemplate Indicator Description

PolicyType


SAPJ2EE_2221

NA CommittedTransactionsCount.

ConfigFile


SAPJ2EE_2223

NA RolledBackTransactionsCount.

ConfigFile


SAPJ2EE_2224

NA SuspendedTransactionsCount.

ConfigFile


SAPJ2EE_2222

NA OpenTransactionsCount.

ConfigFile


SAPJ2EE_2226

J2EETransactionSuccessRate:Low /J2EETransactionSuccessRate:Normal

Transaction - SuccessRate



SAPJ2EE_2225

NA TimedOutTransactionsCount.

ConfigFile

SAP J2EE Web Container Performance

Monitors the performance of web container.This Aspect supports different metrics depending on theSAP versions.



NA Number of current securitysessions in the webcontainer



NA Number of timed out securitysessions in the webcontainer



NA Number of timed out HTTPsessions in the webcontainer






NA Number of current HTTPsessions in the webcontainer



NA AllRequestsCount. ConfigFile


NA Total number of all requestsin the web container.

ConfigFile


NA Web container - Averageprocessing time


SAP J2EE Web Services Performance

Monitors the performance of requests for various services.This Aspect supports only SAP version 7.0and SAP 7.0x.



NA Number of requests thathave failed for any reason



NA Implementation time for theservice



NA Implementation time for theservice



NA Pre-processing time for theservice



NA Post-processing time for theservice



NA Pre-processing time for theservice



NA Number of successfullypassed requests



NA Post-processing time for theservice



NA Number of currentlyprocessed requests




SAP JARM Requests Performance

Monitors the performance of Java Application Response timeMeasurement requests.

CI Type


Description

PolicyType


SAPJ2EE_4001

NA Numberof jarmrequests



SAPJ2EE_4005

JARMRequestsAverageCPUTime:High /JARMRequestsAverageCPUTime:Normal

AverageCPU timefor jarmrequests



SAPJ2EE_4206

NA Numberofrequests



SAPJ2EE_4002

NA Numberof jarmrequestspersecond



SAPJ2EE_4003

NA Numberofcomponent callsby alljarmrequests



SAPJ2EE_4004

JARMRequestsAverageResponseTime:High /JARMRequestsAverageResponseTime:Normal

Averageresponsetime ofjarmrequests



SAPJ2EE_4205

NA Numberofcomponent calls



SAPJ2EE_4201

JARMRequestsAverageResponseTime:High /

Averageresponse

Measurement



CI Type


Description

PolicyType

JARMRequestsAverageResponseTime:Normal

time ofJ2EEEngine

Threshold


SAPJ2EE_4204

NA Averageout bounddata



SAPJ2EE_4202

NA Requestspersecond



SAPJ2EE_4006

NA Averageoutbounddata forjarmrequests



SAPJ2EE_4203

JARMRequestsAverageCPUTime:High /JARMRequestsAverageCPUTime:Normal

AverageCPU time


SAP ABAP Monitoring Templates

TheOMi MP for SAP contains a set of SAP ABAP Monitoring Templates which you configure to run atregular intervals to collect information regarding various Aspects of ABAP Application Servers in yourSAP Environment.

TheOMi MP for SAP enables you to extensively customize the SAP ABAP Monitoring Templates tosuit your monitoring requirements. Each SAP ABAP Monitoring Template enables you tomonitor a setof functionality of the ABAP Application Server and has a set of keywords that can be configured tomonitor a specific functionality.

Eachmonitoring template provided with the OMi MP for SAP defines default settings by usingkeywords. Some keywords can only be used with specific SAP ABAP Monitoring Templates.

How to Access SAP ABAP Monitoring Templates

1. Open SAP ABAP Monitoring Templates:On BSM 9.2x, click Admin > Operations Management > Monitoring > Policy Templates.



OnOMi 10.x, click Administration > Monitoring > Policy Templates.

2. In the Policy Templates Group pane:

On BSM 9.2x, click Policy Templates by group> SAP ABAP Monitoring Templates.

OnOMi 10.x, click Policy Management > Templates grouped by type >SAP ABAP Monitoring.

Remote Monitoring with SAP ABAP Monitoring

Templates

The SAP ABAP Monitoring Templates extends the scope of monitoring ABAP Application Servers byenabling you tomonitor SAP ABAP Application Servers on nodes which does not haveOperationsAgent installed. You set up and perform the remotemonitoring of ABAP Application Servers from anode where Operations Agent is installed andOMi MP for SAP Management Templates are deployed.

Tomake use of the remote-monitoring feature provided by the OMi MP for SAP, for example, to monitoran SAP System running in an environment that is not supported by the OMi MP for SAP, you need toperform the following actions. Specifying Individual Remote Servers toMonitor shows how a new lineis required for each additional SAP server, which you want to monitor remotely.

l Enable theRemoteMonitoring keyword by removing the leading hash symbol “#” in eachmonitor’sconfiguration file.

l Define the name of the local host, on which you want to perform themonitoring. Note that you needa new line for each local host that you want to associate with a remote host.

l Define the name of the remote SAP server (RemoteHost), which you want to monitor.

l Make sure that the remote host is configured with SAP ABAP Configuration Aspect.

The RemoteMonitoring keyword accepts the following parameters:

l LocalHost

This is the name of the local OMi MP for SAP managed node (where Agent is installed) with whichyou want to remotely monitor the SAP server defined in the parameter “RemoteHost”.

l RemoteHost

This is the name of the remote SAP server you want to monitor from the host defined in theparameter “LocalHost”.



l SAP System and SAP Number (SAPABAP_CCMSIntegrationMon only)

The SAPABAP_CCMSIntegrationMonMonitoring Template needs to know both the ID and theNumber of the SAP System running on the SAP server defined in the parameter “RemoteHost”.

Specifying Individual Remote Servers to Monitor

#------------------------------------------------------------

# Remote LocalHost RemoteHost

# Monitoring

RemoteMonitoring =sap1 =sdsap1



#------------------------------------------------------------

Formore information about configuring RemoteMonitoring for SAPABAP_CCMSIntegrationMon, see"SAPABAP_CCMSIntegrationMon".

SAPABAP_BatJobMon

The SAPABAP_BatJobMon enables monitoring of SAP ABAP Batch jobs that are exceeding thedefined time interval, closed before the defined time interval, and not started at the scheduled time.

The job-report alert monitor SAPABAP_BatJobMon identifies and reports on batch jobs for the followingconditions:

l A batch job’s run time is either less than or has exceeded a specified limit.

l A specified period of time passes between a batch job’s scheduled and actual start time (and date).

l A batch job has aborted.

Note:You cannot configure SAPABAP_BatJobMon to sendmultiple messages, for example, firstsend aWARNINGmessage if the run time for a batch job exceeds 5minutes and then send aCRITICALmessage if the run time for the same batch job exceeds 10minutes.

The SAP ABAP Monitoring Template SAPABAP_BatJobMon references:



l Reports created using SAP NetWeaver transaction SM36 or SM38.

l Job details including ID number using SAP NetWeaver transaction SM37.

Monitor Type

The SAPABAP_BatJobMonMonitoring Template is of type time frame. One run gathers only one valueset.

Alert Types

The SAPABAP_BatJobMonMonitoring Template has the following alert types. Note that if you want touse the SAPABAP_BatJobMonMonitoring Template, youmust configure the alert types listed below:

l JOB_MAX_RUN_TIME

Defines themaximum allowed run time for a job. SAPABAP_BatJobMonMonitoring Templatesends an alert if the defined job runs for longer than themaximum defined time, specified inminutes.

l JOB_MIN_RUN_TIME

Defines theminimum allowed run time for a job. SAPABAP_BatJobMonMonitoring Templatesends an alert if the defined job does not run for at least as long as the defined time, specified inminutes.

l START_PASSED

It is themaximum allowed delay between scheduled and actual start time for a defined job.SAPABAP_BatJobMonMonitoring Template triggers an alert if the job does not start within the definedtime, specified in minutes.

l JOB_ABORTED

SAPABAP_BatJobMonMonitoring Template sends an alert whenever the jobs specified in itsconfiguration fail to complete successfully.

First Time Monitoring

Whenmonitoring batch job alerts for a particular alert type for the first time, the Job-report monitorSAPABAP_BatJobMonMonitoring Template checks for the following conditions in SAP:

l Jobs which are not yet scheduled to run

l Jobs which ended within the previous two days



l Jobs which are still running

Performance Aspects

On a production system, the SAP standard table tbtco is usually very big. To speed up the databaseselection, you should specify the job names in as much detail as possible. For more information aboutthemeaning of the query conditions in the SAP ABAP Monitoring Template Configuration, see "QueryConditions for Monitoring Templates".

The runtime cost of a job selection grows in the order shown in the following table:

Specified Jobname Sign Option Selection

JOBNAME I EQ Z5_CRITICAL_JOB_1> select via index

JOBNAME I CP Z5_CRITICAL_JOB*> select via index

JOBNAME E CP Z5_CRITICAL_JOB*> sequential scan

Note:Exclude options tend to bemore expensive than include options in performance terms.Using wild cards such as “*” in general database queries is more expensive than in explicit queries.

File Locations

The SAPABAP_BatJobMonMonitoring Template uses the files listed in this table:

File Description

r3moncol (.exe) Collector executable for the batch jobmonitor

r3monjob.cfg Configuration file for monitored jobs and job conditions.

r3monjob.log Trace file for storing trace data.

The SAPABAP_BatJobMonMonitoring Template do not write history information to a specific history file.For more information, see "SAP ABAP Monitoring Templates, Monitoring Template Configuration Files,and History Files".

Environment Variables

The SAPABAP_BatJobMonMonitoring Template uses the environment variables described inEnvironment Variables.

Command-Line Parameters

The SAPABAP_BatJobMonMonitoring Template uses the command-line parameters described inCommand Line Parameters.

Remote Monitoring



Formore information about configuring the SAPABAP_BatJobMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring Job-Report Monitor Alert Types

You can configure SAPABAP_BatJobMonMonitoring Template, the job-report monitor, for each of thelisted alert types for a specific job, a combination of jobs, or for all jobs. You can also define exceptionsfor jobs that need different monitoring conditions. Note that the general rules for using exclude andinclude parameter values, which are of particular importance for these alert types.

Try to avoid using select option CP with the JOBNAME parameter because CP slows down theselection process. If you do use CP, try to limit its scope, for example, instead of specifying CP *,specify CP SAP*.

Parameter Values

This section describes how theOMi MP for SAP interprets include and exclude parameter values for analert type entry. TheOMi MP for SAP compares values in different parameters using ‘and’; the OMi MPfor SAP compares values in the same parameter as follows.

l Include: use ‘or’ to compare the parameters

l Exclude: use ‘and’ to compare the parameters

TheOMi MP for SAP evaluates include values before exclude values, as shown in the following table:

SelectOptions

Alert Type:JOB_MAX_RUN_TIMEExample Configuration of SelectOptions Comparison

1 =JOBNAME =I =CP =ZREP* ==MAX_RUNTIME =I =GT =10 =

OR

2 =JOBNAME =I =CP =SAP* ==MAX_RUNTIME =I =GT =20 =

OR

3 =JOBNAME =E =CP =SAP_ZREP*=

AND

JOB_MAX_RUN_TIME

The JOB_MAX_RUN_TIME alert type defines themaximum allowed run time for a job. Use the JOB_MAX_RUN_TIME alert type to configure the job-report SAPABAP_BatJobMonMonitoring Template togenerate an alert when a job exceeds the value configured in the parameter MAX_RUNTIME.

The following table lists, the parameters that you can use to configure the JOB_MAX_RUN_TIME alerttype and shows the value assigned to the parameters by default. The configuration of any of the



parameters listed in this table is optional. If both parameters are omitted, SAPABAP_BatJobMonMonitoring Template reports all jobs running in the specified time.

ParameterName Description Query Conditions

DefaultValue

JOBNAME Name of the jobs tomonitor = Sign: I, E I

= Opt: EQ, CP, BT CP

= Low <Name of job> *

= High (Only for use with a range)

MAX_RUNTIME

Job run time inminuteswhich, if exceeded,generates an alert.

= Sign I, E I

= Opt: EQ, GE, GT, BT GT

= Low (Specify this parameter as anumber. Otherwise themonitor ends witha dump.)

5

= High (Only for use with a range)

The following examples illustrates both the default and a customized configuration for the JOB_MAX_RUN_TIME alert type.

l Default JOB_MAX_RUN_TIME Configuration

In Default JOB_MAX_RUN_TIME Configuration, an event generating an alert occurs if any reportnamed <jobname>* has a runtime exceeding fiveminutes.

AlertMonFun =ALL =ALL =ALL =ALL =JOBREPORT =1 \

=WARNING =MaxRunTime =R3_Jobs\

=JOB_MAX_RUN_TIME =JOBNAME =I =CP =<jobname>* =\

=MAX_RUNTIME =I =GT =5 =

l Customized JOB_MAX_RUN_TIME Configuration

In Customized JOB_MAX_RUN_TIME Configuration, an event generating an alert occurs if all thereports named SAP*, except reports SAPZ*, have a runtime exceeding tenminutes.

AlertMonFun =ALL =ALL =ALL =ALL =JOBREPORT =1\

=WARNING =MaxRunTime =R3_Jobs \

=JOB_MAX_RUN_TIME =JOBNAME =I =CP =SAP* = \





=WARNING =MaxRunTime =R3_Jobs \

=JOB_MAX_RUN_TIME =JOBNAME =E =CP =SAPZ* = \


TheOMi MP for SAP optional test transport includes a program that you can run to start a long-runningjob. You can use the job to verify that the SAPABAP_BatJobMonMonitoring Template is correctlyconfigured to send amessage to OMi, if a job runs for more than a defined amount of time. If the testcompletes successfully, a message about the test job appears in the OMi message browser. For moreinformation about Transports, see Transports readme file on the OMi managed node. For moreinformation about importing and applying OMi MP for SAP Transports, seeOMi MP forSAPInstallation Guide.

After importing the transport, the installed test program /HPOV/YSPI0002 can be viewed using theSAP ABAP Object Navigator Transaction SE80.

JOB_MIN_RUN_TIME

The JOB_MIN_RUN_TIME alert type defines theminimum allowed run time for a job. Use the JOB_MIN_RUN_TIME alert type to configure the job-report Monitoring Template SAPABAP_BatJobMon togenerate an alert when a job does not run for the time specified in the parameter MIN_RUNTIME.

The following table lists the parameters that you can use to configure the JOB_MAX_RUN_TIME alerttype and shows the value assigned to the parameters by default:

The configuration of any of the parameters below is optional. If both parameters are omitted, all jobsrunning in the specified time frame are reported.

ParameterName Description

QueryConditions

DefaultValue

JOBNAME Name of thejobs tomonitor

= Sign: I, E I

= Opt: EQ,CP, BT

CP

= Low<Name ofjob>

*

= High: a



MIN_RUNTIME

This definestheminimumallowed runtime. Alertsare triggeredfor jobswhich didnot run forthe timespecified (inminutes).

= Sign I, E I

= Opt:EQ,LE, LT,BT

LT

=Low <Min.value inminutes> b

1

= High

aOnly for use with range.

bSpecify this parameter as a number, otherwise themonitor ends with a dump.

The following examples illustrates both the default and a customized configuration for the JOB_MIN_RUN_TIME alert type.

l Default JOB_MIN_RUN_TIME Configuration

In Default JOB_MIN_RUN_TIME Configuration, an event generating an alert occurs if any reportnamed <jobname>* has a runtime of less than oneminute.


=WARNING =MinRunTime =R3_Jobs\

=JOB_MIN_RUN_TIME =JOBNAME =I =CP =<jobname>* = \

=MIN_RUNTIME =I =LT =1 =

l Customized JOB_MIN_RUN_TIME Configuration

In Customized JOB_MIN_RUN_TIME Configuration, an event generating an alert occurs if allreports named SAP*, except reports SAPZ*, have a runtime of less than twominutes.


=WARNING =MinRunTime =R3_Jobs \

=JOB_MIN_RUN_TIME =JOBNAME =I =CP =SAP* = \



=WARNING =MinRunTime =R3_Jobs \



=JOB_MIN_RUN_TIME =JOBNAME =E =CP =SAPZ* = \


TheOMi MP for SAP optional test transport includes a program that you can run to start a short job.You can use the job to verify that the SAPABAP_BatJobMonMonitoring Template is correctlyconfigured to send amessage to OMi if a job runs for less than a defined amount of time. If the testcompletes successfully, a message about the test job appears in the OMi message browser. For moreinformation about Transports, see Transports readme file on the OMi managed node. For moreinformation about importing and applying OMi MP for SAP Transports, seeOMi MP forSAPInstallation Guide.

After importing the transport, the installed test program /HPOV/YSPI0005 can be viewed using theSAP ABAP Object Navigator Transaction SE80.

START_PASSED

The START_PASSED alert type defines themaximum allowed delay between a job’s scheduled andactual start times. Use the START_PASSED alert type to configure the SAPABAP_BatJobMonMonitoring Template to generate an alert if the specified jobs do not start within the configured TIME_SPAN after the scheduled start time. The following table lists the parameters that you can use toconfigure the START_PASSED alert type and shows the value assigned to the parameters by default.

If a job is scheduled but does not have a start time, SAPABAP_BatJobMonMonitoring Templatecannot monitor it until and unless an assigned start time is visible in the SAP database. SAPassociates a start time with a job only when the job assumes a particular status. The following SAP jobstatuses have a start time whichmeans you canmonitor them with SAPABAP_BatJobMonMonitoring Template: Released, Ready, Active, Finished, and Canceled.

The configuration of any of the parameters below is optional. If both parameters are omitted all jobsrunning in the specified time frame are reported.


DefaultValue

JOBNAME Name of the jobs tomonitor = Sign: I, E I



= High 1




DefaultValue

TIME_SPAN The job run time inminutes that specifieswhen an alert should be raised. Note that itis not necessary to use a time range. Youcan specify a particular time instead.

= Sign I, E I

= Opt: EQ, GT, GE, BT GT

=Low 2 <low_value_of_range _in_minutes_past_ scheduled_start_time>

1

=High <high_value_of_ range_in_minutes_past_scheduled_start_time>

1. Only for use with a range.

2. Specify this parameter as a number. Otherwise themonitor ends with a dump.

Default START_PASSED Configuration

In Default START_PASSED Configuration, an event generating an alert occurs if any report named<jobname>* does not start more than oneminute after the scheduled start time.


=WARNING =StartPassed =R3_Jobs \

=START_PASSED =JOBNAME =I =CP =<jobname>* =\

=TIME_SPAN =I =GT =1 =

JOB_ABORTED

The JOB_ABORTED alert type defines the names of the jobs, which fail to complete successfully.Use the JOB_ABORTED alert type to configure the SAPABAP_BatJobMonMonitoring Template togenerate an alert whenever the jobs specified in its configuration fails. The following table lists theparameters that you can use to configure the JOB_ABORTED alert type and shows the value assignedto the parameters by default:

Note: The configuration of the parameter below is optional.

Parameter Name Description Query Conditions Default Value



JOBNAME Name of the jobs to bemonitored = Sign: I, E I



= High 1

1. Only for use when specifying a range.

l Default JOB_ABORTED Configuration

In Default JOB_ABORTED Configuration, an event generates an alert if any report named<jobname>* aborts.


=WARNING =Aborted =R3_Jobs \

=JOB_ABORTED =JOBNAME =I =CP = <jobname>*

l Customized JOB_ABORTED Configuration

In Customized JOB_ABORTED Configuration, an event generates an alert if jobs named SAP_REORG_ABAPDUMPS or ITOTEST are aborted.


=WARNING =Aborted =R3_Jobs \

=JOB_ABORTED =JOBNAME =I =EQ =SAP_REORG_ABAPDUMPS =


=WARNING =Aborted =R3_Jobs\

=JOB_ABORTED =JOBNAME =I =EQ =ITOTEST =

TheOMi MP for SAP optional test transport includes a program that you can run to generate an ABAPdump. You can use the generated dump to verify that the SAPABAP_BatJobMonMonitoring Templateis correctly configured to send amessage to OMi if a job aborts. Formore information about OMi MP forSAP transports, see the transports read-me file on the OMi managed node. For more information aboutimporting and applying OMi MP for SAP transports, see the OMi MP for SAP Installation Guide.

After importing the transport, installed test program /HPOV/YSPI0004 can be viewed using the SAPABAP Object Navigator Transaction SE80.



SAPABAP_CCMSIntegrationMon

The SAPABAP_CCMSIntegrationMonMonitoring Template enables monitoring the output of SAPCCMS monitoring infrastructure.

This section provides detailed information about the contents of the SAPABAP_CCMSIntegrationMonMonitoring Template.

Monitoring Conditions

Youmust define and enable the keywords———:—Severity<Level>, RFCTimeOut,CCMSMonitorSet, and CCMSAcknowledgeMessage. All other keywords in the SAPABAP_CCMSIntegrationMonMonitoring Template are optional.

CCMS Monitor Sets

The XAL interface allows the OMi MP for SAP to read, write, and reset CCMS alerts directly in theCCMS alert-monitor tree. Themost obvious advantage of this feature is that you can use existingCCMS monitor sets as templates to define your ownmonitor sets, which contain only those CCMSalerts you want to monitor with the OMi MP for SAP.

Remember to logon to SAP and define the new CCMS monitor sets which you want the OMi MP forSAP to use to generatemessages before you start the configuration of the SAPABAP_CCMSIntegrationMonMonitoring Template.

Note: To create or modify items in the CCMS monitor tree, you need tomake sure that theMaintenance Function for the CCMS monitor sets is switchedON. You can find theMaintenance function option in theExtrasmenu, for example, Extras > ActivateMaintenance Function.

If you are not interested in receivingmessages concerning all the alerts present in the default monitorset, for example, OperatingSystem, DatabaseClient, and so on, you can expand the individualapplication-server item and select only the alerts which you want to use to generatemessages that willbe sent to OMi.

Make sure that the new monitor sets you define for the OMi MP for SAP are visible to and usable by theOMi user. If you are logged into SAP as the definedOMi user, then you can see only the CCMS monitorsets that aremarked “Public”. If you are logged into SAP as the administrator, you can see all availablemonitor sets, in which case you have to ensure that youmake the new monitor sets you define for theOMi MP for SAP are visible either to the definedOMi user or everyone by using the “Public” option.



Note:Remember to use only ASCII characters when defining the name of a CCMS monitor set asthe OMi MP for SAP cannot currently interpret non-ASCII characters in monitor-set names.

One SAP System/SID can havemultiple monitor sets. If you need to definemultiple monitor sets for aSAP System/SID, remember to include each new monitor set on a new line in themonitor-set sectionof the SAPABAP_CCMSIntegrationMonMonitoring Template configuration, as illustrated in ConfiguringMultiple Monitor Sets. The name you define in themonitor parameter must match the name of themonitor set as it appears in the CCMS alert-monitor tree. The name of monitors must appear in theconfiguration exactly as they are shown in SAP including, for example, forward slashes (/), as shown inConfiguringMultiple Monitor Sets.

Note that the combination of traditional long SAP names and the line break in the example configurationshown in ConfiguringMultiple Monitor Sets disguises the name of themonitor. The complete name ofthe last monitor is: =System / All Monitoring Segments / All Monitoring Contexts. Note that the namesyou use do not have to be this long. In addition, if you want to associate multiple monitors with one,single monitor set, you have to specify each individual monitor on a new line as shown by the first twoentries in ConfiguringMultiple Monitor Sets, where the OMi MP for SAP monitor set has twoMonitors;System and DB_ALERT.

Configuring Multiple Monitor Sets

#----------------------------------------------------------------------------

--

# Monitor Set SAP SAP Monitor Set Monitor

# System Number

CCMSMonitorSet =WA1 =33 =MPSAP =System

CCMSMonitorSet =WA1 =33 =MPSAP =DB_ALE

RT

CCMSMonitorSet =SP6 =00 =SAP CCMS Technical Expert Monitors =System

/\

All Monitoring Segments / All Monitoring

Contexts

#----------------------------------------------------------------------------

--



The default configuration of individual CCMS alert monitors does not always meet the demands of yourenvironment and, in some instances, you will need to change it. You can check and, if necessary,modify amonitor’s properties in thePerformance Attribute tab of theMonitor: Properties andMethods window. If you decide to change themonitor properties, you need to consider the followingpoints:

l Ensure that the severity level of the CCMS Alerts matches the severity level of the OMi messages,which are generated by the CCMS Alerts.

l Ensure that severity-level thresholds configured for a given CCMS alert monitor are appropriate foryour needs.

To open theMonitor: Properties and Methodswindow for a specific CCMS monitor, browse to thedesiredmonitor in themonitor-set tree and either click theProperties button or double-click themonitoryou want to view.

CCMS Alert Monitors

Alerts are themost basic element of the strategy that SAP uses tomonitor the health of the SAPLandscape. Alerts are associated with objects such as disks and CPUs, and objects have attributessuch as response times and usage statistics. The status of the object as well as its performance andavailability over time are important to the SAP System administrator. The SAP NetWeaver CCMS alertmonitor displays the configured alerts (along with any associated objects and attributes) as CCMSmonitors in amonitor tree, which you can browse.

Note: The public monitor sets are visible to (and usable by) all SAP users.

For ease of navigation, the CCMS monitors are grouped into pre-definedmonitor sets, for example, SAPCCMS Technical Expert Monitors or SAP CCMS Admin Workplace. The pre-definedmonitor setscontain a large number of sub sets andmonitors, which can generate thousands of alerts, some ofwhich you really do not need.

If you switch on themaintenance function for the CCMS monitor sets, you can create your ownCCMSmonitor sets, which contain only themonitors for the alerts you want to know about on a regular basis.When you have created your ownmonitor sets, you can add them to themonitor-set tree and configurethe OMi MP for SAP tomonitor them. In this way, you can reduce the alerts you hear about and theinformation you receive so that it is easier to manage.When a condition is reported in the SAPNetWeaver CCMS monitor, themonitoring object and its attributes are included in the resulting alert.

CCMS Acknowledge Message

The CCMSAcknowledgeMessage feature determines whether SAPABAP_CCMSIntegrationMonMonitoring Template tells SAP to automatically acknowledge (complete) CCMS Alerts, whichmatchthe defined conditions. Enabling the CCMSAutoAcknowledge feature in SAPABAP_



CCMSIntegrationMonMonitoring Template is same as selecting the alert and clicking the [CompleteAlert] button in SAP CCMS.

Automatically Acknowledging CCMS Alerts

# Triggers auto-acknowledge of CCMS alerts

#------------------------------------------------------------

# CCMSAcknowledgeMessage SAP Ack. filtered Enable=1

# System Messages Disable=0

CCMSAcknowledgeMessage =ALL =0 =0

CCMSAcknowledgeMessage =SP6 =0 =0

#------------------------------------------------------------

You can enable or disable the auto-acknowledgment feature for specific SAP Systems defined onindividual lines in the SAPABAP_CCMSIntegrationMonMonitoring Template configuration. However,note that if you disable the auto-acknowledgment feature (=0) for a specific SAP System, SAPABAP_CCMSIntegrationMonMonitoring Template ignores the setting forAck. Filtered Messages defined onthe same line.

If you enable theAck. Filtered Messages keyword, messages that are filtered out (and not sent toOperations Agent) by theAlerMonSyslog specifications (whichmeans, setting Disabled=0 in theappropriate line) will be acknowledged in CCMS. Therefore, these alerts will not be visible in the OMimessage browser or in SAP CCMS anymore.

Note: If you enable theCCMSAcknowledgeMessage keyword, you also need tomake sure thatyou enable the Severity<Level> keyword. The Severity<Level> keyword allows you to filterCCMS alerts according to severity.


The following table lists the environment variables, which you can use to configure the SAPABAP_CCMSIntegrationMonMonitoring Template.

Environment Variable Description

SAPOPC_DRIVE The Windows drive where the Operations Agent is running, for example, E:\usr\...

SAPOPC_HISTORYPATH Path to the r3monal history file

SAPOPC_R3MONAL_CONFIGFILE

Name of the r3monal configuration file



SAPOPC_SAPDIR TheWindows drive where SAP NetWeaver is running, for example,E:\usr\sap

SAPOPC_TRACEPATH Path to the r3monal trace file

File Location

The SAPABAP_CCMSIntegrationMonMonitoring Template uses the default files listed in the followingtable:

File Name Description

r3monal (.exe) Executable for the SAP NetWeaver CCMS alert monitor

r3monal.cfg Configuration file for the CCMS alert monitor

r3monal.his History file for storing data after eachmonitor run

Remote Monitoring

The RemoteMonitoring keyword allows you to configure the OMi MP for SAP on local host to monitoran SAP instance on a remote host. Note that SAP System and SAP Number are only required bySAPABAP_CCMSIntegrationMonMonitoring Template.

Enabling Remote Monitoring

#---------------------------------------------------------

# Remote Host Localhost Remotehost SAP System SAP Number

RemoteMonitoring =hpspi003 =ovsdsap6 =SP6 =00

#-------------------------------------------------------

RFC Time Out

You use the RFCTimeout keyword to define themaximum amount of time in seconds before an RFCXAL function call is canceled, for example: =120. You need to set a time-out which takes into accountthe environment in which SAP is running. For example, if the RFC call takes longer than expected tocomplete, that is, to receive a reply to the initial request, the SAP System is probably down or has aserious performance problem. Note that after the RFC call completes and SAP allocates a free Dialogprocess, the time limit no longer applies.

Setting the Time-out period for XAL Function Calls

#------------------------------------------------------------

# Max. time in sec. before a RFC XAL function call is

# canceled. If the RFC call takes longer than expected, the



# system is probably down or has a major performance problem.

RFCTimeOut = 120

#------------------------------------------------------------

Severity Levels

The Severity Values section of the SAPABAP_CCMSIntegrationMonMonitoring Template defineshow you filter CCMS alerts in the CCMS monitor trees you aremanaging with SAPABAP_CCMSIntegrationMonMonitoring Template andmap the severity level of the filtered CCMS Alerts tothe desired severity level for the corresponding OMi messages. You can use the keywordsSeverityWarning and SeverityCritical in combination with the CCMSAcknowledgeMessage keyword,which is described inmore detail in "CCMS AcknowledgeMessage".

By adding a new line for individual combinations of SAP system ID and SAP number, you can restrictthe severity mapping between CCMS Alerts andOMi messages to a specific SAP System ID and SAPNumber.

Following is the Default settings for Severity Levels in SAPABAP_CCMSIntegrationMon:

#---------------------------------------------------------

#Severity SAP SAP Enabled=1 OpCSeverity

#Values System Number Disabled=0

SeverityWarning =ALL =ALL =0 =WARNING

SeverityCritical =ALL =ALL =1 =CRITICAL

#-------------------------------------------------------------

You can edit the severity levels in SAPABAP_CCMSIntegrationMonMonitoring Template in one of thefollowing ways:

l Enable or disable severity levels

If you want to disable (=0) the generation of messages for CCMS alerts with the severity warning,add a new (or change the existing) SeverityWarning line as follows:

SeverityWarning =ALL =ALL =0 =WARNING

l Change how the OMi MP for SAP maps CCMS severity levels to message severity levels inOMi

If you want the OMi MP for SAP to report all SeverityWarning events as critical, add a new (orchange the existing) SeverityWarning definition, as follows:



SeverityWarning =ALL =ALL =1 =CRITICAL

l Define SID-Specific exceptions

If you want the OMi MP for SAP report as critical all Severity Warning events that occur on SAPsystem LP2, leave the default settings for ALL systems and add the following line:

SeverityWarning =LP2 =ALL =1 =CRITICAL

Following is an example of Severity Levels in SAPABAP_CCMSIntegrationMonMonitoring Template Configuration

# A Monitor Set defines the messages you want to forward to OMi.

#------------------------------------------------------------------------

# Monitor Set SAP SAP Monitor Set Monitor

# System Number

#CCMSMonitorSet =WA1 =33 =MPSAP =System

#CCMSMonitorSet =WA1 =33 =MPSAP=DB_ALERT

#CCMSMonitorSet =SP6 =00 =SAP CCMS Technical Expert Monitors

=System / All Monitoring Segments / All Monitoring Contexts

#------------------------------------------------------------------------

# Remote Host Localhost Remotehost SAP SAP

# System Number

#RemoteMonitoring =hpspi003 =ovsdsap6 =SP6 =00

#------------------------------------------------------------------------

# CCMSAcknowledgeMessage SAP Ack. filtered Enable=1

# System Messages Disable=0

CCMSAcknowledgeMessage =ALL =0 =0

CCMSAcknowledgeMessage =SP6 =0 =0

# XMI compatibility mode

# makes the r3monal send syslog messages r3monxmi style

#------------------------------------------------------------------------

# XmiSyslogMode Enabled =1



# Disabled =0

XmiSyslogMode =0

# Syslog filtering

#------------------------------------------------------------------------

# Alert Classes SAP SAP SyslogId Enabled=1

# System Number From To Disabled=0

AlerMonSyslog =ALL =ALL =A00 =MZZ =1

AlerMonSyslog =ALL =ALL =N00 =ZZZ =0

AlerMonSyslog =LPO =01 =A00 =ZZZ =1

Trace Levels

Formore information about the trace levels the alert monitors used, in particular, the trace levelsavailable to the SAPABAP_CCMSIntegrationMonMonitoring Template, see "TraceLevel".

Alert Classes

In the alert-classes section of the SAPABAP_CCMSIntegrationMonMonitoring Templateconfiguration, you define how theOMi MP for SAP's CCMS alert monitor filters syslog events in theSAP System; the filteringmechanism ensures that you extract and display only those syslog eventsthat you are interested in seeing. You filter the syslog events that you want to monitor by specifyingranges of message numbers (syslog IDs). Each line of the alert-classes section of the SAPABAP_CCMSIntegrationMonMonitoring Template configuration is set up in a particular way. Each entrydefines monitoring for a specified range of syslog events. You can specify which syslog events tomonitor by enabling or disabling ranges of syslog IDs either globally or for specified SAP systems andinstances.

In Syslog events in the SAPABAP_CCMSIntegrationMonMonitoring Template configuration, monitorsthe syslog events with IDs A00 throughMZZ on all SAP Systems and SAP numbers but does notmonitor the syslog events with IDs N00 through ZZZ on all SAP Systems and numbers. Syslog eventmonitoring is enabled on SAP System LPO for IDs A00 through ZZZ.

Syslog events in the SAPABAP_CCMSIntegrationMon Monitoring Template Configuration

# Syslog filtering

#-------------------------------------------------------------

# Alert Classes SAP SAP SyslogId Enabled=1

# System Number From To Disabled=0



AlerMonSyslog =ALL =ALL =A00 =MZZ =1

AlerMonSyslog =ALL =ALL =N00 =ZZZ =0

AlerMonSyslog =LPO =01 =A00 =ZZZ =1

#--------------------------------------------------------------

Monitoring the CEN

The central monitoring system (CEN) is a single SAP system that you designate as the central point ofcontrol for CCMS alerts originating from all over themonitored SAP landscape. The CEN conceptallows you to reduce the overhead of monitoring andmanagingmultiple SAP systems by makingessential information concerning problem alerts available in one, central location. After you configureSAP to use the CEN for the central management of CCMS alerts, you can use the SAPABAP_CCMSIntegrationMonMonitoring Template to intercept the CCMS alerts destined for the CEN and usethe alerts to generatemessages, which it forwards to the OMi message browser.

Testing the Configuration

TheOMi MP for SAP’s optional test transport includes a program that generates an ABAP dumpwhichyou can use to verify that the SAPABAP_CCMSIntegrationMonMonitoring Template checks thesyslog and sends amessage to OMi if a dump occurs in the SAP System. If the test completessuccessfully, a message about the test dump appears in the OMi message browser. Note that this testworks only if you configure SAPABAP_CCMSIntegrationMonMonitoring Template tomonitor theappropriate SAP CCMS monitor sets, for example: <SAPSID>/R3Abap/Shortdumps.

For more information about OMi MP for SAP transports, Transports readme file on the OMi managednode. For more information about importing and applying OMi MP for SAP transports, see theOMiManagement Pack for SAP Installation Guide. After importing the transport, you can view the testprograms installed by using the SAP transaction SE80 to open the ABAP object navigator andbrowsing to the report (or program) /HPOV/YSPI0004.

SAPABAP_CTSMon

The SAPABAP_CTSMonMonitoring Template enables monitoring of SAP Correction and TransportSystem for different transport requests, tasks, and objects. Data collection is application-serverindependent.

The SAPABAP_CTSMonMonitoring Template uses the following SAP elements as a reference:

l Transport requests and object lists created using SAP NetWeaver transaction SE01

l Tasks created using SAP NetWeaver transaction SE09



Monitor Type

The SAPABAP_CTSMonMonitoring Template is of type time frame. Onemonitor run gathers only onevalue set.

Alert Types

The CTS monitor has the following alert types:

l REQUEST_CREATED

Defines when new requests generate an alert

l REQUEST_RELEASED

Defines whether to generate an alert for a released request

l TASK_CREATED

Defines if new tasks should generate an alert

l TASK_RELEASED

Defines whether to generate an alert for released tasks

l OBJECT_USED

Defines whether objects used by a task or a request generate an alert

l OBJECT_RELEASED

Defines whether to generate an alert when a request or task releases an object

File Locations

The SAPABAP_CTSMonMonitoring Template uses the files listed in this table:

File Description

r3moncol (.exe) Collector executable for the CTS monitor

r3moncts.cfg Configuration file for the CTS monitor.

r3moncts.log Trace file for storing trace data.

The SAPABAP_CTSMonMonitoring Template do not write history information to a specific history file.




The SAPABAP_CTSMonMonitoring Template uses the environment variables describedin"Environment Variables".


The SAPABAP_CTSMonMonitoring Template uses the command line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_CTSMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring SAPABAP_CTSMon Monitoring Template Alert

Types

You should keep inmind the following rules when configuring the alert-type parameters for theSAPABAP_CTSMonMonitoring Template:

l By default, the OMi MP for SAP selects all data for each parameter.

l You can restrict data by specifying some or all of the parameters for the alert type.

l The SAPABAP_CTSMonMonitoring Template only considers the named parameters if you changedefault values and overrides the default value ALL for the unspecified parameters.

Use the parameter TRFUNCTION to configure the REQUEST_CREATED, REQUEST_RELEASED,TASK CREATED and TASK RELEASED alert types.

TRFUNCTION has request functions which you can specify using the letter codes indicated in thefollowing table:

Letter Code Function Description

A Request: Unclassified request becomes K, L orW with first object

C Transport with change authorization



D Patch

K Request: Change request with destination consolidation layer

L Request: Local request without transport

R Task: Repair

S Task: Development/correction

T Request: Transport without originals

U Dummy

W Request: Customizing request with cons. layer destination

X Task: Unclassified task becomes S or R with first object

Z (task without request) SE09memory usage

Note: In the descriptions of the use of this parameter for each of the CTS alert types, only the lettercode is shown.

REQUEST_CREATED

Use the REQUEST_CREATED alert type to configure the Correction-and-Transport (CTS) alertmonitor SAPABAP_CTSMonMonitoring Template to generate amessage for any new request createdwithin the last specified time frame. For example, adding a new (or modifying an existing) functionmodule requires a change request. The following table lists the parameters that you can use toconfigure the REQUEST_CREATED alert type and shows the value assigned to the parameters bydefault.

The configuration of any of these parameters is optional.


QueryConditions

DefaultValue

TRFUNCTION The request function. = Sign: I, E I

Opt: CP, EQ CP

= Low:A,K,L,W,C,T,U, D a

*

= High:



TARGET The target system forwhich this requestwas created.

Note: This must be aSID.

= Sign I, E

= Opt: EQ,CP

= Low:<nameof system>

= High

USERNAME The login name of theSAP NetWeaver userwho created therequest.

= Sign I

= Opt: EQ,CP

= Low:<usernamewho createdthisrequest>

= High

aYou can only specify the listed functions (* means all).

In the Default REQUEST_CREATED Configuration, themonitor generates amessage if a newrequest occurs within the last time frame.

The Default REQUEST_CREATED Configuration

AlertMonFun =ALL =ALL =ALL =ALL =CTS =1\

=WARNING =Request =R3_CTS\

=REQUEST_CREATED =USERNAME =I =CP =* =

REQUEST_RELEASED

Use the REQUEST_RELEASED alert type to configure the Correction-and-Transport (CTS)Monitoring Template SAPABAP_CTSMon to generate amessage for any new request released withinthe last specified time frame. The following table lists the parameters that you can use to configure theREQUEST_RELEASED alert type and shows the value assigned to the parameters by default:

Note: The configuration of the parameters below is optional.




DefaultValue

TRKORR Request ID = Sign: I, E

= Opt: EQ

= Low: <Request ID>

= High:

TRFUNCTION The request function. = Sign: I, E

= Opt: EQ

= Low: K,L, W,C,T, U, D.(You can only specify thelisted functions (* means all).)

= High:

TARGET The target system for which thisrequest was created. This must be aSID.

= Sign I, E I

= Opt: EQ, CP CP

= Low: <name of system> *

= High

USERNAME The login name of the SAP NetWeaveruser who created the request.

= Sign I

= Opt: EQ,CP

= Low: <usernamewhocreated this request>

= High

CUSTOMIZING Customizing Requests = Sign I,E

= Opt: EQ

= Low (Any entry other than’X’ will be treated as space.)

= High

WORKBENCH Workbench Requests = Sign I, E

= Opt: EQ

= Low (Any entry other than’X’ will be treated as space.)

= High



In the Default REQUEST_RELEASED Configuration, an event generating an alert occurs if anycustomizing request was released in the last time frame.

The Default REQUEST_RELEASED Configuration


=WARNING =Request =R3_CTS\

=REQUEST_RELEASED =CUSTOMIZING =I =EQ =X

TASK_CREATED

Use the TASK_CREATED alert type to configure the CTS Monitoring Template SAPABAP_CTSMonto generate amessage for any new task createdwithin the last specified time frame. The followingtable lists the parameters that you can use to configure the TASK_CREATED alert type and shows thevalue assigned to the parameters by default.

The configuration of any of these parameters is optional.

Parameter Name Description Query ConditionsDefaultValue


= Opt: CP, EQ CP

= Low: X, S, R, Z a *

= High:

USERNAME The login name of the SAPNetWeaver user who createdthe request.

= Sign: I

= Opt: EQ, CP

= Low:<usernamewhocreated this request>

= High:

In the Default TASK_CREATED Configuration, SAPABAP_CTSMonMonitoring Template generates amessage for any new task created within the last specified time frame.

The Default TASK_CREATED Configuration

AlertMonFun =ALL =ALL =ALL =ALL =CTS =1 \

=WARNING =Task =R3_CTS \

=TASK_CREATED =TRFUNCTION =I =CP =* =



TASK_RELEASED

Use the TASK_RELEASED alert type to configure the CTS Monitoring Template SAPABAP_CTSMonto generate amessage for any new task released within the last time frame. The following table liststhe parameters that you can use to configure the TASK_RELEASED alert type and shows the valueassigned to the parameters by default:

The configuration of the parameters below is optional.


DefaultValue


= Opt: EQ

= Low: <Request ID>

= High:


= Opt: CP, EQ CP

= Low: R, S, Z a *

= High:

USERNAME The login name of theSAP NetWeaver userwho created therequest.

= Sign: I

= Opt: EQ, CP

= Low: <usernamewho created this request>

= High

In the Default TASK_RELEASED Configuration, SAPABAP_CTSMonMonitoring Template generatesamessage for any new task released in the last time frame.

The Default TASK_RELEASED Configuration


=WARNING =Task =R3_CTS\

=TASK_RELEASED =TRFUNCTION =I =CP =* =



OBJECT_USED

Use theOBJECT_USED alert type to configure the CTS Monitoring Template SAPABAP_CTSMon togenerate amessage if a task or a request uses an object matching the defined configuration within thelast time frame. The following table lists the parameters that you can use to configure the OBJECT_USED alert type and shows the value assigned to the parameters by default:



DefaultValue

PGMID Program ID = Sign: I, E

= Opt: EQ, CP

= Low: <Program ID>

= High:

OBJECT Object type ofelement.

= Sign I, E

= Opt: EQ, CP

= Low: <Object type>

= High

OBJ_NAME

Object Name inobject directory.

= Sign I, E I

= Opt: EQ, CP CP

= Low: <Object name> *

= High

OBJ_FUNC

Special functionfor an objectentry: D =Delete, or M =Delete andrecreate.

= Sign I, E

= Opt: EQ, CP

= Low

= High

IN_REQUEST

Alert generatedif objectcontainer is arequest.

= Sign I,E

= Opt: EQ

= Low

= High




DefaultValue

IN_TASK Alert generatedif objectcontainer is atask.

= Sign I, E

= Opt: EQ

= Low

= High

In the Default OBJECT_USED Configuration, an event generating an alert occurs if any object withObject Type LIMU is used by a task or a request.

The Default OBJECT_USED Configuration

AlertMonFun =ALL =SD1 =ALL =ALL =CTS =1\

=WARNING =Object =R3_CTS\

=OBJECT_USED =PGMID =I =EQ =LIMU =

OBJECT_RELEASED

Use theOBJECT_RELEASED alert type to configure the CTS Monitoring Template SAPABAP_CTSMon to generate amessage if a request or a task released the specified object. The following tablelists the parameters that you can use to configure the OBJECT_USED alert type and shows the valueassigned to the parameters by default:



QueryConditions Default Value


= Opt: EQ, CP

=Low:<RequestID>

= High:





PGMID Program ID = Sign: I, E

= Opt: EQ, CP

= Low:<Program ID>

= High:

OBJECT Object type of element = Sign I, E

= Opt: EQ, CP

= Low:<Object type>

= High

OBJ_NAME

Object Name in objectdirectory

= Sign I I

= Opt: EQ, CP CP

= Low:<Objectname>

*

= High

IN_REQUEST

Alert generated if objectcontainer is a request

= Sign I,E

= Opt: EQ

= Low (Anyentry otherthan ’X’ will betreated asspace.)

= High

IN_TASK Alert generated if objectcontainer is a task.

= Sign I, E

= Opt: EQ

= Low (Anyentry otherthan ’X’ will betreated asspace.)

= High



In the Default OBJECT_RELEASED Configuration, an event generating an alert occurs if any object isreleased by a task.

The Default OBJECT_RELEASED Configuration

AlertMonFun =ALL =ALL =AL =ALL =CTS =1\

=WARNING =Object =R3_CTS\

=IN_TASK =I =EQ =X =

SAPABAP_DispMon

The SAPABAP_DispMonMonitoring Template enables monitoring of the size, content, and status ofvarious queues for different types of SAP work processes. The SAPABAP_DispMonMonitoring Template monitors the queues which belong to the SAP instances defined in the OMi MP forSAP and allows you tomanage SAP performance issues more pro-actively by avoiding bottlenecksand helping to ensure that themonitored SAP Systems have enough work processes available to fulfillall user requests, even when loads are typically very high.

This section contains information about the following topics:

l Prerequisites

l File Locations

l Integrating SAPABAP_DispMonMonitoring Template with OMi MP for SAP Monitors

l SAPABAP_DispMonMonitoring Template Configuration

Prerequisites

If SAPABAP_DispMonMonitoring Template is not able to find either the correct version of the SAPexecutable dpmon or the profile of the SAP instance whose queues you want to monitor, it aborts itsrun, writes an entry in its log file, and sends amessage to themessage browser. SAPABAP_DispMonMonitoring Template requires a version of the dpmon executable, which recognizes the -s[snapshot]option.

To check if the correct version of the dpmon executable is available on the SAP server which you wantto monitor with SAPABAP_DispMonMonitoring Template, log on to the SAP server as user <SID>admand run the dpmon commandwith the -help option. If the command output displays the -s[snapshot]option as shown in Checking the snapshot option ON, you can configure and use the SAPABAP_DispMonMonitoring Template.



Checking the snapshot option

$>dpmon -help

Usage: dpmon <options>

with the following options:

-p[ing] check dispatcher with NI ping

-i[nfo] retrieve dispatcher info

-s[snapshot] show info and terminate

-t <trace_level> tracelevel (default:1)

-f <trace_file>] name of the tracefile (default: dev_dpmon)

-T <timeout> network time-out value in ms (default:500)

On both UNIX andWindows operating systems, the SAPABAP_DispMonMonitoring Template usesthe environment variables SAPOPC_DPMON_PATH_ <SID> and SAPOPC_PROFILE_<SID>_<InstNr> to determine the location of dpmon and the SAP instance profile respectively. If the variablesare not set, SAPABAP_DispMonMonitoring Template uses the registry onWindows operatingsystems to determine the path to dpmon and the profile-file for themonitored SAP instances.

On UNIX operating systems, SAPABAP_DispMonMonitoring Template does not require any specialinterface to determine the location of dpmon or the profile-file for themonitored SAP instances: itassumes they are in the default SAP location. If you know the profiles files are not in the defaultlocation, or the name of the profile does not follow standard SAP naming conventions, youmustindicate this in the SAPABAP_DispMonMonitoring Template configuration. The standard namingconvention for an SAP profile is:

<SID>_[D|DVEBMGS]<SysNr>_<hostname>

Formore information on configuring SAPABAP_DispMonMonitoring Template, see "SAPABAP_DispMonMonitoring Template Configuration".

File Locations

The SAP System-security SAPABAP_DispMonMonitoring Template uses the files listed in thefollowing table:

File Description



r3mondisp (.exe) Executable for the ABAP Dispatcher-queuemonitor

r3mondisp.cfg Configuration file for the ABAP dispatcher-queuemonitor.

r3mondisp.log File used to store trace data collected by theABAP dispatcher-queuemonitor.

Integrating SAPABAP_DispMon Monitoring Template with OMi

MP for SAP Monitors

To prevent the OMi MP for SAP from causing excessive and unnecessary load on the SAP System atcritical times, you can configure the SAPABAP_DispMonMonitoring Template to work together withthe other OMi MP for SAP monitors so that themonitors check the status of the ABAP dispatcher andestablish how full the dispatcher queues are before requesting a work process. OMi MP for SAPmonitors require a dialog work process to logon to SAP. To enable this integration feature, use theEnableDPQueueCheck keyword in the SAPABAP_DispMonMonitoring Template configuration to checkthe dispatcher status before starting.

For example, if you want the SAPABAP_DispMonMonitoring Template, to check the status of theABAP dispatcher before SAPABAP_CCMSIntegrationMon starts its monitor run, configure theEnableDPQueueCheck keyword in the SAPABAP_DispMonMonitoring Template as illustrated in"Checking the ABAP Dispatcher Before Startup". If SAPABAP_CCMSIntegrationMon’s request for awork process violated a threshold for dialog work processes defined in theMonitoring Templateconfiguration, the SAPABAP_DispMonMonitoring Template would not start its monitor run; it would sendamessage to themessage browser indicating the reason why it did not start. You should considerusing this feature where SAP System performance could be further compromised as a result of arequest for an additional dialog work process by OMi MP for SAP monitor.

Note:SAPABAP_DispMonMonitoring Template is not affected by the thresholds defined for theEnableDPQueueCheck keyword; theMonitoring Template continues to work normally even if othermonitors do not start as a result of a lack of available dialog work processes.

Checking the ABAP Dispatcher Before Startup

# EnableDPQueueCheck hostname SAP SAP Enable =1

# System Number Disable=0

#

EnableDPQueueCheck =ALL =ALL =ALL =1



Formore information about the EnableDPQueueCheck keyword, see "EnableDPQueueCheck".

SAPABAP_DispMon Monitoring Template Configuration

The SAPABAP_DispMonMonitoring Template allows you to configure theMonitoring Template usingthe keywords listed in this section tomeet the requirements of your particular SAP environment."Excerpt from a SAPABAP_DispMonMonitoring Template Configuration" shows an excerpt from theMonitoring Template’s default configuration.

Note: If you configure the OMi MP for SAP ABAP Monitoring Templates to check the status of theABAP dispatcher before starting themonitor run, make sure theMonitoring Template has therequired privileges to access and read data.

You can use the following keywords in configuring the SAPABAP_DispMonMonitoring Template. Formore information, see allowed values for the parameters in the following list:

l TraceLevel

Set the trace level for SAPABAP_DispMonMonitoring Template when it runs on the specified SAPserver. The TraceLevel keyword accepts the following parameters:

TraceLevel =<hostname> =<TraceLevel>

l TraceFile

Set the name of the trace file, which SAPABAP_DispMonMonitoring Template uses to log entries.The TraceFile keyword accepts the following parameters:

TraceFile =<hostname> =<filename> =<TraceMode> =<TracePeriod>

l DPQueueCheck

Manages the pro-activemonitoring of the ABAP dispatcher. If more than one thresholdmatches forthe samemanaged node and the samework-process, SAPABAP_DispMonMonitoring Templateonly sends themessage with the highest severity. The DPQueueCheck keyword accepts thefollowing parameters:

DPQueueCheck =<hostname> =<SID> =<InstanceNr> \ =<disable/enable>\ =<OVO MsgGroup> =<OVO Msg Object> =<OVO Severity> \ =<WP-Type> =<Idle/Queue> =<Percentageidle/full>

Since the status of queued work-process is, generally speaking, more important than the status ofidle work processes of the samework-process type, we recommend that the severity levelassigned tomessages concerning queued work processes is higher than the severity level you



associate with messages about idle work processes. For example, you can assign the severitylevel Warning tomessages about idle work processes and Critical to messages about queued workprocesses.

l DisableMonitoringWithSeverity

Specify which SAPABAP_DispMonMonitoring Template message severity should trigger thedisabling of integrated OMi MP for SAP monitors to prevent themonitors increasing loadsunnecessarily by requesting additional dialog work processes from the SAP Systems, whosedispatcher you aremonitoring with the OMi MP for SAP. The DisableMonitoringWithSeveritykeyword accepts the following parameters:

DisableMonitoringWithSeverity =<hostname> =<SID> \ =<InstanceNr> =<Severity>

The DisableMonitoringWithSeverity keywordmust be used in conjunction with keywordsDPQueueCheck, which you configure in the SAPABAP_DispMonMonitoring Template, andEnableDPQueueCheck, which you define in the configuration of theMonitoring Template you want tointegrate with SAPABAP_DispMonMonitoring Template. For more information about the keywordEnableDPQueueCheck, see "EnableDPQueueCheck".

l InstanceProfilePath

The path to the profile-configuration file for an SAP instance whose dispatcher you want to monitor;the InstanceProfilePath keyword accepts the following parameters:

InstanceProfilePath =<hostname> =<SID> =<InstanceNr> \ =<path>

Excerpt from SAPABAP_DispMonMonitoring Template configuration shows how to configure themonitoring template to send a warningmessage to themessage browser if less than 15 percent ofthe total allocated dialog work processes for all SAP clients in all the SAP instances monitored bythe OMi MP for SAP are idle.

Excerpt from a SAPABAP_DispMon Monitoring Template Configuration

#------------------------------------------------------------

# TraceLevel hostname only error messages=1 info messages=2 debug

messages=3

# Disable=0

TraceLevel =ALL =0

#------------------------------------------------------------------------

# TraceFile hostname filename TraceMode TracePeriod

# (a=append/w=create(default)) (in mins)



TraceFile =ALL =r3mondisp.log =w =60

#------------------------------------------------------------------------

#InstanceProfilePath =<host> =<SID> =<InstanceNr> =<Path>

#

InstanceProfilePath =ALL =ALL =ALL =default

#------------------------------------------------------------

#DisableMonitoringWithSeverity=<host>=<SID>=<InstanceNr>=<Severity>

#

DisableMonitoringWithSeverity=ALL=ALL=ALL=WARNING

#------------------------------------------------------------

The Excerpt from SAPABAP_DispMonMonitoring Template configuration also shows how to usethe keyword DisableMonitoringWithSeverity to configure SAPABAP_DispMonMonitoring Template to prevent OMi MP for SAP monitors from starting if the start up requires adialog work process (for example, to logon to SAP) and the allocation of that work process wouldviolate a threshold for idle dialog work processes defined in the configuration file and, as a result,generate amessage with the severity warning or higher.

Note that you have to use the EnableDPQueueCheck keyword to configure each individual OMi MPfor SAP monitor that logs on to SAP to check the dialog work-process queue before starting its run.For more information about the keyword EnableDPQueueCheck, see "EnableDPQueueCheck".

SAPABAP_DmpMon

The SAPABAP_DmpMonMonitoring Template enables monitoring of the runtime errors that occur onthe SAP ABAP system. The check is performed once per monitor run for all application servers.

Dumps are usually runtime errors and hence they cannot always be detected by a static syntax check.They can occur for many reasons andmay indicate serious problems. No dumps should occur on aproduction system.

Here are two examples of actions which cause dumps to occur:

l division by zero

l a called functionmodel is not enabled



Since the system administrator generally has to do something to resolve problems associated with anABAP dump, themessages generated by the SAPABAP_DmpMonMonitoring Template include anoperator-initiated action that calls an ABAP program to display details of the dump.

The SAPABAP_DmpMonMonitoring Template references the SAP NetWeaver transaction ST22.

Monitor Type

The SAPABAP_DmpMonMonitoring Template is of type time frame. Onemonitor run gathers only onevalue set.

Alert Types

The SAPABAP_DmpMonMonitoring Template has the following alert type:

l ABAP4_ERROR_EXIST

Each ABAP dump generates one alert.

File Locations

The SAPABAP_DmpMonMonitoring Template uses the files listed in this table.

File Description

r3moncol (.exe) Collector executable for ABAP-dumpmonitor

r3mondmp.cfg Configuration file for monitored application servers.

r3mondmp.log Trace file for storing trace data.

The alert-collector monitors do not write history information to a specific history file.


The SAPABAP_DmpMonMonitoring Template uses the environment variables described in"Environment Variables".




The SAPABAP_DmpMonMonitoring Template uses the command line parameters described"Command-Line Parameters".

Remote Monitoring

Formore information about configuring the SAPABAP_DmpMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

ABAP4_ERROR_EXIST

Use the ABAP4_ERROR_EXIST alert type to configure the SAPABAP_DmpMonMonitoring Template, to generate an alert for each dump that occurred in the last time frame. TheDefault ABAP4_ERROR_EXIST Configuration shows how you can use =MAX_ENTRIES to count thenumber of dumps that have to occur before the OMi MP for SAP generates amessage. In addition, youcan specify a period of time in hours (=TIME_LIMIT)within which the defined number of dumps mustoccur. In this example, the OMi MP for SAP generates amessage if ten dumps occur within twentyfour hours.

The Default ABAP4_ERROR_EXIST Configuration

AlertMonFun =ALL =ALL =ALL =ALL =ABAP4 =1\

=WARNING =ABAP_Dump =R3_ABAP-4\

=ABAP4_ERROR_EXIST

#AlertMonFun =ALL =ALL =ALL =ALL =ABAP4 =1 \

=WARNING =ABAP_Dump =R3_ABAP-4 =ABAP4_ERROR_EXIST\

=MAX_ENTRIES =I =GT =10 = \

=TIME_LIMIT =I =LT =24 =

TheOMi MP for SAP’s optional test transport includes a program that generates an ABAP dumpwhichyou can use to verify that the SAPABAP_DmpMonMonitoring Template correctly reports dumps toOMi in the form of amessage. If the test completes successfully, a message about the test dumpappears in the OMi message browser. For more information about OMi MP for SAP transports, see thetransports read-me file /usr/sap/trans/readme on theOMi managed node; for more information about



importing and applying OMi MP for SAP transports, see theOMi Management Pack for SAPInstallation Guide. After importing the transport, you can view the test programs installed by using theSAP transaction SE80 to open the ABAP object navigator and browsing to the report (or program)/HPOV/YSPI0004.

SAPABAP_IdocStatusMon

The SAPABAP_IdocStatusMonMonitoring Template enables you tomonitor the current status ofdifferent iDocs on the SAP ABAP system.The SAPABAP_IdocStatusMonMonitoring Template, istime-frame based and checks the status of existing iDOCs for errors using the transaction WE02 as thedata source. Themonitoring template is application-server independent and available for global (SAPNetWeaver System-wide) use.

Monitor Type

The SAPABAP_IdocStatusMonMonitoring Template is of type time frame. Onemonitor run gathersonly one value set.

Alert Types

The SAPABAP_IdocStatusMonMonitoring Template has the following alert types:

"IDOC_CURRENT_STATUS"

Defines when to generate an alert concerning the current state of the iDOCs.

File Locations

The SAPABAP_IdocStatusMonMonitoring Template uses the files listed in this table.

File Description

r3moncol (.exe) Collector executable for the iDOC-status monitor

r3monale.cfg Configuration file for iDOC-status monitor

r3monale.log Trace file for storing trace data

The alert-collector monitors do not write history information to a specific history file.




The SAPABAP_IdocStatusMonMonitoring Template uses the environment variables described in"Environment Variables". The environment variables for all the alert-collector monitors share the sameformat, the only difference being that the name of theMonitoring Template varies tomatch eachspecific monitor as indicated in "Environment Variables".


The SAPABAP_IdocStatusMonMonitoring Template uses the command-line parameters described in"Command-Line Parameters". The command-line parameters for all the alert-collector monitors sharethe same format, the only difference being that the name of theMonitoring Template must vary tomatch each specific monitor for both the -cfgfile and -trace parameters as indicated in "Command-Line Parameters".

Remote Monitoring

Formore information about configuring the SAPABAP_IdocStatusMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring SAPABAP_IdocStatusMon Monitoring Template

Alert Types

When configuring the IDOC_CURRENT_STATUS alert type for SAPABAP_IdocStatusMonMonitoring Template, remember that youmust define at least one of the parameters listed in "IDOC_CURRENT_STATUS Configuration Parameters" table.

IDOC_CURRENT_STATUS

The IDOC_CURRENT_STATUS alert type defines the current status of iDOCs, which you want tomonitor. Use the IDOC_CURRENT_STATUS alert type to configure the iDOC-status alert monitorSAPABAP_IdocStatusMonMonitoring Template to generate an alert if the status of an iDOC matchesthe status defined in the STATUS parameter. The following table lists the parameters that you can use



to configure the IDOC_CURRENT_STATUS alert type and shows the value assigned to theparameters by default. Note that ‘ ‘ in the Default Value column signifies an empty string.

IDOC_CURRENT_STATUS Configuration Parameters


QueryConditions

DefaultValue

DOCNUM iDOC number, for example:“05” (error during translation)

= Sign: I, E ‘ ‘

= Opt: GE,GT, LE, LT,BT

‘ ‘

= Low ‘ ‘

= High: ‘ ‘

DOCTYP The basic iDOC type, forexample: DOCMAS01

= Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

MESCOD Logical message code = Sign I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

MESFCT Logical message function = Sign: I ‘ ‘

= Opt: CP,EQ ‘ ‘

‘ ‘

= Low ‘ ‘

= High ‘ ‘

MESTYP Logical message type = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘




QueryConditions

DefaultValue

RCVPFC Partner function of receiver = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

RCVPRN Partner number of receiver = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

RCVPRT Partner type of receiver = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

SNDPFC Partner function of sender = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

SNDPRN Partner number of sender = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘




QueryConditions

DefaultValue

SNDPRT Partner type of sender = Sign: I ‘ ‘

= Opt: CP,EQ

‘ ‘

= Low ‘ ‘

= High ‘ ‘

STATUS * Status of iDOC = Sign: I, E ‘ ‘

= Opt: GE,GT, LE, LT,BT

‘ ‘

= Low ‘ ‘

= High ‘ ‘

*Possible values: CHECK_INBOUND, CHECK_OUTBOUND, MAX_ENTRIES, TIME_LIMIT

In RemoteMonitoring, the SAPABAP_IdocStatusMonMonitoring Template checks the status ofinbound iDOCs. An event generating an alert occurs if the number of in-bound iDOCS specified inIDOC_CURRENT_STATUS is greater than (GT) the value 4 (four) defined inMAX_ENTRIES.

IDOC_CURRENT_STATUS Configuration

AlertMonFun =ALL =ALL =ALL =ALL =ALL =1 \

=WARNING =ALE =R3_IDOC_STATUS \

=IDOC_CURRENT_STATUS =STATUS =I =EQ =CHECK_INBOUND \

=MAX_ENTRIES =I =GT =4

Checking the iDOC Status

Using the IDOC_CURRENT_STATUS alert type in conjunction with the STATUS parameter allowsyou to check any one of the different iDOC statuses that are registered in SAP NetWeaver or a range ofstatuses defined in a group.

In addition, the OMi MP for SAP provides two pre-defined groups that you can use to check for a rangeof errors relating to incoming or outgoing iDOCs. For example, you can use the values CHECK_INBOUNDand CHECK_OUTBOUND to monitor a range of values:



l CHECK_OUTBOUND

monitors iDOCs with status: 02, 04, 05, 25, 26, 29, 30, 32

l CHECK_INBOUND

monitors iDOCs with status: 51, 56, 60, 61, 62, 63, 64, 65, 66, 69

If you want to use the SAPABAP_IdocStatusMonMonitoring Template to check for a specific iDOCstatus, replace the value =CHECK_INBOUND shown in "IDOC_CURRENT_STATUS Configuration"with the iDOC status number listed in "Possible iDOC Status" table that corresponds to the iDOCstatus you want to monitor. For example, to monitor the number of existing iDOCS, use =01. Note thatit is not currently possible to define your own ranges similar to the pre-defined ranges CHECK_INDOUNDand CHECK_OUTBOUND. Instead, you have to define a separate AlertMonFun entry for each additionalvalue, which you want to monitor.

The following table lists all the statuses that the OMi MP for SAP recognizes:

Possible iDOC Status

iDOCStatus Description

CheckInbound

CheckOutbound

00 Not used, only for R/2

01 iDoc created

02 Error passing data to port ✓

03 Data passed to port OK

04 Error within control information of EDIsubsystem

✓

05 Error during translation ✓

06 Translation OK

07 Error during syntax check

08 Syntax check OK

09 Error during interchange handling

10 Interchange handling OK

11 Error during dispatch

12 Dispatch OK

13 Retransmission OK




CheckInbound

CheckOutbound

14 Interchange Acknowledgment positive

15 Interchange Acknowledgment negative

16 Functional Acknowledgment positive

17 Functional Acknowledgment negative

18 Triggering EDI subsystem OK

19 Data transfer for test OK

20 Error triggering EDI subsystem

21 Error passing data for test

22 Dispatch OK, acknowledgment still due

23 Error during retransmission

24 Control information of EDI subsystem OK

25 Processing despite syntax error (outbound) ✓

26 Error during syntax check of iDoc (outbound) ✓

27 Error in dispatch level (ALE service)

28 Not used

29 Error in ALE service ✓

30 iDoc ready for dispatch (ALE service) ✓

31 Error - no further processing

32 iDoc was edited ✓

33 Original of an iDoc which was edited

34 Error in control record of iDoc

35 iDoc reloaded from archive

36 Electronic signature not performed (time-out)

37 iDoc added incorrectly

38 iDoc archived

39 iDoc is in the receiving system (ALE service)

40 Application document not created in receiving




CheckInbound

CheckOutbound

system

41 Application document created in receivingsystem

42 iDoc was created by test transaction

50 iDoc added

51 Error: Application document not posted ✓

52 Application document not fully posted

53 Application document posted

54 Error during formal application check

55 Formal application check OK

56 iDoc with errors added ✓

57 Test iDoc: Error during application check

58 iDoc-Copy from anR/2 connection

59 Not used

60 Error during syntax check of iDoc (Inbound) ✓

61 Processing despite syntax error (Inbound) ✓

62 iDoc passed to application ✓

63 Error passing iDoc to application ✓

64 iDoc ready for transfer to the application ✓

65 Error in ALE service

66 iDoc is waiting for predecessor iDoc(serialization)

67 Not used

68 Error - no further processing

69 iDoc was edited ✓

70 Original of an iDoc which was edited

71 iDoc reloaded from archive

72 Not used, only for R/2




CheckInbound

CheckOutbound

73 iDoc archived

74 iDoc was created by test transaction

SAPABAP_LckChkMon

The SAPABAP_LckChkMonMonitoring Template enables monitoring of the Enqueue process whichmanages the SAP ABAP logical locks for different SAP transactions and SAP reports. Obsolete locksare defined as locks which are older than the time period you specify. The check is performed once permonitor run for all application servers.

An object which is locked cannot be changed by anyone other than the user associated with it and cancause severe problems. The operator can check the locks set for a specific instance in SM12. Here aretwo examples of actions which cause locks to occur:

l Users switch off their computers without first logging off the SAP NetWeaver system - this is themost common cause of locked objects.

l An entire SAP instance fails.

The SAPABAP_LckChkMonMonitoring Template references the SAP NetWeaver transaction SM12.

Messages generated by this alert monitor include an operator-initiated action that calls the SM12 LocksOverview module. The operator can then check the locks set for a specific instance in SM12.

Monitor Type

The SAPABAP_LckChkMonMonitoring Template is of type snapshot and does not make use of alerttypes or parameters. Onemonitor run gathers only one value set.

Alert Types

The SAPABAP_LckChkMonMonitoring Template has only one alert type:

"OLD_LOCKS"

Specifies when to define a lock as old, using the time period you specify in the parameter LOCK_TIME.

File Locations

The SAPABAP_LckChkMonMonitoring Template uses the files listed in this table.



File Description

r3moncol (.exe) Collector executable for the lock_check monitor

r3monlck.cfg Configuration file for the lock_check monitor.

r3monlck.log Trace file for storing trace data.


The SAPABAP_LckChkMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_LckChkMonMonitoring Template uses the command-line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the alert-collector monitors to monitor another SAP Systemremotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

OLD_LOCKS

The LOCK_TIME alert type specifies when to define a lock as “old”, using the time period you specify inthe parameter LOCK_TIME. Use the LOCK_TIME alert type to configure SAPABAP_LckChkMonMonitoring Template to generate an alert when a job exceeds the time span defined in the parameterLOCK_TIME.

The following table lists the parameters that you can use to configure the LOCK_TIME alert type andshows the value assigned to the parameters by default:

Note: The configuration of the parameter below is mandatory.


QueryConditions

DefaultValue



LOCK_TIME

The timespan (inhours) afterwhich a lockisconsideredold.

= Sign: I,E I

= Opt: EQ,GT, GE,LE, LT, BT

GT

= Low:<time inhours> 1

= High:2

1. Specify this parameter as a number. Otherwise themonitor ends with a dump.

2. Only for use when specifying a range.

In The Default OLD_LOCKS Configuration, an event generating an alert occurs if any lock exceeds atime span of 24 hours.

The Default OLD_LOCKS Configuration

AlertMonFun =ALL =ALL =ALL =ALL =LOCK_CHECK =1\

=WARNING =Enqueue =R3_Enqueue\

=OLD_LOCKS =LOCK_TIME =I =GT =24 =

SAPABAP_PerfMon

The SAPABAP_PerfMonMonitoring Template enables you to collect SAP Performancemetrics fromdifferent OMi MP for SAP Performancemonitors.

Overview

The OMi MP for SAP R/3 Performance Agent uses a selection of performance monitors to collect SAP performance data and store them either in the HPE Software Embedded Performance Component(CODA) or the Performance Agent (Unix/Windows). You can use the Performance Manager to monitor, manage, and correlate data, together with data collected by any other application, database, system, and network Performance Agent. The data can then be used to compare trends between SAP business transactions and other system metrics. This section provides information about the following topics:

l Performancemonitoring with the OMi MP for SAP

l UsingOMi to install the OMi MP for SAP R/3 Performance Agent



l Configuring the performancemonitors

Implemented ABAP-functionmodules inside SAP NetWeaver are accessed by means of an RFC-call.The performancemonitors gather a snapshot of SAP-runtime performance data.

TheOMi MP for SAP R/3 Performance Agent can collect more than 130metrics in addition to thosecollected by the SAP NetWeaver Performance alert monitor (ST03), which is part of the SAPNetWeaver CCMS subsystem.

You can configure the OMi MP for SAP R/3 Performance Agent to specify whichmonitors should berun on specified SAP NetWeaver instances and how frequently.

The Performance Agent runs inWindows operating systems as a service and in UNIX operatingsystems as a daemon (background) process that runs independently of the OMi agent processes. Tostart or stop the OMi MP for SAP R/3 Performance Agent processes, use the appropriate OMi MP forSAP tool in the Tool Bank window. For more information, see "Managing the OMi MP for SAP R/3Performance Agent".

Configuring the SAPABAP_PerfMon Monitoring Template

TheOMi MP for SAP provides a default configuration for the SAPABAP_PerfMonMonitoring Template;the default configuration works without modification immediately after installation. However, if youwant to set up the SAPABAP_PerfMonMonitoring Template for your particular SAP environment, youcanmodify the configuration by enabling or disabling the keywords in the following list and, wherenecessary, setting or modifying the appropriate parameters:

l TraceLevel

The TraceLevel keyword accepts the following parameters:

TraceLevel =<Hostname> =<TraceLevel>

Hostname:

=ALL Monitor all hosts with the OMi MP for SAP. This is thedefault setting.

=<SAP_host> The name of an SAP server, where you want tospecify a trace level. Use a new line for eachindividual host.

TraceLevel:



=0 Disable. This is the default setting.

=1 Log only error messages

=2 Log all messages

=3 Log only debugmessages. Note that this trace level logs a lot of information and could veryquickly lead to a very large trace file.

l TraceFile:

The TraceFile keyword accepts the following parameters:

Tracefile =<Hostname> =<Filename>

Hostname:

=ALL Monitor all SAP servers with the OMi MP for SAP. This is the default setting.

=<SAP_host>

The name of a specific host where tracing is enabled and you want to specify atrace level.

Filename:

=r3perfmon.log - This is the default setting, which writes the log file to the default log file directory.Alternatively, you can specify the name of the file to which you want to write the trace log and, ifnecessary, the path. The path can be either absolute or relative to the working directory.

l AgentHostname

Make sure that the AgentHostname keyword set to ALL.

l SyncBack

The SyncBack keyword accepts the following parameters:

SyncBack =<Enable|Disable> =<SyncBack Threshold>

Enable/Disable:

=0 Disable the schedulersynchronization.

=1 Enable the schedulersynchronization. This is the defaultsetting.

SyncBack Threshold:



=<n>mins

The difference inminutes between defined and actual schedules. If the SyncBackthreshold is reached, for example, when the scheduler is nminutes behind schedule, thescheduler restarts to return to the defined schedule. The SyncBack threshold should behigher than the Message Threshold value set in association with theBehindSyncMessage keyword so that you receive amessage warning about scheduleproblems before the scheduler restarts.

l BehindSyncMessage

The BehindSyncMessage keyword accepts the following parameters:

BehindSyncMessage =<Enable|Disable> =<OpC Severity> \

=<OpC Object> =<OpC MsgGroup> =<Message Threshold>

Enable/Disable:

=0 Disable the sending of a behind-schedulemessage

=1 Enable the sending of a behind-schedulemessage. This is the default setting.

OpC Severity:

=WARNING The severity of the behind-schedulemessage sent. This is thedefault value.

OpC Object:

=r3perfagent The HPOM forWindows object to associate with the behind-schedulemessage. This is the default value.

OpC MsgGroup:

=R3_General

The HPOM forWindows message group to which the behind-schedulemessage belongs. This is the default value.

Message Threshold:

=<n>mins

The elapsed time inminutes before a behind-schedulemessage is sent tothe HPOMmanagement server. Themessage-threshold value should beless than the SyncBack Threshold value set in association with theSyncBack keyword so that you receive amessage warning about scheduleproblems before the scheduler restarts.

l RemoteMonitoring

The RemoteMonitoring keyword accepts the following parameters:



RemoteMonitoring =<LocalHost> =<RemoteHost>

LocalHost:

This is the name of the host where the OMi MP for SAP software is running and whose performanceagent will be used to remotely monitor the SAP server defined inRemotehost.

RemoteHost:

This is the name of the remoteSAP server that you want to monitor using the OMi MP for SAP onthe SAP server defined in Localhost. Although the remote host is not usually an OMi managednode and does not have Agent installed.

l PerfMon

The Perfmon keyword requires a value for the following parameters:

PerfMon =<SAP Hostname> =<SAP System> =<SAP Number> \

=<SAP Client> =<RFC FUNCTION> =<Enable|Disable> \

=<Polling Interval> =<Hold Connection>

SAP Hostname:

=ALL Monitor all SAP hosts with the OMi MP forSAP. This is the default setting.

=<SAP_host>

The host name of a specific SAP serverwhose performance you want to monitor. Usea new line for each individual host.

SAP System:

=ALL Monitor all SAP Systems with the OMi MP for SAP. This is thedefault setting.

=<SAP_SID>

The ID of a SAP System whose performance you want to monitor,for example, DEV. Use a new line for each individual SID.

SAP Number:

=ALL Monitor all SAP numbers with the OMi MP for SAP. This is thedefault setting.

=<Instance> The number of a specific SAP instance whose performance youwant to monitor, for example, 00, 99. Use a new line for each newSAP number.

SAP Client:



=ALL Monitor all SAP clients with the OMi MP for SAP. This is thedefault setting.

=<ClientID> The number of a specific SAP client whose performance you wantto monitor, for example, 099. Use a new line for each SAP client.

RFC FUNCTION:

=<metricname>_PERF, where metricname refers to the specific metric list you want theperformancemonitor to use, for example, DBINFO_PERF or SAPMEMORY_PERF. For moreinformation about the possible values you can use, see "OMi MP for SAP PerformanceMonitors ".

Enable/Disable:

=0 Disable the performancemonitor

=1 Enable the performancemonitor. This is the default setting.

Polling Interval:

=nn nn is the time inminutes between each run of theperformancemonitor.

Hold Connection:

=0 Disable:Close the RFC connection after the call has completed.This is the default setting.

=1 Enable: Keep the RFC connection open after the call has completed.

Managing the OMi MP for SAP R/3 Performance Agent

You can control the OMi MP for SAP R/3 Performance Agent using command-line options, which differaccording to the platform and operating system. You canmanage theOMi MP for SAP R/3Performance Agent either by using command-line options or the tools that are installed by the OMi MPfor SAP.

OMi MP for SAP R/3 Performance Agent Command Line Syntax

You an use the following options with the r3perfagent command from the instrumentation directoryon UNIX managed nodes to control the OMi MP for SAP R/3 Performance Agent from the commandline:



l r3mon-perl -S SAPMP_Tool.pl Start

l r3mon-perl -S SAPMP_Tool.pl Stop

l r3mon-perl -S SAPMP_Tool.pl Status

Status option is available only for SAP UNIX nodes.

You can use the following syntax with the r3perfagent command onWindows managed nodes tocontrol the OMi MP for SAP R/3 Performance Agent from the command line:

l r3mon-perl -S SAPMP_Tool.pl Start

l r3mon-perl -S SAPMP_Tool.pl Stop

You can also use the Services option in theWindows Control Panel to control Windows services.

OMi MP for SAP R/3 Performance Agent

TheOMi MP for SAP R/3 Performance Agent requires access to SAP to collect SAP-relatedmetrics,which it then uses to generate reports and graphs. Youmust provide the combination of SAP user-name and password in the SAPABAP_PerfMonMonitoring Template. It is particularly important for theOMi MP for SAP R/3 Performance Agent, which reads the SAP log-in information in the SAPABAP_PerfMonMonitoring Template configuration only once, during startup, and will not start if it cannot log into SAP. TheOMi MP for SAP R/3 Performance Agent attempts to log in to SAP and, if it fails, sends amessage to OMi indicating that it was unable to start as a result of authorization problems.

If you change the SAP user name-password combination that the OMi MP for SAP uses to log in toSAP, you need tomake sure that the changes are reflected in the SAPABAP_PerfMonMonitoring Template Parameters and, in addition, that the OMi MP for SAP components which use theinformation in the SAPABAP_PerfMonMonitoring Template configuration are restarted tomake themaware of the changes.

Stop the SAP/Performance Agent before you change the SAP user/password which the OMi MP forSAP needs for access to SAP, as follows:

1. Stop the SAP/Performance Agent

Stop the SAP/Performance Agent on all OMi MP for SAP managed nodes where it is running. Oneachmanaged node, enter:

r3mon-perl -S SAPMP_Tool.pl Stop

2. Login to SAP



Login to SAP as the administrator and change the user-password combination that OMi MP forSAP uses to log in to SAP as required.

Note:SAP requires you to change the password for dialog users more frequently than othertypes of SAP users.

3. Update SAPABAP_PerfMon Monitoring Template configuration

Configure SAP ABAP Application Server CI using SAPABAP_PerfMonMonitoring Template. Youmust provide the User Name, Password, and Client Number.

4. Restart the SAP/Performance Agent

Restart the SAP/Performance Agent on each of the OMi MP for SAP managed nodes where theSAP/ Performance Agent is running. On eachmanaged node, enter:

r3mon-perl -S SAPMP_Tool.pl Start

Note: TheOMi MP for SAP cannot collect performancemetrics during the period when theSAP/ Performance Agent is not running.

SAP/Performance Agent Tools

The following table shows tools available for the SAP/Performance Agent with OMi MP for SAP—SAPR/3 NT or SAP R/3 UNIX.

Tool Name SAP R/3 NT SAP R/3 UN*X

Start ✓ ✓

Stop ✓ ✓

Status ✓

OMi MP for SAP Performance Monitors

TheOMi MP for SAP performancemonitors can be one of two types: snapshot or time-frame. Asnapshot monitor runs once and gathers only one set of values. Snapshot monitors need to run on aregular basis to create a comprehensive picture of the performance of the SAP NetWeaverenvironment. Time-framemonitors run, as the name suggests, over a period of time.

The following performancemonitors are available with the OMi MP for SAP and are explained in greaterdetail in the individual sections that follow:



l "DBINFO_PERF"

Monitors database-performance analysis values

l "DOCSTAT_PERF"

Collects the document volume statistics for the last full hour

l "EP_PERF"

Monitors the status and performance of the SAP Enterprise Portal

l "ICMSTAT_PERF"

Monitors the status and performance of the SAP Internet CommunicationManager

l "JOBREP_PERF"

Counts the number of jobs per state (scheduled, running)

l "SAPBUFFER_PERF"

Returns values for the use of SAP buffers for a SAP instance

l "SAPABAP_PerfMon"

Monitors SAP memory use by SAP users for a SAP instance

l "SPOOL_PERF "

Counts the number of spool requests in different states

l "SYSUP_PERF "

Monitors the status of the SAP NetWeaver instances

l "UPDATE_PERF"

Monitors the number of update processes

l "STATRECS_PERF"

Monitors the statistical records of SAP Transaction

l "USER_PERF "

Monitors the number of users and user sessions per SAP client

l "WLSUM_PERF "

Collects the performance-workload statistics hourly

l "WP_PERF"



Monitors the number of users/sessions per SAP client for an SAP application server.

DBINFO_PERF

The DBINFO_PERF performancemonitor returns a set of values as they are displayed in the SAPdatabase-performance analysis page. This information can be used to detect database performanceproblems and assess whether database tuning could improve database performance.

Note: The DBINFO_PERF performancemonitor works only with Oracle database data structures.It does not work with data structures from other database products.

Type

The DBINFO_PERF performancemonitor is of type snapshot. Onemonitor run gathers only one valueset.

Frequency

It is recommended to run the DBINFO_PERF performancemonitor once every 15minutes.

Datasource

The DBINFO_PERF performancemonitor uses the SAP transaction ST04 (DB performance overview)as its data source.

Metrics

The following table shows the values in the performance table returned by the DBINFO_PERFperformancemonitor.

Order Metric Name Description%Value Cumulation

1 CPUUSAGE Database CPU usage No

2 BUFPREADS Physical reads Yes

3 BUFPWRITES Physical writes Yes

4 BUFQUAL Quality of data base buffer pool % No

5 BUFSIZE Database buffer pool size Static

6 BUFWAITS Buffer busy waits Yes

7 BUFWTIME Buffer busy wait time Yes



Order Metric Name Description%Value Cumulation

8 DICTSIZE Dictionary cache size Static

9 DDQUAL Quality of Data Dictionary cache % No

10 LOGBLOCKS Redo log blocks written Yes

11 LOGENTRIES Redo log buffer entries Yes

12 LOGSIZE Redo log buffer size Static

13 LOGFAULT Allocation error rate of redo logbuffer

% No

14 LOGALLOC Redo log buffer allocation retries Yes

15 ROLLBACKS Rollbacks Yes

16 SCANLONG Long table scans Yes

17 SORTDISK Sort disk Yes

18 SORTMEM Sort memory Yes

19 SORTROWS Sort rows Yes

DOCSTAT_PERF

The performancemonitor, DOCSTAT_PERF, collects statistics relating to the volume of documentsgenerated and processed for the last full hour. You can only configure this monitor once for every SAPNetWeaver System that you want to monitor.

Type

The DOCSTAT_PERF performancemonitor is of type snapshot. Onemonitor run gathers only onevalue set.

Frequency

It is recommended to run the DOCSTAT_PERF performancemonitor hourly.

Data Source

The DOCSTAT_PERF performancemonitor uses the SAP transaction ST07 (quantity structure) as itsdata source.

Metrics



The following table shows the values in the performance table returned by the DOCSTAT_PERFperformancemonitor.

Order Metric Name Description

1 SID The SAP System ID

2 DESCRIPTION Description of an application-monitor object

3 CNTHEADER Document headers

4 CNTITEM Document items

5 CNTDIV Document division

6 CNTTOTAL Total number of records

7 CNTLINE Number of line items

8 CNTCHGDOC The number of changed documents

9 CNTTEXT Text

EP_PERF

The performancemonitor, EP_PERF, monitors the status and performance of the SAP EnterprisePortal (EP) including (but not limited to) all the J2EE components on which it relies.

Note:EP_PERF is applicable wherever Enterprise Portal is available.

Type

The EP_PERF performancemonitor is of type time-frame. Onemonitor run gathers only one value set.

Frequency

It is recommended to run the EP_PERF performancemonitor approximately once every fifteenminutes.

Datasource

The EP_PERFmonitor uses the CCMS as its data source.

Metrics

The following table shows the values in the performance table returned by the EP_PERF performancemonitor.




1 SID_EP ID of the SAP System hosting the Enterprise Portal

2 HOSTNAME_EP Name of the system hosting the Enterprise Portal

3 START_TIME_EP The time at which the EP-monitor run starts

4 NO_REQ_EP Number of requests to the Enterprise Portal

5 AVG_RESP_TIME_EP Average time to respond to requests to theEnterprise Portal

6 AVG_CPU_TIME_EP* Average CPU time required to respond to requeststo the Enterprise Portal

7 REQ_PER_SEC_EP Number of requests per second to the EnterprisePortal

8 AVG_OUTBND_DATA_EP Average amount of out-bound data per request tothe Enterprise Portal

9 ACC_RESP_TIME_EP Accumulated response time of requests to theEnterprise Portal

10 ACC_CPU_TIME_EP* Accumulated CPU time required to respond to EPrequests

11 OUTBND_DATA_REQ_EP Requests providing outbound data

12 ACC_OUTBND_DATA_EP Amount of accumulated outbound data (in bytes)

13 NO_COMPCALLS_REQ_EP Number of component calls by all requests to theEnterprise Portal

14 AVG_CMPCALLPERREQ_EP Average number of component calls per EP request

15 VALID_MONDATA_REQ_EP EP requests providing correct monitor data

16 REQ_NOT_CORR_CLSD_EP EP requests with components that were notcorrectly closed

17 REQCLSD_TOOMNYCMP_EP Number of EP requests that were closed because oftoomany components

18 REQS_RUNLEVEL_0_EP EP requests running with level 0



21 USRS_SINCE_1_REQ_EP Number of users making EP requests since the firstrequest

22 USRS_SINCE_LSTRST_EP Number of users making EP requests since the last




user reset

23 LST_REQ_RST_TSTMP_EP Time of the last EP-request reset

24 LST_CMPREQ_TSTMP_EP Time of the last component reset

25 LST_USRREQ_TSTMP_EP Time of the last EP-user reset

*Applicable only for SAP NetWeaver portal version 7.0

Note: If the performancemonitor EP_PERF cannot find any data or it encounters a null string inSAP CCMS, it logs some performancemetrics as '0' (zero); this behavior is expected.

ICMSTAT_PERF

The performancemonitor, ICMSTAT_PERF, monitors the status and performance of the SAP InternetCommunicationManager (ICM).

Type

The ICMSTAT_PERF performancemonitor is of type snapshot. Onemonitor run gathers only onevalue set.

Frequency

It is recommended to run the ICMSTAT_PERF performancemonitor approximately once every fifteenminutes.

Datasource

The ICMSTAT_PERFmonitor uses the SAP transaction SMICM (ICMmonitor) as its data source.

Metrics

The following table shows the values in the performance table returned by the ICMSTAT_PERFperformancemonitor:


1 ICM_Status The status of the Internet CommunicationManager

2 Max_Threads The definedmaximum number of open threads allowed by the ICM

3 Peak_Threads

Peak number of open threads in the ICM in a given period




4 Cur_Threads Number of currently open threads in the ICM

5 Max_Connections

The definedmaximum number of open connections allowed by theICM

6 Peak_Connections

Peak number of connections in the ICM in a given period

7 Cur_Connections

Number of current connections in the ICM

8 Max_QueueEntries

Themaximum number of queued requests allowed by the ICMdefined in: icm/req_queue_len

9 Peak_QueueEntries

Peak number of queued requests in the ICM in a given period

10 Cur_QueueEntries

Number of currently queued requests in the ICM

11 Running_Threads

Number of work threads waiting for a request (idle)

12 Dead_Threads

Number of work threads in a problematic state, for example, deador hanging

13 Processed_Threads

Number of work threads currently processing a request

JOBREP_PERF

The JOBREF_PERF performancemonitor counts the jobs per state in the time period between the enddate and time of the last monitor run and the start date and time of the actual monitor run.

Type

The JOBREF_PERFmonitor is of type time-frame. Onemonitor run gathers only one value set.

Frequency

It is recommended to run the JOBREF_PERF performancemonitor between once an hour and once aday.

Datasource

The JOBREF_PERFmonitor uses the SAP transaction SM37 (background job overview) as its datasource.

Metrics



The following table shows the values in the performance table returned by the JOBREF_PERFperformancemonitor:


1 RUNNING The number of jobs with status running since the last monitorrun

2 READY The number of jobs with status ready since the last monitorrun

3 SCHEDULED The number of jobs with status scheduled since the lastmonitor run

4 RELEASED The number of jobs with status released since the lastmonitor run

5 ABORTED The number of jobs with status aborted since the last monitorrun

6 FINISHED The number of jobs with status finished since the last monitorrun

7 PUT_ACTIVE The number of jobs with status put_active since the lastmonitor run

8 UNKNOWN_STATE

The number of jobs with status unknown since the lastmonitor run

SAPBUFFER_PERF

The SAPBUFFER_PERF performancemonitor returns values for the use of SAP memory buffers bySAP users for a given instance, for example, hit ratios, buffer quality, free space available and so on inthe NetWeaver repository, programs, and database tables.

Type

The SAPBUFFER_PERFmonitor is of type time frame.

Frequency

It is recommended to run the SAPBUFFER_PERF performancemonitor once every fifteenminutes.

Data Source

The SAPBUFFER_PERFmonitor reads information from the SAP- buffers transaction ST02.

Metrics



The following table shows the values in the performance table returned by the SAPBUFFER_PERFperformancemonitor.


1 BUFFER_NAME

The name ofthe buffer

2 HITRATIO Bufferobject reads/ logicalrequests.The bufferhit ratioappears asapercentage

3 ALLOCATED_SIZE

The amountof spaceallocated tothe buffers 1

4 FREE_SPACE

The amountof freespace (KB)available inthe buffer

5 FREE_SPACE_PERCENT

Availablefree bufferspace as apercentageof total

6 MAXDIR_ENTR

The numberofdirectoriesavailable forthe buffer 2

7 FREEDIR_ENTR

Number offreedirectoriesavailable forthe buffer

8 FDIR_ENTR_PERCENT

Freedirectoriesavailable forthe buffer as




apercentage

9 BUFFER_SWAPS

Swapactivity bothinwards andoutwardssinceSystemstart 3

10 BUFFER_SWAPS_DELTA

Differencebetween thenumber ofbufferswapsmeasured inthe currentandpreviousmonitor runs

11 DB_ACCESSES

The numberof databaseaccessessinceSystemstart 4

12 DB_ACCESSES_DELTA

Differencebetween thenumber ofdatabaseaccessesmeasured inthe currentandpreviousmonitor runs

1. Buffer size and “available buffer size” differ, because part of the buffer space is used for buffermanagement.

2. The buffer directories point to the location of the objects stored in the buffer.

3. Buffers swap objects out of the buffer to load a new object in, if insufficient free space or free



directories exist.

4. Database access occurs when an object cannot be read from the buffer.

Type

The SAPMEMORY_PERFmonitor is of type snapshot: onemonitor run gathers one value set.

Frequency

It is recommended to run the SAPMEMORY_PERF performancemonitor once every fifteenminutes.

Data source

The SAPMEMORY_PERFmonitor reads information from the SAP- buffers transaction ST02.

Metrics

The following table shows the values in the performance table returned by the SAPMEMORY_PERFperformancemonitor:

OrderMetricName Description

1 MEMORY_AREA

The type of memory buffer

2 CURRENT_USE_PERCENT

The amount of space currently used expressedas a percentage of the total available

3 CURRENT_USE

The amount of space currently used in KB

4 MAX_USE Themaximum value (max. use) since systemstartup

5 IN_MEMORY

The amount of space used in sharedmemory

6 ON_DISK The amount of space used on the disk

SPOOL_PERF

The SPOOL_PERF performancemonitor counts the number of spool requests present in differentstates.

Type



The SPOOL_PERF performancemonitor is of type time frame and does not make use of alert types orparameters. Onemonitor run gathers only one value set. The SPOOL_PERF performancemonitorcollects SID-relatedmetrics and should run only once per monitored SID, that is: either on the SAPcentral instance or on one application server.

Frequency

It is recommended to run the SPOOL_PERF performancemonitor once every 10 to 30minutes.

Data Source

The SPOOL_PERF performancemonitor uses the SAP transaction SP01 (output controller) as its datasource.

Metrics

The following table shows the values in the performance table returned by the SPOOL_PERFperformancemonitor.

OrderMetricName Description

1 ALL_SJ Total number ofspool jobs

2 SJ_ARCHIVE

Number of spooljobs in statusarchive

3 PRINT_REQ

Total number ofprint requests

4 OPEN_PR Number of openprint requests

5 SUCCESS_PR

Number ofsuccessfullyprocessed printrequests

6 ERROR_PR

Number of Printrequests witherrors

7 FAILED_PR Number of failedprint requests



SYSUP_PERF

The SYSUP_PERF performancemonitor is used to determine whether the SAP NetWeaver system isavailable or not.

Type

The SYSUP_PERF performancemonitor is of type snapshot. Onemonitor run gathers only one valueset.

Frequency

The SYSUP_PERF performancemonitor runs once aminute; the run frequency cannot bemodified.

Data Source

The SYSUP_PERF performancemonitor uses internal SAP RFC calls as its data source.

Metrics

The following table shows the values in the performance table returned by the SYSUP_PERFperformancemonitor.

Metric Name Description

SYSTEM_STATUS

Status of the System (UP/DOWN) on the basis of thefollowing values:

l SAP System available

l SAP System logon failure

l SAP System communication problems

l SAP System unknown

Indicates that the performance agent was not runningand could not collect any data.

UPDATE_PERF

The UPDATE_PERF performancemonitor is used to determine whether update errors are occurring.

When the SAP NetWeaver system is behaving well, no update errors should occur. However, anupdate error can occur, if an update is performed on a database table record that has previously beendeleted. A normal update process should not have to wait in status INIT for more than 5minutes for an



update task. If a greater number of work processes exist with the status INIT the reason could be that atable space is full.

Type

The UPDATE_PERFmonitor is of type snapshot. Onemonitor run gathers only one value set.

Frequency

It is recommended you configure the UPDATE_PERF performancemonitor to run once aminute.

Data Source

The UPDATE_PERFmonitor uses the SAP transaction SM13 (update records) as its data source.

Metrics

The following table shows the values in the performance table returned by the UPDATE_PERFperformancemonitor:


1 ALL Number of all VB-update tasks

2 INITIAL Number of initial VB-update tasks

3 ERRONEOUS Number of erroneous VB-update tasks

4 VB1 Number of update tasks having V1 executed

5 VB2 Number of update tasks having V2 executed

STATRECS_PERF

The SAPABAP_StatRecMonMonitoring Template reads the statistical records and returns the averageresponse time per transaction.

The SAPABAP_StatRecMonMonitoring Template uses the alert types RESPONSE_TIME and theparameter TRANSACTION to restrict the data selected. The transactions monitored are specified inthe parameter TRANSACTION. If this parameter is not specified, the average response time isreported for each transaction in the local statistics file for the specified time frame. For moreinformation, see "SAPABAP_StatRecMon" Monitoring Template.



USER_PERF

The USER_PERF performancemonitor provides important information about the number of users anduser sessions per SAP client for a given SAP application server.

Type

The USER_PERFmonitor is of type snapshot.

Frequency

It is recommended to run the USER_PERF performancemonitor once every fiveminutes.

Data source

The USER_PERF performancemonitor the SAP transaction SM04 (overview of users) as its datasource.

Metrics

The following table shows the values in the performance table returned by the USER_PERFperformancemonitor:


1 USER_CLIENT

The SAP client numberassociated with the users

2 USER_CNT The number of users logged inper client

3 SESSION_CNT

The total number of usersessions per client

WLSUM_PERF

The performancemonitor, WLSUM_PERF, collects the performance workload statistics for the last fullhour. You can display the workload statistics for all task types, for example, dialog, background, RFC,ALE, or update. TheWLSUM_PERF performancemonitor is mandatory; youmust configure it forevery application server that you want to monitor.

Note: The data collection for theWLSUMmonitor is based on the internal SAP job COLLECTOR_FOR_PERFORMANCEMONITOR. This jobmust run with the same frequency as specified for



WLSUM_PERF in SAPABAP_PerfMonMonitoring Template. WLSUM_PERF will then pick upthe data collected by the last run of COLLECTOR_FOR_PERFORMANCEMONITOR.

Type

TheWLSUM_PERF performancemonitor is of type time-frame. Onemonitor run gathers only onevalue set.

Frequency

Due to the way in which the performancemonitor, WLSUM_PERF, measures and records time, it ismandatory to configure theWLSUM_PERF performancemonitor to run once an hour.

Data source

TheWLSUM_PERF performancemonitor uses the SAP transaction ST03 (workload analysis) as itsdata source.

Metrics

The following table shows the values in the performance table returned by theWLSUM_PERFperformancemonitor:


1 Hostname The SAP System hostname

2 SID The SAP System ID

3 INSTANCE The SAP instance number, if SAP version < 4.6x

4 TASKTYPE Type of SAP NetWeaver task (RFC, dialog)

5 CNT The number of dialog steps

6 DBACTIVCNT Counter for database-active dialog steps

7 RESPTI Time that elapses between a dialog sending arequest to the dispatcher and receiving a response

8 CPUTI CPU time used in the work process

9 QUEUETI The time an unprocessed dialog step waits in thedispatcher queue for a free work process

10 LOADGENTI Time taken loading and generating objects such asABAP source code and screen information from thedatabase

11 COMMITTI Time required for commit to complete




12 DDICTI Time required for Data Dictionary

13 QUETI Time required for batch-input queue

14 CPICTI Time required for RFC and CPI-C

15 ROLLINCNT Number of roll-ins (rolled-in user contexts)

16 ROLLINTI Processing time for roll-ins

17 ROLLOUTCNT Number of roll-outs (rolled-out user contexts)

18 ROLLOUTTI Processing time for roll-outs

19 READDIRCNT Number of direct read accesses

20 READDIRTI Time for direct read access

21 READSEQCNT Number of sequential read attempts

22 READSEQTI Time for sequential read accesses

23 CHNGCNT Number of modified database accesses

24 CHNGTI Time for modified database accesses

25 BYTES Number of bytes

26 GUITIME Total time taken for the dispatcher to execute aGUIrequest

27 GUICNT Count of GUI steps

28 GUINETTIME Time taken for the application server to respond to arequest from the SAP GUI

WP_PERF

TheOMi MP for SAP performance agent uses theWP_PERFmonitor to detect performance problemsconcerning SAP work processes. For example, WP_PERF can detect and report on the followingsituations:

l Work processes need to wait for semaphores

l Work processes are in privatemode

l A dialog work-process does not return to idle after use/release

Type



TheWP_PERFmonitor is of type snapshot. Onemonitor run gathers only one value set.

Frequency

It is recommended that you configure theWP_PERF performancemonitor to run once every 15minutes.

Data Source

TheWP_PERF performancemonitor uses SAP transaction SM50 (work- process overview) as its datasource.

Metrics

The following table shows the values in the performance table returned by the performancemonitor:


1 ALL_WP Number of all work processes

2 SEMAPHORE_WP

Number of work processeswaiting on a semaphore

3 DEBUG_WP Number of work processes indebugmode

4 LONG_RUNNING

Number of long running dialog wp

5 PRIVAT_WP Number of dialog wp in privatemode

6 NOSTART_WP Number of dialog wpwith norestart capability

7 DIA_IDLE Number of idle dialog workprocesses

8 DIA_ALL Number of dialog work processes

9 DIA_RUNNING

Number of running dialog wp

10 BTC_IDLE Number of idle batch workprocesses

11 BT_ALL Number of batch work processes

12 BTC_RUNNING

Number of running batch wp

13 SPO_IDLE Number of idle spool workprocesses




14 SPO_ALL Number of spool work processes

15 SPO_RUNNING

Number of running spool wp

16 ENQ_IDLE Number of idle enqueue workprocesses

17 ENQ_ALL Number of enqueue workprocesses

18 ENQ_RUNNING

Number of running enqueue wp

19 UPD_IDLE Number of idle update workprocesses

20 UPD_ALL Number of update workprocesses

21 UPD_RUNNING

Number of running update wp

22 UPD2_IDLE Number of idle update2 workprocesses

23 UPD2_ALL Number of update2 workprocesses

24 UPD2_RUNNING

Number of running update2 workprocesses

Removing the OMi MP for SAP R/3 Performance Agent

To remove theOMi MP for SAP R/3 Performance Agent from themanaged node, you need to performthe following steps in the order indicated:

1. Before starting the process of removing the OMi MP for SAP Performance Agent from themanaged node, make sure that you stop the performance agent. You can stop the OMi MP forSAP R/3 Performance Agent by following any of the followingmethod:a. To stop OMi MP for SAP R/3 Performance Agent using SAP ABAP Application Server - Stop

Performance Agent tool, follow these steps:i. Go to the Assignments & Tuning pane:

On BSM, click Admin > Operations Management > Monitoring > Assignments &Tuning



OnOMi, click Administration > Monitoring > Assignments & Tuning

ii. From Browse Views tab, select SAP_DeploymentView. Select theSAP ABAP Application Server or SAP J2EE Application Server on which you want tostop the performance agent.

iii. Right-click, select Launch Tool.

iv. Select Stop Performance Agent tool and click Run Tool.

For ABAP:

SAP ABAP Application Server - Stop Performance Agent

For J2EE:

SAP J2EE Application Server - Stop Performance Agent

OMi MP for SAPPerformance Agent is stopped on the selected SAP Application Server.

b. To stop OMi MP for SAP R/3 Performance Agent using command line, Use the followingcommand as root user in the command line:

r3mon-perl -S SAPMP_Tool.pl Stop

OMi MP for SAP Performance Agent is stopped on the selected SAP CI.

2. Launch SAP ABAP Application Server - Remove Performance Package. To launch the tool followthese steps:a. Go to the Assignments & Tuning window:

On BSM, click Admin > Operations Management > Monitoring > Assignments &Tuning

OnOMi, click Administration > Monitoring > Assignments & Tuning

b. From Browse Views tab, select SAP_DeploymentView. Select theSAP ABAP Application Server or SAP J2EE Application Server from which you want toremove the performance agent.

c. Right-click, select Launch Tool.

d. Select Remove Performance Package tool and click Run Tool.

For ABAP:

SAP ABAP Application Server - Remove Performance Package

For J2EE:

SAP J2EE Application Server - Remove Performance Package

OMi MP for SAP Performance Agent is removed from the selected SAP Application Server.



SAPABAP_ProcMon

The SAPABAP_ProcMonMonitoring Template enables themonitoring of different SAP ABAPprocesses.


l "File Locations"

l "Environment Variables "

l "Monitoring Conditions"

l "Sample Configuration"

File Locations

The SAPABAP_ProcMonMonitoring Template contains the files listed in the following table:

File Description

r3monpro (.exe) Executable for the process monitor.

r3monpro.cfg Configuration file for the process monitor.

r3monpro.his History file for storing data after eachmonitor run.


The SAPABAP_ProcMonMonitoring Template uses the environment variables listed in the followingtable:


SAPOPC_DRIVE TheWindows drive where the HPOM agent is running, forexample, E:\usr\...

SAPOPC_HISTORYPATH Path to the r3monpro history file

SAPOPC_R3MONPRO_CONFIGFILE

Name of the r3monpro configuration file

SAPOPC_SAPDIR TheWindows drive where SAP NetWeaver is running, forexample: E:\usr\sap



SAPOPC_TRACEPATH Path to the r3monpro trace file


Monitoring conditions for SAPABAP_ProcMonMonitoring Template are specified in the templateconfiguration. Individual rows definemonitoring conditions for specific processes. You can use theSAPABAP_ProcMonMonitoring Template to set the rules which define how the number of processesrunning should bemeasured and what severity level should be assigned to the alert that is generated ifthe number of processes exceeds the limits you define.

You can set monitoring conditions for a specific process to any of the followingmodes:

l Exact

The number of processes running on amanaged nodemust be equal to the specified number.

l Min

The number of processes running on amanaged nodemust not be less than the specified number.

l Max

The number of processes running on amanaged nodemust not bemore than the specified number.

l Delta

SAPABAP_ProcMonMonitoring Template triggers an alert if there is any change in the number ofprocesses running on amanaged node or if the specific amount of allowed change in the number ofinstances of the same process exceeds the defined limit. This mode enables you to recognizechanges without having to define an absolute number of processes for amanaged node.

For example, if Delta =2, then a difference of 2 or more between the number of processes (n) foundin the previous and current monitor run on amanaged node triggers an alert. Note that if SAPABAP_ProcMonMonitoring Template triggers an alarm, it resets n to the number of processes discoveredin themost recent monitor run, and calculates the new Delta on the basis of the new number ofprocesses found running.

Sample Configuration

The first row of the following example shows how tomonitor the saposcol process on all configuredhosts. Note that exactly one such process should run at any given time. Any violation of this number iscritical. It affects the OMi process saposcol. The associated OMi MP for SAP message group is R3_State.



The last row of the same example specifies that eight or fewer instances of the dw.sapSID processshould run on all hosts. If the number is larger than eight, themonitor generates a warningmessageassociated with OMi MP for SAP object dw.sap andOMi MP for SAPmessage group R3_State.

The string SID has special meaning in this context. SIDwill be replaced by the SAP system name onthemanaged node. This enables global definitions for different SAP Systems.

AlertInstMonPro =ALL =00 =saposcol =1 =Exact=1 =CRITICAL =saposcol =R3_State

AlertInstMonPro =C01 =00 =explorer =1 =Max =1 =CRITICAL =explorer =R3_State

AlertInstMonPro =T11 =00 =dw.sapSID =1 =Min =8 =WARNING =dw.sap =R3_State

It is also possible to ensure that a process is not running. To do so, use themode Exact and enter 0 asthe number.

Note:On servers running the UNIX operating system, SAPABAP_ProcMonMonitoring Templatecan identify processes at the instance level. On servers running theWindows operating system,you need to define on a single line the total number of work processes on the node. For example, ifthere are two SAP instances, each with four (4) work processes, the total number of processes iseight (8).

For SAP servers running on UNIX operating systems, you can configure the SAPABAP_ProcMonMonitoring Template tomonitor the specific SAP-gateway read process gwrd associated withindividual SAP SIDs, which is especially useful in amulti-SID environment. If you havemultipleinstances of SAP running in the same SID, you can configure SAPABAP_ProcMonMonitoring Template tomonitor the specific SAP-gateway read process gwrd assigned to each,individual instance, too. For more information about how to configure SAPABAP_ProcMonMonitoring Template tomonitor individual gwrd processes in an environment wheremultiple SAPinstances or multiple SAP SIDs are running on the same SAP server, have a look at the followingexamples:

l "Monitoring SAP-Gateway Read Processes per SID"

l "Monitoring SAP-Gateway Read Processes per SAP Instance"

Monitoring SAP-Gateway Read Processes per SID shows how to configure SAPABAP_ProcMonMonitoring Template tomonitor the individual gwrd processes associated with specific SIDs on a SAPserver hostingmultiple SAP SIDs.

Monitoring SAP-Gateway Read Processes per SID

AlertInstMonPro =Q12 =ALL =gwrd -dp pf=/usr/sap/

SID* =1 =Exact =1 =CRITICAL \

=gwrd =R3_State





=gwrd =R3_State

AlertInstMonPro =Q32 =ALL =gwrd -dp pf=/sapmnt/


=gwrd =R3_State



=gwrd =R3_State

Monitoring SAP-Gateway Read Processes per SAP Instance shows how to configure SAPABAP_ProcMonMonitoring Template tomonitor the individual gateway processes associated with specificSAP instances on a SAP server hostingmultiple SAP instances per SAP SID.

Monitoring SAP-Gateway Read Processes per SAP Instance

AlertInstMonPro =Q12 =12 =gwrd -dp pf=/usr/sap/

SID* =1 =Exact =1 =CRITICAL \ =gwrd =R3_State

AlertInstMonPro =Q22 =21 =gwrd -dp pf=/usr/sap/Q22/SYS/profile/

Q22_D21_sap2ap1 \ =1 =Exact =1 =CRITICAL =gwrd =R3_State

AlertInstMonPro =Q22 =22 =gwrd -dp pf=/usr/sap/Q22/SYS/profile/

Q22_D22_sap2ap1 \ =1 =Exact =1 =CRITICAL =gwrd =R3_State

AlertInstMonPro =Q32 =32 =gwrd -dp pf=/sapmnt/


AlertInstMonPro =Q52 =52 =gwrd -dp pf=/usr/sap/


In the SAPABAP_ProcMonMonitoring Template configuration, the path to the SAP-instance profiledefined in the pf parameter is case-sensitive. To avoid problems, make sure that the path to the SAP-instance profile defined in the SAPABAP_ProcMonMonitoring Template configurationmatches thepath displayed in the output of the ps command, for example:

[root@accra]# ps -eaf | grep gwrd



Q22adm 15691 15688 0 Jun 6 ? 52:54 gwrd -dp \ pf=/usr/sap/Q22/SYS/profile/Q22_D21_sap2ap1

root 20756 20599 0 10:22:58 pts/tb 0:00 grep gwrd

SAPABAP_RFCDestMon

The SAPABAP_RFCDestMonMonitoring Template enables monitoring of failed SAP RFCdestinations based on the connection type and name of the SAP RFC destinations. The SAPABAP_RFCDestMonMonitoring Template, references the RFC destinations, which you can display, create,andmaintain by means of the SAP NetWeaver transaction SM59.

Monitor Type

The SAPABAP_RFCDestMonMonitoring Template is of type snapshot. Onemonitor run gathers onlyone value set.

Alert Types

The SAPABAP_RFCDestMonMonitoring Template has the following alert type, which uses asnapshot report type:

CHECK

Defines alert conditions for failed SAP-RFC connections.

File Locations

The SAPABAP_RFCDestMonMonitoring Template uses the files listed in this table.

File Description

r3moncol (.exe) Collector executable for the SAP-RFC monitor.

r3monrfc.cfg Configuration file for the SAP-RFC monitor.

r3monrfc.log Trace file for storing trace data.

The SAPABAP_RFCDestMonMonitoring Template do not write history information to a specifichistory file.




The SAPABAP_RFCDestMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_RFCDestMonMonitoring Template uses the command-line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_RFCDestMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring RFC-destination Alert Types

Youmust configure the parameters CONNECTION_TYPE and NAME for all alert types for SAPABAP_RFCDestMonMonitoring Template, the RFC-destinationmonitor. Note the general rules below onexclude and include parameters for SAPABAP_RFCDestMonMonitoring Template.

Parameter Values

This section describes how the SAPABAP_RFCDestMonMonitoring Template interprets the includeand exclude parameter values for an alert type entry. The SAPABAP_RFCDestMonMonitoring Template compares values in different parameters using ‘and’; the SAPABAP_RFCDestMonMonitoring Template compares values in the same parameter as follows:

l Include:Use ‘or’ to compare the parameters

l Exclude:Use ‘and’ to compare the parameters

TheOMi MP for SAP evaluates include values before exclude values.



CHECK

CHECK is a snapshot alert type for SAPABAP_RFCDestMonMonitoring Template, the OMi MP forSAP’s RFC-destinationmonitor. Snapshot alert types take a picture of the SAP System at themomentthemonitor runs.

The CHECK alert type defines alert conditions for failed SAP-RFC connections. Use the CHECK alerttype to configure SAPABAP_RFCDestMonMonitoring Template to generate an alert if the RFCconnection test for the target system fails. The following table lists the parameters that you can use toconfigure the CHECK alert type and shows the value assigned to the parameters by default.

The parameter CHECK is required. The following tables provides youmore information about themeaning of the query conditions in the alert-collector monitor configuration files:

Parameter Name DescriptionQueryConditions

DefaultValue

CONNECTION_TYPE

Type of SAP RFC connection tomonitor, forexample: 1, 3, M, T... Type 1= App. Server, 3= SAPNetWeaver System, M= CMC, T =TCP/IP, G=HTTP connection to external server, H= HTTPconnections to SAP NetWeaver system.

= Sign I, E I

= Opt: EQ EQ

= Low 3

= High

NAME Name you assigned to the SAP-RFC connection asshown in the transaction /NSM59.

= Sign: I, E I

= Opt: EQ,CP

EQ

= Low:<SID>

**

= High:

The Default Check-RFC_DESTINATION Configuration

In The Default Check-RFC_DESTINATION configuration, an event generating an alert occurswhenever the RFC_DESTINATION test fails for any one of the type 3 SAP-RFC destinations.

AlertMonFun =ALL =ALL =ALL =ALL =RFC_DESTINATION =1 \

=WARNING =RFC_Destinations =R3_RFC \

=CHECK =CONNECTION_TYPE =I =EQ =3 =

Check-RFC_DESTINATION Configuration



In the following example of Check-RFC_DESTINATION Configuration, an event generating an alertoccurs whenever RFC_DESTINATION test fails for the single SAP-RFC destination namedOV_C01_099.

AlertMonFun =ALL =ALL =ALL =ALL =RFC_DESTINATION =1 \

=WARNING =RFC_Destinations =R3_RFC \

=CHECK =NAME =I =CP =OV_C01_099 =

SAPABAP_SecMon

The SAPABAP_SecMonMonitoring Template enables monitoring of the SAP ABAP Securityparameters like the privileges and authorizations of important SAP users, parameters that affect theoverall SAP.

In addition to the other SAP user roles and authorizations required by the OMi MP for SAP, you alsohave to assign the authorizations defined in the SAP user role /HPOV/SAPSPI_SECURITY_MON tothe OMi user under which SAPABAP_SecMonMonitoring Template runs before SAPABAP_SecMonMonitoring Template starts; the user role /HPOV/SAPSPI_SECURITY_MON includes authorizations(such as S_TCODE or S_USER_AUT) that are needed to execute the SAP reports, which SAPABAP_SecMonMonitoring Template calls by means of the SAP RFC interface.


l "File Locations"

l "Alert Types"

l "RemoteMonitoring using SAPABAP_SecMonMonitoring Template "

File Locations

The SAPABAP_SecMonMonitoring Template uses the files listed in the following table:

File Description

r3monsec (.exe) Executable for the SAP System-security monitor.

r3monsec.cfg Configuration file for the SAP System-security monitor.

r3monsecpw.msg Contains encrypted passwords for standard Oracle users in an SAPenvironment.

r3monsec.log File used to store trace data collected by the SAP System-security monitor.



Alert Types

The SAPABAP_SecMonMonitoring Template uses the following alert types:

l "SAP_PARAMETERS"

Monitors security-related parameters such as those defined in the SAP report RSPFPAR.

l "DEFAULT_USERS"

Monitors settings for passwords defined for SAP andOracle users to ensure that insecure defaultpasswords are not in use.

l "PRIVILEGED_USERS"

Monitors any special privileges granted to SAP users or being requested by users who are notnormally entitled.

TheOMi MP for SAP interprets include and exclude parameter values for an alert-type entry accordingto whether the values appear in the same parameters or in different parameters. TheOMi MP for SAPcompares values in different parameters using ‘and’; the OMi MP for SAP compares values in the sameparameter as follows.



TheOMi MP for SAP evaluates include values before it evaluates exclude values.

Note that the OMi MP for SAP ignores include and exclude parameters for the SAPABAP_SecMonMonitoring Template alert types SAP_PARAMETERS and DEFAULT_USERS; however, youmustuse include and exclude parameters for the alert type PRIVILEGED_USERS.

SAP_PARAMETERS

Use the SAP_PARAMETERS alert type to configure the SAPABAP_SecMonMonitoring Template tomonitor the settings of (and any changes to) security-related SAP parameters. The SAP_PARAMETERS alert type compares the values you define in the SAPABAP_SecMonMonitoring Template with the contents of the SAP report RSPFPAR, which contains security-relatedparameters for the SAP instances you aremonitoring.

The default settings for the alert type SAP_PARAMETERS reflect a small selection of the parametersdefined in the SAP report RSPFPAR; you can change the contents of the SAP_PARAMETERS



section of the SAPABAP_SecMonMonitoring Template to suit the needs of your SAP environment byadding, modifying, or removing values accordingly.

Note: The alert type SAP_PARAMETERS ignores the include (=I) and exclude (=E) parameter.

Example SAP_PARAMETERS settings

"Example SAP_PARAMETERS settings" shows how to configure SAPABAP_SecMonMonitoring Template tomonitor the SAP parameter, which defines whether SAP should automaticallyunlock locked SAP users at midnight. The example configuration tells SAPABAP_SecMonMonitoring Template to check that the automatic unlocking of locked SAP users is disabled in SAP(=EQ =0). In this example, SAPABAP_SecMonMonitoring Template would generate amessage with theseverity level “critical” if it is found that the parameter was enabled in SAP and assign the generatedmessage to the OMi message group R3_Security.

AlertMonFun =ALL =ALL =ALL =ALL =SECURITY =1\

=CRITICAL =SAP_PARAMETERS =R3_Security\

=SAP_PARAMETERS =login/failed_user_auto_unlock =I =EQ =0 =

"Default Settings for SAP_PARAMETERS" shows the default settings for the SAP_PARAMETERSalert type; if your SAP Systems are configured differently, SAPABAP_SecMonMonitoring Templatewill generate alerts. For example, in the default configuration, SAP user passwords must have 6characters or more and contain at least 4 letters and 2 integers. If you configure your SAP instance toallow passwords which do not conform to the rules defined in SAPABAP_SecMonMonitoring Templateconfiguration, for example: passwords which contain only five characters or do not contain anyintegers, SAPABAP_SecMonMonitoring Template sends amessage to themessage browser.

Note that SAPABAP_SecMonMonitoring Template does not read or check the SAP passwordsthemselves; SAPABAP_SecMonMonitoring Template compares the rules you define in the policyconfiguration for the length and form of SAP passwords with the rules defined in SAP itself forpassword creation. If the rules for password creation, form, or length in the SAPABAP_SecMonMonitoring Template differ in any way from the rules for passwords defined in SAP, the OMi MP forSAP sends amessage to themessage browser.

Default Settings for SAP_PARAMETERS

Parameter Default Value

login/failed_user_auto_unlock 0 (0=disabled; 1=enabled)

login/fails_to_session_end 3

login/fails_to_user_lock 5



Parameter Default Value

login/min_password_diff 3

login/min_password_lng 6

login/min_password_letters 4

login/min_password_digits 2

login/min_password_specials 0

login/no_automatic_user_sapstar 1

login/password_max_new_valid 10

login/password_max_reset_valid 2

login/password_expiration_time 30

login/disable_password_logon 0 (0=disabled; 1=enabled)

login/disable_multi_gui_login 0 (0=disabled; 1=enabled)

login/disable_cpic 0 (0=disabled; 1=enabled)

login/system_client 100

login/disable_multi_rfc_login 0 (0=disabled; 1=enabled)

rdisp/gui_auto_logout 1800

DEFAULT_USERS

Use the DEFAULT_USERS alert type to configure the SAPABAP_SecMonMonitoring Template, tocheck the passwords for standard SAP or Oracle database users and determine whether any well-known, default passwords are still in use. Standard SAP users include SAP*, DDIC, SAPCPIC, andEARLYWATCH. The DEFAULT_USERS alert typemakes use of the SAP report RSUSR003.

The SAPABAP_SecMonMonitoring Template configuration provides default settings for the alert typeDEFAULT_USERS. Note that the include (=I) and exclude (=E) parameter is ignored for the alert typeDEFAULT_USERS.

Default Settings


=CRITICAL =DEFAULT_USERS =R3_Security\

=DEFAULT_USERS



The default configuration for the DEFAULT_USERS alert type enables the SAP andOracle usercheck, whichmeans themonitor generates an alert if it finds a default password in use.

PRIVILEGED_USERS

Use the PRIVILEGED_USERS alert type to configure the SAPABAP_SecMonMonitoring Template,to check the authorizations granted to SAP users in the Systems you aremonitoring with the OMi MPfor SAP. The PRIVILEGED_USERS alert type compares the values defined in the SAPABAP_SecMonMonitoring Template configuration with the contents of the SAP report RSUSR005, whichlists information concerning the critical authorizations granted to SAP users. The SAPABAP_SecMonMonitoring Template generates an alert for any SAP user who has critical authorizations but is notdefined in the SAPABAP_SecMonMonitoring Template configuration.

Note: The SAP report RSUSR005 is SAP-client dependent; SAPABAP_SecMonMonitoring Template monitors only the users for the SAP clients defined inMonitoring TemplateConfiguration.

The SAPABAP_SecMonMonitoring Template does not provide any default settings for the alert typePRIVILEGED_USERS; you have to decide which user authorizations you want to monitor in SAP andinsert the strings that define them into themonitor template-configurationmanually. You can use thereport RSUSR005 to find the strings defining the authorizations you want to monitor, for example: “Allrights for background jobs”, as illustrated in"Example Settings for PRIVILEGED_USERS". Note thatyou need to use a new line for each user authorization that you want to monitor.

After you have determined which user authorizations you want to monitor, set the include (=I) orexclude (=E) parameter to specify which SAP users you want to check for the use (or misuse) of thedefined authorization "Example Settings for PRIVILEGED_USERS" shows how to exclude SAP userKWAME from the check to determine which users have permission to execute external operating-system commands.

Example Settings for PRIVILEGED_USERS


=CRITICAL =PRIVILEGED_USERS =R3_Security\

=PRIVILEGED_USERS =All rights for background jobs =I =EQ =ALL =



=PRIVILEGED_USERS =Execute external operating system commands\

=E =EQ =KWAME =



Note that the string you paste into the SAPABAP_SecMonMonitoring Templatemust match anexisting string in SAP. If the string you paste into the SAPABAP_SecMonMonitoring Templateconfiguration does not exist in SAP, for example because it contains a typo or is only a sub-set of aknown SAP user-authorization string, nomatch occurs and the SAPABAP_SecMonMonitoringTemplate does not send any message to themessage browser. For example: “Execute externaloperating” would not match, since it is only a part of the complete user-authorization string “Executeexternal operating system commands” defined in the SAPABAP_SecMonMonitoring Template.

Remote Monitoring using SAPABAP_SecMon Monitoring

Template

Tomake use of the remote-monitoring feature provided by the SAPABAP_SecMonMonitoringTemplate, for example, to monitor security on an SAP server running on an operating system that is notsupported by the OMi MP for SAP or on an SAP node where the Operations Agent is not installed, youneed to enable the RemoteMonitoring keyword (by removing the leading hash symbol “#”) in theSAPABAP_SecMonMonitoring Template configuration.

You also need to specify the name of the local host, which you want to perform themonitoring and thename of the remote SAP server, whose security settings you want to monitor. Note that youmust adda new line for each additional SAP server, which you want to monitor remotely.

Default SAPABAP_SecMon Monitoring Template Configuration

#------------------------------------------------------------

# TraceLevel hostname Disable=0 only error messages=1

# info messages=2 debug messages=3

#

TraceLevel =ALL =0

#---------------------------------------------------------------------------



TraceFile =ALL =r3monsec.log =w =60

#--------------------------------------------------------------------------

# History hostname path

# Path



#

HistoryPathUnix =ALL =default

HistoryPathAIX =ALL =default

HistoryPathWinNT =ALL =default

#--------------------------------------------------------------------------

# Remote Local Remote

# Monitoring Host Host

RemoteMonitoring =sap1 =sdsap

#--------------------------------------------------------------------------

# AlertMonFun SAP SAP SAP SAP Alertmonitor Enable =1/

\

# Hostname System Number Client Disable=0

\

#

# OpC OpC OpC \

# Severity Object MsgGroup \

#

# Alerttype RFC Parameter

# =Parameter =Sign =Opt =Low =High

# [=Param =Sign =Opt =Low =High] ...


=CRITICAL =SAP_PARAMETERS =R3_Security\

=SAP_PARAMETERS =login/failed_user_auto_unlock =I =EQ =0 =


=CRITICAL =DEFAULT_USERS =R3_Security\

=DEFAULT_USERS = = = = =





=PRIVILEGED_USERS =All rights for background jobs =I =EQ =ALL =

SAPABAP_SplMon

The SAPABAP_SplMonMonitoring Templatemonitors the following entries in the print requests:

l Spooler entries: The number of spool requests which would generate an alert.

l Error generating spool requests: The number of error-generating spool requests that would generatean alert

l Erroneous spooler entries: A specified printer has received erroneous spool requests.

The SAPABAP_SplMonMonitoring Template references output tasks in SAP NetWeaver transactionSP01 and report sources in SAP NetWeaver transaction SE38.

Monitor Type

The SAPABAP_SplMonMonitoring Template is of type snapshot. Onemonitor run gathers only onevalue set.

Alert Types

The SAPABAP_SplMonMonitoring Template has the following alert types:

l "SPOOL_ENTRIES_RANGE"

This defines the number of spool requests which, if exceeded, would cause an alert.

l "SPOOL_ERROR_RANGE"

This defines the number of error-generating spool requests which, if exceeded, would cause analert.

l "PRINT_ERROR_EXISTS"

This specifies the name(s) of printers for which an alert would be generated if a spool error exists.

File Locations

The SAPABAP_SplMonmonitor uses the files listed in this table.

File Description

r3moncol (.exe) Collector executable for the spooler monitor

r3monspl.cfg Configuration file for the spooler monitor.

r3monspl.log Trace file for storing trace data.



The SAPABAP_SplMonMonitoring Template does not write history information to a specific historyfile.


The SAPABAP_SplMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_SplMonMonitoring Template uses the command line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_SplMonMonitoring Template tomonitor anotherSAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring Alert Types

You can configure SAPABAP_SplMonMonitoring Template, the spooler monitor, for each of the alerttypes and then define exceptions for different monitoring conditions. For more detailed information, seethe alert-type tables which give the parameters and configuration for each alert type.

SPOOL_ENTRIES_RANGE

The SPOOL_ENTRIES_RANGE alert type defines the number of spool requests which, if exceeded,would generate an alert. Use the SPOOL_ENTRIES_RANGE alert type to configure SAPABAP_SplMonMonitoring Template to generate an alert if the number of spool entries exceeds the rangespecified. The following table lists the parameters that you can use to configure the SPOOL_ENTRIES_RANGE alert type and shows the value assigned to the parameters by default:

The configuration of the RANGE parameter is mandatory.


QueryConditions

DefaultValue

RANGE The number of spool entries outside of which analert will be generated.

Note that, despite its name, you do not need tospecify this parameter as a select-option range.

= Sign: I, E I

= Opt: EQ, GT,GE, LE, LT, BT

GT

= Low: * 50

= High:



*Specify this parameter as a number. Otherwise themonitor ends with a dump.

In the Default SPOOL_ENTRIES_RANGE Configuration, an event generating an alert occurs if therearemore than 50 spooler entries.

The Default SPOOL_ENTRIES_RANGE Configuration

AlertMonFun =ALL =ALL =ALL =ALL =SPOOLER =1\

=CRITICAL =Spool =R3_Spooler \

=SPOOL_ENTRIES_RANGE =RANGE =I =GT =50 =

SPOOL_ERROR_RANGE

The SPOOL_ERROR_RANGE alert type defines the number of erroneous spool requests which, ifexceeded, would generate an alert. Use the SPOOL_ERROR_RANGE alert type to configureSAPABAP_SplMonMonitoring Template to generate an alert if the number of erroneous spool entriesexceeds the range specified. The following table lists the parameters that you can use to configure theSPOOL_ERROR_RANGE alert type and shows the value assigned to the parameters by default:

Note: The configuration of the RANGE parameter is mandatory.

Parameter Name DescriptionQueryConditions Default Value

RANGE The number of erroneous spool requestsoutside of which an alert will begenerated.

Note that, despite its name, you do notneed to specify this parameter as aselect option range.

= Sign: I, E I

= Opt: EQ, GT,GE,LE, LT, BT

GT

= Low: * 50

= High:

*Specify this parameter as a number; otherwise themonitor ends with a dump.

In the Default SPOOL_ERROR_RANGE Configuration, an event generating an alert occurs if there aremore than 50 erroneous spool requests.

The Default SPOOL_ERROR_RANGE Configuration


=CRITICAL =Spool =R3_Spooler \

=SPOOL_ERROR_RANGE =RANGE =I =GT =50 =



PRINT_ERROR_EXISTS

The PRINT_ERROR_EXISTS alert type defines the printers to monitor for spool errors. Use thePRINT_ERROR_EXISTS alert type to configure SAPABAP_SplMonMonitoring Template to generatean alert if a spool error exists for the specified printer. The following table lists the parameters that youcan use to configure the PRINT_ERROR_EXISTS alert type and shows the value assigned to theparameters by default.

The SAPABAP_SplMonMonitoring Template generates an alert if a spool error exists for a specifiedprinter. The configuration of the PRINTER parameters is mandatory.


QueryConditions

DefaultValue

PRINTER The printer(s) which should be checked for spoolentries of state error.

= Sign: I, E I

= Opt: CP

= Low: *

= High:

In the Default PRINT_ERROR_EXISTS Configuration, SAPABAP_SplMonMonitoring Templategenerates an alert if any printer has a spool entry-state error.

The Default PRINT_ERROR_EXISTS Configuration


=WARNING =Spool =R3_Spooler \

=PRINT_ERROR_EXISTS =PRINTER =I =CP =* =

SAPABAP_StatRecMon

The SAPABAP_StatRecMonMonitoring Template reads the statistical records and returns the averageresponse time per transaction.

The SAPABAP_StatRecMonMonitoring Template uses the alert types RESPONSE_TIME and theparameter TRANSACTION to restrict the data selected. The transactions monitored are specified inthe parameter TRANSACTION. If this parameter is not specified, the average response time isreported for each transaction in the local statistics file for the specified time frame.

Type



The SAPABAP_StatRecMonMonitoring Template is time-frame based. Each run gathers only onevalue set. To collect a set of values, themonitor must be scheduled on a regular basis. Since variousmonitors have different requirements, you have to specify the interval for eachmonitor individually.This monitor uses the time frame between the last start and the current start times and considers onlythose transactions which complete within the specified time-frame.

The SAPABAP_StatRecMonMonitoring Template collects application-server-specific metrics; itshould run on each application server whose performance you want to monitor.

Frequency

It is recommended that you configure the SAPABAP_StatRecMonMonitoring Template to run once aminute.

Data Source

The SAPABAP_StatRecMonMonitoring Template uses the following SAP transaction as its datasource:

l For SAP 7.0 and higher: STAD

Metrics

The following table shows the values in the performance table returned by the SAPABAP_StatRecMonMonitoring Template.


1 SAP_TCODE Transaction code associated withthemeasured transaction.

This metric is only visible with theHP PerformanceManager.

2 SAP_RESPONSE_TIME Time SAP takes to respond.

3 SAP_NET_TIME Net Time.

4 SAP_REC_COUNT The number of times themeasuredtransaction occurs.

SAPABAP_StatusMon

The SAPABAP_StatusMonMonitoring Template enables monitoring of the SAP ABAP ApplicationServer's Availability Status.



The SAPABAP_StatusMonMonitoring Template is of type time frame. It runs every twominutes andcompares the current value with the previous value stored in the history file and generates amessage ifit finds a difference, which it needs to report.

Note: The lack of response from SAP could be due to a problem which does not mean that theSystem is down. For example, SAP would not respond if all available dialog work processes wereallocated. For more information about how SAPABAP_StatusMonMonitoring Template interpretsthe responses it receives from SAP, see "Establishing the SAP Status".

File Locations

Th following table lists the files used by the SAPABAP_StatusMonMonitoring Template.

File Description

r3status (.exe) Executable for the SAPABAP_StatusMonMonitoring Template

r3status.log The SAPABAP_StatusMonMonitoring Template creates a log/trace file after eachrun of themonitor. The trace file is stored in the standard OMi MP for SAP Agentlog directory.

r3itosap.cfg The SAPABAP_StatusMonMonitoring Template uses the initial user name andpassword in the r3itosap.cfg to determine which SAP instances it is supposedtomonitor.

r3status.cfg The SAPABAP_StatusMonMonitoring Template uses information in templateconfiguration to determine history paths, trace levels, and which SAP instances itis supposed tomonitor on remote SAP servers.

r3status.his History file for storing data after each run of the SAPABAP_StatusMonMonitoring Template. The SAPABAP_StatusMonMonitoring Template usesinformation in this file to determine whether a change of status has occurred. Formore information, see "History File".


The following table lists the environment variables used by the SAPABAP_StatusMonMonitoringTemplate:


SAPOPC_RFC_TIMEOUT Set time out value for RFC connections -default is 20 seconds.

SAPOPC_HISTORYPATH Path to the r3status.his history file.

SAPOPC_R3STATUS_CONFIGFILE Name of the configuration file, which the




SAPABAP_StatusMonMonitoring Template uses.

SAPOPC_R3ITOSAP_CONFIGFILE Name of the general configuration file,which contains information used by theOMi MP for SAP.

SAPOPC_TRACEPATH Path to the SAPABAP_StatusMonMonitoring Template trace file.

History File

The first time the SAPABAP_StatusMonMonitoring Template runs, it writes its findings to the historyfile, r3status.his. The next time the SAPABAP_StatusMonMonitoring Template runs, it uses theinformation in the r3status.his file to determine whether a change of status has occurred since thelast time themonitor ran and, as a consequence, which if any message it has to send to the OMi.

The SAPABAP_StatusMonMonitoring Template updates the entries in the r3status.his file at theend of each time it runs, with the current timestamp and the current status of eachmonitored SAPinstance.

The following excerpt from the r3status.his file shows the format and contents of the r3status.hisfile.

Excerpt from the r3status.his file

021028-11:18:29

#---------------------------------------------------------------

021028-11:18:29 #Keyword SAP SAP SAP State

021028-11:18:29 # System Number Instance

021028-11:18:29 #

021028-11:18:29 ConfiguredInstance =DEV =00 =DVEBMGS00 =UP

021028-11:18:29 ConfiguredInstance =PKR =99 =DVEBMGS99 =DOWN

-----------------------------------------------------------------------------

---



Configuring SAPABAP_StatusMon Monitoring Template

You can configure the SAPABAP_StatusMonMonitoring Template using the keywords listed below tochange the configuration from default settings tomeet the requirements of your particular environment.Where appropriate, possible values for a given keyword are also specified. The default SAPABAP_StatusMonMonitoring Template configuration shows a completeMonitoring Template configuration,whichmonitors the status of both local and remote SAP Systems.

The following standard keywords work as expected in the context of the SAPABAP_StatusMonMonitoring Template:

l TraceLevel

l TraceFile

l HistoryPath [Unix | AIX |WinNT]

The following keywords require special attention when used in the context of the OMi MP forSAPSAPABAP_StatusMonMonitoring Template:

l EnableDPQueueCheck

SAPABAP_StatusMonMonitoring Template requires a dialog work process to log on to SAP anddetermine the System’s status. Enable the EnableDPQueueCheck keyword (=1) if the SAPSystem whose status you aremonitoring is experiencing performance problems and you wantSAPABAP_StatusMonMonitoring Template to check the size and status of the ABAP dispatcherbefore starting its monitor run. If there are no, or too few, dialog work processes available,SAPABAP_StatusMonMonitoring Template sends amessage to themessage browser indicatingthat it did not start due to the violation of a threshold defined for dialog processes. The commanddisables themonitor run only for the SIDs where the threshold violation for the dialog workprocesses occurred.

If you use the EnableDPQueueCheck keyword in the SAPABAP_StatusMonMonitoring Template,remember to configure the keywords DPQueueCheck and DisableMonitoringWithSeverity in theSAPABAP_DispMonMonitoring Template configuration, too. For more information aboutmonitoring the SAPABAP_DispMonMonitoring Template, see "SAPABAP_DispMon"Monitoring Template.

The default run interval for SAPABAP_StatusMonMonitoring Template is twominutes. If your SAPlandscape consists of large numbers of SAP instances running onmultiple hosts, networkcongestion or a slow response from SAP might prevent EnableDPQueue from checking the statusof the ABAP dispatchers on all the configured SAP instances before SAPABAP_StatusMon



Monitoring Template starts its next run. In the unlikely event that this happens, the old instance ofSAPABAP_StatusMonMonitoring Template aborts without reporting the status of any dispatchersthat it has not yet checked. To avoid this problem re-occurring, increase the run interval forSAPABAP_StatusMonMonitoring Template.

l RemoteMonitoring

SAPABAP_StatusMonMonitoring Template cannot check the status of the ABAP dispatcher on aSAP System, which the OMi MP for SAP is monitoring remotely.

Establishing the SAP Status

When the SAPABAP_StatusMonMonitoring Template checks the availability of an SAP System, itreports the status as: Up, Down, or Connection time-out. Although themeaning of “Up” and “Down” isclear, the status of the connection time-out status requires some explanation. The time-out statuscould occur if the SAP System is hanging, in which case the problem could be due to an RFC time out,which itself needs investigating and is a good example to show how difficult it can be sometimes toestablish the exact state of the SAP System theOMi MP for SAP is monitoring.

The SAPABAP_StatusMonMonitoring Template, considers an SAP instance as “not available” if theSAP instance does not respond within 60 seconds. However, the lack of response from SAP could bedue to a problem which does not mean that the System is down, for example: all available dialog workprocesses are allocated, or all available SAP gateway connections are busy. TheOMi MP for SAP's,SAPABAP_StatusMonMonitoring Template, reports the status of the SAP System it is monitoringaccording to the following rules:

l Available:

SAPABAP_StatusMonMonitoring Template reports an SAP System as available if it can log on tothe SAP instance and, in addition, start and receive a response from the SAP functionmoduleRFC_SYSTEM_INFOwithin 60 seconds.

l Not Available:

SAPABAP_StatusMonMonitoring Template reports an SAP System as not available if the SAPinstance does not respond within 60 seconds or the functionmodule RFC_SYSTEM_INFO couldnot start, for example: due to the fact that the instance is down.



Monitoring SAP Remotely

Tomake use of the remote-monitoring feature provided by the OMi MP for SAP, for example, to monitora SAP server running on an operating system that is not supported by the OMi MP for SAP, youmustenable the RemoteMonitoring keyword (by removing the leading hash symbol “#”) in the SAPABAP_StatusMonMonitoring Template. Next, on the same line, define the name of the local host, which youwant to use for monitoring the remote SAP server. Finally, you have to define the name of the remoteSAP server, which you want to monitor. Youmust define a new line to the Default SAPABAP_StatusMonMonitoring Template configuration for each additional SAP server, which you want tomonitor remotely.

Note:You can associate multiple remote SAP servers with one single local host or you canassociate single remote hosts with individual different local hosts. Default SAPABAP_StatusMonMonitoring Template configuration shows amixed approach where one local host “sap1” is used tomonitor two remote hosts; “sdsap” and “sapwolf ”. A third local host “sap2” remotely monitors theremote host “triosap”.

For more information about the contents of the SAPABAP_StatusMonMonitoring Template’sconfiguration including the keywords and parameters you use to define local and remote server names,see the entry concerning “RemoteMonitoring” in "Configuring SAPABAP_StatusMonMonitoring Template".

Default SAPABAP_StatusMon Monitoring Template Configuration

#----------------------------------------------------------------------

# TraceLevel hostname Disable=0 only error messages=1

# info messages=2 debug messages=3

#

TraceLevel =ALL =0

#-----------------------------------------------------------------------



TraceFile =ALL =r3status.log =w =60

#----------------------------------------------------------------------




# Path

#

HistoryPathUniX =ALL =default


HistoryPathWinN =ALL =default

#------------------------------------------------------------

# Check the ABAP dispatcher before a connection to SAP is

# opened. If the dialog queue is too full or not enough

# free work processes are available, monitoring is disabled.

#

# This feature should only be enabled in special cases. For

# regular dispatcher monitoring, use the r3mondisp.

#

# EnableDPQueueCheck hostname SAP SAP Enable=1/

System Number Disable=0

EnableDPQueueCheck =ALL =ALL =ALL =0

#----------------------------------------------------------

# Remote Local Remote

# Monitoring Host Host

RemoteMonitoring =sap1 =sdsap

RemoteMonitoring =sap1 =sapwolf

RemoteMonitoring =sap2 =triosap

#------------------------------------------------------------

SAPABAP_SysChgOptMon

The SAPABAP_SysChgOptMonMonitoring Template enables monitoring of the SAP ABAP SystemChange options based on the global edit Status flag, namespaces, and software components.



SAPABAP_SysChgOptMonMonitoring Template double-checks the SAP system change optionsusing the SAP NetWeaver transaction SE06 as a reference.

Monitor Type

The SAPABAP_SysChgOptMonMonitoring Template is of type snapshot and does not make use ofalert types or parameters. Onemonitor run gathers only one value set.

Alert Types

The SAPABAP_SysChgOptMonMonitoring Template has only one alert type:

CHANGE_OPT

Monitors and double-checks the SAP System change options and generates an alert if the optionmatches the configuration.

File Locations

The SAPABAP_SysChgOptMonMonitoring Template uses the files listed in the following table:

File Description

r3moncol (.exe) Collector executable for the system change optionmonitor.

r3monchg.cfg Configuration file for system change optionmonitor.

r3monchg.log Trace file for storing trace data.

The SAPABAP_SysChgOptMonMonitoring Template does not write history information to a specifichistory file.


The SAPABAP_SysChgOptMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_SysChgOptMonMonitoring Template uses the command line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_SysChgOptMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".



Configuring SAPABAP_SysChgOptMon Monitoring Template

Alert Types

The general rules mentioned in the following section concern the use of exclude and include parametervalues. The rules are particularly important for SAPABAP_SysChgOptMonMonitoring Template alerttypes.

Parameter Values

This section describes how theOMi MP for SAPinterprets include and exclude parameter values for analert type entry. TheOMi MP for SAP compares values in different parameters using ‘and’; the OMi MPfor SAP compares values in the same parameter as follows:



Note that the OMi MP for SAP evaluates include values before exclude values, as shown in thefollowing table:

SelectOptions

Alert Type: CHANGE_OPT (SAP 4.6x) ExampleConfiguration of Select Options Comparison

1 =SYSTEM_CHANGE_OPTION =1 =WARNING=SystemChange =R3_Security = NSP_EDTFLAG =I = CP=/0* =

OR

2 =SYSTEM_CHANGE_OPTION =1 =WARNING=SystemChange = =R3_Security = NSP_EDTFLAG =I =EQ=/SAPQUERY/ =

OR

3 =SYSTEM_CHANGE_OPTION =1 =WARNING=SystemChange =R3_Security = NSP_EDTFLAG =E =EQ=LOCAL =

AND

CHANGE_OPT

The CHANGE_OPT alert typemonitors and double-checks the SAP system change options andgenerates an alert if the settings for the flag parameters allow editing. The configuration of allparameters is mandatory. Multiple parameter entries on a single line are not allowed; use a new line tospecify each one of any multiple configurations. For more information about themeaning of the queryconditions in theMonitoring Template configuration, see "Parameters and Delimiters ". The following



table lists the parameters that you can use to configure the CHANGE_OPT alert type and shows thevalue assigned to the parameters by default:

Parameter Name DescriptionQueryConditions

DefaultValue

EDTFLAG Flag indicatingif an object canbe edited.

= Sign: I I

= Opt: EQ EQ

= Low: ON,OFF,PATCH(PATCH=setto patchsystem)

PATCH

= High:

NSP_EDTFLAG Flag indicatingwhich specifiedname space(s)to set to ON.

= Sign: I I

= Opt: EQ,CP

CP

= Low (Seelist of namespacechangeoptions forSAP 4.6. Xin Table 30.)

*

= High:

SWC_EDTFLAG Flag indicatingwhich specifiedsoftwarecomponents toset to ON.

= Sign: I I

= Opt: EQ,CP

CP

= Low:<specifiedsoftwarecomponent>(See list ofname spacechangeoptions forSAP 4.6. Xin Table 30.)

*

= High:



In the Default CHANGE_OPT Configuration, an event generating an alert occurs when the globalsystem change is OFF or the specified name space is Local Objects (/0LOCAL/), or the specifiedsoftware component is Local Developments (no automatic transport).

The Default CHANGE_OPT Configuration

AlertMonFun =ALL =ALL =ALL =ALL =SYSTEM_CHANGE_OPTION =1\

=WARNING =SystemChange =R3_Security \

=CHANGE_OPT =NSP_EDTFLAG =I =EQ =/0LOCAL/ =



=CHANGE_OPT =SWC_EDTFLAG =I =EQ = LOCAL =



=CHANGE_OPT =EDTFLAG =I =EQ =OFF =

The Customized CHANGE_OPT Configuration

AlertMonFun =ALL =ALL =ALL =SYSTEM_CHANGE_OPTION =1\


=CHANGE_OPT =NSP_EDTFLAG =I =EQ =/SAPQUERY/ =



=CHANGE_OPT =SWC_EDTFLAG =I =EQ = SAP_HR =

AlertMonFun =ALL =ALL =ALL =ALL =SYSTEM_CHANGE_OPTION =1 \


=CHANGE_OPT =EDTFLAG =I =EQ =OFF =

In the Customized CHANGE_OPT Configuration, an event generating an alert occurs when theGlobalChange option is OFF or the system space change optionABAP query /SAP is ON, or the softwarecomponent change option for HumanResources is ON.

Software Components Change Options



Technical ID Description

HOME Customer developments

LOCAL Local developments (no automatic transport)

SAP_ABA Cross-Application Component

SAP_APPL Logistics and Accounting

SAP_BASIS SAP Basis Component

SAP_HR HumanResources

Name System Change Options for SAP 6.x

Technical ID Description

/0CUST/ Customer name range

/0SAP/ General SAP name range

/1BCABA/ ABAP & GUI tools

/1BCDWB/ Development Workbench

/1BCDWBEN/ Enqueue function groups

/1COPA/ Generated objects in CO-PA

/1ISRWP/ IS-R merchandise and assortment controlling

/1ISU/ Generation namespace for CIC (Customer Interaction Center)

/1PAPA/ Personnel administration

/1PAPAXX/ Personnel administration - general

/1PSIS/ Project Information System - Logical database PSJ

/1PYXXFO/ PY-XX Form tool: Generated objects

/1SAP1/ General SAP generation namespace

/1SDBF12L/ Generation of pricing report

/BI0/ Business InformationWarehouse: SAP namespace

/BIC/ Business InformationWarehouse: Customer namespace

/SAPQUERY/ ABAP query /SAP

/SAPRRR/ Ready-to-Run SAP

/SAPSMOSS/ Interface: SAP messages to the SAP Online Service System

/SAPTRAIN/ SAP training



SAPABAP_TraceMon

The SAPABAP_TraceMonMonitoring Template enables monitoring of all the SAP Trace and Log filesfor "ERROR". SAPABAP_TraceMonMonitoring Templatemonitors only what has occurred since itsprevious run. Any error within a trace file generates only a single alert. The file monitor scans thefollowing directories, where <SID> refers to the SAP system ID and <InstanceNumber> refers to theSAP instance number of themonitored SAP System:

l UNIX/Linux: /usr/sap/<SID>/<InstanceNumber>/work/

l Windows: <drive:>\usr\sap\<SID>\<InstanceNumber>\work

Messages generated by this monitor include an operator-initiated action, which calls the vi editor. vidisplays a list of all trace files and log files and prompts you to select a file from the list and display itscontents.

File Locations

The SAPABAP_TraceMonMonitoring Template includes files listed in the following table:

File Description

r3mondev (.exe) Executable for the file monitor.

r3mondev.cfg Configuration file for monitored files

r3mondev.his History file that stores data for eachmonitor run


The SAPABAP_TraceMonMonitoring Template uses environment variables listed in the followingtable:


SAPOPC_DRIVE TheWindows drive where the HPOM agent is running, for example,E:\usr\...

SAPOPC_HISTORYPATH Path to the r3mondev history file

SAPOPC_R3MONDEV_CONFIGFILE

Name of the r3mondev configuration file

SAPOPC_SAPDIR TheWindows drive where SAP NetWeaver is running, for example:E:\usr\sap

SAPOPC_TRACEPATH Path to the r3mondev trace file




This section of the SAPABAP_TraceMonMonitoring Template enables you to specify the devicemonitoring details for the OMi MP for SAP.

For more information about the entries in the SAPABAP_TraceMonMonitoring Template includingkeywords and their possible values along with a description of each editable parameter, see thefollowing excerpt:

#----------------------------------------------------------------------------

-

# TraceLevel hostname only error messages=1 info messages=2 debug

messages=3

# Disable=0

TraceLevel =ALL =0

#----------------------------------------------------------------------------

-



TraceFile =ALL =r3moncts.log =w =60

#---------------------------------------------------------------------------


# Path

#




#------------------------------------------------------------

# AlertDevMon SAP SAP Enable =1 Filemask Severity Opc OpC

# Sys Number Disable=0 Object MsgGro

up

#AlertDevMon =ALL =ALL =1 =dev_* =WARNING =r3mondev =R3_Trace



#AlertDevMon =ALL =ALL =1 =std* =CRITICAL =r3mondev =R3_Trace

#Dispatcher trace file

AlertDevMon =ALL =ALL =1 =dev_disp =WARNING =r3mondev =R3_Trace

#Workprocess trace file for workprocess with number 0

AlertDevMon =ALL =ALL =1 =dev_w0 =WARNING =r3mondev =R3_Trace

#message server trace file

AlertDevMon =ALL =ALL =1 =dev_ms =WARNING =r3mondev =R3_Trace

#screen processor trace file

AlertDevMon =ALL =ALL =1 =dev_dy0 =WARNING =r3mondev =R3_Trace

#tp process trace file

AlertDevMon =ALL =ALL =1 =dev_tp =WARNING =r3mondev =R3_Trace

-----------------------------------------------------------------------------

---

Themonitoring conditions section of the SAPABAP_TraceMonMonitoring Template includes thefollowing default settings:

# AlertDevMon SAP SAP Enable =1 Filemask Severity OpcObject OpCMsgGroup

# System Number Disable=0

#AlertDevMon =ALL =ALL =1 =dev_* =WARNING =r3mondev =R3_Trace

#AlertDevMon =ALL =ALL =1 =std* =MAJOR =r3mondev =R3_Trace

Configuring SAPABAP_TraceMon Monitoring Template

You can edit the SAPABAP_TraceMonMonitoring Template configuration in the following ways:

l Disable messages

If you do not want to receive any messages relating to dev_* files for any of the SAP systems youaremonitoring using the OMi MP for SAP, change the first line of the SAPABAP_TraceMonMonitoring Template configuration file as follows:

AlertDevMon =ALL =ALL =0 =dev_* =WARNING =r3mondev =R3_Trace

l Change a message’s severity level



If you want to reduce the severity of all messages relating to std* files from critical to warning,change the second line of the SAPABAP_TraceMonMonitoring Template configuration file asfollows:

AlertDevMon =ALL =ALL =1 =std* =WARNING =r3mondev =R3_Trace

l Define exceptions to general rules

If you want to increase the severity of messages relating to dev_* files on SAP system LP2 fromwarning to critical, leave the default settings as they are and add the following line:

AlertDevMon =LP2 =ALL =1 =dev_* =CRITICAL =r3mondev =R3_Trace

Note:Wildcards are only allowed at the end of the string. Only SAP trace files located in the workdirectory are relevant and the names of these files must begin with either dev or std.

SAPABAP_TransMon

The SAPABAP_TransMonMonitoring template enables monitoring of the successfullyimported/exported SAP ABAP transports, failed imports/exports, availability of confirmed/unconfirmedrepairs and connections/tptests to the configured systems.

The SAPABAP_TransMonMonitoring template is application-server independent and is used to checkthe following parts of the transport system:

l Successful or failed imports and exports for themonitored system

l The presence of confirmed and unconfirmed repairs in themonitored system

l Connections that use a connection test (PING) to the configured systems

l TP-Tests of the configured systems

The SAPABAP_TransMonMonitoring template references transport routes in SAP NetWeavertransactions STMSand SE01.

Monitor Type

The SAPABAP_TransMonMonitoring template is of type snapshot. Onemonitor run gathers only onevalue set.

Alert Types

The transport alert monitor has the following alert types, which use amixture of snapshot and time-frame report types:



l TRANS

Defines alert conditions for successful and failed transport exports and imports.

l REPAIR

Defines alert conditions for confirmed and unconfirmed repairs.

l RFCONNECT

Defines alert conditions for the RFC connections between the systems.

l TPTEST

Defines alert conditions concerning the TP interface with the database. It includes a connection test(PING), TP call to the connected database, check of the TP interface (version, transport directory,TPPARAM path, file check, and TPLOG check).

File Locations

The SAPABAP_TransMonMonitoring template uses the files listed in the following table:

File Description

r3moncol (.exe) Collector executable for the transport monitor

r3montra.cfg Configuration file for the transport monitor.

r3montra.log Trace file for storing trace data.

The SAPABAP_TransMonMonitoring Template does not write history information to a specific historyfile.


The SAPABAP_TransMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_TransMonMonitoring Template uses the command-line parameters described in"Command Line Parameters".

Remote Monitoring

Formore information about configuring the SAPABAP_TransMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".



Configuring Transport-Monitor Alert Types

Youmust configure the parameter ALERT_THRESHOLD for all alert types for SAPABAP_TransMonMonitoring Template. All other parameters are optional. Note the general rules below on exclude andinclude parameters for SAPABAP_TransMonMonitoring Template.

Parameter Values

This section describes how theOMi MP for SAP interprets include and exclude parameter values for analert type entry. TheOMi MP for SAP compares values in different parameters using ‘and;’ OMi MP forSAP compares values in the same parameter as follows.

l Include:Use ‘or’ to compare the parameters

l Exclude:Use ‘and’ to compare the parameters

TheOMi MP for SAP evaluates include values before exclude values.

TRANS

TRANS is a time-frame based alert type for SAPABAP_TransMonMonitoring Template.TheSAPABAP_TransMonMonitoring Template generates an alert if the number of failed or successfultransport imports and exports exceeds a defined threshold. Note that the parameter USERNAME ismandatory for the TRANS alert type.

The following table lists the parameters that you can use to configure the TRANS alert type and showsthe value assigned to the parameters by default.



ALERT_THRESHOLD

The return code of the transport state above whichan alert occurs. For example, 4 (warning).

= Sign: I, E I

= Opt: GT,GE, LT, LE

GT

= Low: 1 4

= High:





E_SUCCESS Filtering option to include all successfully exportedtransports.

= Sign: I, E I

= Opt: EQ EQ

= Low: 2 X

= High:

E_FAILURE Filtering option to include all failed exportedtransports.

= Sign: I, E I

= Opt: EQ EQ

= Low: 2 X

= High:

I_SUCCESS Filtering option to include all successfully importedtransports.

= Sign: I, E I

= Opt: EQ EQ

= Low: b X

= High:

I_FAILURE Filtering option to include all failed importedtransports.

= Sign: I, E I

= Opt: EQ EQ

= Low 2 X

= High:

USERNAME The login name of the SAP NetWeaver user 3. Thisparameter is mandatory.

= Sign I, E I

= Opt:EQ,CP

EQ

= Low:<username>

ddic 4

= High:

1. Specify as a number, otherwise themonitor ends with a dump.

2. Any entry other than the default is treated as space.

3. Since requests/tasks are user dependent, you can use it to restrict data.

4. SAP user name for database-administration tasks.

In The Default TRANS Configuration, an event generating alert occurs if the threshold for importedor exported transports is greater than four (4).



Note: The number “4” defined in the threshold for the parameter ALERT_THRESHOLD does notrefer to the total number of imports. It refers to the SAP return code associated with the import. Inthis example, transport imports with return codes of 4 (warning) and above (GT=4) would generatean alert. For more information about import return codes, refer to the SAP product documentation.

The Default TRANS Configuration

AlertMonFun =ALL =ALL =ALL =ALL =TRANSPORT =1\

=WARNING =Trans =R3_Transport\

=TRANS =I_FAILURE =I =EQ =X =\

=USERNAME =I =EQ =ITOUSER =\

=ALERT_THRESHOLD =I =GT =4 =



=TRANS =I_SUCCESS =I =EQ =X =\


=ALERT_THRESHOLD =I =GE =4 =



=TRANS =E_FAILURE =I =EQ =X =\


=ALERT_THRESHOLD =I =GT =4



=TRANS =E_SUCCESS =I =EQ =X =\


=ALERT_THRESHOLD = I = GT = 4 =



REPAIR

REPAIR is a time-frame based alert type for SAPABAP_TransMonMonitoring template. TheSAPABAP_TransMonMonitoring template generates an alert if the number of confirmed orunconfirmed repairs exceeds a specified threshold.

The following table lists the parameters that you can use to configure the REPAIR alert type and showsthe value assigned to the parameters by default. Note that the parameter ALERT_THRESHOLD ismandatory.


R_CONFIRM Filtering option to include allconfirmed repairs.

= Sign: I, E I

= Opt: EQ EQ

= Low:1 X

= High:

R_UNCONFIR Filtering option to include allunconfirmed repairs.

= Sign: I, E I

= Opt: EQ

= Low: 1 X

= High:

USERNAME The login name of the SAPNetWeaver user 2. Thisparameter is mandatory.

= Sign I, E I

= Opt: EQ,CP EQ

= Low: <username> ddic 3

= High:

ALERT_THRESHOLD The number of the allowedrepair state above which analert occurs.

= Sign I, E I

= Opt: GT, GE, LT, LE GT

= Low: 4 4

= High:

1. Any entry other than the default is treated as space.

2. Since requests/tasks are user dependent, you can use it to restrict the data.

3. SAP user name for database-administration tasks.

4. Specify the parameter as a number or themonitor ends with a dump.



In the Default REPAIR Configuration, an event generating an alert occurs if the alert threshold of four(=GT =4) R_CONFIRM or R_UNCONFIR errors is exceeded for the specified target System.

The Default REPAIR Configuration

AlertMonFun =ALL =ALL =ALL =ALL =TRANSPORT =1 \

=WARNING =Repair =R3_Transport \

=REPAIR =R_CONFIRM =I =EQ =X = \




=REPAIR =R_UNCONFIR =I =EQ =X = \




=REPAIR =USERNAME =I =CP =* =\

=ALERT_THRESHOLD =I =GT =4 = =

RFCONNECT

RFCONNECT is a snapshot alert type for SAPABAP_TransMonMonitoring Template. Snapshot alerttypes take a picture of the system at themoment themonitor runs. SAPABAP_TransMonMonitoring template generates an alert if the number of RFC-connect errors to the target systemexceeds the specified alert threshold.

The following table lists the parameters that you can use to configure the RFCONNECT alert type andshows the value assigned to the parameters by default. Note that the parameter ALERT_THRESHOLD is mandatory. All other parameters are optional.




ALERT_THRESHOLD

Number ofreconnecterrors abovewhich analert occurs.

= Sign I, E I


= Low: # 4

= High:

CHECKSYSTEM System IDof thesystem youaremonitoring.

= Sign: I, E I

= Opt: EQ, CP EQ

= Low: <SID> '*'

= High:

#Specify this parameter as a number; otherwise themonitor ends with a dump.

In the Default RFCONNECT Configuration, an event generating an alert occurs if the alert threshold offour RFC-connect errors is exceeded for the specified target system.

The Default RFCONNECT Configuration


=WARNING =RfcConnect =R3_Transport\

=RFCCONNECT =CHECKSYSTEM =I =CP =* =\


TPTEST

TPTEST is a snapshot alert type for SAPABAP_TransMonMonitoring template. Snapshot alert typestake a picture of the System at themoment themonitor runs. SAPABAP_TransMonMonitoring template generates an alert if the number of TPTEST errors to the target system exceeds adefined threshold.

The following table lists the parameters that you can use to configure the TPTEST alert type and showsthe value assigned to the parameters by default. Note that the parameter ALERT_THRESHOLD ismandatory. All other parameters are optional.




ALERT_THRESHOLD

Number ofTPTEST errorsabove which analert occurs.

= Sign I, E I


= Low: * 4

= High:

CHECKSYSTEM ID of the systemwhich you aretesting ormonitoring.

= Sign: I, E I

= Opt: EQ, CP EQ

= Low: <SID> ''

= High:

* Specify this parameter as a number; otherwise themonitor ends with a dump.

In the Default TPTEST Configuration, an event generating an alert occurs if the alert threshold of fourTPTEST errors is exceeded for the specified target system.

The Default TPTEST Configuration


=WARNING =TpTest =R3_Transport\

=TPTEST =CHECKSYSTEM =I =EQ =<SID> =\


SAPABAP_UpdProcMon

The SAPABAP_UpdProcMonMonitoring Template enables monitoring of different conditions of SAPABAP Update processes like inactive status and errors.

The SAPABAP_UpdProcMonMonitoring Template monitors the status of both active updates andupdates that have been stopped by a SAP user or by the System. The SAPABAP_UpdProcMonMonitoring Template references update errors and update status in SAP NetWeaver transaction SM13.

Monitor Type

The SAPABAP_UpdProcMonMonitoring Template is of type snapshot. Onemonitor run gathers onlyone value set.

Alert Types

The updatemonitor has the following alert types.



l UPDATE_ACTIVE

Get information about the status of update processes and sends an alert if a process is not active.

l UPDATE_ERRORS_EXIST

Get information about update processes that have errors.

File Locations

The SAPABAP_UpdProcMonMonitoring Template uses the files listed in the following table:

File Description

r3moncol (.exe) Collector executable for the updatemonitor.

r3monupd.cfg Configuration file for the updatemonitor.

r3monupd.log Trace file for storing trace data.

The SAPABAP_UpdProcMonMonitoring Template do not write history information to a specific historyfile.


The SAPABAP_UpdProcMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_UpdProcMonMonitoring Template uses the command-line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_UpdProcMonMonitoring Template tomonitoranother SAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

Configuring Update-Monitor Alert Types

No parameters are used to configure alert types for SAPABAP_UpdProcMonMonitoring Template.You do not need to edit or customize the configuration.

UPDATE_ACTIVE



UPDATE_ACTIVE is an alert type for SAPABAP_UpdProcMonMonitoring Template. SAPABAP_UpdProcMonMonitoring Template generates an alert if the UPDATE task is inactive. The followingexample illustrates the default configuration for the UPDATE_ACTIVE alert type.

In the Default UPDATE_ACTIVE Configuration, an event generating an alert occurs if any update isstopped.

The Default UPDATE_ACTIVE Configuration

AlertMonFun =ALL =ALL =ALL =ALL =UPDATE =1\

=CRITICAL =UpdActive =R3_Update =UPDATE_ACTIVE

UPDATE_ERRORS_EXIST

UPDATE_ERRORS_EXIST is an alert type for SAPABAP_UpdProcMonMonitoring Template.SAPABAP_UpdProcMonMonitoring Template generates an alert if any update errors exist. Thefollowing example illustrates the default configuration for the UPDATE_ERRORS_EXIST alert type.

In the Default UPDATE_ERRORS_EXIST Configuration, an event generating an alert occurs if anyupdate error occurs.

The Default UPDATE_ERRORS_EXIST Configuration

AlertMonFun =ALL =ALL =ALL =ALL =UPDATE =1\

=CRITICAL =UpdError =R3_Update =UPDATE_ERRORS_EXIST

SAPABAP_UsrMon

The SAPABAP_UsrMonMonitoring Template enables monitoring of the SAP ABAP logged-in Users.The SAPABAP_UsrMonMonitoring Template identifies and reports the number of logged-in users. Thecheck is performed for each application server. A very high number of users could indicate thatperformance problems might occur. The alert can then be used to decide whether it is necessary to askor even force users to log out. The SAPABAP_UsrMonMonitoring Template references the SAPNetWeaver transaction SM04.

Monitor Type

The SAPABAP_UsrMonMonitoring Template is of type snapshot. Onemonitor run gathers only onevalue set.

Alert Types

The SAP-user monitor has only one alert type:

USER_LOGGEDIN_MAX



Define themaximum number of logged in users.

File Locations

The SAPABAP_UsrMonMonitoring Template uses the files listed in this table.

File Description

r3moncol (.exe) Collector executable for the user monitor.

r3monusr.cfg Configuration file for the user monitor.

r3monusr.log Trace file for storing trace data.

The SAPABAP_UsrMonMonitoring Template do not write history information to a specific history file.


The SAPABAP_UsrMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_UsrMonMonitoring Template uses the command-line parameters described in"Command-Line Parameters".

Remote Monitoring

Formore information about configuring the SAPABAP_UsrMonMonitoring Template tomonitor anotherSAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

USER_LOGGEDIN_MAX

USER_LOGGEDIN_MAX is an alert type for SAPABAP_UsrMonMonitoring Template. SAPABAP_UsrMonMonitoring Template generates an alert if themaximum number of SAP users exceeds adefined threshold. The following table lists the parameters that you can use to configure the USER_LOGGEDIN_MAX alert type and shows the value assigned to the parameters by default. Theconfiguration of the parameter MAX is mandatory.

The APSERVER parameter allows you to set the application-server- dependent monitors, r3monwpa,r3monusr, and r3monoms to monitor a specific application server. You need to configure APSERVER inthe followingmanner, where <hostname> is the name of the application server you aremonitoring as itappears in the list of application servers displayed in transaction SM51:

=APSERVER =I =CP =<hostname>_<SID>_<Instance_Number> =



Wealso recommend that you explicitly define the host name of the SAP NetWeaver central instancewhose application server(s) you want to specify with APSERVER, as illustrated in the followingexample:

Specifying an Application Server

AlertMonFun =<Central_Inst_Hostname> =ALL =ALL =ALL =USER =1 \

=WARNING =Login =R3_WP \

=USER_LOGGEDIN_MAX =MAX =I =GT =30 = \

=APSERVER =I =CP =hpdev01_MP3_00 =

The remainder of this section describes the specific configuration requirements for this alert monitor.


DefaultValue

APSERVER Specifies the application server to monitor = Sign: I, E

= Opt: CP

= Low :<AppServer_ID>

= High:

MAX The number of logged in users before an alertoccurs. a

= Sign: I, E

= Opt: GT, GE I

= Low: GT

= High: 5

a. Youmust specify the parameter value as a number, otherwise themonitor ends with a dump.

In The Default USER_LOGGEDIN_MAX Configuration, an event generating an alert occurs if thenumber of users logged in exceeds thirty.

The Default USER_LOGGEDIN_MAX Configuration

AlertMonFun =ALL =ALL =ALL =ALL =USER =1\

=WARNING =Login =R3_User\

=USER_LOGGEDIN_MAX =MAX =I =GT =30 =



SAPABAP_WPMon

The SAPABAP_WPMonMonitoring Template enables monitoring of the running work processes,waiting work process, and checking the various Status of work process like Debug/Private/No Restart.

The SAPABAP_WPMonMonitoring Template references the SAP NetWeaver transaction SM50 andreports the following conditions for work processes running on each of the application servers:

l Reports the number of runningwork processes for each work-process type configured in the profileof the current operationmode.

l Reports the number of waitingwork processes for each work-process type configured in the profileof the current operationmode.

l Compares the number of activework processes with the number of configuredwork processes (ofthe samework process type) in the profile of the current operationmode.

l Checks the status of the work processes, as follows:o D (Debug)

No processes run on live systems.

o P (Private)

Processes run usingmaximum available system resources.

o R (No Restart)

Failed processes do not restart, whichmeans that dependent jobs also fail.

The SAPABAP_WPMonMonitoring Template can only monitor alerts from an enqueuework processthat is part of a central instance; it cannot monitor the alerts from an enqueuework process belonging toa stand-alone enqueue server. Tomonitor stand-alone enqueuework processes, use the SAPABAP_CCMSIntegrationMonMonitoring Template to check for SAP CCMS alerts generated by the enqueueserver.

Monitor Type

The SAPABAP_WPMonMonitoring Template is of type snapshot. Onemonitor run gathers only onevalue set.

Alert Types

The work-process alert monitor has the following alert types.



l WP_AVAILABLE

TheWP_AVAILABLE alert type defines alert conditions for the number of expected work processesrunning.

l WP_IDLE

TheWP_IDLE alert type defines alert conditions for the number of idle work processes waiting.

l WP_CHECK_CONFIGURED

TheWP_CHECK_CONFIGURED alert type defines alert conditions for comparing the actualnumber of running work processes with the number of configured work processes in the profile ofthe current operationmode. Themonitor check only compares work processes of the same type.

l WP_STATUS

TheWP_STATUS alert type defines alert conditions for work processes which themonitor finds ina problematic state, for example: D (Debug), P (Private) or R (No Restart).

File Locations

The SAPABAP_WPMonMonitoring Template has the files listed in the following table:

File Description

r3moncol (.exe) Collector executable for theWorkProcess monitor.

r3monwpa.cfg Configuration file for theWorkProcess monitor.

r3monwpa.log Trace file for storing trace data.

The SAPABAP_WPMonMonitoring Template does not write history information to a specific historyfile.


The SAPABAP_WPMonMonitoring Template uses the environment variables described in"Environment Variables".


The SAPABAP_WPMonMonitoring Template uses the command-line parameters described inCommand Line Parameters.

Remote Monitoring

Formore information about configuring the SAPABAP_WPMonMonitoring Template tomonitor anotherSAP System remotely, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".



Configuring Work-Process Monitor Alert Types

This section helps you to configure alert types for SAPABAP_WPMonMonitoring Template. Note thegeneral rules below concerning the use of the exclude and include parameter values; the rules are ofparticular importance for these alert types.

Parameter Values

This section describes how theOMi MP for SAP interprets include and exclude parameter values for analert type entry. TheOMi MP for SAP compares values in different parameters using ‘and’. TheOMiMP for SAP compares values in the same parameter as follows.



TheOMi MP for SAP evaluates include values before exclude values, as shown in the following table:

SelectOptions

Alert Type: WP_AVAILABLE ExampleConfiguration of SelectOptions Comparison

1 =DIA =I =BT =50 =100=OPMODE =I =CP =DAY

OR

2 =DIA =I =GT =5 =OPMODE=I =CP =NIGHT

OR

3 =DIA = E =LT =60 AND

WP_AVAILABLE

WP_AVAILABLE is an alert type for SAPABAP_WPMonMonitoring Template. SAPABAP_WPMonMonitoring Template generates an alert if the number of running work processes for each, selectedwork-process type is outside the specifiedmaximum (or minimum) threshold. The following table liststhe parameters that you can use to configure theWP_AVAILABLE alert type and shows the valueassigned to the parameters by default. The configuration of the parameters listed for theWP_AVAILABLE alert type is mandatory. Youmust specify all threshold parameters as a number otherwisethemonitor ends with a dump.

The APSERVER parameter allows you to set the application-server- dependent monitors, r3monwpa,r3monusr, and r3monoms to monitor a specific application server. You need to configure APSERVER



in the followingmanner, where <hostname> is the name of the application server to monitor as itappears in the list of application servers displayed in transaction SM51:


Wealso recommend that you explicitly define the host name of the SAP NetWeaver central instancewhose application server(s) you want to specify with APSERVER, as illustrated in the Specifying anApplication Server.


AlertMonFun =<Centr_Instance_Hostname> =ALL =ALL =ALL =WP =1 \

=WARNING =Availability =R3_WP \

=WP_AVAILABLE =DIA =I =GT =50 = \


Rest of this section describes the specific configuration requirements for this alert monitor.


DefaultValue

APSERVER Specifies an applicationserver to monitor

= Sign: I, E

= Opt: CP

= Low : <AppServer_ID>

= High:

BTC Threshold for batchwork processes

= Sign: I, E

= Opt: GT, GE, LT, LE

= Low: <number>

= High:

DIA Threshold for dialogwork processes

= Sign: I, E


= Low: <number>

= High:




DefaultValue

ENQ Threshold for enqueuework processes

= Sign: I, E


= Low: <number>

= High:

OPMODE Defines the operationmode for this parameter*

= Sign I, E I

= Opt: CP, EQ= Low: <operation_mode> EQ

= Low: <operation_mode> current

= High:

SPO Threshold for spool workprocesses

= Sign: I, E


= Low: <number>

= High:

UPD Threshold for updatework processes

= Sign: I, E


= Low: <number>

= High:

UP2 Threshold for update2work processes

= Sign: I, E


= Low: <number>

= High:

* A critical alert occurs if you specify a non-existent mode.

In the Default WP_AVAILABLE Configuration, an event generating an alert occurs if the number ofavailable dialog work processes is less than fifty.

The Default WP_AVAILABLE Configuration

AlertMonFun =ALL =ALL =ALL =ALL =WP =1\

=WARNING =Availability =R3_WP\

=WP_AVAILABLE =DIA =I =LT =50 =



Note:Check that the work-process types you want to monitor with SAPABAP_WPMonMonitoring Template are correctly configured in the SAP instance profile.

The SAPABAP_WPMonMonitoring Template can only monitor work-process types that are configuredin the SAP instance profile. If the DIA work-process type is not configured in the SAP instance profile(or "rdisp/wp_no_dia = 0"), then no DIA work processes are started. Since zero (0) DIA workprocesses is clearly less than theminimum allowed (50) specified in the default configuration for theWP_AVAILABLE alert type shown in The Default WP_AVAILABLE Configuration would generate analert under normal circumstances.

However, if the DIA work-process type is not configured in the SAP instance profile, r3monwpa cannotmonitor the number of DIA work processes that are running at any given point in time and, as aconsequence, does not generate an alert. You can check discrepancies between the SAP instanceprofile and the SAPABAP_WPMonMonitoring Template configuration file with the alert typeWP_CHECK_CONFIGURED.

WP_IDLE

WP_IDLE is an alert type for SAPABAP_WPMonMonitoring Template. SAPABAP_WPMonMonitoring Template generates an alert if the number of waiting work processes for each, selectedwork-process type is outside the specifiedmax (or min) threshold.

The following table lists the parameters that you can use to configure theWP_IDLE alert type andshows the value assigned to the parameters by default. The configuration of the parameters for theWP_IDLE alert type is mandatory. Youmust specify all threshold parameters as a number otherwisethemonitor ends with a dump.

The APSERVER parameter allows you to set the application-server- dependent monitors, r3monwpa,r3monusr, and r3monoms to monitor a specific application server. You need to configure APSERVER inthe followingmanner, where <hostname> is the name of the application server to monitor as it appearsin the list of application servers displayed in transaction SM51:


It is also recommended to define explicitly the host name of the SAP NetWeaver central instancewhose application server(s) you want to specify with APSERVER, as illustrated in the Specifying anApplication Server.



=WARNING =Idle =R3_WP \



=WP_IDLE =BTC =I =GT =20 = \


The following table lists the configuration parameters forWP_IDLE:


DefaultValue

APSERVER Specifies an application server to monitor = Sign: I, E

= Opt: CP

= Low : <AppServer_ID>

= High:

BTC Threshold for batch work processes = Sign: I, E


= Low: <number>

= High:

DIA Threshold for dialog work processes = Sign: I, E


= Low: <number>

= High:

ENQ Threshold for enqueue work processes = Sign: I, E


= Low:

= High:

OPMODE Defines the operationmode for thisparameter.1

= Sign I, E I

= Opt: CP, EQ EQ

= Low: <operation_mode>

current

= High:




DefaultValue

SPO Threshold for spool work processes = Sign: I, E


= Low: <number>

= High:

UPD Threshold for update work processes = Sign: I, E


= Low: <number>

= High:

UP2 Threshold for update 2 work processes = Sign: I, E


= Low: <number>

= High:

1. If a non-existent mode is specified, a critical alert occurs.

In the Default WP_IDLE Configuration, an event generating an alert occurs if the number of idle Dialogwork processes is less than ten.

The Default WP_IDLE Configuration


=WARNING =Idle =R3_WP\

=WP_IDLE =DIA =I =LT =10 =

Note:Check that the work-process types you want to monitor with SAPABAP_WPMonMonitoring Template are correctly configured in the SAP instance profile.

The SAPABAP_WPMonMonitoring Template can only monitor work-process types that are configuredin the SAP instance profile. If the DIA work-process type is not configured in the SAP instance profile(or “rdisp/wp_no_dia = 0”), then no DIA work processes are started. Since zero (0) DIA work processesis clearly less than theminimum allowed (10) specified in the default configuration for theWP_IDLEalert type shown in The Default WP_IDLE Configuration, this would, under normal circumstances,generate an alert.



However, if the DIA work-process type is not configured in the SAP instance profile, SAPABAP_WPMonMonitoring Template cannot monitor the number of DIA work processes that are running at anygiven point in time and, as a consequence, does not generate an alert. You can check discrepanciesbetween the SAP instance profile and the SAPABAP_WPMonMonitoring Template with the alert typeWP_CHECK_CONFIGURED.

WP_CHECK_CONFIGURED

TheWP_CHECK_CONFIGURED is an alert type for SAPABAP_WPMonMonitoring Template. TheWP_CHECK_CONFIGURED alert typemakes a comparison between the actual number of runningwork processes and the number of configured work processes in the profile of the current operationmode. Note that themonitor only compares work processes of the same type, for example: DIA, BTC.

The APSERVER parameter allows you to set theMonitoring Template SAPABAP_WPMon,SAPABAP_UsrMon,and so on tomonitor a specific Application Server. You need to configureAPSERVER in the followingmanner, where <hostname> is the name of the application server tomonitor as it appears in the list of application servers displayed in transaction SM51:





=WARNING =Check =R3_WP \

=WP_CHECK_CONFIGURED \


The following table lists the parameters that you can use to configure theWP_CHECK_CONFIGURED alert type and shows the value assigned to the parameters by default:

ParameterName Description Query Conditions Default Value

APSERVER Specifies anapplicationserver tomonitor

= Sign: I, E

= Opt: CP

= Low: <AppServer_ID>

= High:



In the Default WP_CHECK_CONFIGURED Configuration, SAPABAP_WPMonMonitoring Templategenerates an alert if the number of running work processes does not match the number of configuredwork processes for a given work-process type.

The Default WP_CHECK_CONFIGURED Configuration


=WARNING =Check =R3_WP\

=WP_CHECK_CONFIGURED \

=APSERVER =I =CP =ALL =

WP_STATUS

TheWP_STATUS is an alert type for SAPABAP_WPMonMonitoring Template. WP_STATUS definesalert conditions for work processes which themonitor finds in a problematic state, for example: D(Debug), P (Private), or R (No Restart). SAPABAP_WPMonMonitoring Template generates an alert ifthe work processes running in the SAP Systems you aremonitoring with the OMi MP for SAP matchthe conditions defined in the parameters below. The configuration of the parameter below is optional.

The APSERVER parameter allows you to set the application-server- dependent monitors, SAPABAP_WPMon, SAPABAP_UsrMon, etc. to monitor a specific Application Server. You need to configureAPSERVER in the followingmanner, where <hostname> is the name of the application server tomonitor as it appears in the list of application servers displayed in transaction SM51:





=WARNING =WP_Status =R3_WP \

=WP_STATUS =STATUS =I =GT =30 = \


The following table lists the parameters that you can use to configure theWP_STATUS alert type andshows the value assigned to the parameters by default:




DefaultValue

APSERVER Specifies an application server tomonitor

= Sign: I, E

= Opt: CP

= Low: <AppServer_ID>

= High:

STATUS 1 The status which is monitored = Sign: I, E

= Opt:

= Low: 2

= High:

1. Possible additional values: MAX_ENTRIES

2. Possible values: D=Debug, P=Private, R=Restart (no alert).

In the Default WP_STATUS Configuration, an event generating an alert occurs if the status of arunning workprocess is critical. The Default WP_STATUS Configuration also shows how you can use=MAX_ENTRIES to define the number of work processes with a defined status that have to existbefore the OMi MP for SAP generates amessage.

The Default WP_STATUS Configuration


=CRITICAL =WP_Status =R3_WP\

=WP_STATUS =STATUS =I =CP =* =

TempSeqFileMon

Monitoring the TemSe file

To save runtime costs, the OMi MP for SAP monitors the consistency of SAP’s Temporary Sequentialfile (TemSe), using a report you set up in SAP. However, you still need to assign the SAPABAP_TempSeqFileMonMonitoring Template to themanaged nodes.

Monitor Type



The TemSemonitor is of type snapshot. Onemonitor run gathers only one value set.

Report Description

The TemSe report references the SAP NetWeaver transaction SP12. Any inconsistency found in theTEMSE database is serious, use the log in SP12 to correct the cause of the inconsistency. Forexample a disk failure.

Running the TemSe Monitor

To run the TemSemonitor, you need to set up a job in SAP NetWeaver which references a reportnamed /HPOV/ZHPSPIT1.

Note:You can only use the report with SAP version 4.6 and later.

To set up the report:

1. Logon toSAP NetWeaver.

2. Set up a job using transaction SM36.

3. In the job, specify the following details:a. Date on which the report should start.

b. Frequency with which the report should run.

Customizing SAP ABAP Monitoring Templates

This section provides reference information you can use for customizing ABAP Monitoring Templatesto suit your monitoring requirements.

Note:Youmust increment the Version of corresponding SAP ABAP Aspects andSAP ABAP Management Templates after configuring or customizingSAP ABAP Monitoring Templates. For more information on SAP ABAP Aspects andcorresponding SAP ABAP Monitoring Templates, see "SAP ABAP Monitoring Templates,Monitoring Template Configuration Files, and History Files".

SAP ABAP Monitoring Templates, Monitoring Template

Configuration Files, and History Files

OMi MP for SAP's ABAP Monitoring Template uses SAP Monitors to monitor different functionalities ofyour SAP ABAP Application Server. Some SAP monitors store data in a history file for accessing



certain information after each run. This section provides reference information aboutSAP ABAP Monitoring Templates, their corresponding SAP ABAP Aspects, and differentSAP monitors and History Files used by the SAP ABAP Monitoring Templates.

SAP ABAP Aspect SAP ABAP Monitoring Template

MonitoringTemplateConfigurationFile (cfg) History File

SAP ABAP Batch JobHealth

SAPABAP_BatJobMon r3monjob

SAP CCMS Integration SAPABAP_CCMSIntegrationMon r3monal r3monal.his

SAP ABAP Correctionand Transport SystemStatus

SAPABAP_CTSMon r3moncts

SAP ABAP Processesand Dispatcher Status

SAPABAP_DispMon r3mondisp

SAP ABAP DumpStatus

SAPABAP_DmpMon r3mondmp

SAP ABAP Idoc Status SAPABAP_IdocStatusMon r3monale

SAP ABAP Lock Status SAPABAP_LckChkMon r3monlck

SAP ABAP PerformanceMonitor

SAPABAP_PerfMon r3perfagent

SAP ABAP Processesand Dispatcher Status

SAPABAP_ProcMon r3monpro r3monpro.his

SAP ABAP RFCDestination Status

SAPABAP_RFCDestMon r3monrfc

SAP ABAP SecurityStatus

SAPABAP_SecMon r3monsec

SAP ABAP Spool Health SAPABAP_SplMon r3monspl

SAP ABAP PerformanceMonitor

SAPABAP_StatRecMon r3perfstat

SAP System Health SAPABAP_StatusMon r3status r3status.his

SAP ABAP SystemChangeOption Status

SAPABAP_SysChgOptMon r3monchg

SAP TemporarySequential FileMonitoring

SAPABAP_TempSeqFileMon r3monaco



SAP ABAP Aspect SAP ABAP Monitoring Template

MonitoringTemplateConfigurationFile (cfg) History File

SAP System Health SAPABAP_TraceMon r3mondev r3mondev.his

SAP ABAP TransportStatus

SAPABAP_TransMon r3montra

SAP ABAP UpdateTasks Health

SAPABAP_UpdProcMon r3monupd

SAP ABAP User Health SAPABAP_UsrMon r3monusr

SAP ABAPWorkProcess Health

SAPABAP_WPMon r3monwpa

History Path

The HistoryPath[Unix | AIX |WinNT] keyword in the ABAP Monitoring Template configuration fileaccepts the following parameters:

HistoryPath<Unix|Aix|WinNT> <HostName> =<Path>

l Hostname:

=ALL - Monitor all hosts with the SPI for SAP. This is the default setting.

=<SAP_host>Name of a SAP server, where you want to specify the path to themonitor history file.Use a new line for each individual host.

l Path:

UNIX: =default

AIX: =default

Windows: =default

The =default value is associated with the default path to the history files which the OMi MP for SAPMonitoring Templates write.

Some ABAP Monitoring Templates like SAPABAP_IdocStatusMon or SAPABAP_DmpMon do notwrite history information to amonitor-specific history file. Instead, any information relating to SAPalerts which come to the notice of the OMi MP for SAP alert-collector monitors is written directly to theSAP database, where it can be found by the ABAP Monitoring Template collector. At the start of eachmonitor run, ABAP Monitoring Template reads the relevant tables and uses the information todetermine if any events the OMi management server has already been notified about and whether togenerate further messages or not.



For SAP ABAP Monitoring Templates that use a History File, youmust specify the history path, whichis the directory path used to locate aMonitoring Template's history file. SAP ABAP MonitoringTemplate include the following default paths for UNIX, AIX, andWindows servers:




Note:You can configure the ABAP Monitoring Templates to use a specific history path onWindows managed nodes rather than the default: =default, for example: %OvAgentDir%\Tmp. Formore information, see the SAPOPC_HISTORYPATH environment variable and the alert-monitorconfiguration-file keyword.

Each SAP ABAP Monitoring Template creates its own history file. Each time an SAP ABAP MonitoringTemplatemonitor completes a run, it adds a new section to its history file. This feature enables theSAP ABAP Monitoring Template monitor to check for changes since the previous run.

Note:Do not edit any of themonitor history (*.his) files. Editing themonitor history file couldcompromise the accuracy and consistency of your records. Themonitor uses its history file todetermine which, if any, events have occurred since the last run and whether to send anymessages.

Following in an excerpt from SAP ABAP Monitoring Template configuration:

#---------------------------------------------------------------------------


# Path

#




#------------------------------------------------------------



Keywords and Parameters

KeywordKeywordParameter/Configuration Fields Description

TraceLevel Tracelevel =<HostName> =<TraceLevel>

Hostname:=ALL -Monitor all SAP hosts withthe SPI for SAP. This is the defaultsetting.

=<SAP_host> -The name of a SAPserver, where you want to specify atrace level. Use a new line for eachindividual host.

Trace level:

=0 -Disable logging. This is thedefault setting for all configurationfiles.

=1-Log only error messages

=2 -Log all messages

=3-Log everything including debugmessages

TraceFile Tracefile =<HostName>=<FileName> =<TraceMode>=<TracePeriod>

Hostname:=ALL -Monitor all SAP servers withthe SPI for SAP. This is the defaultsetting.

=<SAP_host> -Name of a specifichost where tracing is enabled andyou want to specify a trace level.Use a new line for each individualhost.

Filename:

=r3mon<alert_monitor_name>.log, for example,r3mondev.log, or r3mondmp.log.This is the default setting.Alternatively, you can specify thename of the file to which you wantto write the trace log. By default,monitor trace files are located in thefollowing directories:




l UNIX: /var/opt/OV/log

l AIX:

HTTPS: /var/opt/OV/log

l Microsoft Windows:

HTTPS: %OvDataDir%\log

TraceMode:

=w -default value

=a -append

TracePeriod:

Monitor verifies whether theexisting file's the time period haselapsed the time periodmentionedin the ABAP Monitoring Template.If the time period has elapsed, anew file will be created. Otherwisenew trace log entries will beappended into the already existingfile.

RFCTimeOut RFCTimeOut=%%RFCTimeOutInterval%%

RFCTimeOut defines themaximumamount of time, in seconds, beforean RFC XMI/XAL function call iscanceled, for example: =120. If theRFC call takes longer thanexpected to complete, that is; toreceive a reply to the initial request,the System is probably down or hasa serious performance problem.

EnableDPQueueCheck EnableDPQueueCheck=<Hostname> =<SAP SID>=<SAP Number> \=<Enable/Disable>

Hostname:Name of the SAP Server where theinstance is running whose ABAPdispatcher you want the OMi MP forSAP to check before starting:

=ALL -All the hosts which the OMiMP for SAP monitors. This is thedefault setting.

=<SAP_host> -Name of a SAPserver, where you want to enablechecking of the dispatcher-queue.




Use a new line for each individualhost.

SAP SID:

SAP System ID of the instancewhose ABAP dispatcher you wantthe OMi MP for SAPmonitors tocheck before starting:

=ALL -All System IDs which theOMi MP for SAPmonitors. This isthe default setting.

=<SAP_SID> -SAP System ID of theinstance whose ABAP dispatcheryou want to check, for example:“SP1”.

SAP Number:

Number of the SAP instance whoseABAP dispatcher you want the OMiMP for SAP monitors to checkbefore starting:

=ALL -All instances which the OMiMP for SAP monitors. This is thedefault setting.

=<SAP_InstNr> -Number the SAPinstance whose ABAP dispatcheryou want the OMi MP for SAPmonitors to check, for example:“45”.

Enable/Disable:

Enable (=1) or disable (=0) - is aparticular monitor to monitor theABAP dispatcher for the definedSAP instance, for example: 1. Thedefault is Disable (=0). You have toenable the OMi MP for SAPmonitors individually.

RemoteMonitoring RemoteMonitoring =<LocalHost>=<RemoteHost>

LocalHost:Name of the host which the OMiMP for SAP is already monitoringand whose Agent will be used to




remotely monitor the SAP serverdefined in Remotehost.

RemoteHost:

Name of the remoteSAP serverthat you want to monitor using theOMi MP for SAPon SAP serverdefined in “Localhost”.

AlertMonFun AlertMonFun =<SAP Hostname>=<SAP System> =<SAP Number> \=<SAP Client>=<AlertMonitor>=<Enable/Disable> \ =<OpCSeverity> =<OpC Object> =<OpCMsgGroup> \ =<Alerttype>=<RFC Parameter>

For detailed information aboutparameters/fields supported byAlertMonFun, see"Configuration Fields inABAP Monitoring Templates".

Query Conditions for Monitoring Templates

The data for eachMonitoring Template is split into a number of alert types. For example, theJOBREPORTMonitor has four alert types: JOB_MAX_RUN-TIME, JOB_MIN_RUN_TIME, START_PASSED and JOB_ABORTED. For each alert monitor’s defined alert types you have to:

l Specify which SAP NetWeaver systems should be checked

l Enter selection criteria which defines under what circumstances an alert will be raised. This isdescribed inmore detail below.

Parameter Data Types

Parameters in themonitoring-conditions section of the ABAP Monitoring Template associated witheach alert type define the conditions, which generate an alert. There are two general types of parameterdata:

l Name

Parameter name describes the attributes of the SAP NetWeaver System for which you define themonitoring conditions. For example: MAX_RUNTIME and JOBNAME are the names of parametersfor the alert type JOB_MAX_RUN_TIME, which is associated with the JOBREPORTmonitor.

l Delimiters



Parameter delimiters are used to specify the “select” options for each parameter. The parameterdelimiters define the circumstances under which an alert should be generated. A message will besent for each event that matches your specified conditions. There are four types of ParameterDelimiters, whichmust appear in the following order: SIGN, OPT(ION), LOW, and HIGH.

Specifying Query Conditions

The following points apply generally when using parameter delimiters to specify query conditions:

o All possible and reasonable conditions can be used to configure the query condition, within thelimitations given below.

o Messages which are excluded by your defined conditions will not appear in the OMi messagebrowser.

The following table lists the parameter delimiters used to configure the ABAP MonitoringTemplates:

Note: The order of the parameter delimiters for the query conditions must match the ordershown in following table, such as: SIGN, OPTION, LOW, HIGH.

Parameters and Delimiters

ParameterDelimiters Description

SIGN I: Include

E:Exclude

OPT The standard SAP operators NE (Not Equal to), NB (Not Between... and...), and NP(does Not contain Pattern) cannot be used to configure the alert types described inthis section. You should only use the following operators:

l EQ: equal to

l BT: between... and

l CP: contains pattern

l LE: less than or equal to

l GE: greater than or equal to

l GT: greater than

l LT: less than

LOW l A comparison value such as a string when used with the operator CP.

l The lower value of a range when used in conjunction with the operator BT.

HIGH A numeric comparison value to specify the higher value of a range. This parameterdelimiter should only be used in conjunction with the operator BT.



Configuration Fields in ABAP Monitoring Templates

The following table lists different user configurable fields in SAP ABAP Monitoring Template and theirdescriptions:

Fields Description

#AlertMonFun Name of the keyword used tomonitor a certain job.

=<SAPHostname>

Hostname of the SAP server you want to monitor

=<SAP System> ID of the SAP system you want to monitor.

=<SAP Number> Number of SAP Instance you want to monitor.

=<SAP Client> Client ID of SAP client you want to monitor.

=<AlertMonitor> Alert Type to use for monitoring.

=<Enable/Disable> Enable or Disable monitoring.

=<OpC Severity> Severity level of themessage you want to map the SAP alert to.

=<OpC Object> MP Object associated with the generatedmessage.

=<OpCMsgGroup>

Name of themessage group theOMi message belongs to.

=<Alerttype> Name of the Alert Type.

=<RFCParameter>

Name of a parameter for a given Alert Type.


This section describes the environment variables for all Monitoring Template. The configuration isidentical for all SAP ABAP Monitoring Templates except the name of theMonitoring Template.


SAPOPC_ <R3MONNAME>*_CONFIGFILE Configuration-file name

SAPOPC_R3ITOSAP_CONFIGFILE General SAP NetWeaver loginconfiguration file

SAPOPC_TRACEPATH Trace path config. file



*Where <R3MONNAME> is the name of themonitor whoseMonitoring Template configuration filelocation you want to change. For example, SAPOPC_R3MONDMP_CONFIGFILE.


The command line parameters for all the SAP ABAP Monitoring Template are described in this section.Similarly, for the environment variables, the configuration is identical for all SAP ABAP MonitoringTemplate except the name of theMonitoring Template.

Parameter Description

-cfgfile Name of themonitor’s configuration file. For example, -cfgfile<R3MONNAME>*.cfg

-trace Themonitor writes an initial trace file writetrace.log, which containsinformation about the configuration file r3itosap and themonitor-specificconfig file <R3MONNAME>*.cfg.

*Where <R3MONNAME> is the name of themonitor whose configuration-file location you want toread. For example, r3mondmp.

In the following example, theMonitoring Template writes an initial trace file writetrace.log, whichcontains information about the general configuration file r3itosap and themonitor-specificconfiguration file r3monjob.cfg.

r3moncol -cfgfile r3monjob.cfg -trace

SAP Parameters

Parameters are variables that are an integral component of SAP Management Templates, Aspects,and Policy Templates. Each parameter corresponds to a variable. Parameters contain default valuesthat are used for monitoring different components of SAP Application Server. You can alsomodify thevalues of the variables to suit your monitoring requirements.

Types of Parameters

OMi MP for SAP contains the following set of parameters to monitor ABAP and J2EE applicationservers:



l SAP J2EE Application Server Parameters

l SAP ABAP Application Server Parameters

l SAP ABAP Monitoring Template Parameters

SAP J2EE Application Server Parameters

OMi MP for SAP contains the following parameters for monitoring J2EE Application Server:

ParameterParameterType Description Default Values

Frequency ofVeryHighScheduler

Expert Frequency for the scheduler which is expectedto run on very short interval (in minutes).

5

Frequency ofHigh Scheduler

Expert Frequency for the scheduler which is expectedto run on short interval (in minutes).

15

Frequency ofMediumScheduler

Expert Frequency for the scheduler which is expectedto run onmedium interval (in hours).

1

Frequency of LowScheduler

Expert Frequency for the scheduler which is expectedto run on high interval (in hours).

24

ApplicationInstance

Mandatory Application instance for which data needs tobe fetched.

CI Name

<J2EE aspectname>Frequency

Dependent Frequency tomonitor assigned J2EEcomponent.

VERYHIGH

<J2EE aspectname> Severity

Dependent Severity of the event or component that ismonitored.

MAJOR

<J2EE aspectname> Threshold

Dependent Threshold value of the event or componentthat is monitored.

10000000.000000

SAP ABAP Application Server Parameters

OMi MP for SAP contains the following parameters for monitoring ABAP Application Server:

ParameterParameterType Description

Default/SampleValues

Frequency of VeryHighScheduler

Expert Frequency for the scheduler which isexpected to run on very short interval(in minutes).

5



Frequency of HighScheduler

Expert Frequency for the scheduler which isexpected to run on short interval (inminutes).

15

Frequency of MediumScheduler

Expert Frequency for the scheduler which isexpected to run onmedium interval (inhours).

1

Frequency of LowScheduler

Expert Frequency for the scheduler which isexpected to run on high interval (inhours).

24

ConfgurationFileName for<monitored aspect name>

ReadOnly Configuration file for ABAP applicationserver monitoring.

Example:r3monjob.cfg

FREQ for ABAP<monitored aspect name>

Dependent Frequency for monitoring the assignedaspect.

VERYHIGH

TraceLevel for ABAP<monitored aspect name>

Dependent Trace level for monitoring theassigned ABAP aspect.

0

TraceFileName for ABAP<monitored aspect name>

Dependent Trace file namemonitoring theassigned ABAP aspect.

Example:r3monjob.log

TraceMode for ABAP<monitored aspect name>

Dependent Trace file mode for monitoring theassigned ABAP aspect.

w

TracePeriod for ABAP<monitored aspect name>

Dependent Trace period (in mins) for monitoringthe assigned ABAP aspect.

60

RFCTimeOutInterval forABAP <monitored aspectname>

Dependent RFCTimeout (in seconds) formonitoring the assigned ABAPaspect.

120

IsDPQCheckEnabled forABAP <monitored aspectname>

Dependent DPQCheck for monitoring theassigned ABAP aspect.

0

SAP ABAP Monitoring Template Parameters

TheOMi MP for SAP contains a set of parameters that are used for configuring ABAP MonitoringTemplates tomonitor ABAP Application Server. These parameters are user configurable and enablesyou to change default values as per your monitoring requirements. TheOMi MP for SAP extendsABAP monitoring capability by enabling you to create custom parameters required tomonitor specificfunctionality or areas of your ABAP Application Server. The following table lists the user configurableparameters provided to support ABAP Application Server monitoring:

Parameter Name Variable Name Description

ConfigurationFileName for ConfigurationFileName Name of the configuration file used by



<Monitoring Template Name>* SAP ABAP Monitoring Template.

FREQ for <Monitoring TemplateName>

FREQ Frequency used bySAP ABAP Monitoring Template.

TraceLevel for <MonitoringTemplate Name>

TraceLevel Trace level forSAP ABAP Monitoring Templatemonitoring.

TraceFileName for <MonitoringTemplate Name>

TraceFileName Trace file name forSAP ABAP Monitoring Templatemonitoring.

TraceMode for <MonitoringTemplate Name>

TraceMode Trace file mode forSAP ABAP Monitoring Templatemonitoring.

TracePeriod for <MonitoringTemplate Name>

TracePeriod Trace period (in minutes) forSAP ABAP Monitoring Templatemonitoring.

RFCTimeOutInterval for<Monitoring Template Name>

RFCTimeOutInterval RFCTimeout (in seconds) forSAP ABAP Monitoring Template.

IsDPQCheckEnabled for<Monitoring Template Name>

IsDPQCheckEnabled DPQCheck forSAP ABAP Monitoring Templatemonitoring.

*The default naming convention of thementioned parameters include parameter name followed by theABAP Monitoring Template Name.

Configuring ABAP Monitoring Template Parameters

This section provides information about editing ABAP Monitoring Template Parameters.

You can edit the ABAP Monitoring Template Parameters to suit your monitoring requirements. To editABAP Monitoring Template parameters, follow these steps:

1. Open the Policy Template Groups.

2. To tune the Parameters:

On BSM 9.2x, click Admin > Operations Management > Monitoring > Policy Templates >SAP ABAP Monitoring Template.

OnOMi 10.x, click Administration > Monitoring > Policy Templates.



3. In thePolicy Template Groups tab on BSM 9.2x orPolicy Templates, click Templatesgrouped by type onOMi 10.x.

4. Select SAP ABAP Monitoring.

5. In the Policy Templates pane, select the SAP ABAP Monitoring Template for which you want toedit parameters.

The parameters for the selectedMonitoring Template are listed in the Details pane.

6. Double-click the Parameter you want to edit.

TheMonitoring Template editor menu opens.

7. Select thePolicy Data tab. The Policy Raw Data pane opens.

8. In the Policy Parameters pane, select the parameter you want to edit and then click . The Edit

Parameter dialog box opens. You can edit the Name, Variable Name, UI Order, Variable Type,Default Value, and Flags.

9. Click the Item you want to edit, specify the value, and then click OK.

Creating Custom Parameters for SAP ABAP Monitoring Templates

TheOMi MP for SAP enables you to parametrize frequently changing elements or values in theMonitoring Template Configuration String. The steps to parametrize SAPABAP_DispMonMonitoring Template is shown here as an example:

1. Open the SAP ABAP Monitoring Template.

On BSM 9.2x, click Admin > Operations Management > Monitoring > Policy Templates >SAP ABAP Monitoring Template.

OnOMi 10.x, click Administration > Monitoring > Policy Templates >SAP ABAP Monitoring Template.

2. Select SAPABAP_DispMon Monitoring Template for which you want to create the customparameter.

3. Click and select Edit Policy Template (Raw Mode). The Policy Related Information windowopens.

4. Select Policy Data tab. The SAP ABAP Monitoring Template Configuration appears.

5. Go toDisableMonitoringWithSeverity keyword configuration string.

DisableMonitoringWithSeverity =ALL =ALL =ALL =WARNING



6. To parametrize theWARNING configuration string value, add %% at the start and end of theWARNING value as shown.

DisableMonitoringWithSeverity =ALL =ALL =ALL =%%WARNING%%

7. From thePolicy Parameters tab, click Synchronize parameters. The Synchronizeparameters dialog box opens.

8. Click Change to addWARNING to the list of parameters for SAPABAP_DispMonMonitoring Template.

9. You can now define or edit the Name, Variable Name, UI Order, Variable Type, Default Value, andFlags for theWARNING parameter.

Following is an example of defining a variable name for the Custom Parameter:

a. From the Edit Parameter dialog box of WARNING parameter, select Variable Name textfield.

b. Define a variable name forWARNING parameter.

Note: It is recommended that you provide a Variable Name that is easily recognizable byyou since the parameter will be displayed by the Variable Name during Deployment. Forexample, you can provide DisableMonitoringWithSeverity_ALL_Severity as variablename forWARNING custom parameter for ease of deployment.

c. Click OK and then click Synchronize parameters. The Synchronize parameters dialogbox opens.

d. Click Change to update the changes made to the parameter.

Note:You can also edit theWARNING custom parameter from All Parameter tab duringSAPABAP_DispMonMonitoring Template deployment.

Tuning OMi MP for SAP Parameters

You can edit the parameters of the SAP Management Templates and Aspects that are alreadydeployed to the SAP CIs.

1. Open the Assignments & Tuning pane:

On BSM 9.2x, click Admin > Operations Management > Monitoring > Assignments &Tuning.

OnOMi 10.x, click Administration > Monitoring > Assignments & Tuning.



2. In theBrowse Views tab, select the RTSM View that contains the required Application Server CIfor which you want to tune parameters. Alternatively, you can use theSearch tab to find a CI.

3. In the list of SAP CIs, click aCI. The Assignments pane shows details of any existingassignments for the CI.

4. Click the assignment for which you want to tune parameters. The Details of Assignment paneshows the current parameter values.

5. In the Assignment Details pane, change the parameters:a. (Optional). By default, the list shows only mandatory parameters. To see all parameters, click

.

b. Select a parameter in the list, and then click .

For standard parameters, the Edit Parameter dialog box opens.

Click Value, specify the value, and then click OK.

For instance parameters, the Edit Instance Parameter dialog box opens.

Change the instance values if necessary, and then for each instance value, changedependent parameter values. After you change the instances and dependent parametervalues, click OK.

6. In the Assignment Details pane, click Save Changes. Operations Console deploys the new parameter values to the relevant HPE Operations Agent.

Run-time Service Model (RTSM) Views

RTSM View enables you to build and visualize a subset of the overall RTSMmodel.

How to Access RTSM Views

1. OpenModeling Studio pane:

On BSM 9.2x, click Admin > RTSM Administration > Modeling > Modeling Studio.

OnOMi 10.x, click Administration > RTSM Administration > Modeling > Modeling Studio.

2. Click Resource Type as Views.

3. Click Operations Management > SAP.

By default, OMi MP for SAP includes the following RTSM Views:



l SAP_Deployment: This RTSM view shows the SAP System, SAP J2EE Application Server,J2EE SAP Central Services, Database, SAP ABAP Application Server, SAPWork Process, andABAP SAP Central Services CI Types. The SAP_Deployment view enables you to visualize theEvent and Health perspectives of the SAP Application Server CIs that youmonitor. You can usethe SAP_Deployment view for visualizing events that are specific to themonitored SAP ApplicationServers. You can also use the SAP_Deployment view for assigning and tuning the OMi MP for SAPdeployment in the SAP Application Server environment. The following image shows the relationshipamong the CI Types:

l SAP_ABAP_Deployment: This RTSM view shows the SAP System, SAP ABAP ApplicationServer, ABAP SAP Central Services, SAP Work Process, and Database CI Types. The SAP_ABAP_Deployment view enables you to visualize the Event and Health perspectives of the SAPABAP Application Server CIs that youmonitor. You can use the SAP_ABAP_Deployment view forvisualizing events that are specific to themonitored SAP ABAP Application Servers. You can alsouse the SAP_ABAP_Deployment view for assigning and tuning the OMi MP for SAP deployment inthe SAP ABAP Application Server environment. The following image shows the relationship amongthe CI Types:



l SAP_J2EE_Deployment: This RTSM View shows the SAP System, Database,SAP J2EE Application Server, and J2EE SAP Central Services CI Types. The SAP_J2EE_Deployment view enables you to visualize the Event and Health perspectives of the SAP J2EEApplication Server CIs that youmonitor. You can use the SAP_J2EE_Deployment view forvisualizing events that are specific to themonitored SAP J2EE Application Servers. You can alsouse the SAP_J2EE_Deployment view for assigning and tuning the OMi MP for SAP deployment inthe SAP J2EE Application Server environment. The following image shows the relationship amongthe CI Types:



l SAP_Cluster_Deployment: This RTSM View shows the SAP System, Database, SAP ABAPApplication Server, and ABAP SAP Central Services, ClusterSoftware, ClusterResourceGroup,and Failover Cluster CI types in an SAP Cluster Configuration. You can use the SAP_Cluster_Deployment view for visualizing events that are specific to themonitored SAP ABAP ApplicationServers in cluster. The following image shows the relationship among the CI Types:

Event Type Indicators (ETIs)

ETIs are categorization of events based on the type of occurrence. TheOMi MP for SAP includes thefollowing ETIs tomonitor SAP-related events:

How to Access Event Type Indicators

1. Open the Indicators pane:

On BSM 9.2x, click Admin > Operations Management > Monitoring > Indicators.

OnOMi 10.x, click Administration > Service Health > CI Status Calculation > Health- andEvent Type Indicators.

2. In the CI Type pane, click Configuration Item > InfrastructureElement > ApplicationResource > [Select the related CI Type].



CIType ETI Description Value/Severity

sap_r3_server

TemSe FileInconsistency

This provides the Temporary Sequential FileInconsistency.

High/WARNING

sap_r3_server

IDoc Status This provides the status of SAP IDocs. High/WARNING,Normal/NORMAL

sap_r3_server

LoggedInUsers Max

Indicates the number of users who have loggedinto the SAP system at any given point of time.

High/WARNING

sap_r3_server

SAP UserLogin Status

This provides the status of the users logged ininto the SAP System.

Highl/WARNING

sap_r3_server

ABAP DumpRate

Indicates the frequency of runtime errors thatoccur on the SAP system.

High/WARNING

sap_r3_server

RFC ErrorRate

Indicates the frequency of RFC errors that occurduring the communication between theapplication servers or among the various RFCdestinations.

High/WARNING

sap_r3_server

Logon Failure This provides Logon failure status. Yes/MAJOR

sap_r3_server

SystemChangeOption Status

Indicates the SAP System Change option status. High/WARNING,Normal/NORMAL

sap_r3_server

SAP ProcessStatus

This provides the status of SAP process. Normal/NORMAL,Low/WARNING

sap_r3_server

ABAPDispatcherStatus

This provides the status of the SAP ABAPDispatcher.

High/WARNING,Normal/NORMAL

sap_r3_server

SAPTransportError Rate

Indicates the transport errors on the applicationserver. This includes the errors due to import orexport.

Normal/NORMAL,High/MAJOR

sap_j2ee_app_server

SAP J2EEKernel

Generic Indicator for all the Kernel relatedmetricsof SAP J2EE Application Server

Normal/NORMAL,Warning/WARNING,Major/MAJOR

sap_j2ee_app_server

SAP J2EEServices

Generic Indicator for all Service relatedmetrics ofSAP J2EE Application Server.

Normal/NORMAL,Warning/WARNING,Major/MAJOR

sap_ Unsuccessful Indicates the number of all the unsuccessful Normal/NORMAL,



CIType ETI Description Value/Severity

j2ee_app_server

LogonAttemptsRate

logon attempts by all users from server startup. High/MAJOR

sap_system

SAP SystemLog Status

This provides the status of the SAP System Logmessages.

Highl/WARNING,Normal/NORMAL

sap_system

CTSPerformance

This indicates the performance of the SAPCorrection and Transport System.

High/WARNING

sap_system

SAPFileSystemUtilization

This provides the information on the utilization ofthe SAP File System.

High/WARNING

sap_system

SAP SystemSecurityStatus

This provides the status of SAP System Securityparameters.

Highl/WARNING,Normal/NORMAL,Low/WARNING

sap_system

Work LoadPerformance

Indicates the workload performance on the SAPsystem.

Normal/NORMAL

Health Indicators (HIs)

HIs analyze the events that occur in SAP CIs and report the health of the SAP CIs. TheOMi MP forSAP includes the following HIs tomonitor the SAP-related events:

How to Access Health Indicators (HIs)

1. Open the Indicators pane:

On BSM 9.2x, click Admin > Operations Management > Monitoring > Indicators.

OnOMi 10.x, click Administration > Service Health > CI Status Calculation > Health- andEvent Type Indicators.

2. In the CI Type pane, click Configuration Item > InfrastructureElement > ApplicationResource > [Select the respective CI Type].

CI Type HI Description Value/Severity

database DatabaseCPU Usage

Indicates the database CPU usage on the SAPsystem.

Normal/NORMAL,Highl/WARNING




sap_work_process

BatchWorkProcessAvailability

Indicates the availability of the SAP backgroundwork process.

Available/NORMAL,Unavailable/MAJOR

sap_work_process

GatewayWorkProcessPerformance

Indicates the performance of the SAP Gatewaywork process.

Normal/NORMAL,Low/MAJOR

sap_work_process

SpoolWorkProcessPerformance

Indicates the performance of the Spool workprocess.


sap_work_process

BatchWorkProcessPerformance

Indicates the performance of the SAPbackground work process.


sap_work_process

SpoolWorkProcessAvailability

Indicates the availability of SAP Spool workprocess.


sap_system

SAP SystemMemoryUtilization

Indicates thememory utilized on the SAPsystem.


sap_system

SAP SystemStatus

Indicates whether the SAP system is up ordown.

Up/NORMAL,Down/CRITICAL

sap_j2ee_app_server

SAP J2EEApplicationServer Status

Indicates whether the SAP J2EE ApplicationServer is up or down.


sap_work_process

DialogWorkProcessAvailability

Indicates the availability of the dialog workprocess on the SAP system.


sap_work_process

UpdateWorkProcessPerformance

Indicates the performance of the update workprocess.


sap_work_process

GatewayWorkProcessAvailability

Indicates the availability of the Gateway workprocess.


sap_work_process

EnqueueWorkProcessPerformance

Indicates the performance of the SAP en queuework process.


sap_j2ee_

J2EETransaction

Indicates the ratio between committedtransactions count and total transactions count.





app_server

Success Rate

database DatabasePerformance

Indicates the database performance on the SAPsystem.

Normal/NORMAL,Low/WARNING

sap_system

SAP SystemCPUUtilization

Indicates the average utilization of CPU on theSAP system.


sap_work_process

DialogWorkProcessPerformance

Indicates the performance of SAP Dialog workprocesses.


sap_system

SAPTransactionRate

Indicates the average response time and nettime of SAP transactions.


sap_j2ee_app_server

ApplicationThread PoolUtilization

Indicates the ratio between the allocated taskslots and total number of task slots on theapplication thread pool.


sap_work_process

EnqueueWorkProcessAvailability

Indicates the availability of SAP Enqueue workprocess.


sap_work_process

UpdateWorkProcessAvailability

Indicates the availability of update work process Available/NORMAL,Unavailable/MAJOR

sap_j2ee_app_server

JARMRequestsAverageResponseTime

Indicates the average response time of all theJARM requests on the J2EE application server.


sap_r3_server

SAP ABAPApplicationServer Status

Indicates whether the ABAP application server isup or down


sap_j2ee_app_server

Cache HitRate

Indicates the cache hit rate on the J2EEapplication server.


sap_j2ee_app_

J2EE MemoryUsage Rate

Indicates the ratio between the usedmemoryand available memory.





server

sap_system

SAP BufferHit Ratio

Indicates the ratio of percentage of databaserequests that could be satisfied from the buffer,without requiring the involvement of thedatabase.


sap_j2ee_app_server

JARMRequestsAverage CPUTime

Indicates the average CPU time for all the JARMrequests.


sap_j2ee_app_server

SystemThread PoolUtilization

Indicates the ratio between the allocated taskslots and total number of task slots on thesystem thread pool.


Configuration Items and Configuration Item Types

Configuration Items (CIs) are components that have to bemanaged in order to deliver an IT Service.CIs typically include IT Services, hardware, and software. Configuration Item Types (CITs) describesthe type of a CI and its attributes. The SAP CIs that are discovered in an environment are groupedunder the CITs.

The following table lists the CI Types that aremapped to RTSM in OMi using the OMi MP for SAP:

Package CI Type

OMi_MgmtPack_SAP SAP System


ABAP SAP Central Services

Database

J2EE SAP Central Services

SAP J2EE Application Server

SAPWork Process

Note:OMi MP for SAP Cluster Deployment View contains ClusterSoftware,ClusterResourceGroup, and Failover Cluster CITs.



Topology Based Event Correlation (TBEC) Rules

TheOMi MP for SAP includes the following Topology Based Event Correlation Rules (TBEC Rules) tocorrelate SAP Application Server related events:

For more information on how the correlation rules work, see theOperations Manager i Concepts Guide.

How to Access Topology Based Event Correlation (TBEC) Rules

1. Open Correlation Rules pane:

On BSM 9.2x, click Admin > Operations Management > Event Correlation > Topology-Based Event Correlation.

OnOMi 10.x, click Administration > Event Processing > Correlation > Topology-BasedEvent Correlation.

2. In the Correlations pane, select the respective correlation rule.

SAP::Computer:Node Status >> SAP ABAP Application Server Status

Description: Correlates the node status to the availability of the SAP ABAP ApplicationServer

Symptom

CIT:SAP ABAP Application Server

ETI:SAPABAPApplicationServerStatus

Value: Down

Cause

CIT: Computer ETI: Node Status Value:Down

Value: Hang

Value: Suspended

SAP::Computer:Ping Availability>>SAP ABAP Application Server Status

Description: Correlates unavailability of the node to that of SAP

Symptom

CIT:SAP ABAP Application Server

ETI:SAPABAPApplicationServerStatus

Value: Down



Cause

CIT: Computer ETI: Ping Availability Value: Down

Value: Unavailable

SAP::Computer:Memory Usage Level >> SAP Batch & Dialog Workprocess Performance

Description: Correlates the Computer memory usage level to the SAP Batch Workprocessperformance and Dialog Workprocess Performance

Symptom 1

CIT:SAPWork Process ETI:BatchWorkprocessperformance

Value: Low

Symptom 2

CIT: SAPWork Process ETI:Dialogworkprocessperformance

Value: Low

Cause

CIT: Computer ETI: Memory Usage Level Value: Much Higher thanNormal

SAP::SAP System :SAP System Memory Utilization >> Computer Memory Usage Level

Description: Correlates the SAP System's Memory utilization to the Computer MemoryUsage Level

Symptom


Cause

CIT: SAP System ETI:SAPSystemMemoryUtilization

Value: Much Higher thanNormal

Value: High

SAP::SAP System: SAP System CPU Utilization>>Computer CPU Load

Description: Correlates the SAP System CPU Utilization to the Computer CPU load

Cause

CIT: SAP System ETI: SAPSystemCPUUtilization Value: High



Symptom

CIT: Computer ETI: CPU Load Value: Busy

Value: Constrained

Value: Overloaded

Value: Bottleneck

SAP::Computer:CPU Load>>SAP Batch & Dialog Workprocess Performance

Description: Correlates the Computer CPU Load to the SAP Batch Workprocessperformance and Dialog Workprocess performance

Symptom 1

CIT:SAPWork Process ETI:BatchWorkprocessperformance

Value: Low

Symptom 2

CIT: SAPWork Process ETI:Dialogworkprocessperformance

Value: Low

Cause

CIT: Computer ETI: CPU Load Value: Busy

Value: Constrained

Value: Overloaded

Value: Bottleneck

SAP::SAP ABAP Application Server:ABAP Dump Rate >>SAP Batch WorkprocessAvailability and Performance

Description: Correlates the SAP ABAP Dump rate to the SAP Batch workprocessperformance and availability

Symptom 1

CIT:SAPWork Process ETI:BatchWorkProcessPerformance

Value: Low

Symptom 2

CIT: SAPWork Process ETI:Batchworkprocessavailability

Value:Not Available



Cause

CIT: SAP ABAP ApplicationServer

ETI: ABAPDumpRate Value: High

SAP::Computer:Node Status >>SAP J2EE Application Server Status

Description: Correlates the Computer node status to the availability of SAP J2EEApplication Server

Symptom

CIT: SAP J2EE ApplicationServer

ETI:SAPJ2EEApplicationServerStatus

Value: Down

Cause

CIT: Computer ETI: Node Status Value: Down

Value: Hang

Value: Suspended

SAP::Computer:Ping Availability >>SAP J2EE Application Server Status

Description: Correlates the Computer availability to the SAP J2EE Application ServerStatus

Symptom


ETI: SAPJ2EEApplicationServerStatus Value: Down

Cause

CIT: Computer ETI: Ping Availability Value:Unavailability

SAP::SAP J2EE Application Server:Memory Usage Rate & Transaction Success Rate>>Computer CPU Load

Description:Correlates the SAP J2EE Application Server Memory Usage rate andtransaction success rate to the Computer CPU Load

Cause 1


ETI: J2EEMemoryUsageRate Value: High

Cause 2

CIT: SAP J2EE Application ETI: Value:Low



Server J2EETransactionSuccessRate

Symptom

CIT: Computer ETI: CPULOAD Value: Overloaded

SAP::Computer:CPU Load>>SAP JARM Requests Average Response Time

Description: Correlates the computer CPU Load to the SAP JARM Requests AverageResponse time

Symptom


ETI: JARMRequestsAverageResponseTime Value:High

Cause

CIT: Computer ETI: CPULOAD Value:Overloaded

SAP::Computer:Memory Usage Level >>SAP J2EE Application Server Status & TransactionSuccess Rate & Average Requests Response Time

Description: Correlates the Computer Memory Usage level to SAP J2EE Application ServerStatus, SAP J2EE Transaction Success Rate and SAP JARM Average Requests ResponseTime

Symptom 1


ETI: J2EETransactionSuccessRate Value: Low

Symptom 2


ETI: SAPJ2EEApplicationServerStatus Value:Down

Symptom 3


ETI:JARMRequestsAverageResponseTime

Value: High

Cause


SAP::SAP J2EE Application Server:J2EE Memory Usage Rate >>SAP J2EE ApplicationServer Average Requests Response Time & Average Requests CPU Time



Description: Correlates the SAP J2EE Memory Usage Rate to SAP JARM Average RequestsResponse Time and SAP JARM Average Requests CPU time

Symptom 1


ETI:JARMRequestsAverageResponseTime

Value: High

Symptom 2


ETI: JARMRequestsAverageCPUTime Value:High

Cause


ETI: J2EEMemoryUsageRate Value: High

Tools

TheOMi MP for SAP is packaged with tools which you can use to administer andmonitor SAP CIs.

Note:OMi MP for SAP Tools does not work for remotely monitored SAP Application Server CIs.

Prerequisites

OMi MP for SAP ABAP tools launching SAP GUI for different transactions use theWEBGUI port. Youmust enable theWEB-GUI for SAP for OMi MP for SAP ABAP tools to work with SAP systems in yourenvironment. To configure theWEB-GUI for SAP, follow these steps:

1. Go to transaction SICF and activate the following services:

a. /default_host/sap/bc/gui/sap/its/webgui

b. /default_host/sap/public/bc/ur



c. /default_host/sap/public/bc/its/mimes

2. Publish all the services using the following transaction:

SIAC_PUBLISH_ALL_INTERNAL

3. Go to transaction SMICM

4. From theMenu, open theParameters Displaymenu:

GOTO > Parameters > Display

5. Note the icm/server_port_0 field Port Number. This is theWEBGUI port number used by OMiMP for SAP Tools while launchingWEBGUI based Transactions.



Formore information about SAP Transactions and ActivatingWEBGUI port, seeSAP Documentation.

The following table lists the tools provided with OMi MP for SAP:

CI Type Tool Name Description

SAP ABAP ApplicationServer

SAP ABAPApplicationServer - StopPerformanceAgent

Stops the performance agent.

SAP ABAPApplicationServer -WorkloadMonitor

Displays the SAP transaction ST03 on theSAPGUI.

SAP ABAPApplicationServer -BackgroundJobOverview

Displays the SAP transaction SM37 on theSAPGUI.

SAP ABAPApplicationServer -SAPGUI forHTML

Launches the SAPGUI for HTML.

SAP ABAPApplication





Server -WorkProcessOverview

SAP ABAPApplicationServer -InstancesInformation

Provides information about the running SAPApplication Server instances.

SAP ABAPApplicationServer -InstallPerformancePackage

Installs the performance package.

SAP ABAPApplicationServer -RemovePerformancePackage

Removes the performance package.

SAP ABAPApplicationServer -BackgroundJob Definition


SAP ABAPApplicationServer - StartPerformanceAgent

Starts the performance agent.

SAP ABAPApplicationServer -System LogOverview


SAP ABAPApplicationServer -LoggedInUsersOverview

Displays the SAP transaction AL08 on theSAPGUI.




SAP ABAPApplicationServer -ConfiguredInstanceStatus (OnlyUnix Nodes)

Displays the status of Configured SAP instancesfor Unix Nodes only.

SAP ABAPApplicationServer -GatewayConnections

Displays the SAP transaction SMGW on theSAPGUI.

SAP ABAPApplicationServer -DatabasePerformance

Displays the SAP transaction DB02 on theSAPGUI.

SAP ABAPApplicationServer -BackgroundJob Status

Displays the SAP transaction SMX on the SAPGUI.

SAP ABAPApplicationServer - SAPServerOverview


SAP ABAPApplicationServer -CCMSControl Panel

Displays the SAP transaction RZ03 on the SAPGUI

SAP ABAPApplicationServer -PerformanceAgent Status(Only UnixNodes)

Provides the status of performance agent.

SAP ABAPApplicationServer - SAP

Checks the availability of SAP Database for UnixNodes only.




DatabaseAvailability(Only UnixNodes)

SAP ABAPApplicationServer -ProfileMaintenance

Displays the SAP transaction RZ10 on theSAPGUI.

SAP J2EE Application Server SAP J2EEApplicationServer -RemovePerformancePackage

Removes the performance package.

SAP J2EEApplicationServer -ConnectionStatus

Checks and displays the SAP J2EE ApplicationServer Connection status.

SAP J2EEApplicationServer -PerformanceAgent Status(Only UnixNodes)

Provides the status of performance agent on onlyUNIX nodes.

SAP J2EEApplicationServer - StopPerformanceAgent

Stops the performance agent.

SAP J2EEApplicationServer -ConfigurationCreation

Creates the configuration for the SAP J2EEapplication server monitoring at the node level.

SAP J2EEApplicationServer -InstallPerformance

Installs the performance package.




Package

SAP J2EEApplicationServer - StartPerformanceAgent

Starts the performance agent.



Chapter 4: Creating SAP ManagementTemplates1. Open theManagement Templates & Aspects pane:




Configuration Folders > ERP Management > SAP NetWeaver Application Server

3. Select the SAP NetWeaver Application Server folder and if you need to create a new configuration

folder, click . The Create Configuration Folder dialog box opens.

4. Type the name of the new configuration folder and a description. For example, you can type thenew configuration folder name as <Test>.

5. Click OK. The new configuration folder is created.

Configuration Folders > ERP Management > SAP NetWeaver Application Server > Test

6. In theManagement Templates & Aspects pane, select the configuration folder and click

Create Management Template. The CreateManagement Template wizard opens.

7. In theGeneral tab, type aName for the new SAP Management Template. Click Next.

8. An SAP Management Template enables you tomanage ABAP and J2EE application servers andall the related dependent CIs. Select SAP ABAP Application Server orSAPJ2EE Application Server from the list as the Topology View depending on your monitoringrequirement.

9. Click an item in the topology map to select theCI Type of the CIs that this Management Templateenables you tomanage. This is the type of CI to which theManagement Template can beassigned. For example, you can select SAP J2EE Application Server to monitor SAP J2EEApplication server in your SAP Landscape.

Click Next.

10. In theAspects tab, add the Aspects to theManagement Template. To add an existing Aspect,follow these steps:


a. Select the Aspect you want to add from the Available Aspects matching the CI Types pane.You can useCTRL orSHIFT key to select multiple Aspects.

b. Click to move the Aspect to the Selected Aspects pane. The Aspect is added to the

Management Template.

11. Youmust add the SAP ABAP Base Aspect or the SAP J2EE Base Aspect to the newManagement Template. The SAP ABAP Base Aspect and the SAP J2EE Base Aspect containsthe config file, scheduled task and log file policy templates, which are essential for data collection.

12. For each Aspect that you add, youmust specify at least one Target CI.

Click an Aspect in the list, and then in the topology map click the CIT you want the Aspect tomonitor when this Management Template is assigned. Use theCTRL orSHIFT key to selectseveral CITs. Each CIT that you select heremust correspond to one of the CI types assignedwithin the Aspect itself (or a child of one of those CITs). For example, you can select SAP CI fromthe topology map.

13. In theParameters tab, you see a list of all the parameters from the Aspects that you added to thisManagement Template.

To combine parameters:

a. Press CTRL and click the parameters that you want to combine.

b. Click the . The Edit/Combine Parameters dialog box opens.

c. Type aName for the combined parameters.

d. (Optional). Specify aDescription, Default Value, and whether the combined parameter isRead Only, anExpert Setting, orHidden.

You can specify either a specific default value, or you can click From CI Attribute and thenbrowse for a CI attribute. When you specify a CI attribute, Operations Management sets theparameter value automatically during the deployment of the underlying policy templates, usingthe actual value of this attribute from the CI. You can also change values of conditionalparameters. (The conditions are read-only and cannot be changed at Management Templatelevel.)

ReadOnly prevents changes to the parameter value when theManagement Template isassigned to a configuration item. Hidden also prevents changes, but additionally makes theparameter invisible when theManagement Template is assigned, and during parametertuning. Users can choose whether to show expert settings when they make an assignment.

e. Click OK.

User GuideChapter 4: Creating SAP Management Templates


You can also edit the parameters without combining them, to override the defaults in the

Aspects or policy templates. Click one parameter, and then click . The Edit/Combine

Parameters dialog box opens.

14. In the CreateManagement Template wizard, click Finish to save theManagement Template andclose the wizard. The new Management Template appears in theManagement Templates &Aspects pane.

Editing SAP Management Templates

You can edit the SAP Management Templates andmodify the following components:

l Parameters

l Aspects

Editing Parameters

Use Case:You are using Essential SAP ABAP Management Template tomonitor the status andperformance of batch jobs running on the SAP system. You aremonitoring the SAP ABAP Batch Joband want to modify the corresponding parameters corresponding to closely monitor theSAP ABAP Batch Job health.

To closely monitor the SAP ABAP Batch Job health, youmust modify the parametersSAP ABAP Batch Jobmonitor parameters - FREQ for ABAP Batch Jobs, TraceLevel for ABAP BatchJobs, TraceFileName for ABAP Batch Jobs, TraceMode for ABAP Batch Jobs, TracePeriod forABAP Batch Jobs, RFCTimeOutInterval for ABAP Batch Jobs.

1. OpenManagement Templates & Aspects:




Configuration Folders > ERP Management > SAP NetWeaver Application Server >SAP ABAP Application Server Management Template



3. Select theEssential SAP ABAP Management Template from the list, and then click . The

Edit Management Template dialog box opens.

4. Click theParameters tab. The list of parameters appear.

5. Double-click the ABAP Batch Jobs parameters.

In this instance, FREQ for ABAP Batch Jobs, TraceLevel for ABAP Batch Jobs, TraceFileNamefor ABAP Batch Jobs, TraceMode for ABAP Batch Jobs, TracePeriod for ABAP Batch Jobs, andRFCTimeOutInterval for ABAP Batch Jobs.

The Edit Parameter dialog box appears.

6. You can change the default value by using the drop down text. For example, you can change thevalue of the parameter FREQ for ABAP Batch Jobs to HIGH from VERYHIGH depending on yourmonitoring requirements.

7. Click OK. The Edit Management Template dialog box opens.

8. Click OK. The version of the SAP Management Template is incremented.

Note: The version number of the SAP Management Template is incremented when anycustomizations aremade to the SAP Management Template.

Editing Aspects

Use Case:You are using Extensive SAP J2EE Management Template tomonitor your J2EEenvironment. You do not want to use some Aspects which are part of the Extensive SAP J2EEManagement Template.

1. OpenManagement Templates & Aspects:




Configuration Folders > ERP Management > SAP NetWeaver Application Server >SAP J2EE Application Server Management Template

3. Select theExtensive SAP J2EE Management Template from the list, and then click Edit.The Edit Management Template dialog box opens.



4. Click theAspects tab. The list of Aspects appear.

5. Select the Aspect that you want to delete from the list. For example, you want to delete the SAPJ2EE Connections Manipulator Performance.

6. Click to delete the selected Aspect.

7. Click OK. The version of the Extensive SAP J2EE Management Template is incremented.



Chapter 5: Deployment ScenariosYou can useOMi MP for SAP tomonitor different SAP Application Server configurations likeSAP system with standalone ABAP Application Servers, J2EE Application Server Instances withCentral Server on same system, SAP ABAP Application Servers on remote nodes etc. This sectionprovides information about deploying OMi MP for SAP on different SAP Server configurations.

Monitoring SAP J2EE Application Servers on Single Host

OMi MP for SAP enables you tomonitor multiple SAP J2EE Application Servers running on a singleSAP Host system. To deploy OMi MP for SAPon SAP J2EE Application Servers running on a singlehost, follow these steps:

1. Youmust add the nodes you want to monitor to the OMi console.

2. Deploy the SAP J2EE Discovery Aspect to discover J2EE Application Server CIs on the SAPmanaged nodes.

3. Identify and deploy the SAP J2EE Management Template as per your monitoring requirement. Formore information about Identifying and Deploying SAP Management Templates, see Task 6:Identifying and Deploying an SAP Management Template.

The following figure shows a typical deployment scenario where the OMi MP for SAP is deployed tomonitor SAP J2EE Application Servers on Single Host:


Monitoring SAP J2EE Application Servers on Multiple Hosts

OMi MP for SAP enables you tomonitor J2EE Application Servers running onmultiple SAP Hostsystems. To deploy OMi MP for SAP on SAP J2EE Application Servers running onmultiple hosts,follow these steps:

Note:OMi MP for SAP only requires Agent to be installed on SAP node where SAP J2EE CentralServer Instance is running.

1. Youmust add the nodes you want to monitor to the OMi 10.x console.

2. Deploy the SAP J2EE Discovery Aspect to discover J2EE Application Server CIs on the SAPnodes.

3. Identify and deploy the SAP J2EE Management Template as per your monitoring requirement. Formore information about Identifying and Deploying SAP Management Templates, see Task 6:Identifying and Deploying an SAP Management Template.

User GuideChapter 5: Deployment Scenarios


The following figure shows a typical deployment scenario where the OMi MP for SAP is deployed tomonitor SAP J2EE Application Servers running onMultiple Hosts:

Monitoring Standalone SAP ABAP Application Servers

OMi MP enables you tomonitor Standalone SAP ABAP Application Servers in your SAP Landscape.To deploy OMi MP for SAP on SAP ABAP Application Servers, follow these steps:

1. Youmust add the nodes you want to monitor to the OMi console.

2. Deploy the SAP ABAP Discovery Aspect to discover ABAP Application Server CIs in yourSAP environment.

3. Deploy SAP ABAP Configuration Aspect.

4. Identify and deploy the SAP ABAP Management Template as per your monitoring requirement.For more information about Identifying and Deploying SAP Management Templates, see Task 6:Identifying and Deploying an SAP Management Template.

5. Configure SAP ABAP Monitoring Templates.



The following figure shows a typical deployment scenario where the OMi MP for SAP is deployed tomonitor SAP ABAP Application Servers running on SAP CIs:

Monitoring Remote SAP ABAP Application Servers

OMi MP for SAP enables you tomonitor ABAP Application Servers running on remote nodes whichdoes not haveOperations Agent installed. For using this functionality youmust deploySAP ABAP Remote Configuration Aspect. The SAP ABAP Remote Configuration Aspect enables youto configure the Proxy Node (with Agent) you want to use as host for monitoring and collecting requiredinformation from ABAP Application Server running on the remote node.

Note:You can configure an SAP CI managed by OMi tomonitor any number ofSAP ABAP Application Server running on remote nodes.

To deploy OMi MP for SAP tomonitor ABAP Application Servers running on remote nodes, followthese steps:

1. Add the Node with Agent installed to the OMi console.

2. Deploy the SAP Remote Configuration Aspect to populate remote ABAP Application Server CIs inyour SAP environment.



The ABAP Application Servers on Remote nodes gets populated in RTSM View.

3. Configure ABAP Monitoring Templates to support RemoteMonitoring by adding RemoteHostkeyword.

For more information on configuring ABAP Monitoring Template to support ABAP RemoteMonitoring, see "RemoteMonitoring with SAP ABAP Monitoring Templates ".

4. Identify and deploy the SAP ABAP Management Template as per your monitoring requirement.For more information about Identifying and Deploying SAP Management Templates, see Task 6:Identifying and Deploying an SAP Management Template.

The following figure shows a typical deployment scenario where the OMi MP for SAP is deployed tomonitor SAP ABAP Application Servers running on remote nodes:



Configuring OMi MP for SAP in High-Availability Cluster

OMi MP for SAP enables you tomonitor SAP Application Servers configured in High-Availabilitycluster. The information in this section helps you to understand the process of configuring OMi MP forSAP on SAP servers running in a high-availability environment such as anMC/ServiceGuard cluster.Although the information provided in this section uses MC/ServiceGuard to explain clusterconfigurations, the basic concepts for monitoring are same for high-availability environment.

Pre-requisites

The information in this section is designed to help you configure OMi MP for SAP in a high-availability environment: it is not intended to explain either how to set up the high-availability software or Operations Manager i. Before you start the process of configuring OMi MP for SAP in a high-availability environment, it is recommended to read through and consider the information included in the following sections:

l "Configuration Requirements "

l "Reports"

l "Views"

Configuration Requirements

Youmust complete the following tasks before starting to configure OMi MP for SAP with SAP High -Availability cluster:

l High-availability softwaremust already be correctly installed and configured in your SAPlandscape, and the cluster should function correctly. For example, SAP servers in theMC/ServiceGuard cluster must already be configured as OMi managed nodes with the appropriateOperations Agent software and functionality installed and running. You have to decide whether toconfigure one package for the central instance and the database server or set up separate packagesfor each part.

l Set the SAPOPC_HOSTNAMES variable on themanaged node.

a. On themanaged node, run the following in the command prompt:

ovconfchg –edit

b. Enter the SAPOPC_HOSTNAMES variable as following:

[ctrl.env]

SAPOPC_HOSTNAMES=<hostnames of the Cluster environment>

Example :

[ctrl.env]



SAPOPC_HOSTNAMES=sov02om139 sov02om140

c. Restart Operaions Agent using the following command:

ovc-restart

l Deploy the SAP ABAP Discovery Aspect on all Nodes in the cluster.

l Youmust configure and deploy SAP ABAP Configuration Aspect. The SAP ABAP ConfigurationAspect enables you to configure SAP ABAP Application Server CIs discovered from HAenvironment.

Note: The HostName entry in SAP ABAP Application Server Message Node for HA definesthe name of the host with which you want to associate messages generated by nodes in theSAP high-availability cluster.

Reports

If you want to generate OMi MP for SAP reports for all the nodes in theMC/ServiceGuard cluster, makesure that:

l OMi MP for SAP's R3 Performance Agent Service is started on all nodes in the cluster

l Operations Bridge Reporter (OBR) is installed and correctly configured.

Views

OMi MP for SAP provides SAP_Cluster_Deployment view which enables you to you to build andvisualize a subset of the overall RTSMmodel. For more information about OMi MP for SAP Views, see"Run-time ServiceModel (RTSM) Views".

Note:Youmust deploy the SAP ABAP Discovery and SAP ABAP Configuration Aspect on allcluster nodes for the OMi MP for SAP to generate SAP_Cluster_Deployment view.

Configuring OMi MP for SAP in a High-Availability Environment

This section provides information about configuring the OMi MP for SAP in a High-AvailabilityEnvironment.

To configure OMi MP for SAP in SAP High-Availability Cluster Environment, follow these steps:

1. SAP ABAP Configuration Aspect and Login Credentials

Youmust deploy theSAP ABAP Discovery Aspect to identify SAP Cluster nodes in high-availability environment. Youmust then deploy SAP ABAP Configuration Aspect on all thediscovered SAP CIs in High-Availability Cluster.



Make sure that the SAP Log-in Credentials provided in the SAP ABAP Configuration Aspect ishaving sufficient permissions to access the nodes in the SAP cluster.

2. Configure theOMi MP for SAP ABAP Monitoring Templates

Youmust configure the SAP ABAP Monitoring Templates provided with OMi MP for SAPdeploytheir respective Aspects to monitor SAP ABAP Application Server as per your monitoringrequirements. For more information on configuring SAP ABAP Monitoring Templates, see"SAP ABAP Monitoring Templates".

Note:Youmust increment the version of SAP ABAP Management Templates afterconfiguring or customizing SAP ABAP Monitoring Templates tomake sure the changes inMonitoring Template Configuration are synced at Management Template Level. For moreinformation on SAP ABAP Aspects and corresponding SAP ABAP Monitoring Templates,see SAP ABAP Monitoring Templates, Monitors, and History Files.

3. DeployOMi MP for SAP Management Templates

Youmust deploy OMi MP for SAP's Management Templates on SAP SIDs in the cluster as peryour monitoring requirements. For more information on deployingManagement Templates andAspects, seeGetting Started.

4. Availability of OMi MP for SAP Monitoring Template History Files

Youmust make sure that each node in theMC/ServiceGuard cluster, can access respectivehistory file (r3<monitor_name>.his) before and after a fail-over package switch. For moreinformation on setting history path and history files used by SAP ABAP Monitoring Templates, see"SAP ABAP Monitoring Templates, Monitoring Template Configuration Files, and History Files".

Advanced Configuration

This section provides additional information about configuring OMi MP for SAP in SAP High-AvailabilityEnvironment.

Host Mapping on Cluster Nodes

If the Agent discovers that multiple IP addresses are assigned to a single physical node in the high-availability cluster, themessages the agent sends show the host name associated with the IP addressthat is registered on theOMi management server for the cluster node, this is the name of the nodewhere the cluster package is running at the time themessage is sent.

Although this behavior is a feature of the OMi HTTPS agent in cluster environments, it overrides theOMi MP for SAP’s host-mapping functionality, which can lead to a situation where the wrong nameappears to be associated with messages displayed in themessage browser. To ensure that the host-mapping feature works as intended and the correct hostname is displayed in OMi MP for SAP



messages coming from the high-availability cluster, youmust disable the OMi HTTPS agent feature onthemanaged node, as follows:

1. Log on as a user with administrative privileges to each physical node in the high-availability clusterwhere anOMi HTTPS agent is running and open a command shell.

2. On HTTPS agents managed by OMi for Unix:

ovconfchg -ns eaagt -set OPC_SET_PROXY_FLAG_FOR_IP_ADDRESSES

'<IP_Address,IP_Address,...>'

Use the ovconfchg command on each physical node in the high-availability cluster to specify theIP address of the package (the virtual node) that you want to replace the cluster-node name asregistered on theOMi management server, when amessage from one of the cluster nodesappears in themessage browser. If multiple packages are running in the cluster (for example, forOMi and for Oracle), use commas "," to separatemultiple IP addresses in the list.

Note:Spaces are not allowed in the list of IP addresses defined by OPC_SET_PROXY_FLAG_FOR_IP_ADDRESSES. Never include the IP address specified in OPC_IP_ADDRESS in the list of IP addresses.

3. Restart the agent with the new configuration using the following command:

opcagt -kill; opcagt -start

SAP ABAP Monitoring Template History Files in a High-availability Cluster

The SAPABAP_CCMSIntegrationMon, SAPABAP_TraceMon, SAPABAP_ProcMon, and SAPABAP_StatRecMon SAP ABAP Monitoring Template have their own history files with the extension .his, forexample, r3monal.his. Each time one of theseOMi MP for SAP SAP ABAP Monitoring Templatestarts, it relies on the contents of its history file r3<monitor_name>.his to determine the last eventsmonitored and, as a result, the point at which the current monitor run should start. This mechanism isdesigned to avoid the problem of duplicate messages.

Note that SAPABAP_CCMSIntegrationMonMonitoring Template writes new information to its historyfile only if the SAP System it is monitoring is available and theOMi MP for SAP monitors can connect.If the SAP System beingmonitored is not available, SAPABAP_CCMSIntegrationMonMonitoring Template only updates the time stamp to reflect the time of the latest monitor run. Themonitoring templates SAPABAP_TraceMon, SAPABAP_ProcMon, and SAPABAP_StatRecMon SAPABAP Monitoring Template, on the other hand, write to their respective history file after eachmonitorrun whether the SAP System they aremonitoring is available or not.

History File r3monal.his for the SAPABAP_CCMSIntegrationMon Monitoring Template

#-----------------------------------------------------------



# Keyword SAP SAP SAP Last Scan

# System Number Instance Time

LastScannedSystem =SP6 =33 =DVEBMGS33 =1073908785

----------------------------------------------------------------

The history files for the OMi MP for SAP SAP ABAP Monitoring Template are usually stored on themanaged node where themonitors are running in a directory specified in eachmonitor’s configurationfile, r3<monitor_name>.cfg. By default, this directory is /var/opt/OV/conf/sapspi for all UNIXmanaged nodes except AIX, which uses the directory /var/lpp/OV/conf/sapspi, and%OVAGENTDIR%/conf/sapspifor Microsoft Windows managed nodes. However, if the cluster packageswitches to another node, then the OMi MP for SAPABAP Monitoring Template can no longer accessthemost recent history files stored on the failed cluster node. This may lead to the generation ofduplicate messages that have already been sent to OMi. For SAPABAP_CCMSIntegrationMon, theduplicate messages can be avoided by enabling CCMSAcknowledgeMessage, see SAPABAP_CCMSIntegrationMon.

Note: TheOMi MP for SAPcollector monitors keep their history information in the SAP tables. Asa result, they do not have a .his history file. The SAPABAP_TraceMonmonitor reads the SAPtrace and log files, and keeps the line number for each file in r3mondev.his. Therefore, in principle,SAPABAP_TraceMon is prone to sending duplicate messages if the package is switched to theother node. If r3mondev.his is stored on the local disks and SAPABAP_TraceMon on the new node,the OMi MP for SAP starts scanning from a point that was scanned on the previous node already.

However, after starting an SAP instance, new dev_* files will be created. Most of the dev_* files will becopied to dev_*.old files before creating new files. Therefore, r3mondev never monitors the dev_*.old files.

SAPABAP_TraceMon detects (through the Inode column in r3mondev.his) if a file is created as new,and then starts scanning the new file from the beginning. Therefore, you can use the defaultconfiguration for SAPABAP_TraceMonand it is not necessary to place r3mondev.his on a shared disk.For more information on SAP monitor to SAP ABAP Monitoring Template Mapping, see "OMi MP forSAP ABAP Monitoring Template Configuration Files".

Special Considerations for the SAP ABAP Monitoring Templates

This section contains information which is intended to help you set up the OMi MP for SAP alertmonitors in a high-availability environment. To set up the OMi MP for SAPSAP ABAP Monitoring Templates in a high-availability environment, follow these steps:

1. Enable (=1) theSAPABAP_CCMSIntegrationMonMonitoring Template’s auto-acknowledgmentfeature for CCMS alerts in SAP to avoid duplicate messages appearing in the OMi message



browser.

2. Define a CCMS monitor set. For example, "OMi", and a CCMS monitor: for example, "SAPMPMonitoring", for themessages you want to forward from CCMS to the OMi message browser.Note that themonitor-set feature can be only used with the XAL interface.

Special-Case Scenarios

For reasons of efficiency or cost, the secondary (or backup) node in a high-availability cluster mightalready be in use as an application server. If this in the case in your environment and regular high loadsmean that you need the central instance tomaintain the same performance level after the fail-overpackage switch as before, you have the option of shutting down the application server on thesecondary node after the fail-over so that themachine’s performance is available solely to the centralinstance. You can then share the user load between any other available application servers.

If performance is not an issue in your environment, you can choose to keep the application serverinstance running on the secondary node even after the fail-over package switch. However, if aninstance of an SAP application server is running on the samemachine as an SAP central instance, youwill need to ensure that the OMi MP for SAP SAP ABAP Monitoring Template monitors aremade awareof this fact and do not generatemessages for both the central instance and the application server. TheOMi MP for SAP SAP ABAP Monitoring Template monitors which are only designed to work with thecentral instance should be set up to excludemonitoring of the application-server instance. TheOMi MPfor SAP collector monitor and SAPABAP_ProcMon, for example, require special attention.

EachOMi MP for SAP SAP ABAP Monitoring Template monitor has a configuration file that you use todefine which SAP NetWeaver instances in your SAP landscape it should watch and, in addition, whatinformation it should collect. For example, you can use the SAPABAP_ProcMonMonitoring Templateconfiguration to collect information about either the central-instance processes or the processes tied tothe application-server instance.

Note: The SAP instance number associated with the application server already running on thesecondary node cannot be the same as the SAP instance number associated with the SAP centralinstance, which starts on the secondary node after the fail-over package switch.

OMi MP for SAP ABAP Monitoring Template Configuration Files

SAP ABAP Monitoring Template

MonitoringTemplateConfigurationFile (cfg)

CentralInstance

ApplicationServer

SAPABAP_TempSeqFileMon r3monaco ✓

SAPABAP_IdocStatusMon r3monale ✓



SAPABAP_CCMSIntegrationMon r3monal a ✓

SAPABAP_SysChgOptMon r3monchg ✓

SAPABAP_CTSMon r3moncts ✓

SAPABAP_TraceMon r3mondev ✓ ✓

SAPABAP_DispMon r3mondisp ✓ ✓

SAPABAP_DmpMon r3mondmp ✓

SAPABAP_BatJobMon r3monjob ✓

SAPABAP_StatRecMon r3perfstat ✓ ✓

SAPABAP_PerfMon r3perfagent ✓ ✓

SAPABAP_LckChkMon r3monlck ✓

SAPABAP_ProcMon r3monpro ✓ ✓

SAPABAP_RFCDestMon r3monrfc ✓

SAPABAP_SplMon r3monspl ✓

SAPABAP_SecMon r3monsec ✓

SAPABAP_StatusMon r3status ✓ ✓

SAPABAP_TransMon r3montra ✓

SAPABAP_UpdProcMon r3monupd ✓

SAPABAP_UsrMon r3monusr ✓

SAPABAP_WPMon r3monwpa ✓

a. CCMS 4.x only

The OMi MP for SAPCollector in a High-Availability Cluster

TheOMi MP for SAPcollector collects alerts from all the OMi MP for SAPABAP Monitoring Templatessuch as, for example, SAP ABAP Idoc Status Monitoring Template, SAP ABAP DumpStatusMonitoring Template, etc. The alert monitors themselves ensure that alert collectors are executedaccording to a defined schedule and report any messages that come back from the called function.

Note: TheOMi MP for SAP collector monitor is only intended to run on an SAP central instance: itis not designed to run on an application server.

If the secondary node in a high-availability cluster is running an application server, care has to be takento ensure that themonitors that are started when the central instance comes up on the secondary node



after the fail-over switch do not become confused about which SAP instance tomonitor—applicationserver or central instance.

To avoid problems when the central instance and the application server are running on the same clusternode at the same time, for example, after a system fail over, you need to ensure that each of themonitors which the collector monitor starts when the central instance comes up on the secondary nodeis configured to ignore alerts associated with the application server andmonitor only those alerts thatbelong to the central instance. This means modifying the configuration file of each of the OMi MP forSAP’s central-instancemonitors in such a way as tomake sure that themonitor is tied to a particularSAP central-instance number, for example, 00. By default, the OMi MP for SAPABAP Monitoring Template monitors are configured tomonitor all SAP instances present on the node,which in this special-case scenario would include the unwanted application-server instance, too.

Tying the SAPABAP_IdocStatusMon to an SAP Instance Number illustrates how the configuration forthe SAPABAP_IdocStatusMonMonitoring Template on the secondary node would look if youconfigured SAPABAP_IdocStatusMonMonitoring Template tomonitor only the central instance (forexample=00) on the secondary node nodename2.com and not the instance of the application server(=01), which is already running. Note that the node name you specify in this file is the name of thephysical cluster node.

Tying the SAPABAP_IdocStatusMon Monitoring Template to an SAP Instance Number

#AlertMonFun SAP SAP SAP SAP Alert Enable=1 (...)

# Host System Number Client Monitor Disable=0 (...)

#----------------------------------------------------------------------------

--

AlertMonFun =ClusterNodeA =CI =00 =099 =ALE =1 (...)

AlertMonFun =ClusterNodeB =CI =00 =099 =ALE =1 (...)

The SAPABAP_ProcMon Monitoring Template in a High-Availability Cluster

The SAPABAP_ProcMonMonitoring Template scans for and checks all processes associated with agiven SAP instance, for example, the dialog, en queue, update, batch, dispatch, message, gateway,and spool work processes. However, the SAPABAP_ProcMonMonitoring Template can be used tomonitor database processes, too.

If the secondary node in a high-availability cluster is running an application server, then care has to betaken after a package switch that the SAPABAP_ProcMonMonitoring Template started by thepackage does not assume that the processes associated with the application server also need to bemonitored along with the processes belonging to the central instance. One way of ensuring this is tospecify the exact number of processes to bemonitored by SAPABAP_ProcMonMonitoring Template



in the configuration (in the column: Process number=#). The number of processes tomonitor must bethe same on each node both before and after the fail-over package switch.

In addition, if you want to ensure that the SAPABAP_ProcMonMonitoring Template monitors onlythose processes belonging to a specific SAP instance on a node wheremultiple SAP instances arerunning, for example, after a package switch, you have tomake sure that the SAPABAP_ProcMonMonitoring Template knows which SAP instances it is supposed to watch. You can do this bymodifying the SAPABAP_ProcMonMonitoring Template configuration on the adoptive node in thecluster in such a way that each SAP instance number (defined in the column: SAP Number=) is linkedto the appropriate process name, as illustrated in the following example:

Tying the SAPABAP_ProcMon Monitoring Template to an SAP Instance Number

#AlertInstMonPro SAP SAP Process Enable Mode Process (...)

# System Number name =1 number (...)

#--------------------------------------------------------------------------

AlertInstMonPro =T11 =00 =saposcol =1 =Exact =1 (...)

AlertInstMonPro =T11 =01 =saposcol =1 =Exact =1 (...)

OMi MP for SAP R3 Performance Agent in a High-availability Environment

Note:SinceOMi MP for SAP Performance Agent will always use the physical hostname in acluster environment, youmust specify the clustered SAP-system details by configuring OMi MPfor SAP Performance Agent with themanual mode (r3perfconfig -manual).

In the event of a fail over and subsequent package switch, the Performance Agent stops collectingvalues for the SAP metrics on the host node and, as soon as the package comes up on the secondarynode, starts to monitor and report the appropriate SAP metrics on the secondary node. Metrics forphysical components such as CPU and disk performance continue to be collected on both nodesirrespective of where the package is running. This needs to be taken into account when generating andpublishing performance reports and graphs.

Removing the OMi MP for SAP in a High-availability Environment

TheOMi MP for SAP software and functionality has to be removed from each individual physical nodein theMC/ServiceGuard cluster, where the product was installed and configured. This will involve thefollowing steps:

1. If you installed the OMi MP for SAP R/3 Performance Agent on themanaged nodes in the cluster,you will have to remove it and its components from the SAP managed nodes in theMC/ServiceGuard cluster before you proceed to step two. For more information, see"Removing



the OMi MP for SAP R/3 Performance Agent"

2. After removing the OMi MP for SAP R/3 Performance Agent, youmust remove theOMi MP forSAPcomponents from the SAP managed nodes in theMC/ServiceGuard cluster.

The following figure shows a typical deployment scenario where the OMi MP for SAP is deployed inHigh Availability Environment:



Chapter 6: TroubleshootingThe following section provides information about troubleshooting scenarios:

Note:OnUNIX nodes, youmust replace %OvDataDir%with /var/opt/OVwhile runningcommands mentioned in this section.

Multiple SAP CIs discovered on MA Server with same Display Label

Problem:Display Label does not have name attribute.

Solution: If you want to Youmust add name as part of the default display label forSAP ABAP Application Server and SAP J2EE Application Server CI. For more information, seeOMiMP for SAP Installation Guide.

"Request does not match component version" error while adding the SAP MP Transports tothe import queue

Problem: “Request does not match component version” error displayed while adding the SAP MPtransports to the import queue.

Solution:You can select the option “Ignore the invalid component version” while importing Transportrequest. The “Ignore the invalid component version” option can be used as the contents of the OMi MPfor SAP Transports are independent of the component version and SAP support pack.

SAP ABAP Performance Monitor is not logging the performance data for DBINFO_PERFPerformance Monitor

Problem:SAP reports the following runtime error along with errors in the r3perfmon.log:

Runtime Errors DBIF_DSQL2_OBJ_UNKNOWN

Exception CX_SY_NATIVE_SQL_ERROR

Date and Time [...]

r3perfmon.log on an SAP System contains the following errors:

140520-11:10:23 Info : Try to get performance data from ASE interface

140520-11:10:23 Info : Calling rfc function module /HPOV/OV_DISPATCH

140520-11:10:23 Info : Timeout variable is set to: 30.000000

140520-11:10:28 ERROR: RFC CALL ERROR.KEY :

140520-11:10:28 ERROR: RFC CALL ERROR.STATUS :


140520-11:10:28 ERROR: RFC CALL ERROR.MESSAGE: - Table does not exist in database.

140520-11:10:28 ERROR: RFC CALL ERROR.INTSTAT:

140520-11:10:28 Info : call RfcLastError

140520-11:10:28 Info : set rfc error variables

140520-11:10:28 ERROR: OvCHandleIO::vHandle > Can't call the Performance Monitor :- DBINFO_PERF

140520-11:10:28 ERROR: OvCPerfScheduler::RemoveSAPLoginPtr - No Connection to SAP

140520-11:10:28 Info : Scheduled Monitor: - Wed May 20 11:10:28 2014

S99 00 DBINFO_PERF

Solution: The DBINFO_PERF performancemonitor works only with Oracle database data structures. Itdoes not work with data structures from other database products. Disable DBINFO_PERF in the policytemplate r3perfagent.cfg associated with the OMi MP for SAP Aspect to avoid the unnecessaryerror. For more information about DBINFO_PERF performancemonitor, see "DBINFO_PERF"

"librfc32.dll not found" error while executing the OMi MP for SAP Aspects

Problem:OMi MP for SAP displays SAP RFC SDK Files not found errors while deploying OMi MP forSAP.

Solution: To resolve SAP RFC SDK Files not found error, follow these steps:

1. DownloadSAP RFC SDK 6.40 from SAP Software Download Center.

Note:Youmust download SAP RFC SDK 6.40 irrespective of SAP version in yourenvironment. Select the appropriate RFC Library from the list based on theOperating Systemof the SAP system that needs to bemonitored.

2. Uncar the downloaded RFC Library files and copy the library to Instrumentation folder onSAP managed nodes. Instrumentation folder is available at the following locations:

Windows Node:

%OvAgentDir%\bin\instrumentation

UNIX Node:

/var/opt/OV/bin/instrumentation

Formore information about OMi MP for SAP Transports and un-carring the Transport files, seeOMi MP for SAP Installation Guide.

User GuideChapter 6: Troubleshooting


Checking OMi MP for SAP Transports currently installed on SAP system

Problem:OMi MP for SAP ABAP Monitoring is not working as expected. You want to check theTransports currently installed on SAP system.

Solution: To check OMi MP for SAP Transports currently installed on SAP system, follow thesesteps:

1. Log into the SAP system using the SAPGUI.

2. Open STMS (/nstms) transaction.

3. Go toMenu Overview > Imports (F5). Select the queue for the SID of the SAP System you wantto check.

4. Click History > Import history. ‘No log information in selected area’ notification window appears.Close the window. Last week's import history is displayed. The list may be empty.

5. Select theDate column, and click onEdit > Filters (Ctrl+F10). In the window, specify a startdate to cover the installation of OMi MP for SAP Transports. A list of requests for the specifiedtime range is displayed.

6. If the result list contains many non-OMi MP for SAP Transports, then you can restrict the list byfiltering on the Transport owner.

7. Select theOwner column title, and click onEdit -> Filters (Ctrl+F10). In the window, specifyowner HPMP, and press ENTER. The list of Transports is now restricted to HPMP owner.

OMi MP for SAP JAVA Discovery not working as expected

Problem:OMi MP for SAP JAVA Discovery not working as expected.

Solution: To troubleshoot the OMi MP for SAPJAVA Discovery, perform the following checks onSAP managed nodes:

1. Check Environment Variable:

Set SAPMP_REMOTE_CLUSTID Environment variable with Remote Application Server cluster ID forSAP NetWeaver 7.0.

2. Check if SAP J2EE Discovery ovpolicy -l -polname SAPJ2EE_Discovery is present andenabled.

You deploy SAP J2EE Discovery Aspect if SAP J2EE Discovery ovpolicy -l -polnameSAPJ2EE_Discovery is not present. Confirm successful deployment at deployment tab in OMiserver. For more information about deploying SAP J2EE Discovery Aspect, see Task 3:Deploying the SAP Discovery Aspect.

3. Check if SAP J2EE Discovery policy is in enabled state.



Enable SAP J2EE Discovery policy using ovpolicy -e -polname SAPJ2EE_Discovery if theSAP J2EE Discovery policy is not in enabled state.

4. Check if OMi MP for SAP instrumentation is available at the following location on the SAP node:

%ovDataDir%\bin\instrumentation\

You can deploy SAP J2EE Discovery Aspect if the OMi MP for SAP Instrumentation is notpresent at the required location.

5. You can identify errors by verifying the sapmp_j2ee_discovery.log file available at the followinglocation:

%OvDataDir%\App_Monitoring\SAPJ2EE\log\sapmp_j2ee_discovery.log

6. If you have the Discovery policy ID, you can check the availability of the following files:

The files are available at %OvDataDir%\tmp\agtrep

o <Policy ID>.cis.xml

o <Policy ID>.out

o <Policy ID>.services.xml

o <Policy ID>_ci.xml

o <Policy ID>.ci_refs.xml

If you do not have the Discovery policy ID, you can get the policy ID by running the followingcommand on SAP managed node:

ovpolicy -list -level 4 -polname "SAPJ2EE_Discovery"

In case of failover, check if the abovementioned files are updated on all cluster nodes.

You can run the following command on respective cluster node to update the policy files:

Ovagtrep -run "SAPJ2EE_Discovery"

OMi MP for SAP ABAP Remote Discovery is not working as expected

Problem:OMi MP for SAP ABAP Remote Discovery not working as expected.

Solution: To troubleshoot the OMi MP for SAPABAP Remote Discovery, perform the following checkson SAP managed nodes:

1. Check if SAP ABAP Discovery ovpolicy -l -polname SAPABAP_RemoteDiscovery isavailable.



You can deploy SAP ABAP Remote Configuration Aspect to make policy available. Afterdeployment, you can confirm successful deployment job at deployment tab in OMi Server.

2. Check if Remote Discovery policy is in enabled state.

You can enable policy using ovpolicy -e -polname SAPABAP_RemoteDiscovery.

3. Check if OMi MP for SAP Instrumentation is available on SAP node at the following location:


You can deploy SAP ABAP Remote Configuration Aspect to confirm availability of OMi MP forSAP instrumentation.

4. Check and identify errors in the sapmp_abap_remotediscovery.log file available at the followinglocation:

%OvDataDir%\App_Monitoring\SAPABAP\log\sapmp_abap_remotediscovery.log




o <Policy ID>.out





ovpolicy -list -level 4 -polname "SAPABAP_RemoteDiscovery"



Ovagtrep -run "SAPABAP_RemoteDiscovery"

SAP ABAP Discovery not working as expected

Problem:SAP ABAP Discovery is not working after deploying SAP ABAP Discovery Aspect.

Solution: To troubleshoot the OMi MP for SAP ABAP Discovery, perform the following checks onSAP managed nodes:



1. Make sure that you have provided Fully Qualified computer name for all SAP managed nodes.

2. Check if SAP ABAP Discovery ovpolicy -l -polname SAPABAP_Discovery is available.

You can deploy SAP ABAP Discovery Aspect to make ABAP Discovery available. You canconfirm successful deployment job at deployment tab in OMi Server.

3. Check if SAP ABAP Discovery policy is in enabled state.

You can enable the SAP ABAP Discovery policy using ovpolicy -e -polname SAPABAP_Discovery.

4. Check if OMi MP for SAP Instrumentation is available on SAP node at the following location:


You can deploy SAP ABAP Discovery Aspect to ensure availability of Instrumentation.

5. You can identify errors by verifying the r3sdisc.log file available at the following location:

%OvDataDir%\App_Monitoring\SAPABAP\log\r3sdisc.log




o <Policy ID>.out





ovpolicy -list -level 4 -polname "SAPABAP_Discovery"



Ovagtrep -run "SAPABAP_Discovery"

OMi MP for SAP Discovery is working on node but CIs are not discovered in RTSM

Problem:OMi MP for SAP Discovery is working on node but CIs are not discovered in RTSM.

Solution: If the OMi MP for SAP Discovery runs successfully on node,you can troubleshoot theproblem by checking the following logs at specific locations onMA Server:



OnOMi Server (for debugging Service Discovery)

1. You can enable Trace Level to DEBUG:a. In %TOPAZ_HOME%\conf\core\Tools\log4j\wde\opr-svcdiscserver.properties

b. Select value loglevel=, and update value to DEBUG.

c. Select value loglevelcitrace=, and update value to DEBUG.

2. You can check and identify errors from the Discovery logs available at the following locations:

o %TOPAZ_HOME%\log\wde\opr-svcdiscserver-citrace.log

o %TOPAZ_HOME%\log\wde\opr-svcdiscserver.log

o %OvDataDir%\shared\server\log\OvSvcDisc.log

OMi MP for SAP J2EE Data collection is failing or alerts are not reaching MA Event browser

Problem:OMi MP for SAP J2EE Data collection is failing or alerts are not reachingMA Event browser.

Solution:You can troubleshoot the problem by performing the following checks on SAP managednodes:

1. Check if SAP J2EE Discovery policy is available and is in enabled state.

2. Check if OMi MP for SAP Instrumentation is available at the following location:


If Instrumentation is available but the Instrumentation file which starts with sapmp is missing, youcan redeploy SAP J2EE Discovery Aspect.

3. Check SiteConfig availability at the following location:

%OvDataDir%\conf\sapspi\global\SiteConfig

If SiteConfig is unavailable, you can run the following command from the instrumentation folder torun the OMi MP for SAP Discovery:

r3mon_perl -S sapmp_j2ee_discovery.pl

4. Check SAP J2EE Discovery log available at the following location for errors:

%OvDataDir%\App_Monitoring\SAPJ2EE\log\sapmp_j2ee_cfg.log

Identify and resolve the errors from log. You can run the following command from theinstrumentation folder to re-run the SAP J2EE configuration:

r3mon_perl -S sapmp_j2ee_cfg.pl

5. OMi MP for SAP uses MetricDefinitions.xml file for J2EE data collection.The



MetricDefinitions.xml is available at the following location:

%OvDataDir%/conf/sapspi/global/

You can run the following command from the instrumentation folder if theMetricDefinitions.xml isnot available:

r3mon_perl -S r3mon_configCheck -f

6. Check if OMi MP for SAP J2EE policies starting with SAPJ2EE_* is available and is in enabledstate.

You can perform the check running the following command:

ovpolicy -l

7. You can run the SAP J2EE data collectionmanually in debugmode and check logs to identify theerrors. To run the SAP J2EE data collectionmanually in debugmode:

SAPMP_CollMgr -app=SAPJ2EE -freq=<VERYHIGH|HIGH|MEDIUM|LOW> -d

Check the following logs to identify the errors:

o %OvDataDir%\App_Monitoring\SAPJ2EE\log\SAPMP_CollMgr.pl.log

o %OvDataDir%\App_Monitoring\SAPJ2EE\log\SAPMP_ConfHandler.pl.log

OMi MP for SAP J2EE Data logging is failing

Problem: J2EE Data logging is failing for OMi MP for SAP

Solution:Perform the following checks on SAP managed node:

1. Check if SAP J2EE policies starting with SAPJ2EE_* is available and is in enabled state.

You can perform the check by running the following command:

ovpolicy -l

2. Check the availability of Datasources.

You can run the following command to check the availability of Datasources:

ovcodautil -showds SAPSPINW_RPT_METRICS

If the Datasources are unavailable, you can run the following command to activate Datasources:

On Windows:

"%OvDataDir%\bin\R3PerfAgent\bin\r3PerfConfig.exe" -j2ee

On UNIX:



"/var/opt/OV/bin/R3PerfAgent/bin/r3PerfConfig" -j2ee

3. Check if the SAP J2EE data logging is enabled.

You can check the value DATA_LOGGING_ENABLED=TRUE in the configuration file available at thefollowing location:

%OvDataDir%\conf\sapspi\global\SPIConfig

4. You can run the SAP J2EE data collectionmanually in debugmode and check logs to identify theerrors. To run the SAP J2EE data collectionmanually in debugmode:

SAPMP_CollMgr -app=SAPJ2EE -freq=<VERYHIGH|HIGH|MEDIUM|LOW> -d


o %OvDataDir%\App_Monitoring\SAPJ2EE\log\SAPMP_CollMgr.pl.log

o %OvDataDir%\App_Monitoring\SAPJ2EE\log\SAPMP_ConfHandler.pl.log

OMi MP for SAP ABAP Data collection is failing or alerts not reaching on MA event browser

Problem:OMi MP for SAP Data collection is failing or alerts not reaching onMA event browser.

Solution:Perform the following checks on SAP managed node:

1. Check if SAP ABAP Discovery policy is available and is in enabled state.

2. Check the availability of OMi MP for SAP Instrumentation at the following location:

%ovDataDir%/bin/instrumentation/

Deploy SAP ABAP Discovery Aspect again if OMi MP for SAPInstrumentation is available but thefiles which starts with sapmp aremissing.

3. Check the availability of r3itodsap at the following location:

%OvDataDir%/conf/sapspi/global/r3itosap

If r3itosap is unavailable, re-run the SAP ABAP Configuration by running the following commandfrom the instrumentation folder:

r3mon_perl -S sapmpcfg.pl

4. You can check for errors in the SAP ABAP Configuration log file. You can check the availability ofSAP ABAP Configuration log file at the following location:

%OvDataDir%/App_Monitoring/SAPABAP/log/sapmp_abap_cfg.log

You can verify and resolve the errors using the log file. To run the SAP ABAP Configuration again,run the following command from the instrumentation folder:




5. Check if the Client and Username (password is in encrypted state) values in r3itosap file issame as provided during deployment of SAP ABAP Configuration Aspect.

6. Check SAP ABAP policies for type sapconfigfile is available and is in enabled state.

7. You can run the SAP ABAP data collectionmanually in debugmode and check logs to identify theerrors. To run the SAP ABAP data collectionmanually in debugmode:

SAPMP_CollMgr -app=SAPABAP -freq=<VERYHIGH|HIGH|MEDIUM|LOW> -d


o %OvDataDir%/App_Monitoring/SAPABAP/log/SAPMP_CollMgr.pl.log

o %OvDataDir%/App_Monitoring/SAPABAP/log/SAPMP_ConfHandler.pl.log

OMi MP for SAP ABAP Data Logging is failing

Problem:OMi MP for SAP ABAP Data Logging is failing.

Solution:Perform the following checks on SAP managed nodes:

1. Make sure the OMi MP for SAP performance agent is started using Performance Agent tool fromMA server.

You can check the status of OMi MP for SAP performance agent by running the followingcommand:

On Unix nodes:

/var/opt/OV/bin/instrumentation/r3mon_perl -S SAPMP_Tool.pl Status

You can start the Performance Agent by running the following command:

/var/opt/OV/bin/instrumentation/r3mon_perl -S SAPMP_Tool.pl Start

On Windows nodes:

%OvAgentDir%\bin\instrumentation\r3mon_perl -S SAPMP_Tool.pl Start

2. Check the availability of Datasources.

You can run the following command to display status of datasources for configured instances:

ovcodautil -showds

You can run the following command to activate Datasources for configured instances:

UNIX:



"/var/opt/OV/bin/R3PerfAgent/bin/r3PerfConfig.exe" -abap

Windows:

"%OvDataDir%\bin\R3PerfAgent\bin\r3PerfConfig" -abap

3. Youmust manually create Datasources for Remote Application servers using the followingcommand:

UNIX:

"/var/opt/OV/bin/R3PerfAgent/bin/r3PerfConfig.exe" -manual

Windows:

"%OvDataDir%\bin\R3PerfAgent\bin\r3PerfConfig" -manual

Youmust provide the SAP SID, HostName, and Instance to create data sources.

4. Agent Installation command returns errors if the r3PerfConfig file is not available onmanagednode at the following location:

%OvDataDir%\bin\R3PerfAgent\bin\r3PerfConfig

You can run the following command to re-install OMi MP for SAPPerformance Agent:

%OvAgentDir%\bin\instrumentation\r3mon_perl -S SAPMP_Tool.pl Install

5. You can identify datasources errors by verifying the sapmp_abap_dscmd.log file available atthe following location:

%OvDataDir%\App_Monitoring\SAPABAP\log\sapmp_abap_dscmd.log

OMi MP for SAP ABAP Data collection on ABAP Application Server in HA environment isfailing or alerts are not reaching MA event browser

Problem:OMi MP for SAP ABAP Data collection on ABAP Application Server in HA environment isfailing or alerts are not reachingMA event browser.

Solution:You can perform the following checks onmanaged nodes to troubleshoot the problem:

1. Check if SAP ABAP Discovery policy and SAP ABAP Configuration policy is available and is inenabled state.



Deploy SAP ABAP Discovery Aspect again if OMi MP for SAP Instrumentation is available butthe files which starts with sapmp aremissing.



3. Check the availability of r3itosap at the following location:

%OvDataDir%/conf/sapspi/global/r3itosap

If r3itosap is unavailable, re-run the SAP ABAP Configuration by running the following commandfrom the instrumentation folder:


4. You can check for errors in the SAP ABAP Configuration log file. You can check the availability ofSAP ABAP Configuration log file at the following location:

%OvDataDir%\App_Monitoring\SAPABAP\log\sapmp_abap_cfg.log

You can verify and resolve the errors using the log file. To run the SAP ABAP Configuration again,run the following command from instrumentation folder:


5. Check if the Client and Username (password is in encrypted state) values in r3itosap file issame as provided during deployment of SAP ABAP Configuration Aspect.

6. Check for the HostMapping value in r3itosap file. The HostMapping value provides details aboutcluster nodes participating in HA environment, Central Instance, SID, Virtual Server node name,and Hostnamewith which you associate themessages at MA event browser.

The following is a sample HostMapping line syntax:

HostMapping =<SID> = <Central Instance> =<Physical node name1 >, <Physical NodeName 2>,<Virtual Node Name > = <Message Node Name>

Message Node Name is optional. If not specified, Virtual Server Namewould act as MessageNode Name.

The following is a sample HostMapping configuration:

HostMapping =NA9 =09=ipv6winclus1.hpeswv6lab.com,ipv6winclus2.hpeswv6lab.com,saphanw.hpeswv6lab.com =IXYZE01XXX.hpeswlabs.adapps.hpe.com

Make sure the details provided in HostMapping entry is valid. If the HostMapping configuration isinvalid, you can check the sapmp_cluster_details.txt available at the following location toverify the details:

%OvDataDir%\App_Monitoring\SAPABAP\sapmp_cluster_details.txt

OMi MP for SAP Cluster discovery is not working as expected

Problem:OMi MP for SAP Cluster discovery is not working as expected.



Solution:You can perform the following checks to troubleshoot the problem:

1. Make sure that you have provided Fully Qualified computer name for all SAP managed nodes.

2. Check if SAP ABAP Discovery ovpolicy -l -polname SAPABAP_Discovery is available.

You can deploy SAP ABAP Discovery Aspect to make ABAP Discovery available. You canconfirm successful deployment job at deployment tab in OMi Server.

3. Check if SAP ABAP Discovery policy is in enabled state.

You can enable the SAP ABAP Discovery policy using the ovpolicy -e -polname SAPABAP_Discovery command.



You can deploy SAP ABAP Discovery Aspect again if OMi MP for SAP Instrumentation isunavailable.

5. You can verify the Discovery logs files available at the following locations for more details:

o %OvDataDir%\App_Monitoring\SAPABAP\log\r3sdisc.log

o OvDataDir%\App_Monitoring\SAPABAP\log\sapmp_cluster_discovery.log


The files are available at %OvDataDir%/tmp/agtrep


o <Policy ID>.out





ovpolicy -list -level 4 -polname "SAPABAP_Discovery"




7. Make sure that after Discovery the removeRelationOnPassive file is present only on active nodeat the following location:



%OvDataDir%\App_Monitoring\SAPABAP\

Note:SAP Cluster Deployment view will not get updated for passive nodes, if theremoveRelationOnPassive file is not available.

8. The SAP_Cluster_Deployment view will not get updated for first run of Discovery immediatelyafter fail over. The SAP_Cluster_Deployment view will get updated after the first run of ScheduledDiscovery on Passive node.

If you want to update the view before the Scheduled Discovery run, you can run the discoverymanually on active nodes (passive before failover) after failover using the following commands:

To run the SAP ABAP Discovery:


To publish CIs to RTSM:

Ovagtrep -publish -all

SAP Cluster Deployment view not getting updated with current SAP active node after SAPCluster failover

Problem:SAP Cluster Deployment view is not getting updated with current SAP active node afterSAP Cluster failover.

Solution:SAP Cluster Deployment view is updated with the next schedule of SAP ABAP Discovery.If you want to update the SAP Cluster Deployment view before scheduled run of SAP ABAPDiscovery, deploy SAP ABAP Discovery Aspect on current active node.

"Could not connect to the node. Please check if the agent is up and running, the certificates are in placeand your firewall configuration is correct" error when deploying SAP Management Templates onRemote SAP Systems.

Problem:On remote configured SAP Application Server CI, Management Template deploymentshows the Could not connect to the node. Please check if the agent is up andrunning, the certificates are in place and your firewall configuration is correct”error message in Deployment Jobs Wizard.

Solution: This error is only for SAP systems where the Operations Agent is not installed. You can ignore this error since the SAP Aspects are successfully deployed. This error shows when the system attempts to deploy the Infrastructure Aspects within the SAP Management Templates on SAP systems which do not have the Operations Agent. For more information, see Task 5: Deploying SAP ABAP Remote Configuration Aspect.



Appendix: Metrics and DatasourcesTheOMi MP for SAP creates data store tables to enable data collection frommetrics. OMi MP for SAPuses two separate Datasources and relatedmetrics for logging the data collected fromSAP ABAP Application Servers and SAP J2EE Application Servers in your SAP Environment.


TheOMi MP for SAP creates the following data store table to log the data collected by metrics fromSAP ABAP Application Server:

Note: R3_<SAP_Hostname>_<SAP_SID>_<SAP_Instance_ Number>_DATA is the Datasource usedby SAP ABAP Application Server Policy Templates. The R3_<SAP_Hostname>_<SAP_SID>_<SAP_Instance_ Number>_DATADatasource is created for every SAP ABAP Application ServerInstance to log the collected data.

Aspect Name

PolicyTemplateName Table Name Metric Name

MetricData Type

SAP ABAPPerformanceMonitor

SAPABAP_PerfMon

DBINFO_PERF CPUUSAGE

BUFPREADS

BUFPWRITES

BUFQUAL

BUFSIZE

BUFWAITS

BUFWTIME

DICTSIZE

DDQUAL

LOGBLOCKS

LOGENTRIES

LOGSIZE

LOGFAULT

R64

I32

I32

R64

I32

I32

I32

I32

R64

I32

I32

I32

R64


Aspect Name


MetricData Type

LOGALLOC

ROLLBACKS

SCANLONG

SORTDISK

SORTMEM

SORTROWS

HOSTNAME_DBINFO

SID_DBINFO

INSTANCE_DBINFO

KEY_DBINFO

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

DOCSTAT_PERF

APPMODE_DOC

CNTHEADER

CNTITEM

CNTDIV

CNTTOTAL

CNTLINE

CNTCHGDOC

CNTTEXT

HOSTNAME_DOCSTAT

SID_DOCSTAT

INSTANCE_DOCSTAT

KEY_DOCSTAT

UTF8

I32

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

EP_PERF SID_EP

HOSTNAME_EP

START_TIME_EP

NO_REQ_EP

UTF8

UTF8

UTF8

I32

User GuideAppendix: Metrics and Datasources


Aspect Name


MetricData Type

AVG_RESP_TIME_EP

AVG_CPU_TIME_EP

REQ_PER_SEC_EP

AVG_OUTBND_DATA_EP

ACC_RESP_TIME_EP

ACC_CPU_TIME_EP

OUTBND_DATA_REQ_EP

ACC_OUTBND_DATA_EP

NO_COMPCALLS_REQ_EP

AVG_CMPCALLPERREQ_EP

VALID_MONDATA_REQ_EP

REQ_NOT_CORR_CLSD_EP

REQCLSD_TOOMNYCMP_EP

REQS_RUNLEVEL_0_EP

REQS_RUNLEVEL_1_EP

REQS_RUNLEVEL_2_EP

USRS_SINCE_1_REQ_EP

USRS_SINCE_

R64

R64

I32

I32

R64

R64

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8



Aspect Name


MetricData Type

LSTRST_EP

LST_REQ_RST_TSTMP_EP

LST_CMPREQ_TSTMP_EP

LST_USRREQ_TSTMP_EP


SAPABAP_PerfMon

ICMSTAT_PERF

ICM_STATUS

MAX_THREADS

PEAK_THREADS

CUR_THREADS

MAX_CONNECTIONS

PEAK_CONNECTIONS

CUR_CONNECTIONS

MAX_QUEUEENTRIES

PEAK_QUEUEENTRIES

CUR_QUEUEENTRIES

RUNNING_THREADS

DEAD_THREADS

PROCESSED_THREADS

HOSTNAME_ICMSTAT

SID_ICMSTAT

INSTANCE_ICMSTAT

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8



Aspect Name


MetricData Type

KEY_ICMSTAT


SAPABAP_PerfMon

JOBREP_PERF RUNNING

READY

SCHEDULED

RELEASED

ABORTED

FINISHED

PUT_ACTIVE

UNKNOWN_STATE

HOSTNAME_JOBREP

SID_JOBREP

INSTANCE_JOBREP

KEY_JOBREP

UTF8

I32

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

SAPBUFFER_PERF

BUFFER_NAME

HITRATIO

ALLOCATED_SIZE

FREE_SPACE

FREE_SPACE_PERCENT

MAXDIR_ENTR

FREEDIR_ENTR

FDIR_ENTR_PERCENT

BUFFER_SWAPS

BUFFER_SWAPS_DELTA

DB_ACCESSES

DB_ACCESSES_

UTF8

R64

I32

I32

R64

I32

I32

R64

I32

I32

I32

I32

UTF8

UTF8



Aspect Name


MetricData Type

DELTA

HOSTNAME_SAPBUFFER

SID_SAPBUFFER

INSTANCE_SAPBUFFER

KEY_SAPBUFFER

UTF8

UTF8


SAPABAP_PerfMon

SAPMEMORY_PERF

MEMORY_AREA

CURRENT_USE_PERCENT

CURRENT_USE

MAX_USE

IN_MEMORY

ON_DISK

HOSTNAME_SAPMEMORY

SID_SAPMEMORY

INSTANCE_SAPMEMORY

KEY_SAPMEMORY

UTF8

R64

I32

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

SPOOL_PERF ALL_SJ

SJ_ARCHIVE

PRINT_REQ

OPEN_PR

SUCCESS_PR

ERROR_PR

FAILED_PR

HOSTNAME_SPOOL

SID_SPOOL

I32

I32

I32

I32

I32

I32

I32

UTF8

UTF8

UTF8



Aspect Name


MetricData Type

INSTANCE_SPOOL

KEY_SPOOL

UTF8


SAPABAP_PerfMon

SAP_STATRECS_PERF

SAP_TCODE

SAP_RESPONSE_TIME

SAP_NET_TIME

SAP_REC_COUNT

SAP_HOST_STATRECS

SAP_SID_STATRECS

SAP_INSTNO_STATRECS

SAP_KEY_STATRECS

UTF8

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

UPDATE_PERF ALL_TASKS

INITIAL_TASKS

ERRONOUS_TASKS

VB1

V2

HOSTNAME_UPDATE

SID_UPDATE

INSTANCE_UPDATE

KEY_UPDATE

UTF8

I32

I32

I32

I32

UTF8

UTF8

UTF8

UTF8


SAPABAP_PerfMon

USER_PERF USER_CLIENT

USER_CNT

SESSION_CNT

HOSTNAME_USER

UTF8

I32

I32

UTF8



Aspect Name


MetricData Type

SID_USER

INSTANCE_USER

KEY_USER

UTF8

UTF8

UTF8


SAPABAP_PerfMon

SAP_WLSUM_PERF

SAP_HOSTNAME _WLSUM

SAP_SID_WLSUM

SAP_INSTANCE_WLSUM

SAP_KEY_WLSUM

SAP_TASKTYPE

SAP_CNT

SAP_DBACTIVCNT

SAP_RESPTI

SAP_CPUTI

SAP_QUEUETI

SAP_LOADGENTI

SAP_COMMITTI

SAP_DDICTI

SAP_QUETI

SAP_CPICTI

SAP_ROLLINCNT

SAP_ROLLINTI

SAP_ROLLOUTCNT

SAP_ROLLOUTTI

SAP_READDIRCNT

SAP_READDIRTI

SAP_READSEQCNT

SAP_READSEQTI

UTF8

UTF8

UTF8

UTF8

UTF8

I32

I32

R64

R64

R64

R64

R64

R64

R64

R64

I32

R64

I32

R64

I32

R64

I32

R64

I32

R64



Aspect Name


MetricData Type

SAP_CHNGCNT

SAP_CHNGTI

SAP_BYTES

SAP_GUITIME

SAP_GUICNT

SAP_GUINETTIME

I32

R64

I32

R64


SAPABAP_PerfMon

WP_PERF ALL_WP

SEMAPHORE_WP

DEBUG_WP

LONG_RUNNING

PRIVAT_WP

NOSTART_WP

DIA_IDLE

DIA_ALL

DIA_RUNNING

BTC_IDLE

BT_ALL

BTC_RUNNING

SPO_IDLE

SPO_ALL

SPO_RUNNING

ENQ_IDLE

ENQ_ALL

ENQ_RUNNING

UPD_IDLE

UPD_ALL

UPD_RUNNING

UPD2_IDLE

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32

I32



Aspect Name


MetricData Type

UPD2_ALL

UPD2_RUNNING

HOSTNAME_WP

SID_WP

INSTANCE_WP

KEY_WP

I32

I32

UTF8

UTF8

UTF8

UTF8

SYSUP_PERF SYSTEM_STATUS

HOSTNAME_SYSUP

SID_SYSUP

INSTANCE_SYSUP

KEY_SYSUP

UTF8

UTF8

UTF8

UTF8

UTF8

Note: The default frequency of the SYSUP_PERF availability monitor is oneminute and the valuecannot be changed.

SAP J2EE Application Server

TheOMi MP for SAP creates the following data store table to log the data collected by metrics fromSAP J2EE Application Server:

Note: SAPSPINW_RPT_METRICS is the Datasource and table used by SAP J2EE Application ServerPolicy Templates for logging the collected data.

Table Name Metric Name Metric Data Type

SAPSPINW_RPT_METRICS METRICID

VALUEID

VALUE

SORTID

SERVERNAME

OBJECTNAME

I32

I32

R64

UTF8

UTF8

UTF8



Send documentation feedbackIf you have comments about this document, you can contact the documentation team by email. If anemail client is configured on this system, click the link above and an email window opens with thefollowing information in the subject line:

Feedback on User Guide (OMi Management Pack for SAP 1.00)

Just add your feedback to the email and click send.

If no email client is available, copy the information above to a new message in a webmail client, andsend your feedback to [email protected].

We appreciate your feedback!


mailto:[email protected]?subject=Feedback on User Guide (OMi Management Pack for SAP 1.00)

omi management pack for sap -1.00 - user guide ep_perf 153 icmstat_perf 155 jobrep_perf 156...

Documents