...
The Hub and Spoke interaction does not depend on a specfic file transfer protocol. Any of the following file transfer protocols are valid: FTP (SFTP), MQ, JMS ,or Web Service.
| Info | ||
|---|---|---|
| ||
I2I was introduced in the 2015 September monthend EagleML/EJM Release. You need this release or higher in order to leverage I2I functionality. |
The main artifacts of I2I processes include:
Run Task Request (RTR) Message – The spoke sends a RTR message to start the extract data process in Hub. For more information, see the About Control Messages page in the EagleML wiki.
Task Status Response (TSR) Message – The hub sends a TSR message to Spoke about the completion of the extract process. For more information, see the About Control Messages page in the EagleML wiki.
Extracted Data – The hub generates an extracted data file (or files) and sends it (them) to Spoke.
For example: Hub creates an archive of extracted data files and loads this archive into the Spoke's FTP.Spoke SID – The unique Security Identifier (automatically set variable) of the Spoke environment, based on which the Hub defines necessary settings to run the extract process and sends it to the Spoke.
Spokes Map – The configuration file in the Hub containing the Spoke SID and parameters related to this Spoke, including extract parameters (for example, Entity List linked to Spoke SID), the Spoke delivery method and settings (for example, Spoke FTP URL, Spoke FTP credentials, delivery FTP stream and so on.)
IWS I2I Solution – IWS I2I solution which is located in the Spoke environment. It provides a good representation of the I2I process, parameter settings and tracking the I2I process. The IWS I2I solution generates an I2I workflow which can be launched manually or on a defined schedule.
| Info | title | Note
|---|
eagle_i2i_full_extract and eagle_i2i_delta_extract have been renamed as eagle_wrf_full_extract and eagle_wrf_delta_extract, respectively. |