SOA Web Services - Runtime Patterns for Broker

Runtime Patterns for Broker

As in the case of application patterns discussed earlier, a broker may be introduced in the runtime nodes, which will act as a message distributor. A source application connects to many target applications through a broker.

A typical configuration for this pattern that uses a router to connect to multiple target applications is shown in the following figure.

As in the case of application patterns, the router defines the rules for routing the consumer requests to one of the target applications. During the call, the router converts the transport protocols between the consumer and the provider. It also transforms the message formats between the two parties.

Another variation of this pattern is shown in the following figure.

In this case, the router connects to the service bus and is responsible for transforming a service request from one protocol to another. For example, an HTTP call may be converted to a JMS call or an RMI-IIOP call.

Again, a service registry may be implemented by creating a Rules Repository node for clients to discover the services.

Having studied the various business and application patterns for SOA implementation, we will now look at the implementation of SOA in B2B and EAI domains.