The necessary I2I functional set is installed as part of the EagleML package. To use it you have to go thru certain configuration steps that depend on the structure of the process for each specific case.

Before you start installing and configuring the I2I , please decide:

• which role is going to be given to the local and which to the remote environment (Extract or Load)

• which delivery methods you are going to use

• find out the name of the remote environment

Navigate to the link relevant for your Choose a relevant case:

Local Extract, Remote Load

Local Extract Settings

FTP and WS delivery methods do not require any streams (you will use the i2i distribution rule), please define the following parameters for them:

If you want to use JMS or MQ, you have to create a separate inbound stream for each of them

Remote Load Settings

For JMS, MQ or FTP you will use default control message rule, please define the following parameters

WS delivery method requires a specific inbound stream to be created

Local Load, Remote Extract

Local Load Settings

JMS, MQ or FTP delivery methods do not require any streams (you will use the i2i distribution rule), please define the following parameters for them:

If you want to use WS, you have to create an inbound stream for it

Remote Extract Settings

For JMS or MQ delivery methods you will use default i2i distribution rule, please define the following parameters

...

Set specific configuration parameters if you are using custom streams to read RTRs and TSRs:

• w_i2i_delivery_stream

• w_i2i_tsr_reader_stream

Assign LinkIds, if necessary.

Make up a control message and you are ready to go!