Which starting method would you use for a scenario: Starting Multiple Processes at Once with MNI that needs to run on multiple Execution Engines?

Which starting method would you use for a scenario: Starting Multiple Processes at Once with MNI that needs to run on multiple Execution Engines?

• A. Subprocess(synchronous)
• B. Subprocess(asynchronous)
• C. Start Process smart service
• D. Start Process

Answer: (C)

Starting multiple independent processes across different Execution Engines requires a mechanism that can programmatically spawn several process instances, rather than nesting a single subprocess inside one flow. The Start Process smart service is designed for that purpose. It lets you start a new instance of a specified process model, pass input parameters, and run asynchronously if you want to avoid blocking the initiator. Because you can trigger many starts in parallel (for example, within a loop or a control structure that leverages MNI), you can distribute the workload across multiple Execution Engines effectively. Subprocess nodes are intended to run a child process model within the context of the current process instance. They execute on the same engine and are generally used for modularizing a single process flow, not for launching many separate processes across engines. The standard Start Process node, used inside a process model, starts one process instance and is also bound to the current engine, making it less suitable for multi-engine, parallel initiation. So, for starting multiple processes at once with MNI across multiple Execution Engines, the Start Process smart service is the best approach.

Starting multiple independent processes across different Execution Engines requires a mechanism that can programmatically spawn several process instances, rather than nesting a single subprocess inside one flow. The Start Process smart service is designed for that purpose. It lets you start a new instance of a specified process model, pass input parameters, and run asynchronously if you want to avoid blocking the initiator. Because you can trigger many starts in parallel (for example, within a loop or a control structure that leverages MNI), you can distribute the workload across multiple Execution Engines effectively.

Subprocess nodes are intended to run a child process model within the context of the current process instance. They execute on the same engine and are generally used for modularizing a single process flow, not for launching many separate processes across engines. The standard Start Process node, used inside a process model, starts one process instance and is also bound to the current engine, making it less suitable for multi-engine, parallel initiation.

So, for starting multiple processes at once with MNI across multiple Execution Engines, the Start Process smart service is the best approach.