Join and Spawn Activities
The join and spawn activities are used together. Use the join activity to wait for subprocesses to be merged. Use the spawn activity to start up a new process from within an existing process.
The join waits only for the subprocesses initiated from the same process in which the activity is run.
The syntax for the spawn activity is simple:
<spawn ref='another process'/>
The ref attribute must match the name of a process in Sterling B2B Integrator. After this process is run, a new instance of a business process is created and run. The child process starts off with a copy of process data from its parent. The two processes are completely independent of one another—the original process will not wait for the spawned process to complete unless you explicitly configure it to.
The original and spawned processes can communicate using the produce and consume activities.