osb thread management brief explanation

if you are wondering with the threads in request-response pipelines, this shorty brief explanation is enough for developers and operator for defining the rules.

In Oracle Service Bus, several transports for proxy and business services provide a configuration option called "Dispatch Policy" that lets you associate a Work Manager with a service to prioritize service work. This section describes how proxy and business services use Work Managers.

By configuring the Dispatch Policy of an Oracle Service Bus proxy service, the startup and execution of its request pipeline are governed by the rules of the Work Manager. For example, given a proxy service using a Dispatch Policy with a Max Constraint of 5, the proxy service will have no more than 5 request pipeline tasks executing simultaneously.

While the request pipeline is governed by the proxy service's Dispatch Policy, the response pipeline is governed by the business service or Split-Join Dispatch Policy. The RouteTo action specifies a business service or Split-Join to route the message to, and the response is subject to any Dispatch Policy on that business service or Split-Join.

When a RouteTo action specifies a local proxy service, the Dispatch Policy of the original proxy applies to work done in the local proxy's request pipeline. When the local proxy or chain of local proxies reaches a RouteTo action that invokes a business service or Split-Join, the business service, Split-Join, and all the following response pipelines are governed by the Dispatch Policy of that business service or Split-Join.

http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/modelingmessageflow.htm#OSBAG1428