File connection points

The file connection point defines a connection from ION to an application that cannot send or receive BODs, but can create / process files.

In this way, data can be retrieved using files that are processed in ION and then sent to one or more Infor applications. In addition, ION can create files using data from Infor BODs, JSON, DSV or ANY documents that can be processed by other applications. In a document flow, a file connection point can be used in a similar way as any other type of connection points.

The message size limit for an individual message is 5 MB in all versions of ION. As of May 2020, there are new license tiers available that have increased usage limits for the individual message size. From this date, there is also a 1 MB buffer available to all customers to provide flexibility and to prevent over-size message warnings for just a few bytes over the 5 MB limit.

In a document flow, a file connection point can be used in a similar way as any other type of connection points. Data from a file is packed as a ION document in the ION Service. All documents with BOD type can be delivered to any other connection point or used in:

  • An event monitor.
  • Workflow activation policy.
  • Document flow mapping.
  • Content-based routing.

Support for other document types such as JSON, DSV or ANY is added throughout ION. For information about support in a specific ION component, see the appropriate section in the documentation.

Data from any connection point can be converted to a file.

Each file has its own structure and format. To use a file connection point, an ION document or a file template must be defined. The document defines schema and properties of the file. The template describes what type of files are processed and how the content is mapped to a BOD.

A file connection point can handle files in two ways. It can:

  1. Use the file content as is. In that case no transformation is done on the file content. The content can be of type BOD, JSON, DSV or ANY.

    For details on these types, see the Infor ION User Guide.

  2. Transform the file content to and from BODs. In that case a file template is used. Each file has its own structure and format. The file template describes the ‘schema’ of a file.

    See File templates.

A file connection point specifies:

  • The standard properties for any connection point, such as name and tenant. Note that for file connection points the logical ID type is fixed ('file'). The logical ID is lid://infor.file. followed by the connection point name. In the logical ID, the characters from the name are converted to lowercase.
  • The protocol and connection settings to access the file system.
  • Which documents are sent and received and how the file is read or written.

The connection properties in a file connection point are described in Connection properties.

To create a file connection point, see Infor ION User Guide.

After setting the connection properties, click Test. You are informed whether the test is successful and if the connection details are correct.

If you selected the Shared Folder transfer protocol, the path to the shared folder is not yet known. Clicking Test is then testing the connectivity to the host, not validating the connection details.

The name of the shared folder is defined in the Documents tab. The shared folder's user name and password and the SMB settings can only be tested for the specified read or write scenarios.

Note: 
  • In an ION CE ION, the file connection points that are provisioned for you by Infor Cloud Operations do not show connection parameters.
  • Infor is not responsible for files and their maintenance in shared folders and on FTP/sFTP servers. Files must be maintained by their owners.