Outbound Transactions How Oracle JCA Adapters Ensure No Message Loss

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.