Horizontal behavior of shared I/O boxes

This section describes horizontal behavior of ION when configuring connection points that share a multi-tenant or a multi-logical ID I/O box.

Horizontal behavior of shared I/O boxes happens:

  • When the message processing preference by tenant or by logical ID is marked as false, ION will process all messages. The messages that cannot be processed are marked with status code 9 in the outbox. You can let the connection point process only those messages that belong to its tenant or logical id. Other messages that do not match this criteria are not processed. When you publish a message in your outbox with a tenant or logical id in the header that does not match any connection point, these messages are left unattended in the outbox. The application must take action.
  • All the metrics displayed in the active connection points show counters applicable to a specified connection point. These values are different than the total count of processed/ unprocessed messages in the inbox or outbox.
  • While a connection point is activated to process messages by tenant or by logical ID, it can happen that this functionality is not supported yet by the application or by the ION Service. This can be the cause:
    • The version 3.0 scripts are not run on the I/O box table.
    • You imported a connection point with the value true into an ION 11.1.0 or 11.1.1 environment.
    • You registered a dynamic database driver with ION that does not support this functionality.

      In these cases you receive an error while testing or activating the connection.

  • Until ION version 11.1.1, the tenant value in the BODs delivered by third party connectors to the Infor application connection point was in upper case. From ION version 11.1.2 onwards the tenant value preserves the case as specified in the third party connection point.

    To continue receiving BODs with upper case tenant value, edit the connection point accordingly and reactivate.