# Infor ION Connection Point Types Reference (On-Premises and Cloud) > Source: https://netray.co/tools/infor-ion-connection-point-types-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Compare ION connection point types by edition, how messages move, document types supported, Enterprise Connector need and typical use. ## Category developer ## Erp Infor ION ## Audience - ION administrator - Integration developer - Infor OS architect ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Connection point type **Key:** type **Type:** text #### Edition **Key:** edition **Type:** text #### How messages move **Key:** how **Type:** text #### Document types **Key:** docs **Type:** text #### Enterprise Connector (Cloud)? **Key:** ec **Type:** text #### Best for **Key:** best **Type:** text #### Watch-outs **Key:** watch **Type:** text **Rows:** **Type:** Application - inbox/outbox (I/O box) **Edition:** On-premises; Cloud through Enterprise Connector (Infor Application connection point) **How:** Application writes to COR_OUTBOX_ENTRY / COR_OUTBOX_HEADERS; ION reads them and delivers to COR_INBOX_ENTRY / COR_INBOX_HEADERS **Docs:** BOD **Ec:** Yes **Best:** Infor applications that use the database I/O box **Watch:** ION does not purge the inbox tables; the application must, or the database fills up **Type:** Application - IMS (bidirectional) **Edition:** On-premises and Cloud **How:** ION Messaging Service: application and ION exchange messages over HTTP(S) in both directions **Docs:** BOD **Ec:** Yes when the application is on premises **Best:** Current Infor applications that support IMS **Watch:** Configure both directions and test each **Type:** Application - IMS (unidirectional) **Edition:** On-premises and Cloud **How:** One-direction IMS configuration; see the guide for polling properties **Docs:** BOD **Ec:** Yes when the application is on premises **Best:** Flows that only need one direction **Watch:** Check polling properties **Type:** Application - IMS via ION API **Edition:** On-premises and Cloud (IMS via properties) **How:** IMS traffic routed through the ION API Gateway with an authorized app **Docs:** BOD **Ec:** No **Best:** Cloud or hybrid applications that already use ION API **Watch:** Needs an authorized app and credentials **Type:** Infor LN / Baan connection point **Edition:** On-premises; Cloud through Enterprise Connector **How:** Connector specific to Infor LN and Baan **Docs:** BOD **Ec:** Yes **Best:** On-premises LN and Baan systems **Watch:** Match the logical ID to the LN company setup **Type:** File **Edition:** On-premises; Cloud through Enterprise Connector **How:** Read and write file actions against configured file locations, with file templates, optional encrypt and decrypt **Docs:** BOD, JSON, ANY, DSV **Ec:** Yes **Best:** ERPs without BOD support that can export or import files **Watch:** File name pattern restrictions; files must be complete before pickup **Type:** File (SFTP from Cloud) **Edition:** Cloud **How:** ION in the cloud reads from and writes to an SFTP server **Docs:** BOD, JSON, ANY, DSV **Ec:** No **Best:** Partners or sites that expose SFTP **Watch:** Firewall and key management on the SFTP side **Type:** Database **Edition:** On-premises; Cloud through Enterprise Connector **How:** ION runs read and write statements against a database through JDBC on a schedule **Docs:** BOD **Ec:** Yes **Best:** Older ERPs with no BOD support, staging tables **Watch:** Mark rows as processed in your read logic to avoid resending **Type:** Database - AnySQL modeler **Edition:** On-premises (read action) and Cloud (AnySQL connection point) **How:** Model a read with SQL instead of a fixed table mapping; object schemas can be generated **Docs:** BOD **Ec:** Yes when the database is on premises **Best:** Reading from views or joins **Watch:** Keep queries indexed; they run on a schedule **Type:** Message Queue (JMS) **Edition:** On-premises; Cloud through Enterprise Connector **How:** ION acts as a JMS client to a vendor queue (vendor driver uploaded) **Docs:** BOD **Ec:** Yes **Best:** Sites with an existing JMS broker **Watch:** Vendor client jars must be prepared and deployed **Type:** API connection point (ION API connection point on premises) **Edition:** On-premises and Cloud **How:** Calls REST APIs, including those exposed through ION API, as a step in a data flow **Docs:** BOD, JSON, ANY **Ec:** No **Best:** Calling a REST API from a data flow **Watch:** Not for delimited (DSV) documents **Type:** ION Network **Edition:** Cloud and on-premises **How:** Exchanges documents with another tenant or partner over the ION network **Docs:** BOD, JSON, ANY, DSV **Ec:** No **Best:** B2B with partners on Infor OS **Watch:** Partner must accept the connection **Type:** Web service **Edition:** On-premises **How:** Web service connection points managed in ION Technology Connectors **Docs:** See guide **Ec:** Not applicable **Best:** Legacy SOAP integrations **Watch:** Consider API connection points for new work **Type:** Infor Cloud (1.0 / 2.0) connection points **Edition:** On-premises **How:** Connects an on-premises ION to Infor cloud applications **Docs:** BOD **Ec:** Not applicable **Best:** Hybrid estates before moving ION to the cloud **Watch:** Version specific modelling **Type:** API flow (not a connection point) **Edition:** Cloud **How:** Chains REST calls synchronously and publishes them as one endpoint **Docs:** JSON **Ec:** No **Best:** Composite APIs **Watch:** 5-minute gateway time-out and payload limits **Type:** Data Lake activities (not a connection point) **Edition:** Cloud **How:** Data flow activities that query or retrieve from Data Lake **Docs:** As per activity **Ec:** No **Best:** Feeding analytics data into a flow **Watch:** Data Lake query costs and latency **Type:** Workflow, monitors, scripts (not connection points) **Edition:** Both **How:** Activities inside or beside data flows: workflow from data flow, monitors and alerts, ION Scripting **Docs:** BOD **Ec:** No **Best:** Approvals, alerts, transformation **Watch:** Keep logic out of connection points **Notes:** Type names follow the ION Desk and ION Technology Connectors guides (cloud 2026.x and on-premises 2023.x). The document type matrix (BOD, JSON, ANY, DSV) is from 'Document types supported by various connectors'. Enterprise Connector types per 'Integration with your local applications': Infor Application, IMS, Infor LN/Baan, File, Database and Message Queue. ## Content **Intro:** A side-by-side reference of the Infor ION connection point types, showing which edition offers each one, how messages move, which document types it carries and whether ION in the cloud needs the Enterprise Connector to reach it. Use it to pick the right connector before modelling a data flow. **Sections:** #### Picking a type for an on-premises ERP with no BOD support **Body:** If the ERP cannot produce BODs, ION can still integrate it. A File connection point picks up exports (BOD, JSON, delimited or any content) from a folder and writes files for imports, which suits ERPs with good flat-file tools. A Database connection point reads and writes tables or staging tables through JDBC; use the AnySQL modeler to read from a view or join. Both run where the data is: on premises directly, or, with ION in the cloud, through the Enterprise Connector installed on a local host. Prefer staging tables over writing into ERP tables so the ERP's own import validates the data. **Bullets:** - Can export files reliably: File - Has a database you can stage into: Database - Has a JMS broker: Message Queue - Has REST APIs: API connection point #### I/O box vs IMS **Body:** The older Infor application pattern uses database tables as an inbox and outbox: the application writes COR_OUTBOX_ENTRY and COR_OUTBOX_HEADERS, ION polls them and delivers into COR_INBOX_ENTRY and COR_INBOX_HEADERS. ION removes sent outbox messages (by default after a retention period, or immediately with Delete Processed Messages=true), but does not clean the inbox tables; the application must. IMS replaces the tables with direct HTTP(S) messaging between application and ION, bidirectional or unidirectional, which avoids polling delays and table growth. Newer Infor applications favour IMS. #### What the Enterprise Connector does for Cloud Edition **Body:** ION in the cloud cannot reach a database, file share or queue inside your network. The Enterprise Connector is a component you install on a local host (it runs on an Infor Grid) that connects outbound to ION in the cloud and runs the local connection points for it. Infor lists six types it supports: Infor Application, IMS, Infor LN/Baan, File, Database and Message Queue. Plan it like any server: sizing, memory for its components, certificates, proxy settings, log archiving, disaster recovery and upgrades, all documented in the ION Desk user guide. #### Testing and where errors show **Body:** Every connection point has a test action in ION Desk; run it after any credential or network change. Then activate the data flow and watch ION OneView, which shows each document's path through connection points with its status, and lists error messages you can mark handled. The connection points list also shows active connection points and lets you pause message processing while you fix a target system. For files, test with a small file that matches the file name pattern; for databases, run the read statement by hand first. **Cta:** If you want to connect an older on-premises ERP to ION, or put a private AI assistant on top of the data ION moves, we can design and build it. **Faq:** #### What is an Infor ION connection point? **Answer:** It is the configured endpoint ION uses to send or receive documents for one application or technology: an application (I/O box or IMS), file location, database, message queue, API or network partner. Data flows connect connection points with mappings, filters and routing in between. #### What is the Infor ION API connection point? **Answer:** It lets a data flow call REST APIs, including APIs exposed through the ION API Gateway, and supports BOD, JSON and any-content documents. On premises it is documented as the ION API connection point in the technology connectors guide. #### Do I need the Enterprise Connector on premises? **Answer:** No. With ION installed on premises, local connection points run directly on your ION servers. The Enterprise Connector is for ION in the cloud reaching applications, files, databases or queues inside your network, installed on a local host that connects outbound to the cloud tenant. #### Which connection points support JSON? **Answer:** According to Infor's document type table, File, Network and API connection points carry JSON. The inbox/outbox, Message Queue and Database types are BOD only. File and Network also carry delimited (DSV) and any-content documents, while API does not carry DSV. ## Search terms infor ion connection point, infor ion api connection point, infor ion enterprise connector, infor ion integration, infor ion on premise, ion iobox, ion ims connection point, ion database connection point --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json