Deploying with JDeveloper Monitoring Using the Fusion Middleware Control Console

8-52 Oracle Fusion Middleware Users Guide for Technology Adapters 4. Modify the server.xml file of the 10.1.3.4 server to include the environment-naming-url-factory-enabled=true property, as shown in the following example: application-server ... ... environment-naming-url-factory-enabled=true ... 5. Restart the 10.1.3.4 server to make the changes come into effect.

8.4.10 Configuring the 11G Server to Access Queues Present in 10.1.3.X OC4J

You can configure your 11G server to access queues present in 10.1.3.x OC4J with the following steps.

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

Copy the following jar files under the domainsDOMAIN_NAMElib folder of the WebLogic Server: ■ J2EE_HOMElibjms.jar ■ J2EE_HOMElibjta.jar ■ J2EE_HOMEoc4jclient.jar ■ AS_HOMEopmnliboptic.jar

8.4.10.2 Add Connector factory in the weblogic-ra.xml File

The next step is to add the Connector Factory in the weblogic-ra.xml file: connection-instance jndi-nameeisoc4jjmsQueuejndi-name connection-properties properties property nameConnectionFactoryLocationname valuejmsXAQueueConnectionFactoryvalue property property nameFactoryPropertiesname valuejava.naming.factory.initial=com.evermind.server.rmi. RMIInitialContextFactory;java.naming.provider.url= PROVIDER_URL;java.naming.security.principal=oc4jadmin; java.naming.security.credentials=welcome1value property property nameAcknowledgeModename valueAUTO_ACKNOWLEDGEvalue property property Note: The isTransacted configuration property value must typically be set to FALSE. Currently, XA integration with WebLogic JMS is not supported unless the adapter is deployed on Oracle WebLogic Server. Oracle JCA Adapter for JMS 8-53 nameIsTopicname valuefalsevalue property property nameIsTransactedname valuefalsevalue property property nameUsernamename valueoc4jadminvalue property property property namePasswordname valuewelcome1value property properties connection-properties connection-instance where PROVIDER_URL=opmn:localhost:6003 or, ormi:localhost:12401 to use against a specific node or, opmn:ormi:localhost:6003:oc4j_soa to use against the oc4j_soa instance.

8.4.11 Accessing Distributed Destinations Queues and Topics on the WebLogic Server JMS

A distributed destination is a set of destinations queues, set of physical JMS queue members, or topics, set of physical JMS topic members that are accessible as a single, logical destination to a client. The JMS Adapter can process messages addressed to a distributed destination member after receiving available notification; it can process available, unavailable, and failure notifications related to a distributed destination member.To have the JMS Adapter process such messages, you need to provide additional properties to provide access to distributed destinations queues or topics with the JMS Adapter. When you provide additional properties, you can separate multiple FactoryProperty values with a semi-colon. See the following example. property nameFactoryPropertiesname valueClientID=SOACLient2; TopicMessageDistributionAll=truevalue property

8.4.11.1 Providing JMS Adapter Access to Distributed Destinations

You use three FactoryProperty parameter values to provide adapter access to distributed destinations, to specifically enable the Client ID to be shared by multiple connections, to enable the sharing of Durable subscriptions among multiple Note: For more information on distributed destinations, and a definition of terms used in this context, visit the Using Distributed Destinations pages at http:download.oracle.comdocscdE13222_ 01wlsdocs103jmsdds.html