You can view the state of a collaboration object either by logging on to System Monitor and opening a view that contains collaboration object information or by using the InterChange Server Component Management view in System Manager. To log on to System Monitor, follow the instructions in Steps for logging on to System Monitor.. To use System Manager, follow the instructions in Steps for connecting to an InterChange Server Express instance..
The state of a collaboration object is represented differently, depending on which tool you are using.
Perform the following steps in System Monitor to view the state of collaboration objects:
When the product is installed, the default view is set to System Overview, and the default monitor contained in that view is set to System Overview. These defaults can be changed to suit your monitoring needs. See Setting up views to monitor the system for instructions.
Figure 29. System Monitor, System Overview displaying collaboration object status
Perform the following steps in System Manager to view the state of collaboration objects:
The collaboration objects appear under the expanded Collaboration Objects folder with different colored lights to indicate their different states (see Figure 30.
Figure 30. Collaboration Objects folder in the InterChange Server Component Management view
Table 9 describes the collaboration object states that are viewable
from System Monitor and the Collaboration Objects folder in the InterChange
Server Component Management view:
Table 9. Collaboration object states
Collaboration object state | Description |
---|---|
Start | A started collaboration subscribes to its triggering business objects and processes them as they arrive. If you stop and then restart InterChange Server Express, collaboration objects in the Start state automatically start running when InterChange Server Express restarts. |
Pause | A paused collaboration cannot receive new flow initiators. It
completes all of the current processing, then enters an idle state.
A connector maintains its subscription information; therefore, it continues to send flow initiators to the connector queues. The collaboration processes these when it resumes. To resume collaboration execution, click Start in System Monitor or in the Collaboration Object menu in the InterChange Server Component Management view. |
Stop | Stopping a collaboration causes it to unsubscribe to business
objects. The collaboration completes all of the current processing,
then becomes inactive. Unlike the Pause command, the Stop command
causes connectors to stop sending business objects to the
collaboration.
To properly stop a collaboration without losing any flows, first stop the associated connectors from polling, allow all flows to process, then stop the collaboration. |
Shut Down | Shutting down a collaboration immediately ends processing of current flows. When the collaboration is restarted, the system recovers by processing those flows that were interrupted by the shut down and recovering those flows waiting in the queue. This recovery is not immediate, so prepare to wait when the system completes the recovery interval. |