Deactivating a data flow
Deactivation stops the subscriptions of documents to the receiving applications. This topic helps you to understand the consequence before deactivating a data flow.
When a data flow is deactivated, some unprocessed messages for the receiving applications can still be present. These messages are not processed. To process all messages before deactivation, we recommend to pause the source connection point.
See Pausing message processing of connection points.
Pausing stops new messages from entering ION. After pausing the source connection point, go to the Active connection points status page and ensure that all pending messages are processed. Only then proceed to deactivate the data flow.
A connection point is deactivated only when all data flows, where the connection point is used, are deactivated. Documents and transactions are not processed anymore by that connection point. All schedulers of the specific connection point are stopped, IMS connection point is rejecting incoming messages. No new messages enter ION.
Even though a data flow is deactivated, the associated connection point that is used in that flow can still be active. It can be used in other active data flows. The scheduler is still running and new messages configured in the deactivated document flow can enter ION. These messages are not routed by the deactivated flow. When you reactivate the same flow again, the messages that are entered in the intermediate window of deactivation to activation are not processed. To prevent this we recommend that you pause the source connection point. New messages are stopped from entering ION. Now you can proceed with the deactivation. No messages are missed.
Not all scenarios require a deactivation. Most configurations can be refreshed with a single step reactivate action than with an explicit + . This ensures that no messages are missed.
To deactivate a data flow: