JMS backend activity includes all JMS message send and publish activity. By default, Splunk AppDynamics identifies JMS back ends using the properties of the JMS server such as: vendor, destination name, and destination type. The default configuration uses all three properties of the JMS queue.

JMS Backend Naming Properties

You can enable or disable the use of the following properties for JMS backend identification:

Transaction names are derived from the enabled properties, for example, "ActiveMQ-OrderQueue".

For examples of common message queue configuration scenarios, see Example Message Queue Backend Configuration.