Monitoring Using the Fusion Middleware Control Console

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 Oracle JCA Adapter for JMS 8-3 interface=http:xmlns.oracle.compcbpeladapterjmsutf8jcamessageencoding jms_inboundwsdl.interfaceConsume_Message_ptt binding.jca config=jms_inbound_jms.jca property name=jca.message.encoding type=xs:string many=false override=mayGBKproperty binding.jca service The following code snippet is an example of setting values in the composite.xml file for message encoding for an outbound reference: reference name=jms_outbound ui:wsdlLocation=jms_outbound.wsdl interface.wsdl interface=http:xmlns.oracle.compcbpeladapterjmsutf8jcamessageencoding jms_outboundwsdl.interfaceProduce_Message_ptt binding.jca config=jms_outbound_jms.jca property name=jca.message.encoding type=xs:string many=false override=mayGBKproperty binding.jca reference ■ Supports the JMS message selector Supports the JMS message selector for performing filtering while subscribing to JMS topics and queues. This parameter is based on the SQL 92 language for filtering messages based on fields present in the JMS header and properties section. ■ Is DOM2 compliant The Oracle JMS Adapter can process and generate document objects that are compliant with DOM2 specification. ■ Supports normalized message. Header manipulation and propagation is a key business integration messaging requirement. Oracle BPEL PM, Mediator, Oracle JCA, and Oracle B2B rely extensively on header support to solve customers integration needs. For example, a user can preserve a file name from the source directory to the target directory by propagating it through message headers. Another example: the outbound Oracle JMS Adapter facilitates asynchronous requestresponse by propagating the correlationId and the JMSReplyTo address as JMS headers. In Oracle BPEL PM and Mediator, users can access, manipulate, and set headers with varying degrees of UI support. For more information, see Section 2.15, Oracle BPEL Process Manager Correlation Support Within Adapters . Propagating Headers in a Normalized Message: Normalized Message is simplified to have only two parts, properties and payload.Typically, properties are name-value pairs of scalar types. To fit the existing complex headers into properties, they will be flattened into scalar types. Manipulating Headers in Design-Time: The user experience while manipulating headers in design time is simplified, because the complex properties are predetermined. In Mediator or Oracle BPEL designer, you can manipulate the headers with some reserved key words. For