Agents Administration - Tests
 

Configuration of JDBCConnPoolTest

This test monitors the usage of the standalone and application portal JDBC connection pools, and accurately pinpoints the connection pool that is being over-utilized and is hence running out of free connections.

The default parameters associated with this test are:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • Specify host name of the server for which the test is to be configured, in the HOST text box.

  • Enter the port to which the specified HOST listens, in the PORT text box.

  • 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.

  • Provide the PASSWORD that corresponds to the specified USERNAME in the PASSWORD text box.

  • Confirm the password by retyping it in the CONFIRM PASSWORD box.

  • In the INSTANCENAME text box, provide 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, which is incidentally the central instance of the SAP web application server. To know the available server instances, use the Programs -> SAP Management Console menu sequence on the application server host, and open the SAP Management Console. In the tree-structure in the left pane of the console, you will find a SAP Systems node. When you expand the SAP Systems node, the available server instances will appear as its sub-nodes. Any one of the displayed instance names can be specified in the INSTANCENAME text box.

  • The SSL parameter appears only if the USE SAPCONTROL flag is set to Yes - i.e., if the test uses the SAPControl web service for collecting measures. Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.

  • 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. The default port number of the P4 protocol is 50004. However, if the P4 protocol listens at a different port in your environment, then specify the exact port number here. To know the P4 protocol port, first open the adminCFG.properties file in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\classes directory. The value specified against the LOGIN_PORT parameter in that file, is the P4 protocol port.

  • In the DISPATCHERID text box, specify the cluster ID of the j2ee dispatcher that needs to be monitored. To know the cluster ID of the dispatcher, do the following:

    • Start the J2EE Engine Visual Administrator tool by executing the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go.bat at the command prompt, if you use a Windows platform. If you use a Unix platform, execute the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go at the command prompt.

    • Login to the J2EE Engine Visual Administrator using a valid user name and password.

    • Proceed to the Global Configuration tab that appears in the left panel of the Visual Administrator.

    • Upon clicking on the Dispatcher node, the information pertaining to that dispatcher will appear in the right panel.

    • Pick the cluster ID that is displayed in that panel and specify in the DISPATCHERID text box.

  • Specify the cluster IDs of the servers that need to be monitored in the SERVERIDS text box, as a comma separated list. To know the cluster ID of the servers, do the following:

    • Start the J2EE Engine Visual Administrator tool by executing the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go.bat at the command prompt, if you use a Windows platform. If you use a Unix platform, execute the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go at the command prompt.

    • Login to the J2EE Engine Visual Administrator using a valid user name and password.

    • Proceed to the Global Configuration tab that appears in the left panel of the Visual Administrator.

    • A list of servers will appear in the left panel of the Visual Administrator. Upon clicking on a particular Server node, the information pertaining to that server, including its cluster ID, will appear in the right panel.

    • This way, you can determine the cluster ID of each of the servers to be monitored. Specify these cluster IDs as a comma-separated list in the SERVERIDS text box.

    Providing a comma-separated list of cluster IDs will ensure that these cluster IDs alone appear as the descriptors of the test. If need be, you can have server 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 name:Cluster ID of the server. For example, if the cluster ID of a server named Server0 is 12621850, then you can specify the SERVERID in the format: Server0:12621850.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.