Page Comparison

...

{
    "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 is used. 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 has all parameters required for WebSphere MQ connections - port, channel, queueManager name, host name:

...

• 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)
• Sequential Reading parameter should be set to N.
• Concurrent Consumers can be set to 20, which means that one MC2 Worker will process processes concurrently 20 messages from the queue. If we have there are 8 MC2 workers (this corresponds to four servers running MC2), MC2 will process processes 160 messages from the queue concurrently. If this parameter is not set, MC2 will process processes one message per worker. For example, for 8 workers only 8 messages are processed concurrently.

...