Composite Availability and Inbound Adapters

2-20 Oracle Fusion Middleware Users Guide for Technology Adapters ■ Section 2.14, Singleton ActivePassive Inbound Endpoint Lifecycle Support Within Adapters ■ File and FTP adapters: Section 4.2.18, High Availability ■ Database adapter: Section 9.3.7, High Availability ■ MQ adapter: Section 10.3.4, High Availability ■ Section 2.12, How Oracle JCA Adapters Ensure No Message Loss ■ Section 5.9 Oracle JCA Adapters and High Availability Concepts in the Oracle Fusion Middleware High Availability Guide.

2.14 Singleton ActivePassive Inbound Endpoint Lifecycle Support Within Adapters

The JCA Binding Component supports active fail-over of inbound Adapter Services. To enable this fail-over feature for a given inbound adapter endpoint, you must add the singleton JCA service binding property in the composite.xml within the binding.jca element and set it to a value of true as Example 2–1 shows. To disable this feature, set the singleton property to a value of false or remove the property from the binding.jca element. Example 2–1 singleton Property in composite.xml service name=JmsTopicSubscr ui:wsdlLocation=JmsTopicSubscr.wsdl interface.wsdl interface=http:xmlns.oracle.com...wsdl.interfaceSubscr_ ptt binding.jca config=JmsTopicSubscr_file.jca property name=singletontrueproperty binding.jca service

2.14.1 Multiple Activations of the Same Adapter Endpoint

In an Oracle WebLogic cluster, multiple activations of the same for example, JMS adapter inbound endpoint for a specific composite service are detected implicitly and automatically by all instances of the adapter framework active in that cluster. However, only one activation will be allowed to start the reading or publishing of messages. The JCA Binding Component instances choose one among the activations, randomly the activation that will assume the Primary Activation responsibility.

2.14.2 Hot-Standby State

The other activations also called instances in the Oracle WebLogic cluster initiate to a hot stand-by state, without invoking EndpointActivation on the JCA resource adapter. These activations can be reassigned primary activation responsibility. If a primary activation at some point becomes unresponsive, is deactivated manually, or crashes or exits, any one of the remaining JCA Binding Component members of the Oracle WebLogic cluster immediately detect this, and reassign the primary activation responsibility to one of activation agents that is in stand-by state. ADAPTER Life-Cycle Management 2-21 For more information, see Section 2.13, Composite Availability and Inbound Adapters .

2.15 Oracle BPEL Process Manager Correlation Support Within Adapters

You can use Native Correlation to correlate an inbound asynchronous message with a previous outbound message, by defining a callback interface for a Reference or by a mid process BPEL Receive: For example, the following composite would define such a correlation: reference name=’Outbound’ interface.wedl interface=http:xmlns.oracle.compcbpeldemowsdl.interface JMSOutbound_PortType callbackinterface=http:xmlns.oracle.compcbpeldemowsdl.interface JMSCallback_PortType binding.jca.operation=Consume config=SampleOutbound_adapter.jca The jca file must contain both JCA interaction and JCA activation. The correlation between the request and the response is done transparently by the JCA binding runtime. For a JMS use case, the third party application must copy the JMS message ID from the request message to the JMS CorrelationID of the response message. For the Oracle AQ Adapter and Oracle JMS Adapter use cases, if an external application copies the MessageId from the request Invoke message to the CorrelationId of the response Receive message, the adapter framework ensures that the BPEL correlation occurs.

2.15.1 CorrelationID of Receive Message Not Matching Invoke: Log Error Message

However, when the CorrelationId of the Receive message does not match any earlier Invoke message, the message is mapped to a BPEL conversation that does not actually exist. In this case, although the message is persisted in the database, you might see the SEVERE log message that Example 2–2 shows: Example 2–2 Log Error When CorrelationId of the Receive Does not Match any Earlier Invoke SEVERE: JCABinding= aqadapter aqadapterAdapter Service aqadapter was unable to perform delivery of inbound message to the composite ... due to: Cannot simply post callback message to the composite as there is no service element associated with the callback. Recommendation: addset the JCA referencebinding property rejectUncorrelatedMessages to true ... SEVERE: JCABinding= aqadapter Unable to createsave Composite Instance Fault due to: null

2.15.1.1 Rejecting Nonmatching Native Correlation IDs

You can explicitly alter the adapter framework behavior so that it rejects nonmatching native correlation IDs by adding the rejectUncorrelatedMessages service binding property to the composite.xml file as shown in Example 2–3 .