| Measurement |
Description |
Measurement
Unit |
Interpretation |
| IsActive |
Indicates the current state of the EMS Server |
Number |
The value 0 for this measure indicates that the server being monitored is inactive, and the value 2 indicates that it is active. The value 1 on the other hand indicates that the server is currently in the fault tolerant standby mode. The fault-tolerant state is operated by configuring a pair of servers - namely, primary and backup. The primary and backup servers act as a pair, with the primary server accepting the client connections and performing the work of handling messages, and the secondary server acting as a backup in case of failure. If the primary server fails, the backup server resumes operation in its place.
|
| Tot_no_of_topics |
Indicates the total number of topics available in the server. |
Number |
Topics is a distribution mechanism for publishing messages that are delivered to multiple subscribers.The publisher generally addresses messages to a topic. Many publishers can publish to the same topic, and a message from a single publisher can be received by many subscribers. Subscribers subcribe to topics and all messages published to the topic are received by all subscribers to the topic.
The value reported by this measure includes dynamic, static and temporary topics, and thus indicates the total topic load on the server. |
| Dyna_topics |
Indicates the total number of dynamic topics on the server |
Number |
Destinations for message can be either queues or topics, and these destinations can either be created statically or dynamically. Dynamic topics do not appear in the configuration files and exist as long as there are messages or consumers on the destination. Since these topics are created dynamically by applications, this measure serves as a good indicator of the topic load imposed by applications on the EMS server. |
| Tmp_topic |
Indicates the number of temporary topics on the server
|
Number |
Temporary destinations (temporary queues or temporary topics) are proposed as a lightweight alternative in a scalable system architecture that could be used as unique destinations for replies. Such destinations have a scope limited to the connection that created it, and are removed on the server side as soon as the connection is closed. Owing to their short life span, these topics may not have a lasting effect on the load/overall performance of the EMS server. For the same reason and those listed below, the temporary topics are not ideal destinations for messages:
- A temporary destination can only be consumed by the connection that created it.
- When you close the connection that has a temporary destination, the destination is closed and its contents are lost.
- You cannot have durable subscriptions to a TemporaryTopic.
- Each temporary destination is unique and cannot be copied.
- Temporary destinations cannot be routed using an enterprise messaging service.
Typically, the value of this measure will be low. However, if the value appears to significantly increase with time, it could indicate a bottleneck in the closure of connections; further investigation may be required in this regard.
|
| Static_topic |
Indicates the number of static topics on the server.
|
Number |
The destination for a message can be either created statically in the server configuration files or dynamically by a client application. Static topics are those topics for which configuration information resides within configuration files for the EMS server. These topics are typically administered by the server itself. The value of this measure therefore indicates the server workload in terms of the number of static topics it is currently administering. |
| Tot_no_of_queues |
Indicates the total number of queues.
|
Number |
The point-to-point
style of messaging uses a queue to store messages until they are received. The
message producer sends the message to the queue; the message consumer
retrieves messages from the queue and sends acknowledgement that the message
was received.
Based on how it is created, a queue can be classified as dynamic, static, or temporary. Based on what its created for, a queue can be configured to be 'exclusive' or 'non-exclusive'. If a queue is exclusive, then all
messages in this queue can only be retrieved by the first consumer specified for the queue. Exclusive queues are useful when you want only one application to receive messages for a specific queue. If the queue is not exclusive, any number of receivers can retrieve messages from the queue. Non-exclusive queues are useful for balancing the load of incoming messages across multiple receivers.
The value of this measure includes queues of all the above-mentioned types, and is useful for determining the load on the server in terms of the number of queues it handles.
|
| Dyna_queues |
Indicates the total number dynamic queues that are created.
|
Number |
Dynamic queues do not appear in the configuration files and exist as long as there are messages or consumers on the destination. Since these queues are created dynamically by applications, this measure serves as a good indicator of the queue load imposed by applications on the EMS server. |
Dynamic queues will be deleted if the server is restarted and there are
no persistent messages on them. Dynamic queues will survive a server
restart if there are persistent messages on the queue.
| Tmp_queues |
Indicates the number of temporary queues on the server.
|
Number |
Temporary destinations (temporary queues or temporary topics) are proposed as a lightweight alternative in a scalable system architecture that could be used as unique destinations for replies. Such destinations have a scope limited to the connection that created it, and are removed on the server side as soon as the connection is closed. Owing to their short life span, temporary queues may not have a lasting effect on the load/overall performance of the EMS server. For the same reason and those listed below, the temporary queues are not ideal destinations for messages:
- A temporary destination can only be consumed by the connection that created it.
- When you close the connection that has a temporary destination, the destination is closed and its contents are lost.
You cannot have durable subscriptions to a TemporaryTopic.
- Each temporary destination is unique and cannot be copied.
- Temporary destinations cannot be routed using an enterprise messaging service.
Typically, the value of this measure will be low. However, if the value appears to significantly increase with time, it could indicate a bottleneck in the closure of connections; further investigation may be required in this regard.
|
| Static_queues |
Indicates the number of static queues on the server.
|
Number |
The destination for a message can be either created statically in the server configuration files or dynamically by a client application. Static queues are those queues for which configuration information resides within configuration files for the EMS server. These queues are typically administered by the server itself. The value of this measure therefore indicates the server workload in terms of the number of static queues it is currently managing. |