How does eG Enterprise Monitor Swift AMH Node?

eG Enterprise monitors the SWIFT AMH Node in both agent-based and agentless manners. However, eG Enterprise recommends the agent -based approach for monitoring the target AMH node. For this purpose, you need to deploy an eG agent in the target node for monitoring the connectivity, availability, and metrics related to physical and logical nodes, queues, services, etc. To monitor the AMH node, a set of pre-requisites explained in the following section should be fulfilled first.

Pre-requisites for monitoring Swift AMH Node

Before attempting to manage and monitor Swift AMH Node, make sure that the following pre-requisites are fulfilled:

• Determine the correct port using which the target JBoss EAP 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 JBoss EAP topic.

• The eG tests have to be configured with the credentials of a special user who is assigned with operator role. The eG agent connects to the target node 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 user in the WildFly JBoss server topic.

To know how to enable JMX support for JRE, refer to the Configuring JVM Monitoring for a JBoss EAP Server JBoss AS EAP document.