Agents Administration - Tests
 

Configuration of WebLogicEjbTest

This test monitors the state of EJB component groups hosted on a WebLogic server 6.0 or higher using JMX.

Use the Click here hyperlink in this page to configure the EJB groups to be monitored. Note that the eG system monitors only those EJBs that belong to an EJB group. The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

  • The port number to which the selected WebLogic server 6.0 or higher is listening to has to be specified in the PORT text box.

  • The USER text box, indicates the admin user name of the WebLogic server 6.0 or higher being monitored.

  • The PASSWORD text box, indicates the password of the specified admin user.

  • Confirm the password by retyping it in the CONFIRM PASSWORD text box. 

  • 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.

  • Select Yes if SSL (Secured Socket Layer) is to be used to connect to the WebLogic server, and No if it is not. 

  • In the SERVER text box, specify the name of the specific server instance to be monitored for the WebLogic server. The default value is localhome.

  • In the URL text box, specify 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. 

  • The USEWARFILE flag indicates whether 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.

  • In the WEBLOGICJARLOCATION text box, 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.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, any parameter value that is prefixed with a "$" symbol signifies that this value has to be manually configured by the user. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.

Note:

The eG system monitors only those EJB components that are part of an EJB group. To create EJB groups and add components to them, click on the Click here hyperlink present just above the Test Parameters section of this page.