Integrations, triggers, and orchestration styles
Domain 3 - Integrations, triggers, and orchestration styles
This domain tests style selection, trigger behavior, and orchestration activities. The exam expects you to match a business event to the right style and to know which constructs can start or stop an instance.
Core rules
- App Driven Orchestration is used for event- or request-driven flows. The trigger can be a REST, SOAP, SaaS, file, FTP, or JMS trigger; the flow can return a synchronous response or continue asynchronously.
- Scheduled Orchestration starts from a schedule, not an adapter trigger. It is used for polling, batch imports, and recurring jobs. The schedule is part of the integration, so activation starts the clock.
- Basic Routing is a lightweight style for content-based routing. It is not the place for complex multi-step orchestration or heavy transformation.
- Common activities include Invoke, Map, Assign, Switch, For Each, While, Scope, Fault Handler, Notification, Wait, and Stop. A Scope groups activities and can have its own fault handler.
- Synchronous flows return the response on the original call. Asynchronous flows return a receipt and later deliver a response through a callback; the caller must correlate it.
Worked example
A REST client submits an order and needs an immediate confirmation. Use App Driven Orchestration with a REST trigger. Validate the order, invoke the ERP connection to create the sales order, map the ERP order number, and return it in the response. If the ERP call takes minutes, return a receipt and use an asynchronous callback instead of holding the client connection open.
Traps
A Scheduled Orchestration cannot receive a REST request. Basic Routing does not replace a full orchestration. An invoke connection cannot be the trigger. Asynchronous callers must handle callbacks and duplicate delivery, and a Stop activity ends the instance rather than continuing the branch.