Pre-requisites for Monitoring WildFly JBoss server

Before attempting to manage and monitor WildFly JBoss, make sure that the following pre-requisites are fulfilled:

• Determine the correct port using which the target WildFly JBoss server has to be managed in the eG admin interface. To know what port to use and where to find it, refer to Determining the Port Number for Managing WildFly JBoss Server topic.

• The eG tests have to be configured with the credentials of a special user who is authorized to access the web-based Management Console and remote instances of the Management CLI. The eG agent connects to the target WildFly JBoss server and monitors it using this user's credentials only. If you are monitoring a JBoss server running in standalone mode, you need to provide management user credentials as test parameters and if you are monitoring a JBoss server running in domain mode, you need to provide application user credentials as test parameters in the test configuration page. For creating application/management user, refer to the steps mentioned in Creating a new Management/Application user in the WildFly JBoss server topic.

• To enable the eG agent to collect JVM-related metrics for WildFly JBoss server, make sure the requirements for JVM monitoring detailed in the Configuring JVM Monitoring for a WildFly JBoss Server topic are satisfied.

• By default, WildFly JBoss server is not BTM enabled. To enable eG Java Business Transaction Monitoring, refer to Installing eG Java BTM on WildFly JBoss server / JBoss AS EAP server topic.