Configuring the Data Sources in the Oracle WebLogic Server Administration Console

8 Oracle JCA Adapter for JMS 8-1 8 Oracle JCA Adapter for JMS This chapter describes how to use the Oracle JCA Adapter for JMS Oracle JMS Adapter, which enables an Oracle BPEL process or an Oracle Mediator component to interact with JMS. This chapter includes the following topics: ■ Section 8.1, Introduction to the Oracle JMS Adapter ■ Section 8.2, Oracle JMS Adapter Features ■ Section 8.3, Oracle JMS Adapter Concepts ■ Section 8.4, Oracle JMS Adapter Use Cases

8.1 Introduction to the Oracle JMS Adapter

The JMS architecture uses one client interface to many messaging servers. The JMS model has two messaging domains, point-to-point and publish-subscribe. In the point-to-point domain, messages are exchanged through a queue and each message is delivered to only one receiver. In the publish-subscribe model, messages are sent to a topic and can be read by many subscribed clients. You can obtain JMS adapter sample files by accessing the Oracle SOA Sample Code site, and selecting the Adapters tab. This section includes the following topics: ■ Section 8.1.1, Oracle JMS Adapter Integration with Oracle BPEL Process Manager ■ Section 8.1.2, Oracle JMS Adapter Integration with Oracle Mediator

8.1.1 Oracle JMS Adapter Integration with Oracle BPEL Process Manager

The JCA Binding Component is used for the bidirectional integration of the JCA 1.5 resource adapters with BPEL Process Manager. The JCA Binding Component is based on standards and employs the Web service Invocation Framework WSIF technology for exposing the underlying JCA interactions as Web services. For information on Oracle JMS Adapter architecture, adapter integration with Oracle BPEL Process Manager Oracle BPEL PM, and adapter deployments, see Chapter 3, Adapter Integration with Oracle Application Server Components.

8.1.2 Oracle JMS Adapter Integration with Oracle Mediator

Mediator supports Oracle JCA Adapters and enables you to define inbound and outbound adapter services for each. An inbound adapter service receives data from an 8-2 Oracle Fusion Middleware Users Guide for Technology Adapters external messaging system and transforms it into an XML message. An outbound adapter service sends data to a target application by transforming an XML message into the native format of the given adapter. In the case of Oracle JMS Adapter service, by using Mediator, you can send or receive messages from a JMS queue or topic. Oracle BPEL PM pre-dates Mediator, and most of this guide and the samples implicitly assume use with Oracle BPEL PM. However, the adapters work equally well with either Oracle BPEL PM or Mediator. For any mention of Oracle BPEL PM in this chapter, you may substitute Mediator, instead.

8.2 Oracle JMS Adapter Features

The Oracle JMS Adapter includes the following features: ■ Is based on JMS version 1.0.2b ■ Is a generic Oracle JMS Adapter Works with any JMS provider. It has been certified against AQ JMS JMS providers OJMS 8.1.7, 9.0.1.4, and 9.2, TIBCO JMS, IBM Websphere MQSeries IBM MQSeries JMS 6.0, Weblogic JMS, Apache, and Active MQ. ■ Supports JMS topics and queues ■ Supports byte, text, and map message types . Supports these data types only for this release. The Adapter Configuration Wizard provides the Native Format Builder wizard for consuming native data payloads at run time. The Native Format Builder wizard creates XSD definitions for the underlying native data. ■ Supports JMS headers and properties ■ Supports jca.message.encoding property The Oracle JMS Adapter supports the jca.message.encoding property for inbound and outbound payloads. If the jca.message.encoding property is used along with the adapter.jms.encoding property and the nxsd:encoding attribute, then the jca.message.encoding property takes precedence over the adapter.jms.encoding property, and the nxsd:encoding attribute is given the last preference. The nxsd:encoding value can be UTF, which-8 is typically recommended for interoperability and Unicode support. However, you can specify any legal encoding supported by the Java runtime environment. For a complete listing of supported encodings, visit http:www.oracle.comtechnetworkjavaindex.html . Note that you you can specify the encoding in the NXSD associated with the adapter proxy meta data. For example, you can specify the following attribute, nxsd:encoding=iso-8859-1 The jca.message.encoding property is supported as an endpoint yu76y76 defined in composite.xml You can define this property using the Properties tab of the Adapter Configuration Wizard or by editing the composite.xml file. The jca.message.encoding property can be passed as a normalized message property for both inbound and outbound interactions. The following code snippet is an example of setting values in the composite.xml file for message encoding for an inbound service: service name=jms_inbound ui:wsdlLocation=jms_inbound.wsdl interface.wsdl