/
I2I Frequently Asked Questions (FAQs)

I2I Frequently Asked Questions (FAQs)

Instance to Instance (I2I) EagleML is an EJM feature that provides data interaction between several Eagle environments.

I2I was introduced in the 2015 September monthend EagleML/EJM Release. You need this release or higher in order to leverage I2I functionality.

The following are some helpful FAQs, click a question to see the answer.

General Questions

There is only one default filter – maxrows (count of max returned records in the extract file) – the default value of this parameter is 100.000 records. For more information, see the Available Filters page in the EagleML wiki.

There are two different cases:

Case #1 is for the STOP-START steps in the EJM Monitoring Tool. In the STOP step, the EJM core tries to stop the previously launched instance of the same workflow. This means that if we submit the eagle_i2i_full_extract_event twice, only one (1) instance will start.

Case #2 is for the I2IProcessUID parameter. This parameter is used only for the I2I delta mode and is related to the last run time. We can store several I2I delta workflows in one environment, so to separate the last time values for each delta workflow, this parameter will be used in the EagleML code.

We have 5 tries to connect to FTP and the default time sleep between tries is 1 second. In the current EagleML version, we can't change these parameters in the config file.

Yes, it is possible. Do not set "historyOnlyFlag" filter value to "Y" – skip it in RTR or set to "N". In this case, Composite SMF table will be used. For more information, see the Available Filters page in the EagleML wiki.

Yes, it is possible. In this case, two (2) EntityList filters will be applied: first in the Hub and second in the Spoke.

Filter Questions

Security Master File (SMF) Filters Questions

Held Security Filters Questions

Date Filters Questions

Planned Enhancements and Resolved Issues