Event linkages Test

The type linkage describes the assignment of a receiver function module and a receiver type to a particular combination of object type and event.

A type linkage must be created if the system is always to react to an event of a particular object type. The type linkages are evaluated at runtime by the event manager.

The event receiver should define a type linkage using a function module provided.

Type linkages are client-dependent and are written automatically into a Customizing transport request if the client is configured (in table T000 ) for changes to be recorded automatically. All entries are then transported including activation indicators.

In the case of client copy, you should ensure that the type linkages are copied into the target client, but are always deactivated in the target client. The activation indicator of each individual type linkage is only copied with client copy if explicitly requested (parameter option for copying tables of class A).

The event manager begins the evaluation of the active type linkages when it is notified of the ID of a created event. For event handling to take place, either the event created and its triggering object type or the event created and a supertype of the triggering object type must be entered for the type linkage.

An appropriate workflow is always started as a reaction to an event of a particular object type. Whenever workflow start is delayed or there is a sudden decrease in the number of workflows that are started, then the administrators may need to analyze the real cause behind such delays! Usually such delays are caused when the event linkages are inactive and when errors are detected in the event linkages. Therefore it becomes essential to monitor the event linkages and keep a constant vigil on the number of inactive linkages and the number of linkages with errors. The Event linkages test helps you in this regard.

This test monitors the event linkages and helps you figure out how many linkages are available on the server and how many are currently active/inactive on the server. In addition, this test helps the administrators identify the number of event linkages with errors and figure out the real reason behind such errors.

Target of the test : A SAP ABAP instance

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed

Host

Host name of the server for which the test is to be configured.

PortNo

Enter the port to which the specified host listens.

ClientName

Specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.

SAPUser

Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.

Password

The password of the specified SAPUser.

Confirm Password

Confirm the password by retyping it here.

SysNo

An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SysNo will have to be specified as ‘01’. Therefore, in the SysNo text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.

Router

If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the Router text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.

InstanceName

This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time. 

Timeout

Indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.

JCO Version

The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO Version – in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x. 

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency. 

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Total linkages

Indicates the number of type linkages defined on the server.

Number

 

Active linkages

Indicates the type linkages that are currently activated on the server.

Number

 

Inactive linkages

Indicates the number of type linkages that are currently inactive on the server.

Number

The event receivers will respond to events only when the type linkages are active.

The detailed diagnosis of this measure if enabled, lists the linkage details such as the Client, Business object, event description, receiver type, receiver function modules, error linkage etc.

Percentage of linkages that are inactive

Indicates the percentage of type linkages that were inactive.

Percent

A low value is desired for this measure.

Error linkages

Indicates the number of type linkages with errors.

Number

Receivers will immediately respond to events only if the event linkage is active is without any errors. Active linkages with errors result in the event being queued with error status and these linkages have to be reprocessed manually, if needed.

Ideally, the value of this measure should be zero. If the value of this measure is abnormally high, then it indicates that there are too many errors in the linkages which eventually results in the delay in processing and lead to a delayed response to the events by the receivers.

The detailed diagnosis of this measure if enabled, lists the corresponding type linkage details such as Client, Business object type, event description, receiver type, receiver function modules, error linkage etc.

Percentage of linkages with errors

Indicates the percentage of type linkages with errors.

Number

A high value for this measure is a cause of concern.