Queues are the staging area that contains messages that have been sent and are waiting to be read. Queue's properties are set when the destination is created. The administration interfaces allow you to create and manage administered object of Queues, and this test shows the messaging model of current queues.

Queues can import messages, but cannot export them.You can configure the queue definitions (in the configuration file queues.conf) with the import property that specify one or more external transports. Import instructs tibems to import messages that arrive on those transports from Rendezvous, and deliver them to the EMS destination.

Note that, contrary to what the name queue suggests, messages don't have to be delivered in the order sent. If the message driven bean pool contains more than one instance then messages can be processed concurrently and thus it is possible that a later message is processed sooner than an earlier one. A JMS queue guarantees only that each message is processed only once.

This test provide the details of the queue such as its status, number of current active receivers, number of pending messages, size of the pending messages pertaining to the queue.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• In the PORT text box, mention the port at which the specified HOST listens.

• Prior to monitoring the Tibco EMS server, you will have to build a .bat or .sh file (depending upon the operating system on which Tibco EMS is functioning) bundled with the commands that the eG agent needs to execute on the Tibco EMS server for collecting the required metrics. The commands to be invoked by the the .bat or .sh file are as follows:

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show server

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show durables

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show queues

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show topics

  tcp://{IPAddressorHostName_of_TibcoEMS}:{PortNumber_of_TibcoEMS} show connections

  For instance, if the IP address of your Tibco EMS server is 192.168.10.28 and its port is say, 9090, then a sample command in the .bat or .sh file would be:

  tcp://192.168.10.28:9090 show server

  The .bat/.sh file so created can be saved to any location on the Tibco EMS host. Then, while configuring this test, make sure you provide the full path to this .bat or .sh file in the COMMANDPATH text box so that, the agent can execute the file, invoke the commands bundled into it, and extract the desired metrics from the server.

• Specify the queues that is not required for monitoring in the IGNORE QUEUES text box. Queues can be listed in a comma seperated form. The queue names can be provided in the following format *Queue *, *Queue , Queue*). For an example to ignore the queues starting with sys from being monitored specify as * sys in the IGNORE QUEUES text box. Also you can specify the complete queue name to prevent from being monitored.  

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.