Next we need to create a new TestSuite and TestCase and add a Soap TestRequest.
You can add as many JMS endpoints this way as you need. Available queues and topics depend on what we have configured in HermesJMS, so if we add another queue for example it will be available in this combo box also. Last one is useful in cases when you send something to a queue and checks topic as response immediately as it first subscribe to this topic (durable subscription ) and then send to a queue.Īll combinations are allowed. * send and receive jms://activeMQsession::topic_TestQ1::topic_TestQ2 * receive only jms://activeMQsession::-:: topic_testQ2 * send only jms://activeMQsession:: topic_testQ1 You can choose send-publish only by leaving Receive Queue field blank and also receive-subscribe only by leaving Send Queue-Topic blank. hermes), than select the above configured session and queue- topic for sending- publishing and queue-topic for receiving-subscribing. Open the project and right-click on interface SampleServiceSoapBinding and choose Add JMS Endpoint.įirst set the Hermes Config path to the folder where hermes-config.xml is (usually.
Request and reply messages can beĬorrelated to provide service response times. Messages may be monitored (snooped) as they pass through the server. Messages may be sent/received, queues may be browsed and message contents inspected. Including, general server configuration, JMS destinations, JNDI factories, users/groups, permissions, bridges, Server state and main statistics are automticaly updated, warning and error limits may be configured. Gems provides the following main features: It's pretty good tool for setup and monitoring EMS server. You can use Gems utility tool for monitoring tibco EMS Correct exception handling and internal logging should be sufficient to solve the problem at hand. Personally I do not see the need for monitoring your destinations from your application, in fact I would strongly question that design.
It sounds to me like you have not gotten sufficient documentation with your client libraries. You do however need elevated user rights. Subscribing to a monitor topic is like subscribing to any other topic and is possible with the client libraries, you do not need a specific tool for this. (a practical example is "$.*.queue.sample"). When monitoring destinations they will most likely use the monitoring topics mentioned by both Anders and c. There are several tools that will allow you to monitor the EMS and specific destinations. The exceptions thrown by the client depend on the problem, they all inherit from and they are all listed in your API documentation(!). In the second case the number of attempts depends on how the connection factory is configured (ask your EMS administrator). I suggest you log this internally just above the client dll level (see next question).ĭepending on the specific problem the EMS client dlls will either throw an exception or in the case of a lost connection, attempt to reconnect. I suggest log4Net or similar library for that. What is it exactly that you want to monitor, is it the actual messages on the bus/EMS or the workings of your client (not including the client libraries)? The first I'll answer below, the second you can handle with regular logging.