...
Expand | ||
---|---|---|
| ||
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 (refer to http://eagle.helpdocsonline.com/available-filters$Common%20Filter).. For more information, see the Available Filters page in the EagleML wiki. |
Expand | ||
---|---|---|
| ||
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. |
...
Expand | ||
---|---|---|
| ||
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. For more details, refer to http://eagle.helpdocsonline.com/available-filters$History%20Only%20Filter)information, see the Available Filters page in the EagleML wiki. |
Expand | ||
---|---|---|
| ||
Yes, it is possible. In this case, two (2) EntityList filters will be applied: first in the Hub and second in the Spoke. |
...
Expand | ||
---|---|---|
| ||
I2I is part of EagleML, we don't have a separate version for I2I. EagleML/I2I have the same version. To determine which EagleML version you have in your environment, open Message Center Editor and open the following file: /eagle_ml-2-0_cm/w_config.inc. In the top line of this file, you will find information about the installed EagleML version. For example: <!-BR-EAGLEML_PRD_20151007.1-> In this example, you see BR-EAGLEML_PRD_20151007.1. This indicates that this environment contains the September 2015 monthend release. The date for the monthend release is typically the first Wednesday after the first Tuesday of the following month. For example, September 2015 EagleML monthend package was released on October 7th 2015. Refer to the related wiki page: http://eagle.helpdocsonline.com/checking-your-eagleml-version.You can For more information, see the Checking Your EagleML Version page in the EagleML wiki. You can also find detailed information about each EagleML release in the EagleML Release Notes section. |
...
Expand | ||
---|---|---|
| ||
Yes, if you don't specify any filters for SMF, then all SMF will be extracted. There are no default filters, with one exception: maxrows (count of max returned records in the extract file). The default value of this parameter is 100,000 records (refer to. For more information, see the Available Filters page in the EagleML wiki page). |
Held Security Filters Questions
...
Expand | ||
---|---|---|
| ||
Yes, they can be used in SMF extracts. But, the date filters are different for Date filters without Held Mode and Date filters with Held Mode. |
Expand | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
Date filters without Held Mode:
This means that all SMF records from the history table with EFFECTIVE_DATE value greater than or equal to the effective date filter value will be extracted.
This means that all SMF records from the composite or history table with the UPDATE_DATE value greater than or equal to the update date filter value will be extracted. Date filters with Held Mode:
entityselectiontype / entityselectionvalue
|
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
"effectivedate", "fromeffectivedate" and "toeffectivedate" filters are available only for SMF history extract and not available in Held Mode as follows:
|
...