WebLogic EJBs Test

This test monitors the state of EJB component groups hosted on a WebLogic server 6.0 or higher using JMX. This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle WebLogic as the desired Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Use the Click here hyperlink in the test configuration page to configure the EJB groups that need to be monitored by the eG Enterprise suite. Note that the eG Enterprise system monitors only those EJBs that are part of a group.

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 EJB group configured.

Configurable parameters for the test
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.

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.

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.

WeblLgicJARLocation

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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Transaction commit rate

Indicates the rate at which transactions are committed for a particular bean.

Trans/Sec

Comparing this value across all the deployed beans can give an idea of the relative importance of the beans in supporting user accesses. A sudden change in user access patterns can be indicative of a change in the user workload.

Transaction rollback rate

Indicates the rate at which the transactions are rolled back for a particular bean.

Trans/Sec

A high rollback rate indicates a problem with specific beans. Possible reasons for this could be problems with the design and implementation of the specific bean or problems with any of the dependent servers of the bean (e.g., database server).

Transactions inflight

Number of transactions currently in progress through a particular bean.

Number

A significantly high value may denote a load on the specific bean. This may indicate that specific transactions are taking too long to process requests.

Num waiting rate

This measure corresponds to only stateless session bean. This indicates the rate at which connections are established by the client with the instances of the bean.

Conns/Sec

A high value signifies that it is taking more time for the clients to access an instance of the bean from the pool.

Timeout rate

This measure also corresponds to the stateless session beans. The measure indicates the rate at which instances are timed out by the bean.

Conns/Sec

A high value indicates a problem with a specific bean. Again, the problem can be specific to the bean implementation or with any of the dependent servers of the bean.

Idle bean percent

The percentage of beans those are idle in the cache.

Percent

A high percentage indicates a memory bottleneck. The timeout of the session beans could be one of the possible reasons.