Mule scopes async_scope

Mule scopes async_scope

• 1.
  Mule Concepts Scopes Async Scope
• 2.
  • A branchprocessing block that executes simultaneously with the parent message flow. • can prove useful for executing time-consuming operations (such as printing a file or connecting to a mail server) — as long as those operations do not require sending a response back to the initiating flow. • The main flow can continue execution while it initiates and processes the asynchronous scope. • It does not have to pause until the last message processor embedded in the asynchronous flow has completed its task. Async Scope
• 3.
  • The simultaneousbranch processing - How does it work: – The async scope sends one copy of the message it has received to the first embedded message processor in its own processing block. – at the same time it sends another copy of the message to the next message processor in the main flow. Async Scope
• 4.
  • Async scopescannot, by definition, support request-response exchange patterns, Since they operate on a copy of the message on a different thread. • Instead, they must implement one of several supported one-way processing strategies. • If no processing strategy is configured for the async scope, Mule applies a queued- asynchronous processing strategy. Async Scope
• 5.
  1.Drag the asyncscope to the canvas and position it within the sequence of message processors that make up your flow at the point where you want to initiate an asynchronous processing block. Async Scope - Configuration
• 6.
  2. Within thescope area, add and configure the sequence of message processors that you want to execute asynchronously with the main flow. Async Scope - Configuration
• 7.
  3. Optionally, configurethe async scope itself with a Display Name. If you wish to specify a Processing Strategy, you can specify it Async Scope - Configuration
• 8.
  • Configuring aProcessing Strategy : – Configuring a processing strategy is optional. – Mule applies the queued-asynchronous processing strategy to the scope by default, unless a different one is applied. Async Scope - Configuration
• 9.
  • Available ProcessingStrategies : – Queued-Asynchronous Processing Strategy: • Uses a queue to decouple the flow’s receiver from the rest of the steps in the flow. • Works the same way in a scope as in a flow. • Mule applies this strategy unless another is specified. • Select this to fine-tune this processing strategy by: – Changing the number of threads available to the flow. – Limiting the number of messages that can be queued. – Specifying a queue store to persist data. – Asynchronous Processing Strategy : • Same as queued-asynchronous processing strategy, except that it doesn’t use a queue. • To be used only if you do not want your processing to be distributed across nodes. Async Scope - Configuration
• 10.
  • Available ProcessingStrategies : – Queued Thread Per Processor Processing Strategy: • Writes messages to a queue, then every processor in the scope runs sequentially in a different thread. • Not applicable to most use cases. – Thread Per Processor Processor Strategy: • Every processor in the scope runs sequentially in a different thread. • Not applicable to most use cases. – Custom Processing Strategy : • A user-written processor strategy. Async Scope - Configuration