Page Comparison

...

Configure the non-pooled connection to WebSphere or ActiveMQ in a .json file in estar/tpe/dynamic/mc2/eaglejms/connections. The following non-pooled ComponentNames for ActiveMQ and WebSphere MQ are defined in the Eagle MC2 out of the box: wmq-no-pool, wmqssl-no-pool, eagle-amqssl-no-pool and eagle-amq-no-pool. For example for ActiveMQ, create a amq.json file with the following content:

Code Block

language	js
theme	DJango
title	ActiveMQ Non-pooled Connection Configuration
linenumbers	true

{
    "Region": "BND13XLN", /*Oracle SID of region name to which this config belongs */
    "Connections": [
           {
            "ConnectionName": "activemq.nopool", /* name of ActiveMQ connection to be used in the stream*/
            "ComponentName": "eagle-amq-no-pool", /* name of component */
            "Parameters": {
                "brokerURL": "tcp://eglwwvm22.eagleinvsys.com:61616" /* connection url */
            }
     ]
}

You can note that we use the eagle-amq-no-pool Eagle defined core component. If the connection should be encrypted, set ComponentName to eagle-amqssl-no-pool.

...

NOTE: The Client ID set on the connection will be the "SID-stream_name", where SID is the oracle database SID MC2 is connected to and stream_name is the stream name for which the subscription is created.

Publishing To Queue or Topic

The publishing to a JMS Queue or Topic is implemented in MC2 Rules with a new element named SENDADAPTER For simple extracts, Generic Extracts, Generic Loader distribution of data, TSRs and ACKs this is implemented in EJM distribution rules.

To configure the destination to be used for publishing a MC2JMS Outbound stream has to be created. This stream is used as a definition of the destination, i.e. it defines the JMS connection to be used, the destination name, the credentials, if required, and other parameters defining the connection to JMS - the RuleSet file and the Stream Format is ignored.

When configuring the stream to be used for publishing to JMS a pooled JMS component must be used. The standard components delivered as part of release for ActiveMQ and WebSphere MQ are wmq, wmqssl, eagle-amqssl and eagle-amq.

For example the connection definition can be:

Code Block

language	js
theme	DJango
title	WebSphere MQ Non-pooled Connection Configuration
linenumbers	true

        {
            "ConnectionName": "wmq.pool",
            "ComponentName": "wmq",
	        "Parameters": {
    			"transportType": 1,
			    "port": 1414,
			    "channel": "S_eglwwvm24c",
			    "queueManager": "QM_eglwwvm24c",
			    "HostName": "10.130.36.42"
            }
        }

The Outbound MC2JMS stream definition using the above defined connection should be configured like this:

Image Added

Versions Compared

Old Version 4

New Version 5

Key

Publishing To Queue or Topic