Copy Jar Files into the domains Folder of the Web Logic Server

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.