On This Page:
| Table of Contents |
|---|
Inbound Queue MC2JMS Stream With Concurrent Processing
The MC2JMS stream for consumption from a queue should use requires a connection with a pool. MC2 will start starts consumers on for all workers in the cluster and will process processes the messages in parallel on all workers.
...
- Configure the pooled connection to WebSphere or ActiveMQ in a .json file in estar/tpe/dynamic/mc2/eaglejms/connections. The following ComponentNames for ActiveMQ and WebSphere MQ are defined in the Eagle MC2 out of the box: wmq-no-pool, wmqssl-no-pool, wmq-tds, eagle-amq-tds, eagle-amqssl-no-pool and eagle-amq-no-pool. For example for ActiveMQ, create a amq.json file with the following content:
| Code Block | |||
|---|---|---|---|
|
...
|
...
{
"Region": "BND13XLN", /*Oracle SID of region name to which this config belongs */
"Connections": [
{
"ConnectionName": "activemq.pool", /* name of ActiveMQ connection to be used in the stream*/
"ComponentName": "eagle-amq", /* name of component */
"Parameters": {
"brokerURL": "tcp://eglwwvm22.eagleinvsys.com:61616" /* connection url */
}
]
}
|
You can note that we use the eagle-amq Eagle defined core component. If the connection should be encrypted, set ComponentName to eagle-amqssl.
One connection JSON definition file can contain multiple Connection definitions.
The region is the Oracle database SID to which MC2 is connecting (Eagle Oracle Database server).
For WebSphere MQ the connection will have all parameters required for WebSphere MQ connections - port, channel, queueManager name, host name:
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
{
"ConnectionName": "wmq.pool",
"ComponentName": "wmq",
"Parameters": {
"transportType": 1,
"port": 1414,
"channel": "S_eglwwvm24c",
"queueManager": "QM_eglwwvm24c",
"HostName": "10.130.36.42"
}
}
|
...
2. Create an inbound MC2JMS stream in Message Center Console:
3. Set the Connection Name parameter to the ConnectionName used in the connection configuration file.
The Destination Type should be QUEUE or ALIAS. If the parameter is set to QUEUE then Destination Name should be set to the physical queue name as defined in ActiveMQ or WebSphere MQ queue manager. If the Destination Type is set to ALIAS, the name should be an alias defined in the aliases definition file, as described in JMS Logical names configuration (Aliases)
...