On This Page:
Table of Contents |
---|
...
Optional Stream Properties
- JMS Connection User - it is the login/user name which you have to provide to connect to JMS Broker if this one was set up to check user authorization.
- JMS Connection Password - the connection password.
- URI parameters - extra parameters for fine-tuning JMS Producer.
...
MC events log - scope of information to print in MC log
Sequential Reading - this option allows us make current Eagle JMS Stream as single JMS Consumer (single reader) across cluster.
Acceptable values: Y/N or empty value means N
Supported JMS destination types: QUEUE & TOPIC
Durable Subscription Name - this option allows us enable Topic Durable Subscription mode for current Eagle JMS Stream. A durable subscriber is a message consumer that receives all messages published on a topic, including messages published while the subscriber is inactive. In short it means that we want to have many topic subscribers, but additionally add persistence for our messages.
Acceptable values: alphanumeric and undersore characters. Empty value means that option is disabled. This option can be enabled if and only if Destination Type parameter is TOPIC, otherwise you will get Sequential-Reading JMS Consumer for appropriate QUEUE.
...
For example, you can create a new connection for Durable Topic Subscription Stream connection.json, using eagle-amq-no-pool as the component name:
Code Block |
---|
{ "ConnectionName": "myactivemq3-tds.connection", "ComponentName": "eagle-amq-no-pool", "Parameters": { "brokerURL": "tcp://inno-jenever03.eagleinvsys.com:61616" } } |
- JMS Connection User - it is login/user name which you have to provide to connect to JMS Broker if this one was set up to check user authorization.
- JMS Connection Password - the connection password.
- Consumer Selector - A JMS message selector allows the user to specify, by header field references and property references, the messages it is interested in.
- Concurrent Consumers - you can specify the default number of concurrent consumers when consuming from JMS. Note: for ActiveMQ we should use the number of concurrent consumers calculated by this equation:
...