How can I monitor a route (i.e connected, disconnected, etc)?
Article ID: KB0085127
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Resolution:
==============
You can try the following methods:
1). Use system monitor topics.
EMS can publish messages to various topics when certain events occur. All system event topic names begin with $sys.monitor. Monitor topics are similar to other topics. To view these topics, create a client application that subscribes to the desired topics.
The following are the system monitor topics related to route:
$sys.monitor.route.connect
A route connection is attempted.
$sys.monitor.route.disconnect
A route connection is disconnected.
$sys.monitor.route.error
An error occurs on a route connection.
$sys.monitor.route.interest
A change in registered interest occurs on the route.
Refer to EMS User's Guide -> Monitoring Server Activity -> Monitoring Server Events
and to Appendix B Monitor Messages -> Description of Monitor Topics.
Generating a monitor message does consume system resources. For more details on the potential performance impact of using monitor topics, refer to "Performance Implications of Monitor Topics" in "Monitoring Server Events".
2). Use Hawk to monitor. TIBCO Hawk is a tool for monitoring and managing applications and operating systems. EMS provides classes for monitoring and administering the EMS server. For example, you can use getRoutes() in com.tibco.tibjms.admin.hawk.HawkListener class.
Refer to the EMS User's Guide -> Appendix A Using TIBCO Hawk.
3). Use the "show route <route_name>" or "show routes" command from the EMS admin tool. There are also EMS Admin APIs corresponding to these commands which allows yo to write a program that uses the Admin API to monitor the route.
Platforms:
=================
All
Keywords
=================
route monitor hawk EMS Admin
Resolution:
==============
You can try the following methods:
1). Use system monitor topics.
EMS can publish messages to various topics when certain events occur. All system event topic names begin with $sys.monitor. Monitor topics are similar to other topics. To view these topics, create a client application that subscribes to the desired topics.
The following are the system monitor topics related to route:
$sys.monitor.route.connect
A route connection is attempted.
$sys.monitor.route.disconnect
A route connection is disconnected.
$sys.monitor.route.error
An error occurs on a route connection.
$sys.monitor.route.interest
A change in registered interest occurs on the route.
Refer to EMS User's Guide -> Monitoring Server Activity -> Monitoring Server Events
and to Appendix B Monitor Messages -> Description of Monitor Topics.
Generating a monitor message does consume system resources. For more details on the potential performance impact of using monitor topics, refer to "Performance Implications of Monitor Topics" in "Monitoring Server Events".
2). Use Hawk to monitor. TIBCO Hawk is a tool for monitoring and managing applications and operating systems. EMS provides classes for monitoring and administering the EMS server. For example, you can use getRoutes() in com.tibco.tibjms.admin.hawk.HawkListener class.
Refer to the EMS User's Guide -> Appendix A Using TIBCO Hawk.
3). Use the "show route <route_name>" or "show routes" command from the EMS admin tool. There are also EMS Admin APIs corresponding to these commands which allows yo to write a program that uses the Admin API to monitor the route.
Platforms:
=================
All
Keywords
=================
route monitor hawk EMS Admin
Issue/Introduction
How can I monitor a route (i.e connected, disconnected, etc)?
Feedback
Yes
No
Powered by
