Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

When more than one input stream is connected to an activity, Stream Selector is used to specify the input stream to be consumed by the activity. To understand the use of Stream Selector, consider the following process flow.

In this process flow, you can see that two input streams are passed to the File_Target. The desirable execution sequence is that first File_Source will be executed then File_Target and thereafter the Gateway. Now, if the condition specified at the Gateway is satisfied, the process flow will be finished. If the condition specified at Gateway is not satisfied, the control will be passed to the FTP _Source and further to File_Target. Practically, when this process flow will be executed, the File_Target activity will get confused whether to take input from File_Source or from FTP_Source. Thus, this process flow will fail.

To avoid such situation, Stream Selector is used. Streams from File_Source and FTP_Source are passed to the Stream Selector and then from the Stream Selector to the File_Target.

Stream Selector takes input from the activity that has just executed. If the File_Source has executed before the execution of the Stream Selector, it will take input from the File_Source. If the FTP_Source has just executed, it will take input from the FTP_Source.

To use Stream Selector:

  1. In Web Process Designer, click Repository View icon. All the items in the Activities list are displayed.
  2. Expand Selector.

  3. Click Stream Selector Service and drag it to the Canvas area. 



  4. Connect the required activities with the Stream Selector Service.

  • No labels