WebLogic Health of Running Servers Test

WebLogic Server provides a self-health monitoring feature to improve the reliability and availability of server instances in a domain. Selected subsystems within each server instance monitor their health status based on criteria specific to the subsystem. If an individual subsystem determines that it can no longer operate in a consistent and reliable manner, it registers its health state as "failed" with the host server instance.

Each server instance checks the health state of all its registered subsystems to determine the overall viability of the server. If one or more critical subsystems have reached the "failed" state, the server instance marks its own health state as "failed" to indicate that it cannot reliably host an application. Using the WebLogic Health of Running Servers test, the administrators can figure out the number heath issues caused to the server based on warning, critical, failed and overloaded statuses and provide the appropriate remedial measures.

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.

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

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
OK	Indicates the number of Weblogic servers with health status showing as OK.	Number	The OK status represents the server service is healthy. Use the detailed diagnosis of this measure to know the Weblogic server name.
Warning	Indicates the number of Weblogic servers with health status showing as Warning.	Number	The Warning status denotes the server service could face problems in the future.
Overloaded	Indicates the number of Weblogic servers with health status showing as Overloaded.	Number	The Overloaded status shows the server service is functioning normally but there is too much work in it.
Critical	Indicates the number of Weblogic servers with health status showing as Critical.	Number	The Critical status denotes that some activities to be performed to prevent service failure.
Failed	Indicates the number of Weblogic servers with health status showing as Failed.	Number	The Failed status denotes that the service has failed and it should be restarted.