Configuring the JMS monitor adapter
Adapter type: ro-adapter-jms-monitor[baob201301:version]
The following table describes the configuration elements of the JMS monitor adapter.
JMS monitor adapter configuration node elements
The following figure shows an XML template for the JMS monitor adapter configuration.
XML template of the JMS monitor adapter configuration
<config>
<jndi>
<property name 1></property name 1>
<property name 2></property name 2>
...
</jndi>
<connection-factory></connection-factory>
<user-name></user-name>
<password></password>
<number-of-retries></number-of-retries>
<retry-wait></retry-wait>
<client-id></client-id>
<queues>
<queue>
<destination-context-name></destination-context-name>
<maximum-messages-per-second></maximum-messages-per-second>
<message-class></message-class>
</queue>
...
</queues>
<topics>
<topic>
<destination-context-name></destination-context-name>
<message-class></message-class>
<durable-subscriber-name></durable-subscriber-name>
</topic>
...
</topics>
<character-set></character-set>
</config>
<jndi>
<property name 1></property name 1>
<property name 2></property name 2>
...
</jndi>
<connection-factory></connection-factory>
<user-name></user-name>
<password></password>
<number-of-retries></number-of-retries>
<retry-wait></retry-wait>
<client-id></client-id>
<queues>
<queue>
<destination-context-name></destination-context-name>
<maximum-messages-per-second></maximum-messages-per-second>
<message-class></message-class>
</queue>
...
</queues>
<topics>
<topic>
<destination-context-name></destination-context-name>
<message-class></message-class>
<durable-subscriber-name></durable-subscriber-name>
</topic>
...
</topics>
<character-set></character-set>
</config>
The following figure shows an XML sample of the JMS monitor adapter configuration.
XML sample of the JMS monitor adapter configuration
<config>
<jndi>
<java.naming.factory.initial>org.apache.activemq.jndi.ActiveMQInitialContextFactory
</java.naming.factory.initial>
<java.naming.provider.url>tcp://10.254.1.113:61616
</java.naming.provider.url>
</jndi>
<connection-factory>ConnectionFactory</connection-factory>
<number-of-retries>3</number-of-retries>
<retry-wait>2000</retry-wait>
<queues>
<queue>
<destination-context-name>dynamicQueues/queue1.activemq.queue
</destination-context-name>
<maximum-messages-per-second>10</maximum-messages-per-second>
<message-class>com.realops.adapter.jms.message.ByteMessageProcessor
</message-class>
</queue>
</queues>
<topics>
<topic>
<destination-context-name>dynamicTopics/topicnew
</destination-context-name>
<message-class>com.realops.adapter.jms.message.GenericMessageProcessor
</message-class>
</topic>
<topic>
<destination-context-name>dynamicTopics/topicnewnew
</destination-context-name>
<message-class>com.realops.adapter.jms.message.GenericMessageProcessor
</message-class>
</topic>
</topics>
<character-set>Shift_JIS</character-set>
</config>
<jndi>
<java.naming.factory.initial>org.apache.activemq.jndi.ActiveMQInitialContextFactory
</java.naming.factory.initial>
<java.naming.provider.url>tcp://10.254.1.113:61616
</java.naming.provider.url>
</jndi>
<connection-factory>ConnectionFactory</connection-factory>
<number-of-retries>3</number-of-retries>
<retry-wait>2000</retry-wait>
<queues>
<queue>
<destination-context-name>dynamicQueues/queue1.activemq.queue
</destination-context-name>
<maximum-messages-per-second>10</maximum-messages-per-second>
<message-class>com.realops.adapter.jms.message.ByteMessageProcessor
</message-class>
</queue>
</queues>
<topics>
<topic>
<destination-context-name>dynamicTopics/topicnew
</destination-context-name>
<message-class>com.realops.adapter.jms.message.GenericMessageProcessor
</message-class>
</topic>
<topic>
<destination-context-name>dynamicTopics/topicnewnew
</destination-context-name>
<message-class>com.realops.adapter.jms.message.GenericMessageProcessor
</message-class>
</topic>
</topics>
<character-set>Shift_JIS</character-set>
</config>
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*