Integration with your local applications

You can use the Enterprise Connector to integrate your local deployed applications with ION. The Enterprise Connector currently supports these types:

  • Infor Application connection point

    Defines a connection from ION to a local application that can send and receive messages. The messages are sent using Outbox tables and received using Inbox tables. ION connects to the Inbox and Outbox through JDBC.

    For configuration details, see Application connection points.

  • IMS connection point

    Defines an ION Messaging Service based connection point that can send and receive messages. The communication is https and REST based.

    For configuration details, see Application connection points.

  • Infor LN/Baan connection point

    A special type of application connection point that connects to a local LN/Baan system. The connection is made from the Infor LN/Baan connection point created through the Enterprise Connector to the LN application. The typical connection information of Infor LN, such as the hostname, BSE environment, username, password, and Bshell, is used.

    The Maximum processing time per message property in the Infor LN/Baan connection point defines the timeout for the processing of a single message. If there is no response from Infor LN/Baan after this time, processing of this message is stopped and a Confirm BOD is generated. ION continues with the processing of the next message. A timeout can happen if the message processing in LN is taking more time than the defined limit, or if the bshell does not respond anymore.

    When using the channels to enable parallel processing, the maximum number of bshells allowed per channel is limited to 10.

    For details about configuring an Infor LN/Baan connection point, see the Infor LN Configuration Guide for Infor ION in Infor Support Portal KB 22945150.

  • File connection point

    Defines a connection from ION to a local application that cannot send or receive messages, but can create/process files. The connection is made from the File connection point through the Enterprise Connector to the local File application. It supports connecting to a local file server using FTP or SFTP and to a local Windows shared folder. For details about configuring a File connection point, see the Infor ION Technology Connectors Administration Guide.

  • Database connection point

    With the Database Connector you can connect applications that cannot send or receive documents, but have a database available.

    In this way, you can retrieve data from a database and send it to one or more Infor applications. Or you can use data from Infor BODs to update your database.

    There are two types of database connection point:

    • Stored Procedure
    • AnySQL Modeler

    With the Stored Procedure type you can call stored procedures that are defined in your database, pass inputs, and receive output in the form of Infor BODs.

    With the AnySQL Modeler you can create SQL select statements to read data from a database in visual modeler with minimum knowledge of SQL language. Learning specifics of each database protocol is not required. The same modeling experience is used for each of the supported database server types. Output is provided in the form of JSON documents.

  • Message Queue Connection Point

    You can use connectivity through message queues.

    You can create a connection point to read or write a message queue. The Message Queue Connector of ION Enterprise Connector acts as a JMS client.

    A connection point that is configured as a JMS Client, enables ION to directly connect to external JMS queues that are provided by other vendors. Messages are transported back and forth.

    The use of this connection type requires a JMS BundleWrapper. For details, see the Infor ION Technology Connectors Administration Guide.