Add Connector factory in the weblogic-ra.xml File

8-54 Oracle Fusion Middleware Users Guide for Technology Adapters subscribers, and to specify whether you want one copy of a message per application or per endpoint. The properties include: ■ ClientIDPolicy Use the FactoryProperties parameter ClientIDPolicy property with a value of UNRESTRICTED to enable the Client ID to be shared by multiple connections. The default, if no value is specified, is UNRESTRICTED. The non-default value is RESTRICTED. The default is used in almost all uses, so typically you do not need to set it. See the following example: property nameFactoryPropertiesname valueClientIDPolicy=UNRESTRICTEDvalue property ■ SubscriptionSharingPolicy Use the FactoryProperties parameter with a value of SHARABLE to enable the sharing of Durable Subscriptions among multiple subscribers. A value of SubscriptionSharingPolicy EXCLUSIVE means you cannot share Durable Subscriptions among multiple subscribers. If you do not specify a value, the default is SHARABLE; in most cases, you will not need to change the value. property nameFactoryPropertiesname valueSubscriptionSharingPolicy=SHARABLEvalue property ■ TopicMessageDistributionAll See the section on Distirbuted Topics for more information on the TopicMessageDistributionAll FactoryProperties parameter. You can set it as in the following example: property nameFactoryPropertiesname valueTopicMessageDistributionAll=truevalue property

8.4.11.2 The JMS Adapter with Distributed Queues and Distributed Topics

Specific inbound and outbound queue and error handling behaviors apply to the JMS Adapter with JMS Distributed Queues and Distributed Topics. For inbound queues, the JMS Adapter creates an inbound poller thread and registers a notification listener with the WebLogic Server JMS on endpoint activation; it unregisters notification listener upon endpoint deactivation. The JMS Adapter handles errors in the Distributed environment in the same fashion as such errors are handled in a non-Distributed environment: retriable exceptions lead to message retry; non-retriable exceptions lead to message rejection. There is no change from the behavior of other Adapters to JMS adapter behavior when the Adapter produces a message to a Distributed Queue. JMS messages for Distributed Destinations are produced by creating a MessageProducer for the Distributed Destination and not for a specific member. Outbound errors are processed based on fault-policies previously defined for the outbound reference. Oracle JCA Adapter for JMS 8-55 For inbound adapters with distributed topics, the JMS Adapter registers a notification listener with the WebLogic Server JMS on endpoint activation. The JMS Adapter creates an inbound poller thread for each available notification received from WebLogic Server JMS for a Distributed Topic member. The inbound poller thread stops working and necessary cleanup is performed if an unavailable notification is received for the member for which the poller thread was created. The durable subscription is maintained in a similar fashion as in a non-Distributed topic scenario. The Adapter unregisters the notification listener upon endpoint deactivation. Any message arriving at a Distributed Topic is processed based on the various settings used and the type of Distributed Destination in use: either one copy of a message per application, or one copy of a message per adapter endpoint. The behaviors for each of these types of Distributed Destination are provided below.

8.4.11.3 One Copy of a Message Per Application Default Behavior

The default behavior for WebLogic Server Partitioned Distributed Topics when used with the JMS Adapter is to provide one copy of a message per application. Each message needs to be processed exactly once that is, there is no duplicate processing.. In this scenario, where there is one copy of a message per application, the client id and subscription name are the same for every Distributed Destination and each adapter instance creates subscriptions on every member. The name is unique and immutable across server restarts. When using Partitioned Distributed Topics you must configure the JMS adapter to use unrestricted clientid and shared subscription policy. These two are the default settings for Distributed Destinations. When using Replicated Distributed Topics, you must configure JMS adapter to use the unrestricted clientid and shared subscription policy, which are the default settings. To achieve better performance you should use Partitioned Distributed Topics. In addition, you need to specify the following message selector, NOT JMS_WL_ DDForwarded when defining an activation spec. Refer to the following example, consisting of a snippet of a connection instance from the weblogic-ra.xml file for a local cluster: property nameFactoryPropertiesname valueClientID=SOAClient1;value property

8.4.11.4 One Copy Of a Message Per Adapter Endpoint

The second type of scenario you can employ with Distributed Topics is to have one copy of message per adapter endpoint. In this case, either the client id or the subscription name is unique for each adapter instance. The unique part of the member name is immutable across server restarts. When using Partitioned Distributed Topics you need to configure the JMS adapter to use unrestricted clientid and shared subscription policy, which are the default settings. At the same time, to achieve subscription name uniqueness, JMS adapter requires that the property TopicMessageDistributionAll default value of false is set to true. You can define this property by setting the FactoryProperties property of the