Oracle Service Bus Federation With JMS Store-and-Forward and Dynamic Routing in SOA

It is important to know the architecture, design, and configuration of the federation of Oracle Service Buses before implementation. This paper looks at an architecture where two peripheral clustered domains initiate request-response communication with the a third, central and domain. The peripheral domains use SAF to transmit the requests. The central domain uses SAF to transmit responses back to the peripheral domains. Oracle Service Bus JMS is an enterprise-class messaging system that supports the Java Message Service (JMS) specification JMS 1.1, and also provides numerous extensions to the standard JMS APIs. It is tightly integrated into the Oracle WebLogic Server platform so one can build secure Java EE applications that can be monitored and administered through the Oracle Service Bus console. There are three common deployment topologies: Distributed Hubs (responsible for routing to each other, with no central coordinator), Enterprise Hub (a centralized enterprise OSB domain serving as a central coordinator), Composite Model (a combination of both the Enterprise and Distributed scenarios). The goal of this paper is to show that Oracle Service Bus is designed with flexibility to form federations. They want to encourage IT departments to take advantage of the network of Service Buses at the onset of the deployments. That would be the right strategic approach in the anticipation of the future growth of the IT infrastructure.