Pre-requisites for Monitoring Swift AMH JBoss

Swift AMH is setup on WildFly JBoss, so AMH monitoring includes WildFly JBoss monitoring as well. Before attempting to manage and monitor Swift AMH 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. To know the type of user required for this purpose and how to create such a user, refer to Creating a new Management/Application user in the WildFly JBoss server topic.

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

• By default, the eG agent cannot perform Java business transaction monitoring on a WildFly JBoss server. For that, you need to enable the eG Java Business Transaction Monitor (BTM) on the WildFly JBoss server. To know how to achieve this, refer to Installing eG Java BTM on WildFly JBoss server / JBoss AS EAP server topic.