BTM transaction pathway

An activity implementation corresponds to the EMS Server being monitored. The activity implementation extension details contains the name of the EMS Server. The server connection parameters (host, port, credentials) are configured when you deploy the transaction pathway.

TrueSight Middleware and Transaction Monitor (TMTM) monitors JMS destinations in the EMS Server (i.e. not in the JMS application). This means that monitoring on activity inputs corresponds to a message sent from the server (delivered to a consumer), while activity output corresponds to a message delivered to the server (sent from a producer).

When defining the activity associations, the Input and Output Destination names represent the topics or queues on which messages are monitored. The following naming convention is used.

• Prefix with "Q" for Queues (e.g. "Qqueue.sample")
• Prefix with "T" for Topics (e.g. "Ttopic.sample")

Wildcards in the resource names are supported but discouraged. If wildcards are used, limit the scope. Do not monitor "T>" because that would be all topics published in the EMS server.

Refer to the TIBCO documentation to understand the supported wildcards for System Monitoring Topics specific to the version of TIBCO EMS being monitored. Note that TMTM handles the "$sys.monitor.D.E." part of the topic name – resource names in the BTM model should only specify the destination name (prefixed as described above), and not the fully qualified system monitoring topic.