Configuring data replication to the Infor Data Lake via IMS

Use this procedure if you want to replicate data to the Infor Data Lake via IMS. Note that you can select Data Lake rather than IMS as the data destination and batch ingestion will be used to replicate the data to the Data Lake. Batch ingestion provides significantly better performance and is enabled by default.

  1. Check that a working ION connection exists. To check this, search for "IONConnection" using the Web UI navigation pane search feature. Expand the Data menu item and click IONConnection, On the ION Connection form, note the status of the ION connection. The status should be "Healthy".
  2. Confirm that an IONRegistry record exists in the O Auth Records form. To check this, search for "OAuth" using the Web UI navigation pane search feature. Expand the Data menu item, click OAuth, and open the IONRegistry record. It should have a type of "Generic 10a" and values for the Application Key and Application Secret fields. The values for these should be provided by the administrator of the ION Messaging Service (IMS).
  3. From the ION Desk application, gather information on the connection point for the ION Messaging Service. You will need the following in order to define configuration parameters:

    • Endpoint for IMS

    • Tenant ID

  4. In the Web UI, for each application or data area for which you want to configure replication to the Infor Data Lake, select Administration Console > Other > System Configuration Parameters > All.
  5. On the Configuration Parameter List form, click Create for each of the following parameters and specify the values shown below:
    Component Key Type Required? Description
    Replication schema.registration.destination AlphaUpper Yes Specify IMS. If you are doing replication using other destination types, you can enter multiple values separated by a vertical bar or pipe ("|").
    Replication chunk.size Numeric No

    Specify the byte size. The default is 1000000 (1MB). This controls the size of the chunks of data sent for replication.

    This is an approximate size. After a row of data is exported, if the current buffer size exceeds this value, additional file will be created for the replicated data. The data files will include a number, starting at 0, to indicate the incremental files. Note also that the names of the data files are based on the replication set name and the replication set class name, but that any dots and spaces in those names are replaced with underscores.
    config IONREGISTRY.WSI.ENDPOINT Alpha Yes

    The endpoint definition can be set for both the application data area and the environment data area. The application data area value overrides the environment data area value.

    Note that this parameter can also be found and managed in the "ion" component.
    config IONREGISTRY.WSI.TENANTID Alpha Yes Specify the ION CE tenant ID. The tenant ID can be set for both the application data area and the environment data area. The application data area value overrides the environment data area value.
    oauthclient header.tenant.key Alpha No The tenant header OAuth key can be explicitly set if it has changed from the default value of "x-tenantid".