Oracle Enterprise Messaging Service Standards-based, reliable messaging for SOA
As IT organizations deploy and integrate Service Oriented Architectures (SOA) and Enterprise Service Bus (ESB) based solutions to integrate their distributed applications it is becoming increasingly important that the underlying messaging infrastructure provide the reliability, scalability, and performance required to meet these demands.
The Oracle Enterprise Messaging Service (OEMS) is a standards based solution built on the Java Message Service (JMS) and the J2EE Connector Architecture (J2CA) which allows customers to develop and integrate distributed applications. It is built on a robust messaging platform which offers varying levels of service for message persistence and recovery -- in-memory, filesytem, or database backed message persistence. OEMS also provides a standards-based JMS Router for seamlessly integrating the OEMS platform with a customer's existing non-Oracle messaging infrastructure; WebSphereMQ, Tibco Enterprise JMS, or SonicMQ.
Applications Server: Messaging and JMS How-To's There is an extensive set of code examples detailing setup and configuration of the JMS Connector and JMS Router. They explain how to integrate with non-Oracle message providers; WebSphereMQ, Tibco JMS, and SonicMQ. There are also examples showing setup of OEMS JMS for in-memory, filesystem, and database persistence. These How-To's are designed to run with the Oracle Application Server 10g R3 (10.1.3) release that is available from OTN -- see the link in the upper right corner of this page.