Data Publishing Parameters (ttdpm5130m000)

Use this session to define the parameters for publishing to Data Lake.

For details on how to configure publishing in hybrid deployment, see the Infor LN Enterprise Server Library (Secured) (On-premises) and select Administrator > Enterprise Server > Configuration with Infor OS (Cloud) > Configuring LN for publishing to Data Lake.

Buttons

These buttons are available:

Check IMS Connection
Checks if publishing to IMS with the current connection parameters is possible.

This button is available only if IMS is supported and is valid for the IMS Connection parameters.

Check Catalog Connection
Checks if publishing to Data Catalog with the current connection parameters is possible.

This button is only valid for the Data Catalog Connection parameters.

Check Ingestion Connection
Checks if publishing to Data Lake with the current connection parameters is possible.

This button is only valid for the Batch Ingestion Connection and Streaming Ingestion Connection parameters.

Field Information

Publication Method for Initial Load
Data Lake Ingestion
If this check box is selected, the messages are published directly to Data Lake through the Data Lake Batch Ingestion API.

If this check box is selected, the Message Size (in MB) field in the Publish Data (ttdpm5205m000) session is automatically increased to 50 MB.

If this check box is cleared, data cannot be published to Data Lake.

Note: In an IGS environment, you can select one of these methods:
  • Data Lake Ingestion

    The messages are published directly to Data Lake through the Data Lake Batch Ingestion API and not through ION. In this way, it is not required to model a data flow in ION.

    If this option is selected, the Message Size (in MB) field in the Publish Data (ttdpm5205m000) session is automatically increased to 50 MB. This is because the Data Lake Batch Ingestion API can handle larger messages than IMS.

  • ION Messaging Service

    Data is published from LN to ION. You must model document flows in ION to distribute the data to its final destination.

    If this option is selected, the Message Size (in MB) field in the Publish Data (ttdpm5205m000) session is limited to 5 MB, because this is the maximum file size allowed by IMS.

Publication Method for Changes
Data Lake Ingestion
If this check box is selected, the messages are published directly to Data Lake using the Data Fabric Streaming Ingestion API.

Because the Streaming Ingestion API uses its own batching mechanism within the Data Fabric architecture, micro-batching is not used in LN and the data is sent to the API with due diligence.

For information about the arrival time window and other limits defined by the Data Fabric Streaming Ingestion, see the Infor OS User and Administration Documentation Library (Cloud) and select User > Data Fabric > Sending data to Data Lake > Streaming Ingestion > Micro-batching of streamed data.

If this check box is cleared, changes cannot be published to Data Lake.

Note: In an IGS environment, you can select one of these methods:
  • Data Lake Ingestion

    The messages are published directly to Data Lake using the Data Fabric Streaming Ingestion API and not through ION. In this way, it is not required to model a data flow within ION.

    Also, because the Streaming Ingestion API uses its own batching mechanism within the Data Fabric architecture, micro-batching is not used in LN and the data is sent to the API with due diligence.

    For information about the arrival time window and other limits defined by the Data Fabric Streaming Ingestion, see the Infor OS User and Administration Documentation Library (Cloud) and select User > Data Fabric > Sending data to Data Lake > Streaming Ingestion > Micro-batching of streamed data.

  • ION Messaging Service

    Data is published from LN to ION. You must model document flows in ION to distribute the data to its final destination.

    The changes are not published immediately, but they are batched into larger messages during a user-defined period of time before publishing. This is called micro-batching. The period during which the changes are batched and the message size are specified in the Micro-Batching Parameters in the current session.

Note: 
  • The available options for the Publication Method for Initial Load and the Publication Method for Changes are interdependent. You cannot select Data Lake Ingestion for changes if it is not selected as the publication method for the initial load.
  • If the LN data must be replicated to a location other than Data Lake, then the LN data must first be sent to the Data Lake from where the data can be distributed to other locations.
  • For cloud environments, the connection point parameters are not displayed. These parameters are defined on system resources at the Landlord level.
Logical IDs
Logical ID

The logical ID is used to identify the origin of the messages; it is part of the message envelope.

Data Catalog Connection

These connection parameters are used to publish schemes (meta data) to Data Catalog.

Select OAuth version 1.0 or 2.0.

Select OAuth 1.0 if the LN server directly communicates with the Infor OS server. Usually this is the case in full on-premises environments.

Select OAuth 2.0 if the integration is set up using the API Gateway.

URL

The Data Catalog endpoint URL.

  • Infor OS on premises:

    The full URL is https://<ion>/datacatalog/v1/document/json. Replace <ion> with the FQDN and the port number of the Infor OS router or the load balancer pointing to it.

    Example:

    https://inforos.domain.com:9543/datacatalog/v1/document/json

  • Infor OS CE:

    See the Infor LN Enterprise Server Library (On-premises) and select Administrator > Enterprise Server > Configuration with Infor OS (Cloud).

OAuth Consumer Key

The OAuth consumer key to connect to Data Catalog. This applies if OAuth version 1.0 is selected.

The OAuth 1.0 credentials can be generated in the ION Grid Management under Security – OAuth Credentials. The required roles are grid-run-as-user and datacatalog-admin.

OAuth Secret Key

The OAuth secret key to connect to Data Catalog. This applies if OAuth version 1.0 is selected.

OAuth 2.0 Parameter Set

The OAuth 2.0 Parameter Set. This applies if OAuth version 2.0 is selected.

Specify the parameter set or zoom to the OAuth 2.0 Parameter Sets (ttaad0108m000) session to select an OAuth 2.0 parameter set.

Batch Ingestion Connection

These connection parameters are used to publish data (initial load) to Data Lake through the Data Lake Batch Ingestion API.

For the integration from LN on premises you must use OAuth 2.0, because the integration is set up using the API Gateway.

URL:

The Data Lake Batch Ingestion API endpoint URL.

See the Infor LN Enterprise Server Library (On-premises) and select Administrator > Enterprise Server > Configuration with Infor OS (Cloud).

OAuth 2.0 Parameter Set

This applies if OAuth version 2.0 is selected.

Specify the parameter set or zoom to the OAuth 2.0 Parameter Sets (ttaad0108m000) session to select an OAuth 2.0 parameter set.

Streaming Ingestion Connection

These connection parameters are used to publish data (changes) to Data Lake through the Data Lake Streaming Ingestion API.

For the integration from LN on premises you must use OAuth 2.0, because the integration is set up using the API Gateway.

Web Socket URL:

The Data Lake Streaming Ingestion API web socket URL.

See the Infor LN Enterprise Server Library (On-premises) and select Administrator > Enterprise Server > Configuration with Infor OS (Cloud).

OAuth 2.0 Parameter Set

This applies if OAuth version 2.0 is selected.

Specify the parameter set or zoom to the OAuth 2.0 Parameter Sets (ttaad0108m000) session to select an OAuth 2.0 parameter set.

Tenant ID

The ID of the tenant to which the data is sent.