Configuration of DeploymentStatusTest

For each WAR/JAR file deployed on the target WildFly JBoss server, this test reports the current deployment status. In addition, this test also reports whether/not each WAR/JAR file is enabled and the deployment is managed or not. This way, the test helps administrators to be forewarned on any unpredicted issues before it hits the application performance.

The default parameters associated with this test are:

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

• Specify he host for which the test is to be configured in the HOST text box..

• Specify the port to which the specified host listens in the PORT text box. By default, this is 9990.

• If the WildFly JBoss server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No.

• Specify whether the server to be monitored is currently running in Domain Mode or not in the IS JBOSS RUNNING IN DOMAIN MODE? parameter. By default, this flag is set to No which implies that the server is currently running in Standalone Mode. If you have started the target JBoss server using the default web profile configuration in domain mode i.e, if you have executed the ./domain.sh command from the <JBoss_INSTALL_DIR>/bin directory, then specify Yes against this flag.

• Specify whether the target server to be monitored is a master or a slave in a JBoss cluster in the JBOSS HOST NAME parameter. By default, none will be specified here which implies that the target JBoss server is a standalone server. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to know how to identify whether the target server is a master or slave in your environment.

• Specify the name of the server instance that is to be monitored in JBOSS SERVER INSTANCE NAME text box. By default, none will be specified here. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to identify the name of the server instance that is to be monitored.

• Specify the credentials of the user who is authorized to access the management console of the target JBoss server in the MANAGEMENT USER and MANAGEMENT PASSWORD text box. To create a new user, refer to Creating a new management user in the WildFly JBoss server of this document.

• Confirm the Management Password by retyping it in the CONFIRM PASSWORD textbox.

• To make diagnosis more efficient and accurate, eG 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, by default, 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.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button 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.