|
Default
Parameters for P4UsageTest
The P4UsageTest measures the capability of the P4 Provider Service (which provides functions for the communication of remote objects over the P4 protocol on the J2EE Engine) in handling P4 requests. This page depicts the default parameters that need to be configured for the P4UsageTest.
-
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 user name which the test should use for connecting to the server instance.
-
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.
-
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.
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.
When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.
|