A real-time session runs continuously unless it fails or you manually stop it. You can stop a session by issuing a stop command in
or from the Workflow Monitor. You might want to stop a session to perform routine maintenance.
When you stop a real-time session, the Integration Service processes messages in the pipeline based on the following real-time sources:
JMS and WebSphere MQ.
The Integration Service processes messages it read up until you issued the stop. It writes messages to the targets.
MSMQ, SAP, TIBCO, webMethods, and web service messages.
The Integration Service does not process messages if you stop a session before the Integration Service writes all messages to the target.
When you stop a real-time session with a JMS or a WebSphere MQ source, the Integration Service performs the following tasks:
The Integration Service stops reading messages from the source.
If you stop a real-time recovery session, the Integration Service stops reading from the source after it recovers all messages.
The Integration Service processes messages in the pipeline and writes to the targets.
The Integration Service sends an acknowledgement to the source.
The Integration Service clears the recovery table or recovery file to avoid data duplication when you restart the session.
When you restart the session, the Integration Service starts reading from the source. It restores the session and transformation state of operation to resume the session from the point of interruption.
If the real-time session hangs after you stop it, the session might remain in a stopping state. You can abort the real-time session if it remains in stopping mode. The Integration Service processes the messages that it read before you issued the stop.