7: CCM_Streaming

The process has this structure:

1. Loop body script, or the CCM_DoStreaming script, which relies on the Run function of the Streaming component for processing a single stack. The order to process stacks is not determined. For more information on the Run function, see Run function in streaming.
2. Surrounding loop, which ensures that the CCM_DoStreaming script is called repeatedly.

Loop body script

The CCM_DoStreaming script calls the Run function and monitors the result:

• If a stack is processed successfully, the script ends.
• If no stack is found, the script waits five seconds, and then ends.
• If an exception marked as Handled is thrown, the script ends.
• If an exception is thrown that is not marked as Handled, the script throws an exception.

When the script ends normally, the surrounding loop immediately calls the script again. Therefore, as long as stacks are available for streaming, they are picked up one by one without delay. If no stack is available, the next check is delayed for five seconds.

Surrounding loop

The surrounding loop continues indefinitely until the process receives a Stop or Cancel signal, or the CCM_DoStreaming script throws an exception. As long as the CCM_Streaming process is running, stacks are continuously streamed.

It is safe to run multiple streaming processes simultaneously, even if they transform stacks from the same run-time database.