#INSTALL TIBCO GEMS INSTALL#

Support for Managing and Monitoring TIBCO SubStation.

Customisable display and look and feel.Server statistics may be logged automatically when warning or error limits are breached. Server statistics may be charted in real time, data may be saved to CSV files for export to other tools such as Excel.

Eg purging messages, copy messages from a queue to another queue on a different server. 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(!).

#INSTALL TIBCO GEMS INSTALL#

But where to install those pem files i am not sure, hence getting the ssl e. In the second case the number of attempts depends on how the connection factory is configured (ask your EMS administrator). We have internal singed certificates for which i have the singer/trust certificates. 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.

Install tibco gems