This page depicts the default parameters that need to be configured for the WLDFServerDiagnostic_cf.

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

• The USER text box, indicates the admin user name of the WebLogic server 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.

• Specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 seconds.

• 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 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 ver. 10 only.

• 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 ver. 10 only.

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

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. e.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.