Configure JMS/MQ as I2I Delivery Method

JMS/MQ as delivery method is supported for I2I as of the EagleML June 2016 release.

Queues List

The following message queues are needed:

MQ for processing RTR – Required
MQ for processing TSR – Required
MQ for sending extracted data from Hub to Spoke env – Optional

If FTP is used to delivery extracted data from Hub to Spoke then MQ for sending extracted data from Hub to Spoke env is not necessary.

On this page

1 Queues List
2 Custom Streams List
3 Manually Configure JMS/MQ as I2I Delivery Method in Hub and Spoke
4 Run Eagle I2I Full or Delta Extract Workflows Using JMS/MQ Delivery Method
5 Use I2I Tool to Configure JMS/MQ as I2I Delivery Method in Hub and Spoke

Custom Streams List

To link message queues to Hub and Spoke environments, you need have created following custom streams.
For Hub env:

Inbound stream to read RTR from Spoke via JMS/MQ (based on EagleML core ruleset file - eagle_ml-2-0_cm\in\xml\control_messages.rsf, XML delivery format) – Required
Outbound stream to send TSR to Spoke via JMS/MQ (based on custom ruleset file, CSV delivery format) – Required
Outbound stream to send extracted data to Spoke via JMS/MQ (based on custom ruleset file, CSV delivery format) – Optional

For Spoke env:

Outbound stream to send RTR to Hub via JMS/MQ (based on custom ruleset file, CSV delivery format) - Required
Inbound stream to read TSR from Hub via JMS/MQ (based on EagleML core ruleset file eagle_ml-2-0_cm\in\xml\taskstatusresponse.rsf, XML delivery format) - Required
Inbound stream to read extracted data from Hub via JMS/MQ (based on EagleML core ruleset file eagle_ml-2-0_cm\eis\in\xml\eis_save_file.rsf, XML delivery format) - Optional

Manually Configure JMS/MQ as I2I Delivery Method in Hub and Spoke

Make sure that all necessary message queues are available before configuring Hub and Spoke environments.

Manually Configure JMS/MQ as I2I Delivery Method in Hub

To configure JMS/MQ as I2I delivery method in Hub, follow these steps:

Open Message Center Console (MCC) and login to Hub env.
Create necessary inbound and outbound JMS streams. For more information, see the Creating Outbound JMS Streams and Creating Inbound JMS Streams pages in the EagleML wiki.
Open Message Center Editor (MCE) and login to Hub env.
Open Spokes Map file: /eagle_ml-2-0_custom_cm/i2i_spokes_map.inc.
Add/Edit Code section related to Spoke env:

<CODE>
IF :param_SpokeSID: = '[Replace by SpokeID]' THEN  [
:varSpokeDeliveryMethod: := 'JMS';
:varSpokeEnitityList: := '[Replace by Entity List name, which is availbale for this Spoke]';
:varSpokeDeliveryStreamName: := '[Replace by outbound stream name, which sends TSR to Spoke]';
:varAlwaysUseFTPToDeliveryExtractedData: := '[Replace by Y or N value]';
:varSpokeJMSStreamForExtractedData: := '[Replace by outbound stream name, which sends extracted data to Spoke, optional]';

:varSpokeFTPURL: := '[Replace by spoke FTP IP or URL]';
:varSpokeFTPUser: := '[Replace by spoke FTP login]';
:varSpokeFTPPass: := '[Replace by spoke FTP pass]!';
:varSpokeFTPFolderForExtractFile: := 'CMW/inbound/';
:varSpokeFTPFolderForRemoteTSR: :='CMW/remotereply/';

:varFromFolder: := 'data/msgcenter/cmw/extracts/';
:varToFolder: := 'data/msgcenter/cmw/extracts/';
:varSpokeEnvURL: := '[Replace by spoke env URL]';
:varSpokeEnvLogin: := '[Replace by spoke env login]';
:varSpokeEnvPass: := '[Replace by spoke env pass]';
];
</CODE>

Where:

varSpokeDeliveryStreamName – outbound stream name, which send TSR to Spoke.
varAlwaysUseFTPToDeliveryExtractedData – boolean flag (Y or N), which defines the delivery method to send extracted data to Spoke.
If set Y - extracted data will be sent via FTP, if set N - extracted data will be sent via channel defined in varSpokeDeliveryMethod variable. If varAlwaysUseFTPToDeliveryExtractedData = Y then need define other FTP settings (like varSpokeFTPURL, varSpokeFTPUser, varSpokeFTPPass, see full list in /wiki/spaces/EAGLEML/pages/69730948).
varSpokeJMSStreamForExtractedData – outbound stream name, which sends extracted data to Spoke. Required if varAlwaysUseFTPToDeliveryExtractedData = N.

Save the file.
Re-initialize Message Center cache.

Manually Configure JMS/MQ as I2I Delivery Method in Spoke

To configure JMS/MQ as I2I delivery method in Spoke, follow these steps:

Open Message Center Console (MCC) and login to Spoke env.
Create necessary inbound and outbound JMS streams. For more information, see the Creating Outbound JMS Streams and Creating Inbound JMS Streams pages in the EagleML wiki.
Re-initialize Message Center cache.

Run Eagle I2I Full or Delta Extract Workflows Using JMS/MQ Delivery Method

To run Eagle I2I full or delta extract workflows using JMS/MQ delivery method, need set i2icmdeliverystream (required), 2ideliverymethod (required) and readdatatoloadfromftp (optional) parameters.
For example:

i2icmdeliverystream is Outbound stream name, which sends RTR to Hub via JMS/MQ
i2ideliverymethod is JMS
if extracted data is sent from Hub to Spoke via FTP channel then set Y to readdatatoloadfromftp parameter

Use I2I Tool to Configure JMS/MQ as I2I Delivery Method in Hub and Spoke

As of June 2016, I2I Tool (ver. 1.0.0.16) doesn't support configure JMS/MQ as I2I delivery method in Hub and Spoke environments.