Knowledge Base > Automation Engine and Target Systems > SAP > Monitoring Monitors

Monitoring Monitors

SAP offers various monitors that can be used to monitor the SAP environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. including corresponding components. The functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… R3_GET_MONITOR reads the provided information and makes it available for further processing.

The following example reads the monitor "All Monitoring Contexts" and stores its content to a text file:

R3_GET_MONITOR MONITOR_SET="SAP CCMS Technical Expert Monitors", MONITOR="All Monitoring Contexts", FILE="C:\UC4_and_SAP\AllMonitoringContexts.txt"

Use the scriptA particular Automation Engine object type. function PREP_PROCESS if only parts of the monitored information should be filtered. Based on these filter specifications, the script function supplies a data sequenceAn internal listing of Console outputs or lines of Variable objects, etc. The lines of a data sequence can be accessed by using a PROCESS loop or the script element GET_PROCESS_LINE. The script elements PREP_PROCESS* generate data sequences. which can then be processed. The SAP agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host lists the monitor's information in columns. The following example filters lines with the content "Enqueue". Four columns are used for further processing:

:SET &HND# = PREP_PROCESS("SAP01","R3MONITOR","*Enqueue*","MONSET=SAP CCMS Technical Expert Monitors","MONNAM=All Monitoring Contexts","COL=FILE","UC_LOGIN=LOGIN.SAP")

:PROCESS &HND#
:   
SET &Context# = GET_PROCESS_LINE(&HND#, CONTEXT)
:   
SET &Name# = GET_PROCESS_LINE(&HND#, NAME)
:   
SET &Value# = GET_PROCESS_LINE(&HND#, VALUE)
:   
SET &Status# = GET_PROCESS_LINE(&HND#, STATUS)
:   
PRINT "&Context# --- &Name#"
:   
PRINT "Value: &Value#"
:   
PRINT "Status: &Status#"
:   
PRINT ""
:
ENDPROCESS

The above example calls the function R3_GET_MONITOR in the background. Refer to the document that describes the script function PREP_PROCESS for more detailed information.

The RemoteTaskManagerIt monitors and controls external Jobs that were not started by the Automation Engine (AE). An AE object type. [Formerly called "QueueManager."] objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task also provides monitoring functions in the SAP system. Depending on the specified filter criteria, it displays jobs triggered by SAP.

AE JCL for SAP

Script Element

Description

R3_GET_MONITOR

Reads the data of a SAP monitor

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH