Connections

Connections are what Infor OS uses to communicate with products, both Infor and non-Infor.

A connection to or from Infor OS is accomplished by a connection point defined either in ION or an API suite defined in the API Gateway. Both connection points and API suites can be active, ready to do work as soon as the correct event occurs, or inactive where they cannot do any work. The existence of any active connection points or API suites counts as a connection. The connections can be used for integrations but also for any other use cases. For example, the API suite may be used by a custom Mongoose application, a custom widget, an in-context app, and so on.

Some examples of connection counting:

Integration with product A via APIs and integration with product B via SFTP

  • An API-based integration with product A via an API suite counts as one connection.
  • An SFTP-based integration defined in a connection point with product B counts as one connection.

In total, two connections are required.

Custom Mongoose application using an API suite over an API for product C and an integration with product C via SFTP

  • An API-based connection to product C via an API suite counts as one connection.
  • An SFTP-based integration defined in a connection point with product C counts as one connection.

In total, two connections are required.

Custom Mongoose application using an API suite over an API for product D and an integration with product D via APIs

  • An API-based connection with product D via an API suite counts as one connection.
  • The API-based integration defined in a connection point uses the same product D API suite, so the connection has already been counted.

In total, one connection is required.

Therefore, based on the examples above:

An active Infor connection is any connection in an active state that connects to an Infor product.

An active non-Infor connection is any connection in an active state that connects to a non-Infor product.