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

Before you start 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, just define the following parameters:

If you want to use JMS or MQ, you have to create a separate inbound stream based on the default distribution rule:

...

...

Remote Load Settings

For JMS, MQ or FTP you have to create a stream on the base of default control message rule:

...

...

...

WS delivery method requires only some configuration parameters to be set:

Local Load, Remote Extract

Local Load Settings

For JMS, MQ or FTP delivery methods you have to create streams based on the default distribution rule:

...

...

...

If you want to use WS, please define the following parameters:

Remote Extract Settings

For JMS or MQ delivery methods you have to create streams on the base of default distribution rule:

...

...

...

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!