AMH JMS Queue Test

A key component of AMH is the AMH node, which runs a user interface, a database, and a messaging system. The AMH node provides the web front end that runs the user interface and Signal Transfer Point (STP) message processing.

• The AMH node runs on JBoss Enterprise Application Platform (EAP) on Red Hat Enterprise Linux (RHEL).

• The database runs on Oracle.

• The messaging system typically is JMS–compliant messaging service.

• Additional virtual machines (HA-VM 1 and HA-VM 2) monitor and maintain the route tables of SAG, NSL, and other components.

The JMS messaging service implements messaging queue which ensures that messages are stored until they are used for processing. For reliable delivery of messages it is important to have JMS message queue in operational status.

This test monitors the JMS message queue and reports the current status of queue which helps administrators plan the workloads better and ensures system is available and ready to use for important financial transactions.

Target of the test : A Swift AMH messaging node instance

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each JMS Queue in Swift AMH node being monitored.

Configurable parameters for the test

Parameter	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.
SSL	If the JBoss AS/EAP server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No.
JMX Remote Port	Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application Java Applications chapter.
JNDI Name	Specify the lookup name for connecting to the JMX connector of the Swift AMH.
JMX User, JMX Password and Confirm Password	These parameters appear only if the Measurement Mode is set to jmx. If JMX requires authentication only (but no security), then ensure that the JMX User and JMX Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter. Confirm the password by retyping it in the Confirm Password text box.

Measures made by the test

Measurement	Description	Measurement Unit	Interpretation
Status	Indicates the current status of current JMS Queue.		The numeric values that correspond to these measure values are as follows: Measure Value Numeric Value Started 3 Open 4 Connected 5 Active 6 Ready 7 Starting 12 Stopping 13 Restarting 14 Recovering 15 Reconnecting 16 Recovered 32 Alerted 33 Partially started 34 Disabled 42 Stopped 43 Not active 44 Start failed 52 Restart failed 53 Stop failed 54 Init failed 55 Recovery failed 56 Error 65 Note: By default, this measure reports the Measure Values listed in the table above to indicate the status. In the graph of this measure however, the same is indicated using the numeric equivalents only.
Batch size	Indicates the current batch size for current AMH JMS queue.	Number	Batch size is the number of messages which are received and buffered before the processing of messages is invoked.
Sliding time window execution rate	Indicates the current execution rate at which the messages are being processed by the current JMS Queue.	Seconds	The sliding window rate is algorithmically adjusted based on the current traffic and congestion status. If the rate is too high it might indicate high network congestion.
Execution	Indicates the time it takes for one message to be processed by current JMS Queue.	Seconds	In case the execution time is trending upwards over the measurements, it means the queue consumer might not be working well.