Can you send me an example of how is the configuration of the JMS Topic Subscriber element in BW looks like using $sys.monitor.D.E.destination?
Article ID: KB0093136
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
If you use JMS Topic Subscriber to listen on $sys.monitor.T.... topic, you are listening on JMS server events,
not the topic message content. The monitor message is generated by the JMS server and it is always a
Map message. Thus, you need to use Map message type on the JMS Topic Subscriber activity.
Please see the attached example for your review.
Before you run the example you need to "tibemsd.conf" and enable:
authorization = enabled
Keep in mind only Administrator has the priviledge to see $sys.monitor messages so you need to use your admin
password in BW EMS connection.
KEYWORDS: TOPIC, $sys.monitor, MAP
If you use JMS Topic Subscriber to listen on $sys.monitor.T.... topic, you are listening on JMS server events,
not the topic message content. The monitor message is generated by the JMS server and it is always a
Map message. Thus, you need to use Map message type on the JMS Topic Subscriber activity.
Please see the attached example for your review.
Before you run the example you need to "tibemsd.conf" and enable:
authorization = enabled
Keep in mind only Administrator has the priviledge to see $sys.monitor messages so you need to use your admin
password in BW EMS connection.
KEYWORDS: TOPIC, $sys.monitor, MAP
Issue/Introduction
Can you send me an example of how is the configuration of the JMS Topic Subscriber element in BW looks like using $sys.monitor.D.E.destination?
Attachments
Feedback
Yes
No
Powered by
