Oracle Service Bus JMS Integration Patterns

Oracle Service Bus integrates service end points using different transports and protocols. In this post I will explain basic integration patterns which can provide more insight into Oracle Service Bus integration with JMS.

JMS integration with OSB supports following messaging patterns.

Request Response Messaging

OSB receives request from remote or local inbound JMS queue and returns response back to remote or local outbound JMS Queue.

One way Messaging

OSB receives request from local or remote inbound JMS queue and does not deliver response.

Protocol Switching

OSB receives HTTP message and forwarded to JMS Subsystem.

Like any other integrations in OSB, JMS message can be transformed, enriched in service bus. Message received through JMS integration can also routed to more than one services using routing and publish functions of OSB. OSB monitoring provides key performance metrics i.e. Number of messages processed, average execution time of message processing and number of alerts associated with service.

One Way Messaging - OSB Proxy Service Using JMS

Request/Response Messaging - OSB Proxy Service using JMS

Protocol Switching (HTTP --> JMS) using Proxy and Business Service

Business service can be used for JMS end point for a local or remote queue or topic. Business service is act as remote JMS client to publish or send message to remote JMS destination. Proxy service can b created from JMS Business service with any protocol end point supported by Oracle Service Bus.

In addition of the above basic messaging patterns, proxy and business services can be combined to implement advanced messaging patterns like Asynchronous Web Service and call back.