|
Configuration of HttpResponsesTest
The HTTP Provider Service represents a server socket that listens for client HTTP connections on the J2EE Engine. It takes care of parsing the URL of the incoming HTTP requests, dispatching them to the correct J2EE Engine's module for processing, and returning the generated responses back to the client. The HTTP Responses test monitors how well the HTTP Provider Service returns each type of response for the HTTP connection requests received from clients.
The default parameters associated with this test are:
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.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.
Provide the name of the application server instance in the INSTANCENAME text box, 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 topic in the Monitoring Sap Web Applications Server document.
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 topic in the Monitoring Sap Web Applications Server document.
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 DISPATCHERID 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 Cluster ID of the J2EE Dispatcher topic in the Monitoring Sap Web Applications Server document.
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 Server IDs topic in the Monitoring Sap Web Applications Server document.
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.
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.
|