The WLEJBTransTest reports measures related to the EJB transaction activity performed by the WebLogic server. This page appears by clicking the CONFIGURE / COMPONENT button corresponding to the WLEJBTransTest in the CONFIGURE TESTS page. Here, the discovered WebLogic servers that need to be configured are available in the COMPONENTS WITH DEFAULT CONFIGURATION section. Select the required server from this box and click the CONFIGURE button at the bottom to configure the parameters pertaining to this test. The default parameters associated with this will be displayed at the bottom of this page.

• The TESTPERIOD 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 textbox.

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

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

• To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• The VERSION textbox 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.

• 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 and the selected server will move over to the CONFIGURED COMPONENTS panel.

• The test parameters for an already configured server can be reconfigured using the RECONFIGURE button. The parameter configuration page reappears and the required changes can be made to the existing values of the parameters.

• If the test under consideration is not to be executed for any of the configured servers, they can be removed from the list using the EXCLUDE button doing which will move the server to the EXCLUDED COMPONENTS panel.

• Clicking on the INCLUDE button in this panel will add the excluded server to the list of servers to be configured.

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.

The << button enables the user to go back to the previous screen.