[CONF] Apache ServiceMix: NMR Flows (page edited)

[confluence]

Page Edited : SM : NMR Flows NMR Flows has been edited by Eric Johnson (Mar 12, 2008). (View changes) Content: ServiceMix allows for different message dispatch policies within the Normalized Message Router (NMR) Broker. There are four basic types, that have different characteristics and are suited to different usage cases. They are as follows: Straight-through (ST) Flow A MessageExchange is routed straight to it's destination with no staging or buffering. A straight through flow is best suited for the cases where the ServiceMix JBI Container is deployed with simple flows (no state) or embedded, or where latency needs to be as low as possible. ST Flow Seda Flow The Seda Flow introduces a simple event staging between the internal processes in the NMR Broker. A Seda flow, which is the default flow used by most components, is suited for general deployment. The additional staging is well suited buffering exchanges between heavily routed to components (where state may be being used) for example. Seda Flow JMS Flow A JMS Flow is used for cases where you need collaboration between more than one ServiceMix JBI Container (for fail-over or scalability). Component deployment happens in the same way as a normal SericeMix JBI container (both for POJO and archive Component deployment) but all the containers in the cluster are notified of a deployment, and the JMS Flow will handle automatic routing (and failover) of MessageExchange(s) between the container instances. A Message Queue is used for each JBI endpoint, so multiple instances of the same named Component will have requests load balanced across them. JMS Flow JCA Flow The JCA Flow is very similar to the JMS Flow, in that it allow to cluster ServiceMix containers together. The main difference is that it uses JCA to provide support for XA transactions when sending and receiving JBI exchanges. You can find more informations on transactions here. Configuring flows In versions of ServiceMix prior to 3.3 Flows were configured on the JBI container by usually using the flowNames attribute on the main container element. <sm:container flowNames="seda"> ... </sm:container> JMS and JCA flows should be configured with an ActiveMQ url to the broker. <sm:container flowNames="jms?jmsURL=tcp://localhost:61616"> ... </sm:container> You can define several flows by using a comma separated list. <sm:container flowNames="seda,jms?jmsURL=tcp://localhost:61616"> ... </sm:container> For more complex configuration, you define the flow explicitly. This method is also the recommend method for configuring flows in ServiceMix 3.3 and later. <sm:container> <sm:flows> <sm:sedaFlow /> <sm:jcaFlow bootstrapContext="#bootstrapContext" connectionManager="#connectionManager" jmsURL="vm://localhost" /> <sm:jmsFlow jmsURL="tcp://localhost:61616" /> </sm:flows> </sm:container> See also: How Stuff Works

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences