Configuring data replication to the Infor Data Lake through IMS

Use this procedure to replicate data to the Infor Data Lake through IMS. You can select Data Lake instead of IMS as the data destination and batch ingestion is 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.
    1. Search for IONConnection using the Web UI navigation pane search feature.
    2. Expand the Data menu item and select IONConnection.
    3. On the IONConnection form, note the status of the ION connection. The status should be Healthy.
  2. Confirm that an IONRegistry record exists in the OAuth Records form.
    1. Search for OAuth using the Web UI navigation pane search feature.
    2. Expand the Data menu item and select OAuth.
    3. Open the IONRegistry record and confirm if it has a Generic 10a type.
    4. Confirm values for the Application Key and Application Secret fields.

      The values for these fields should be provided by the administrator of the ION Messaging Service or IMS.

  3. From the ION Desk application, gather information on the connection point for the ION Messaging Service. These are the details you need to define configuration parameters:

    • Endpoint for IMS

    • Tenant ID

  4. In the Web UI, to configure replication to the InforData Lake for each application or data area, select Administration Console > Configuration Parameters.
  5. On the Configuration Parameter List form, click Create.

    This table shows each parameters to create along with the values to specify for each one:

    Component Key Type Required? Description
    Replication schema.registration.destination AlphaUpper Yes Specify IMS. If you are doing replication using other destination types, you can specify 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 is created for the replicated data. The data files includes a number, starting at 0, to indicate the incremental files.
    Note: The names of the data files are based on the replication set name and the replication set class name, but any dots and spaces in those names are replaced with underscores.
    config IONREGISTRY.WSI.ENDPOINT Alpha Yes

    The endpoint definition is 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 is 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 is set if it has changed from the default value of x-tenantid.