Agents Administration - Tests
 

Configuration of WLEJBCacheTest

To improve the performance and the scalability of the EJB container, WebLogic server caches EJBs. The WLEJBCacheTest test collects measures related to EJB caching activity by the WebLogic server. 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 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. 

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

  • WebLogic version 8.0 and above prefixes the names of the EJBs it hosts, with the server name specified in the SERVER text box. For example, if the SERVER text box contains MedRecServer, then an EJB named MedRecEAR_EntityEJB_PatientEJB on that server will be renamed by WebLogic as MedRecServer_MedRecEAR_EntityEJB_PatientEJB. This could pose a challenge while applying EJB groups configured (using eG) on a particular WebLogic server to another server. This is because, when the eG suite lists the EJBs available for grouping, each of the displayed EJBs will be prefixed by the corresponding SERVER name. When such EJBs are grouped and the group is then applied to another WebLogic server, the eG system will not be able to extract metrics for the EJB grouping applied to the new server due to the server name mismatch. Therefore, by default, the eG system sets the SHOWSERVERNAME flag to No. This ensures that the server name specified in the SERVER text box does not prefix the EJB listing during EJB group configuration. To enable the prefix, select the Yes option against SHOWSERVERNAME.

    Note:

    If you modify the SHOWSERVERNAME setting after configuring the EJB groups, then wait for the test to run once so that the eG agent rediscovers the EJBs on that server. Then, delete the existing EJB groups, and repeat the group configuration.

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

  • By default, the eG suite allows administrators to configure EJB groups using the eG administrative interface, and reports metrics pertaining to every group so created. Accordingly, by default, AUTODISCOVERY is set to NO. If you want EJBs to be discovered and monitored automatically, then select the YES option against AUTODISCOVERY. When this is done, the eG agent automatically discovers all the EJBs on the WebLogic server, and reports one set of measures for every EJB hosted on the server.

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