Alternative publishing option
Sending a JavaScript Object Notation (JSON) file from Infor d/EPM through IMS to Data Lake is an alternative method of publishing data.
This list describes high-level steps of how to send data in a JSON file from the OLAP database to Data Lake:
- In Application Engine, perform these steps:
- Create a script that uses the
OLAPConnection
object to connect to the OLAP database and theOLAPDataArea
object to define a data area in an OLAP cube.You can use filters to limit the data set.
- In the script, create a newline-delimited JSON string that contains the data from the OLAP cube.
- Create the
NotifyDebug(returnvalue)
line to show the JSON content. - Run the script, copy the output into a notepad and save it as the JSON file.
- Create a script that uses the
- In ION Desk, perform these steps:
- Select
The object name must be the same as the JSON file name.
and create an object schema to which to download the JSON file. - Select IMS connection
point.
The bice connection point is provisioned by Infor. If you cannot find this connection point in ION Desk, contact the Infor CloudOps team.
and add the file to the bice - Select Data Lake flow and activate
it.
Only one Data Lake flow is needed to transfer JSON files to Data Lake.
, create a
- Select
- In the Application Engine script, comment out the
NotifyDebug(returnvalue)
line, and add theIONPublishMessage(string documentType, returnvalue)
line. Then publish and run the script. - In ION Desk, select and verify whether the data from the JSON file has been loaded into Data Lake.
- Optionally, to verify the JSON file content and the details of the JSON file transfer, select ION Desk. You can investigate deeper if there were errors during the data transfer. in
For information on Data Lake, Compass, and OneView, see Infor ION Desk User Guide-Cloud Edition and Infor ION Development Guide-Cloud Edition on Infor Support Portal.
For more information on Application Engine and how to create Application Engine scripts and processes, see the Application Engine section of this documentation.