This presentation is for informational purposes only and may not be incorporated into a contract or agreement.

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle.

Oracle Enterprise Messaging Service Features and Overview John Lang Oracle Application Server Product Manager Oracle Corporation Session S703 This presentation is for informational purposes only and may not be incorporated into a contract or agreement.

Agenda Fusion Middleware Overview Oracle Enterprise Messaging Service Overview Solution Areas Java Message Service Quality of Service Choices Enterprise Messaging Integration Store and Forward Message Integration with the Oracle Database Management and Monitoring Customer Use Cases Key Messages and Summary

OEMS

Oracle Fusion Middleware Addresses key business challenges Rapid business change Greater systems flexibility With lower technology costs Differentiators Comprehensive Hot Pluggable Unbreakable Proven

Oracle Enterprise Messaging Service JMS API Enterprise Messaging Service QoS Integration In-memory WebSphere MQ File Tibco Single API Quality of Service Choice for message persistence Seamless Integration Support existing non- Oracle messaging systems Database SonicMQ Flexible infrastructure for distributed application architectures

OEMS Overview Complete enterprise quality messaging solution Comprehensive messaging integration solutions Flexible solutions for different use cases and topologies Ease of development Single interface Leverage standards Configurable Qualities of Service In-memory, file-based, database

OEMS Overview Full management and monitoring support Lower integration costs Seamless integration with non-oracle messaging providers WebSphere MQ, Tibco, SonicMQ Enterprise customer base Fortune 500 customers in every industry vertical Thousands of customers currently depend on OEMS for their messaging infrastructure

Oracle Transport Framework Messaging infrastructure for Oracle s Grid platform Service Oriented Arch. Enterprise Service Bus BPEL Process Manager Web Services Portal.NET B2B WSDL WSDL WSDL SOAP/HTTP/ reliable SOAP JMS WebSphere MQ, Tibco, Sonic In-memory, Filesystem, Database WSDL WSDL WSDL ERP Legacy CRM

Oracle Enterprise Messaging Service Oracle Enterprise Messaging Service JMS 1.1 Enterprise Manager Oracle Application Server Oracle Database JMS Router JMS Connector Persistence Persistence Native Interface Messaging Gateway Memory File Database SonicMQ WebSphereMQ Tibco WebSphereMQ Tibco

J2EE Java Message Service Simplify Development Costs Single interface for developing messaging solutions Single interface to different levels of persistence Open Standard Oracle supports both JMS 1.1 and 1.0.2b Fully J2EE standards compliant

Java Message Service Full XA support High Performance and Scalable on inexpensive hardware JMS In-Memory 4000+ msg/sec through one queue JMS Database 300+ msg/sec through one queue Scales linearly supports 3000+ msg/sec through 10 queues Upwards of 10,000+ msg/sec through one queue on high end hardware

Message Persistence Options No code changes required just re-configure In-Memory Messages are volatile File-Based Messages persisted to a user configurable location Database Messages persisted to Streams Advanced Queuing Complete RAC & TAF support XMLType support PL/SQL API to access JMS DB Destinations

Quality of Service Properties Quality of Service In-Memory File DB JMS 1.1 Exception Handling Guaranteed Delivery Clustering Lightweight Recoverable Native XML Msg Support Auditing / Tracking / History

Use Case If you require Non-Oracle JMS messaging integration to your J2EE application Standards based integration Bi-directional message flow Distributed transaction support then use the JMS Connector Non-Oracle JMS Message Provider

J2EE Connector Architecture J2CA provides a standard way for integrating a J2EE application server and Enterprise Information Systems (EISs) JCA 1.0 is part of J2EE 1.3 JCA 1.5 is part of J2EE 1.4 Documents JMS Provider pluggability

J2EE Connector Architecture OC4J (J2EE Application Server) Container-Component Contract J2EE Application Component Client API System Contracts Resource Adapter Lifecycle Management Work Management Message inflow Transaction inflow Transaction Management Security Management Connection Management EIS specific contracts Enterprise Information System

J2EE Connector Architecture OC4J (J2EE Application Server) Container-Component Contract Client API System Contracts J2EE Application Component JMS Connector Lifecycle Management Work Management Message inflow Transaction inflow Transaction Management Security Management Connection Management EIS specific contracts JMS Provider

JMS Connector Oracle Application Server J2EE Container J2EE application integration with JMS providers OEMS JMS integrated through the JMS Connector In-memory, File-based, DB Oracle has certified: IBM WebsphereMQ 6.0 & 5.3 Tibco Enterprise JMS 3.1.0 SonicMQ 6.0 J2EE / EJB Component JMS Connector generic JMS JCA Resource Adapter MDB JMS Messaging Systems

JMS Connector Benefits Provides additional Quality of Service for all JMS providers: Performance and resource utilization improvements Connection pooling MDB s react to changing message load Dynamic monitoring and management Transaction management Lazy evaluation Start order independence Error logging & tracing

Use Case If you require Store and forward message capability Reliable message propagation Bridge between different JMS providers Content based routing then use the JMS Router Non-Oracle JMS Message Provider JMS In-memory & File-based JMS Streams AQ

JMS Router Message routing between JMS Destinations Oracle JMS In-memory Oracle JMS File-based Oracle JMS Database IBM WebsphereMQ Tibco Enterprise JMS SonicMQ OC4J Service Oracle Application Server J2EE Container JMS Router JMS Connector J2EE Application JMS Connector WebSphereMQ Tibco JMS SonicMQ Oracle

JMS Router Reliable message delivery from source Destination to target Destination Content based routing Routing between OC4J Instances over HTTP Administration choices: Application Server Control Programmatically via MBean jms.xml OC4J Memory File Oracle DB WMQ OC4J Memory or File JMS Router Tibco SonicMQ

Use Case If you require Oracle Database access to information in non- Oracle messaging systems Bi-directional message propagation Guaranteed, one-time only delivery of messages then use the Messaging Gateway Non-Oracle Messaging System Streams AQ

Messaging Gateway Bi-directional message propagation engine between AQ and non-oracle messaging systems Support for: IBM WebSphere MQ 6.0 & 5.3 Tibco Rendezvous 7.3 Microsoft MSMQ (future release)* Available with Enterprise Edition of the Oracle Database Streams AQ MGW Agent WebSphere MQ Tibco/Rv MSMQ*

MGW Features Support for native message formats AQ messages can be RAW or any ADT payload Automatic and user-defined message transformation Management API similar to AQ Quality of Service When non-oracle message systems support transactions and persistent queues Guaranteed, exactly once delivery When non-oracle message systems do not support transactions and persistent queues At most once delivery RAC Support

Summary of Integration Features Feature JMS Connector JMS Router MGW Use Case Integration of non-oracle messaging systems directly into OC4J Bi-directional content based propagation of JMS messages between Oracle and non-oracle messaging systems Bi-directional propagation of messages between the Oracle Database and non-oracle messaging systems

Management and Monitoring Management Modify system properties Process control Monitoring Performance metrics View log files

Monitoring a JMS Destination Choose a Destination Monitor the Destination

Management and Monitoring JMX based dynamic configuration No server restart for Destination and ConnectionFactory creation/deletion No server restart for JMS server property changes Complete Application Server Control (ASC) support for message administration in OC4J OEMS JMS JMS Connector JMS Router

OEMS Customers and Use Cases Sabrix builds solutions for applications that require the determination, calculation, and reporting of taxes. JMS In-memory Require high performance 16ms/transaction resulting in 1M transactions per hour on relatively inexpensive h/w Cache synchronization across Oracle Application Server nodes in a cluster

OEMS Customers and Use Cases Agile builds enterprise class Product Lifecycle Management solutions for over 600 companies. JMS File-based Require a high performance, cost effective solution to: Sending email notifications Cache synchronization in a cluster Handling subscriptions so users can subscribe to certain application events Asynchronous actions for long running tasks in the background

OEMS Customers and Use Cases FTD, Inc., supported by its worldwide FTD brand, is a leading provider of floral services and products. JMS Database Require high performance (100,000 orders/day), scalable, fault tolerant messaging infrastructure for mission critical applications: FTD.com order processing Customer service applications

OEMS Customers and Use Cases TAM is the leading airline carrier in the Brazilian domestic market. JMS Database Require high availability for mission critical applications Message synchronization between Oracle Databases Mobile SMS notification for e-tickets Retrieval of Sabre system reservation data Nationwide is one of the largest insurance and financial companies in the world. Messaging Gateway Require integration between a Forms application and CICS program Sends an XML message from Streams AQ to WebSphere MQ for processing by a CICS program CICS program creates a reply XML message which is sent to WebSphere MQ and then to Streams AQ

Summary of Key Features Oracle Enterprise Messaging Service Enterprise quality message infrastructure Messaging foundation for Oracle s ESB and BPEL solutions Flexible integration choices Quality of Service for persistence Managed and monitored Support for open standards JMS 1.1 and 1.0.2b JCA 1.5 Java Message Service Quality of Service Messaging Integration Single API to Oracle s messaging infrastructure No code changes when choosing a persistence quality of service Multiple choices for persisting messages In-memory File-based Database Easily switch through configuration changes Easy integration into existing messaging infrastructure Support for: WebSphereMQ Tibco Sonic MQ

Key Messages Comprehensive Broad enterprise quality messaging and integration solution Pluggable Integration and quality of service choices Proven Fortune 500 customers look to Oracle for messaging solutions Built on Open Standards OEMS supports all J2EE messaging standards Oracle delivers a full Enterprise Messaging solution

Learn the Technology Visit OTN Microsites: otn.oracle.com http://www.oracle.com/technology/products/ias/oems/index.html Products -> Application Server -> OEMS Presentation will be posted at this OTN site Try the Software Visit the Hands-On Labs in Moscone West 1003, 1004 Ask Our Experts Fusion Middleware Demogrounds; Sessions

Q U E S T I O N S A N S W E R S Thanks for attending!!

This presentation is for informational purposes only and may not be incorporated into a contract or agreement.