Page Comparison

...

Instance to Instance (I2I) EagleML is an EJM feature which provides data interaction between several Eagle environments. You can build complex cross-environment workflows, for example, extracting data in the data storage environment (Hub) and loading extracted data into the recipient environment (Spoke). The process can involve several Spoke environments which send data extract requests to one Hub environment and respond back. This is sometimes referred to as the Spokes-Hub distribution paradigm.

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. 

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 (learn more about RTR at [{+}http://eagle.helpdocsonline.com/rtr-message+)
• Task Status Response (TSR) Message – The hub sends a TSR message to Spoke about the completion of the extract process (learn more about TSR at [{+}http://eagle.helpdocsonline.com/tsr-message+)
• 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

• Anchor
  Spoke_SID Spoke_SID

  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

• Anchor
  Spokes_map Spokes_map

  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 (see more about IWS here). 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.