Active connection points
Click the hamburger icon to open the menu. Select .
This page shows the connection points that are active.
For each active connection point these details are displayed:
- Information from the model:
- Type: the type of the connection point (application, database, web service, file or message queue).
- Name: the name of the connection point as specified in the model.
- Logical ID: the logical ID of the connection point, which is derived from the type and the name.
- Status information from the ION Service:
- Timestamp: the date and time from when the displayed status was retrieved.
-
Status: the
current status of the connection point in the ION Service. The status is OK
if:
- The connector is available and, for application connection points, a connection to the application can be established.
- The polling daemon is running to read messages from the application's outbox.
If one of the criteria is not met, then the status is Error. Note that an Error status does not indicate a persistent failure. It can also mean that a connection is temporarily unavailable or the application server is busy and does not respond.
- Pause status of connection point from the ION Service:
- Receiving Paused: Use this option to pause the delivery of messages to the connection point.
- Sending Paused: Use this option to pause the pickup of new messages from the connection point.
- Statistics from the ION Service on handled and unhandled messages:
- Pending (Incoming Pending Messages): the number of messages that are sent to the connection point, but not yet delivered. They are waiting because no connection can be established, or because the connection point is still busy processing older messages.
- Received Unprocessed: the number of messages that are posted in the in-box of the connection point, but not yet processed. The status in the in-box is 0. This is only relevant for application connection points of type Infor Application and Cloud 2.0, because other types of connection points do not use an in-box. For Cloud 2.0 this indicates the number of messages already sent from the on-premises ION to the Cloud application but not yet processed by the Cloud application.
- Received: the number of messages that are received and processed by the connection point. Note that this counter increases when connector internally processes a message for the next step. Though the actual transaction can still be in progress by the server. If an incoming BOD resulted in a Confirm BOD being published, then the incoming BOD is also counted as processed.
- Sent Unprocessed: the number of messages that are sent from a connection point but are not yet processed by ION. This is not relevant for database and web service connection points, because they are based on a schedule. The resulting BODs are immediately handled in the ION Service. For Cloud 2.0 this indicates the number of messages that are sent by the Cloud application but not yet processed by the on-premises ION.
-
Sent No Route:
the number of messages that are sent from a connection point but not
relevant for any other party. No document flow exists for these messages and
they are not relevant for Workflow
or Event Management.
Only messages that were not archived by OneView archiving are counted. The OneView history retention – Complete limit is used.
For more information on types of OneView history retention days, see the Infor OS Service Limits.
You can find the messages in OneView with the Processing Exception filter set to No route.
-
Sent (Sent Processed
Messages): the number of messages that were sent and handled
in the ION Service. There are several
options for these messages:
- Processed in the final destinations.
- Incoming pending messages.
- Unprocessed messages for another connection point.
- Incoming pending messages for a mapping, content-based routing or filter.
A processed message can result in a Confirm BOD, when the message was incorrect or the processing in a next step of the flow failed.
- In the details view of an Application connection point, these categories are
displayed:
- Sent Processed Messages in Outbox: the number of sent processed messages that still exist in the Outbox. These messages have status 1 and remain in the outbox until they are cleared. This is only relevant for application connection points of type Infor Application. Other types of connection points do not use an outbox or do not keep processed messages in the outbox.
- Received Processed Messages in Inbox: the number of processed messages that still exist in the in-box. These messages have status 1 and remain in the in-box until they are cleared. This is only relevant for application connection points of type Infor Application, because other types of connection points do not use an in-box.
-
Note:
- The statistics are empty if they are not applicable for the connection point. For example, The Sent Processed Messages in Outbox are empty for database and web service connection points. The statistics can also be empty if the connection point has status Error, because the ION Service cannot always determine the correct value then.
- The messages are counted since the (first) activation of the connection point. The counters for messages in in-box and outbox and the incoming pending messages do not hold any historic data. They show the current number of entries that exist in the in-box or outbox.
- Use the Active Data Flows page, to view the message statistics for mappings, content-based routings and filters.
The status and statistics information are automatically refreshed using a configurable time interval from the setting Automatic counter update.
Refreshing is done per connection point. The data is gathered asynchronously. Therefor not all counters are displayed simultaneously. For some connection points it can take longer than the refresh interval before the counters are displayed. The previous counters are displayed although the new values are not available. The automatic refresh does not update the list of connection points. For example, connection points that are activated or deactivated meanwhile are not shown in the list automatically.
The automatic refresh does not update the list of connection points. For example, connection points that are activated or deactivated meanwhile are not shown in the list automatically.
To refresh the data on demand, click . Results for each of the listed connection point is displayed after they are available from ION Service. The manual refresh action also refreshes the list of connection points.
To display more details for a connection point, select the connection point and click . Or double-click the connection point.
To display a list of active data flows that use the connection point, select the connection point and click .