Status
Panel | |
---|---|
|
Disclaimer
...
Template Name | Version | Notes | ||
---|---|---|---|---|
CS SAP Event History Monitor | 2.1.7 |
|
Refer to Changelog for version history information.
Software Requirements
Software Requirements for Universal Agent
...
Fill Out the Universal Task for each SAP Event and Parameter to monitor.
Field | Description | |||||
Agent | Linux or Windows Universal Agent to run the USAP commands. | |||||
Agent Cluster | Optional Agent Cluster for load balancing. | |||||
SAP Connection Type | [ Application Server Connection, SAPNWRFC.INI Connection ] The Universal Task support SAP Application Server and SAPNWRFC.INI Destination connections. Application Server Connection:
SAPNWRFC.INI Connection:
| |||||
SAP ASHOST | SAP Application to connect to. This field is visible only if SAP Connection Type = “Application Server Connection” | |||||
SAP CLIENT | SAP Client ( 3 digits ); for example, 100 The Imported calendar will have the SID as prefix Imported Calendar Name: <SID>_<SAP CLIENT>_<SAP CALENDAR ID> | |||||
SAP SysNr | SAP System Number ( 2 digits ) e.g. 00 This field is visible only if SAP Connection Type = “Application Server Connection” | |||||
SAP Destination | SAP Destination in the nwrfc.ini. This field is visible only if SAP Connection Type = “NRFW.ini Connection” | |||||
USAP Dir | Directory where the USAP binary is stored Linux: /opt/universal/usap/bin Windows: C:\Program Files\Universal\USap\bin | |||||
Event ID | Name of the Event to Scan for in the SAP Event History Table. | |||||
Event Parameter | Name of the parameter to scan for. Note: wildcard “*” is supported ; for example, ua* searches for all event parameters beginning with ua. to scan for any Event Parameter, enter “*”. “*” also matches if no Event Parameter is provided in SM62. | |||||
Event Status to Select | [ New, Confirmed, Any Status ]
| |||||
Universal Controller URL | Universal Controller URL. For example, https://192.168.88.40/uc | |||||
Task(s) | Name of the tasks to start in case a new event has been identified. Multiple tasks are separated by a Comma. e.g., FINANCE_REPORT1, FINANCE_REPORT2, FINANCE_REPORT3 If no task is specified, the UT runs in monitoring mode and goes to success in case an Event has been identified; for example, you can add the Event Monitor to a Workflow.(Note: In that case, remove the action, which automatically re-starts the UT in if status is “success”) | |||||
Confirm Events | [ Confirm , New ] Default is “Confirm”. Confirm: This ensures that the same event only triggers the event monitor once. New: Leaves the event in status “New”, mainly for testing purpose. | |||||
USAP loglevel | Log level of the Universal Connector for SAP trace | audit | info | warn | error | |||||
rfc_logon_retry_interval in s | interval in seconds between an new logon attempt to SAP. Per default, 10 retries will be performed; for example, 120s means every 120s a new logon attempt to SAP is performed. If after 10 retries no logon to SAP was possible the Task fails. | |||||
Loglevel | Universal Task logging settings [DEBUG | INFO| WARNING | ERROR | CRITICAL] |
Example for SAP Event History Monitor Task
...