The closedown process flow, if configured, is executed immediately before iSM is shut down. All listeners and channels are closed, but providers remain available. The result of this process flow is ignored, and a shut down of iSM proceeds regardless of the actions taken by the process flow. In a sample scenario, the closedown process flow can be used to send a notification to an administrator that iSM has shut down, releasing resources as a result, and so on. You can use an internal emit to send a start up message to a persistent internal queue to be acted upon whenever iSM is started again. You cannot use the Controls Channel Service (com.ibi.agents.XDControlAgent) to manage channels or otherwise affect iSM.