SAP WAS Standalone Connector Services Test

SAP provides a set of standalone connectors that enable you to connect SAP NetWeaver to different types of non-SAP systems.

In particular, the following core connectors are available:

• SAP Business Connector (SAP BC)

• SAP Java Connector (SAP JCo)

• SAP .Net Connector (SAP NCo)

• SAP NetWeaver RFC Library (SAP NW RFC SDK)

Often, administrators find it difficult to identify those connectors that are overloaded i.e., from which maximum managed connections are already utilized and clients are waiting for connections through the connectors. To help administrators identify those connectors, eG Enterprise offers the SAP WAS Standalone Connector Services test.

This test auto-discovers the standlone connectors in the target environment, and for each connector, reports the number of connection that are already utilized and those that are available for use. Besides, this test points out to the count of clients waiting for a connection through each connector. This way, administrators can identify the connector that is overloaded and is most popular to connect to.

Target of the test : A SAP Web Application Server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each standalone connector connected to the target SAP Web AS.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	Specify the server for which the test is to be configured.
Port	The port number at which the specified server listens.
UserName	This test connects to a specific SAP web application server instance, and extracts critical metrics from it. Therefore, in the UserName text box, provide a valid j2ee admin user name which the test should use for connecting to the server instance.
Password	Provide the Password that corresponds to the specified UserName.
Confirm Password	Confirm the OS Password by retyping it here.
InstanceName	Provide the name of the application server instance to which the test should connect. For example, if you specify tpp here, then the test will use the login credentials (UserName and Password) provided here to connect to an instance named TPP. To know the available server instances, use the instructions provided in Determining the Name of the SAP Web AS Instance.
ConnectorPort	This test uses the P4 protocol for connecting to the SAP web application server. Therefore, the port at which the P4 protocol listens needs to be specified as the ConnectorPort. To know how to determine the P4 port, use the procedure detailed in Determining the P4 Port.
DispatcherID	This test reports a set of metrics for the Java dispatcher that receives client requests. By default, the cluster ID  of the dispatcher is auto-discovered by the eG Enterprise. Therefore, default option is specified against this parameter. Alternately, if you wish to monitor a specific cluster ID, then you can mention that cluster ID against this parameter. To know the cluster ID of the dispatcher, follow the steps discussed in Determining the Name of the SAP Web AS Instance and P4 Protocol Port .
ServerIDs	Typically, the Java dispatcher or the ICM distributes the client requests it receives to the server processes executing on the Java component of the SAP Web AS for processing.  By default, the ServerIDs are auto-discovered by the eG Enterprise. To monitor specific server processes, specify a comma-separated list of the cluster IDs of these server processes in the ServerIDs text box. To know the cluster IDs of the server processes, follow the procedure detailed in Determining the Name of the SAP Web AS Instance and P4 Protocol Port. Providing a comma-separated list of server process cluster IDs will ensure that these cluster IDs alone appear as the descriptors of the test. If need be, you can have server process name-cluster ID pairs appear as the test descriptors. To achieve this, the specification in the ServerIDs text box should be of the following format: Server process name:Cluster ID of the server process. For example, if the cluster ID of a server process named Server0 is 12621850, then you can specify the ServerID in the format: Server0:12621850.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Free connections	Indicates the number of managed connections of this connector that are currently available.	Number
Used connections	Indicates the number of managed connections of this connector that are already in use.	Number	This measure is a good indicator of load on the standalone connector. A high value for this measure indicates that that the managed connection reserve is dwindling and the requests had to wait for a longer duration for a connection. Compare the value of this measure across connectors to identify the connector that is overloaded.
Maximum connections	Indicates the maximum number of connections available in the connection pool to connect to this connector.	Number
Connection usage	Indicates the percentage of managed connections that are already in use for this connector.	Percent	A value close to 100% indicates that the managed connections are exhanusted adn that the requests had to wait for a longer duration for want of a connection.
Connection request timeout rate	Indicates the number of requests for a managed connection to connect to this connector that timedout per minute.	Requests/minute	A low value is desired for this measure.
Clients waiting for connection	Indicates the number of clients waiting for a managed connection to connect to this connector.	Number