Kernel Config Test
This test monitors the Configuration Manager’s interactions with the database. The Configuration Manager enables J2EE Engine modules to store and access data from a relational database management system (RDBMS). It provides properties for configuring a database connection.
Target of the test : A SAP NetWeaver Application Server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each of the Dispatchers and each of the configured server processes of the SAP Web AS.
| 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. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Commit duration |
Indicates the time taken for a commit to take place for data storage in the last measurement period. |
Secs |
|
|
Locked exception ratio |
Indicates the number of database lock exceptions that occurred for every database access in the last measurement period. |
Exceptions/Db_tries |
|
|
Cache hit rate |
Indicates the percentage of time data was retrieved from the database cache in the last measurement period. |
Percent |
Ideally, the ratio of cache hits to database accesses should be high, as direct database accesses are expensive operations. |
|
Db read ratio |
Indicates the number of database reads that occurred for every database access in the last measurement period. |
Reads/Db_tries |
|
|
Db write ratio |
Indicates the number of database writes that occurred for every database access in the last measurement period. |
Writes/Db_tries |
|
