Oracle JMS Adapter Integration with Oracle BPEL Process Manager

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