Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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, 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

Choose a case most relevant for you:

 Local Extract, Remote Load

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:

 For JMS (click to expand):


 For MQ (click to expand):


Remote Load Settings

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

 For JMS (click to expand):


 For MQ (click to expand):


 For FTP (click to expand):


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

 Local Load, Remote Extract

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:


 For JMS (click to expand):


 For MQ (click to expand):


 For FTP (click to expand):


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:


 For JMS (click to expand):


 For MQ (click to expand):


FTP and WS delivery methods require specific configuration parameters:

  • No labels