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 (

  Hub

  Extract or

  Spoke

  Load)

• which delivery methods you are going to use

• find out the name of

  Spoke

  the remote environment

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

Local Hub, Remote Spoke

Local Hub Settings

FTP and WS delivery methods do not require any streams, please define the following global parameters for them in w_config_custom.inc:

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

Remote Spoke Settings

WS delivery method does not require any streams, please define the following global parameters for it in w_config_custom.inc:

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

Local Spoke, Remote Hub

Local Spoke Settings

WS delivery method does not require any streams, please define the following global parameters for it in w_config_custom.inc:

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

Remote Hub Settings

FTP and WS delivery methods do not require any streams, please define the following global parameters for them in w_config_custom.inc:

...

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!