JBoss Deployments Test

With Wildfly, you can deploy file types such as EJB-JAR, WAR, EAR, or any kind of standard archive (such as RAR). If the deployment of these files fail or stop then, it can lead to unavailable ,sluggish or stopped applications, decreased throughput and degraded performance. Deployment failures when left unnoticed for a prolonged period may affect the performance of the applications which may directly impact user experience. To ensure that the performance of the applications are on par, it is essential for the administrators to periodically monitor the deployment of the file types in the target WildFly JBoss server. The JBoss Deployments test helps administrators in this regard!

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.

Target of the test : A WildFly JBoss server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each WAR/JAR file on the target WildFly JBoss that is to be monitored.

Configurable parameters for the test

Parameters	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port at which the specified HOST listens. By default, this is 9990.
SSL	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.
Is JBoss Running In Domain Mode?	Specify whether the server to be monitored is currently running in Domain Mode or not. 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.
JBoss Host Name	Specify whether the target server to be monitored is a master or a slave in a JBoss cluster. 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.
JBoss Server Instance Name	Specify the name of the server instance that is to be monitored. 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.
Management User and Management Password	Specify the credentials of the user who is authorized to access the management console of the target JBoss server. To create a new user, refer to Creating a new management user in the WildFly JBoss server of this document.
Confirm Password	Confirm the Management Password by retyping it here.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise suite 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. 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Is deployment managed?	Indicates whether/not the deployment of this WAR/JAR file is managed.		The numeric values that correspond to these measure values are discussed in the table below: Measure Value Numeric Value No 0 Yes 1 Note: This measure reports the Measure Values listed in the table above to indicate whether/not the deployment of the WAR/JAR file is managed. However, in the graph, this measure is indicated using the Numeric Values listed in the table above.
Is deployment enabled?	Indicates whether/not this WAR/JAR file is enabled.		The numeric values that correspond to these measure values are discussed in the table below: Measure Value Numeric Value No 0 Yes 1 Note: This measure reports the Measure Values listed in the table above to indicate whether/not the WAR/JAR file is enabled. However, in the graph, this measure is indicated using the Numeric Values listed in the table above. Use the detailed diagnosis of this measure to identify the enabled timestamp, disabled time stamp, and disabled duration(mins).
Deployment status	Indicates the current deployment status of this WAR/JAR file.		The numeric values that correspond to these measure values are discussed in the table below: Measure Value Numeric Value Running 10 Stopped 20 Failed 30 Unknown 5 Note: This measure reports the Measure Values listed in the table above to indicate the current status of the WAR/JAR file. However, in the graph, this measure is indicated using the Numeric Values listed in the table above. Use the detailed diagnosis of this measure to identify the enabled timestamp, disabled time stamp, and disabled duration(mins).

The detailed diagnosis of Deployment status reveal further details like enabled timestamp, disabled time stamp, and disabled duration (mins):

Figure 1 : Detailed diagnosis of Deployment status measure

The detailed diagnosis of Is deployment enabled? reveal further details like enabled timestamp, disabled time stamp, and disabled duration (mins):

Figure 2 : Detailed diagnosis of Is deployment enabled? measure