Shutting down InterChange Server Express stops all running collaborations and connectors and InterChange Server Express itself. All connections to the database are closed and the machine's system resources used by InterChange Server Express are returned.
Perform the following steps to shut down the server gracefully:
Gracefully shutting down the system allows all currently processing and queued flows to complete before shutting down. This may take a long time because all flows waiting to be processed by a running collaboration must complete. Existing flows are processed by the collaborations, but no new flows are accepted.
If you want to gracefully shut down the system, the following occurs:
If the collaboration object is a member of a collaboration group, all collaboration objects in the group stop.
If messages from the connectors are in transit to the collaboration object when it stops, they remain in the messaging queues until the collaboration object starts.
Perform the following steps to shut down the server immediately:
Immediately stopping the system forces the system to shut down without processing any more flows. Running connectors and collaborations are stopped immediately. When the system is restarted, flows that were interrupted by the immediate shutdown are redelivered in the same processing order. If one of these flows wrote data to an application, when the flow is redelivered, it tries to duplicate the data and fails because the data already exists. If the collaboration processing the flow is transactional, a rollback occurs. If the flow is not transactional, it is moved to the resubmission queue. See Flow failures for more information on submitting a flow that fails to process.
Use this option when you need to quickly shut down the system. For example, you may want to reboot the system, but a collaboration has multiple events waiting to be processed. Shutting down gracefully may take too much time because the collaborations need to complete all existing work before stopping.