In this page:
...
Note |
---|
Please note, that smf_mi should not be used for volume data load or in processes sensitive to load speed |
Issuer Role Load
Issuer Role can be loaded
- with a dedicated interface Reference Issuer Role via eagle_ml-2-0_default_in_xml_reference stream (objectType = IssuerRole, the message should be formatted as an <issuerRole> message) - read more on Issuer Role Inbound Interface page.
- with SMF MI stream (objectType = GenericSMF, the message should be formatted as a <genericSMF> message)
Batch Mode Specifics
SMF MI supports Issuer Role batch load. In order to turn it on you should have EagleML/referenceTransaction/header/processingOptions/ set to ISSUER_ROLE_GROUPING in the incoming SMF:
Code Block | ||
---|---|---|
| ||
<header> <objectType>GenericSMF</objectType> <processingOptions>ISSUER_ROLE_GROUPING</processingOptions> </header> |
This can be turned off by adding a counter-flag DIRECT_ISSUER_ROLE_OPTIONS
Code Block | ||
---|---|---|
| ||
<header> <objectType>GenericSMF</objectType> <processingOptions>ISSUER_ROLE_GROUPING,ISSUER_ROLE_GROUPING</processingOptions> </header> |
...
Here is the list of available processing options:
ISSUER_ROLE_GROUPING - enables batch mode (also enables ISSUE_ROLE_UPSERT_MODE, USE_LATEST_START_DATE by default)
Info ISSUER_ROLE_GROUPING has no sense outside of SMF MI interface
- ISSUE_ROLE_UPSERT_MODE - prevents the delete step in batch mode
- USE_LATEST_START_DATE - finds the latest start date in the incoming message and uses it for each incoming record as the start date
DIRECT_ISSUER_ROLE_OPTIONS - counter-flag for ISSUER_ROLE_GROUPING, allows to set options directly
.Info DIRECT_ISSUER_ROLE_OPTIONS has no sense outside of SMF MI interface
Issue Variable Rate Model - Load Details
...