Gateways Test
The SAP Gateway carries out CPI-C services within the SAP world, which are based on TCP/IP. These services enable SAP systems and external programs to communicate with one another. As RFC is based on CPI-C, all RFC connections also pass through the SAP Gateway. This test reports statistics pertaining to this SAP gateway.
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 the SAP ABAP instance being monitored.
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 |
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. |
IsPassive |
If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP INSTANCE cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Gateway clients |
The number of gateway clients who are currently connected to the SAP server, expressed as a percentage of the maximum number of gateway clients allowed. |
Percent |
For example, if the gateway can administrate 300 clients, and there are currently 30 clients logged on to the gateway, the value is 10%. If the value is near 100%, the maximum number of clients can be changed using the profile parameter gw/max_sys. |
Gateway connections utilized |
The number of gateway connections currently utilized, expressed as a percentage of the maximum number of gateway connections allowed. |
Percent |
|
Remote gateways |
Of the total number of gateways, what percentage is consumed by remote gateways. |
Percent |
If the value is near 100%, the maximum number of gateways can be changed using the profile parameter rdisp/max_gateways. To administrate gateway connections, call transaction SMGW on the server in question. |
Gateway admin entries |
Of the maximum number of gateway admin entries that are allowed, what percentage is being currently utilized. |
Percent |
If the value is near 100%, the maximum number of entries can be changed using the profile parameter rdisp/max_comm_entries. |
Gateway work processes |
Of the maximum number of gateway work processes allowed, what percentage is being used currently. |
Percent |
If a value is near 100%, the maximum number of work processes can be changed using the profile parameter gw/max_wp. |
Gateway overflow usage |
Of the total gateway size, what percentage of gateway overflow has been used. |
Percent |
If a value is near 100%, the maximum overflow size can be changed using the profile parameter gw/max_overflow_size. |