WebLogic JTA Test
This test reports transaction-related statistics for a WebLogic server.
Target of the test : A WebLogic Application Server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every WebLogic server monitored.
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the host for which this test is to be configured. |
|
Port |
The port at which the specified host listens. By default, this is NULL. |
|
UseWarFile |
This flag indicates whether/not monitoring is to be done using a Web archive file deployed on the WebLogic server (in which case, HTTP/HTTPS is used by the server to connect to the server). If this flag is set to No, the agent directly connects to the WebLogic server using the T3 protocol (no other file needs to be deployed on the WebLogic server for this to work). Note that the T3 protocol-based support is available for WebLogic servers ver.9 and above. Also, if the UseWarFile parameter is set to No, make sure that the EncryptPass parameter is set to No as well. When monitoring a WebLogic server deployed on a Unix platform particularly, if the UseWarFile parameter is set to No, you have to make sure that the eG agent install user is added to the WebLogic users group. |
|
AdminServerHost and AdminServerPort |
In some highly secured environments, the eG agent may not be able to collect certain critical metrics related to JDBC from a managed WebLogic server. In such cases, to enable the eG agent to collect the required metrics, you should specify the IP address and Port of the WebLogic admin server to which the managed WebLogic server is associated with. This will enable the eG agent to connect to the WebLogic admin server and collect the required metrics pertaining to the managed WebLogic server. Specify the IP address and Port of the WebLogic admin server in the AdminServerHost and AdminServerPort text boxes. By default, these parameters are set to none. |
|
JSPTimeOut |
Specify the duration (in seconds) within which the eG agent should receive the response from the eGurkha WAR file deployed on the WebLogic server in this text box. By default, this is set to is 120 seconds. |
|
User |
The admin user name of the WebLogic server being monitored. |
|
Password |
The password of the specified admin user. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
EncryptPass |
If the specified password needs to be encrypted, set the EncryptPass flag to Yes. Otherwise, set it to No. By default, the Yes option will be selected. Note: If the UseWarFile flag is set to No, then make sure that the EncryptPass flag is also set to No. |
|
SSL |
Indicate whether the SSL (Secured Socket Layer) is to be used to connect to the WebLogic server. |
|
Server |
The name of the specific server instance to be monitored for a WebLogic server (the default value is "localhome") |
|
URL |
The URL to be accessed to collect metrics pertaining to the WebLogic server. By default, this test connects to a managed WebLogic server and attempts to obtain the metrics of interest by accessing the local Mbeans of the server. This parameter can be changed to a value of http://<adminserverIP>:<adminserverPort>. In this case, the test connects to the WebLogic admin server to collect metrics pertaining to the managed server (specified by the Host and Port). The URL setting provides the administrator with the flexibility of determining the WebLogic monitoring configuration to use. Note: If the admin server is to be used for collecting measures for all the managed WebLogic servers, then it is mandatory that the egurkha war file is deployed to the admin server, and it is up and running. |
|
Version |
The Version text box indicates the version of the Weblogic server to be managed. The default value is "none", in which case the test auto-discovers the weblogic version. If the value of this parameter is not "none", the test uses the value provided (e.g., 7.0) as the weblogic version (i.e., it does not auto-discover the weblogic server version). This parameter has been added to address cases when the eG agent is not able to discover the WebLogic server version. |
|
WebLogicJARLocation |
Specify the location of the WebLogic server's java archive (Jar) file. If the UseWarFile flag is set to No, then the weblogic.jar file specified here is used to connect to the corresponding WebLogic server using the T3 protocol. Note that the T3 protocol-based support is available for WebLogic servers ver.9 and above. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Total active transactions |
Returns the number of active transactions on the server |
Number |
This metric gives an idea of the server load. |
|
Transaction aborts |
Returns the rate of transactions that were abandoned |
Trans/Sec |
Typically, the abandoned transaction rate should be low. |
|
Application rollbacks |
Returns the rate of transactions that were rolled back due to an application error |
Trans/Sec |
Rollbacks can occur due to various reasons. Correlate the rollbacks on the application server with that on the database to isolate the cause of the rollbacks. |
|
Resource rollbacks |
Returns the rate of transactions that were rolled back due to a resource error |
Trans/Sec |
|
|
System rollbacks |
Returns the rate of transactions that were rolled back due to an internal system error |
Trans/Sec |
|
|
Rollback timeouts |
Returns the rate of transactions that were rolled back due to a timeout expiration |
Trans/Sec |
|
|
Commits |
Returns the rate of committed transactions |
Trans/Sec |
|
|
Heuristic transactions |
Returns the rate of transactions that completed with a heuristic status |
Trans/Sec |
|
|
Total rollbacks |
Returns the rate of transactions that were rolled back |
Trans/Sec |
A high value (rate) here would mean that more number of transactions are being rolled back. |
|
Total transactions |
Returns the total rate of transactions processed. This total includes all committed, rolled back and heuristic transaction completions |
Trans/Sec |
|
