The adapter.jms.DistributedDestinationConnectionEveryMember property is available as the Service binding property for the JMS Adapter.

This property takes boolean values [true | false]. The default value is true.

When true, the JMS Adapter creates a consumer/subscriber for each member of the distributed destination. If set to false, the JMS Adapter creates a consumer/subscriber for only local members of the distributed destination. When the JMS Adapter is connecting to distributed destination on a remote cluster or a server on remote domain, the adapter.jms.DistributedDestinationConnectionEveryMember property should always be set to true. When the JMS Adapter is connecting to distributed destination on a local cluster, the property can be set to either true or false. If set to true, the JMS Adapter behavior remains the same as before (that is, there is a consumer for each distributed destination is created). If set to false, the JMS Adapter only creates consumer/subscriber for the local members.

You will not see this property in JDeveloper as a binding property on Service side. Consequently, you must manually add it in the composite.xml as shown below under the <service>/<binding.jca> tag:

<property name="adapter.jms.DistributedDestinationConnectionEveryMember" type="xs:string" many="false" override="may">false</property>

1. Open JDeveloper.
2. In the Application Navigator, click New Application.

   The Create Generic Application - Name your Application page is displayed, as shown in Figure 8-1.

3. Enter a name for the application in the Application Name field. For example, AQQueue2Queue.
4. In the Application Template list, choose Generic Application.

   Figure 8-1 The Create Generic Application - Name your application Page

   
   Description of "Figure 8-1 The Create Generic Application - Name your application Page"
5. Click Next.

   The Name your project dialog is displayed, as shown in Figure 8-2.

6. In the Project Name field, enter a descriptive name. For example, AQQueue2Queue.
7. In the Available list in the Project Technologies tab, double-click SOA to move it to the Selected list.

   Figure 8-2 The Create Generic Application - Name your Generic project Page

   
   Description of "Figure 8-2 The Create Generic Application - Name your Generic project Page"
8. Click Next.

   The Create Generic Application - Configure SOA settings page is displayed, as shown in Figure 8-3.

   Figure 8-3 The Create Generic Application - Configure SOA Settings Page

   
   Description of "Figure 8-3 The Create Generic Application - Configure SOA Settings Page"
9. Select Composite With BPEL from the Composite Template list, and then click Finish.

   You have created a new application, and a SOA project. This automatically creates a SOA composite.

   The Create BPEL Process page is displayed, as shown in Figure 8-4.

   Figure 8-4 The Create BPEL Process Page

   
   Description of "Figure 8-4 The Create BPEL Process Page"
10. Enter a name for the BPEL process in the Name field. In this example, use the default name.
11. Select Define Service Later in the Template list, and then click OK.

    You have created a BPEL process.

1. Drag and drop JMS Adapter from the Service Adapters list to the Exposed Services swim lane in the composite.xml page.

   The Adapter Configuration Wizard is displayed.

2. Enter a name for the service, and then click Next.

   The JMS Provider page is displayed.

   Figure 8-5 The Adapter Configuration Wizard - JMS Provider Page

   
   Description of "Figure 8-5 The Adapter Configuration Wizard - JMS Provider Page"
3. Select any one operation. In this example, select Oracle Weblogic JMS.

   • Oracle Enterprise Messaging Service (OEMS): This enables you to integrate with the WebLogic service or Advanced Queueing messaging service.

   • Third Party: Select this option to integrate with a third-party provider.

4. Click Next.

   The Adapter Configuration Wizard - Service Connection page is displayed.

5. You must establish connectivity between the design-time environment and the server you want to deploy it to.

   Perform the steps mentioned in Creating an Application Server Connection for Oracle JCA Adapters to create an application server connection.

6. Click Next. The Adapter Interface page is displayed.
7. In the Adapter Interface page, select Define from operation and schema (specified later).

   Figure 8-6 The Adapter Configuration Wizard - Adapter Interface Page

   
   Description of "Figure 8-6 The Adapter Configuration Wizard - Adapter Interface Page"
8. Click Next.

   The Adapter Configuration Wizard- Operation page is displayed.

9. Select Consume Message, Produce Message, or Request/Reply, or Synchronous Consume a Message. In this example, select Consume Message.

   The operation name is filled in automatically.

   Figure 8-7 The Adapter Configuration Wizard - Operation Page

   
   Description of "Figure 8-7 The Adapter Configuration Wizard - Operation Page"

   The Consume Message option enables the adapter to consume (receive) inbound messages from a JMS destination.

10. Click Next.

    The Consume Operation Parameters page is displayed.

    Figure 8-8 The Adapter Configuration Wizard - Consume Operation Parameters Page

    
    Description of "Figure 8-8 The Adapter Configuration Wizard - Consume Operation Parameters Page"
11. Enter values for the following fields:

    • Destination Name

      This is the JNDI name of the JMS queue or topic from which to receive the message. This is not an editable field. You must click Browse to browse for the queue or topic. The queue or topic to be chosen is based on the type of JMS provider you are using.

      For more information, see the following sections:

      • Configuring the Oracle JMS Adapter with TIBCO JMS

      • Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS

    • Message Body Type

      The supported values are TextMessage, BytesMessage, MapMessage. The StreamMessage message type is not supported in this release.

    • Durable Subscriber ID

      This field is optional. If you are setting up a durable subscriber, then the durable subscriber ID is required. Generally, a subscriber loses messages if the subscriber becomes disconnected, but a durable subscriber downloads stored messages when it reconnects.

      Note:

      When the JMS provider is Oracle WebLogic JMS or Oracle Advanced queueing messaging service, then the Durable Subscriber option appears only when a topic is selected. However, the Durable Subscriber option always appears when the JMS provider is a third-party.

    • Message Selector

      This field is also optional. It filters messages based on header and property information. The message selector rule is a Boolean expression. If the expression is true, then the message is consumed. If the expression is false, then the message is rejected.

      For example, you can enter logic, such as:

      • JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected.

      • JMSType = 'car' AND color = 'blue' AND weight > 2500

      • Country in ('UK', 'US', 'France')

    • Use MessageListener

      This field is always set to False by default.

    • JNDI Name

      The value specified in the JNDI name should exist in the Oracle JMS Adapter weblogic-ra.xml file to ensure that the adapter runs in managed mode.

    Note:

    This example shows a consume message operation. For a produce message operation, this page is different. See Produce Message Procedure to see how this part of the procedure differs.

    After you enter the appropriate parameters, click Next.

12. Messages page is displayed. The settings in this page define the correct schema for the message payload.

    You can perform one of the following:

    • Check Native format translation is not required (Schema is Opaque), which disables the rest of the fields.

    • Click Define Schema for Native Format to start the Native Format Builder wizard, which guides you through the process of defining the native format.

    • Enter the path for the schema file URL (or browse for the path).

    The following steps demonstrate the last option: browsing for the schema file URL.

    Figure 8-9 The Adapter Configuration Wizard - Messages Page

    
    Description of "Figure 8-9 The Adapter Configuration Wizard - Messages Page"
13. Click the Browse button.

    The Type Chooser dialog is displayed, with the Type Explorer navigation tree.

14. Browse the tree and select the appropriate schema type, and then click OK.

    Figure 8-10 Selecting a Schema from the Type Chooser Dialog

    
    Description of "Figure 8-10 Selecting a Schema from the Type Chooser Dialog"

    The Messages page is displayed again, this time with the Schema File URL field and the Schema Element field filled up.

    Figure 8-11 Completed Messages Dialog

    
    Description of "Figure 8-11 Completed Messages Dialog"
15. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
16. Click Next.

    The Finish page is displayed. This box shows the path and name of the adapter file that the wizard creates.

17. Click Finish.

    The composite.xml page is displayed.

A produce message operation has certain differences in the definition procedure, particularly in Step 13 of Using the Adapter Configuration Wizard to Configure . Instead of specifying consume operation parameters, you specify the following produce operation parameters. This enables the adapter to produce (send) outbound messages for a JMS destination. The Produce Operation Parameters page is shown in Figure 8-12.

• Destination Name:

  The JNDI name of the JMS queue or topic to which the message must be delivered. The name to enter is based on the type of JMS provider you use.

  For more information about destination name, see the following:

  • Configuring the Oracle JMS Adapter with TIBCO JMS

  • Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS

• Message Body Type:

  The supported values are TextMessage, BytesMessage, and MapMessage. StreamMessage is not supported in this release.

• Delivery Mode:

  The values are Persistent or Nonpersistent. A persistent delivery mode specifies a persistent JMS publisher; that is, a publisher that stores messages for later use by a durable subscriber. A durable subscriber is a consume message with a durable subscriber ID in the corresponding field in Step 15 of Using the Adapter Configuration Wizard to Configure . A nondurable subscriber loses any messages that are produced when the adapter is not active. A durable subscriber downloads messages that have been stored in the persistent publisher, and therefore does not have to remain active at all time to receive all the messages.

• Priority:

  Select a priority value, with 9 representing the highest priority and 0 representing the lowest priority. The default is 4.

• TimeToLive:

  The amount of time before the message expires and is no longer available to be consumed.

• Unit Of Order

  This parameter only applies when the selected JMS Provider is a WebLogic Server JMS provider. It enables a message producer or group of message producers acting as one, to group messages into a single unit that is processed sequentially in the order the messages were created. The message processing of a single message is complete when a message is acknowledged, committed, recovered, or rolled back. Until message processing for a message is complete, the remaining unprocessed messages for that Unit of Order are blocked. The UnitOfOrder property enables you to set the unit-of-order value for the MessageProducer when producing a message. Refer to the Use Case Using the WLS JMS Unit-Of-Order with the JMS Adapter and Using Message Unit-of-Order in Developing JMS Applications for Oracle WebLogic Server.

• JNDI Name

  This field enables you to specify the JNDI name for the JMS connection. The deployment descriptor for the deployed instance of the JMS Adapter must associate this JNDI name with a set of configuration properties required by the JMS Adapter to access the JNDI destination at runtime.

Figure 8-12 Produce Operation Parameters Page

Description of "Figure 8-12 Produce Operation Parameters Page"

1. For example,

   create factory QueueConnectionFactory queue url=tcp://localhost:7222 
   create queue TibcoQueue 
   

2. Open the Weblogic Administration Console to modify an existing connection pool for connection to a Tibco Server. Navigate to Deployment->JmsAdapter->Configuration-> oracle.tip.adapter.jms.IJmsConnectionFactory->Outbound Connection Pools->eis/tibjms/Queue
3. Set the ConnectionFactoryLocation to QueueConnectionFactory. This is the name of the connection factory created earlier using TIBCO Enterprise Message Service Administration Tool.
4. Set the FactoryProperties to the following (separated into multiple lines for easier reading):

   java.naming.factory.initial=com.tibco.tibjms.naming.   TibjmsInitialContextFactory; 
   java.naming.provider.url=tibjmsnaming://localhost:7222; 
   java.naming.security.principal=<user name on Tibco server>; 
   java.naming.security.credentials=<password>; 
     ThirdPartyJMSProvider=true 
   

5. You can also create your own connection pool by modifying the weblogic-ra.xml file in AS11gR1SOA/soa/connectors/JmsAdapter.rar as shown in the example below. (You can use this as an example for creating a Topic connection pool, also):

   Example - Creating Your Own Connection Pool

   <connection-instance> 
        <jndi-name>eis/tibjms/QueueConnectionPool</jndi-name> 
            <connection-properties> 
                <properties> 
                    <property> 
                        <name>ConnectionFactoryLocation</name> 
                        <value>QueueConnectionFactory</value> 
                    </property> 
                    <property> 
                        <name>FactoryProperties</name> 
                        <value>java.naming.factory.initial=com.
                             tibco.tibjms.naming.
                             TibjmsInitialContextFactory;
                               java.naming.provider.
                                    url=tibjmsnaming://localhost:7222;
                                       java.naming
                                .security.principal=<user name on
                                           Tibco server>;
                                java.naming.security.credentials=
                                           <password>;
                                    ThirdPartyJMSProvider=true 
                            </value> 
                        </property> 
                        <property> 
                        <name>AcknowledgeMode</name> 
                        <value>AUTO_ACKNOWLEDGE</value> 
                    </property> 
                    <property> 
                        <name>IsTopic</name> 
                        <value>false</value> 
                    </property> 
                    <property> 
                        <name>IsTransacted</name> 
                        <value>true</value> 
                    </property> 
                    <property> 
                        <name>Username</name> 
                        <value></value> 
                    </property> 
                    <property> 
                        <name>Password</name> 
                        <value></value> 
                    </property> 
                </properties> 
            </connection-properties> 
    </connection-instance> 
    

6. Update the JMSAdapter connection pool deployment after making these changes. Copy EMS_HOME/lib/tibjms.jar to the <SOA Installation>/user_projects/domains/<DOMAIN_NAME>/lib directory. Restart the Weblogic Server.
7. In the project you deploy, the JMS jca file for the JMS adapter might look like the following. Note that the value of DestinationName is TibcoQueue which is the queue created using TIBCO Enterprise Message Service Administration Tool.

   <connection-factory UIJmsProvider="THIRDPARTY" 
                             location="eis/tibjms/Queue" 
                         UIConnectionName="SOADEV"/> 
     <endpoint-interaction portType="Produce_Message_ptt" 
                        operation="Produce_Message"> 
        <interaction-spec 
          className="oracle.tip.adapter.jms.                  outbound.JmsProduceInteractionSpec"> 
          <property name="TimeToLive" value="0"/> 
          <property name="PayloadType" value="TextMessage"/> 
          <property name="DeliveryMode" value="Persistent"/> 
          <property name="DestinationName" value="TibcoQueue"/> 
        </interaction-spec> 
      </endpoint-interaction> 
   

8. After messages are published, you can use the TIBCO Enterprise Message Service Administration Tool to verify the number of messages in a Tibco queue, for example:

   show queue TibcoQueue 
     Queue:                 TibcoQueue 
     Type:                  static 
     Properties:            *prefetch=5 
     JNDI Names:            <none> 
     Bridges:               <none> 
     Receivers:             0 
     Pending Msgs:          2, (2 persistent) 
     Delivered Msgs:        0 
     Pending Msgs Size:     1.2 Kb, (1.2 Kb persistent)
    

1. Use the TIBCO Enterprise Message Service Administration Tool to create a queue or topic.

   create queue TibcoQueue
   

2. Set the ConnectionFactoryLocation to com.tibco.tibjms.TibjmsQueueConnectionFactory.
3. Set the FactoryProperties to ServerUrl=tcp://<HOST>:<PORT>;UserName=<USERNAME>;UserPassword=<PASSWORD>
4. If the Tibco server does not require a user name and password to connect remove the user name and password fields.
5. Save and update the JMS Adapter connection pool deployment.
6. Copy EMS_HOME/lib/tibjms.jar and EMS_HOME/lib/jms-2.0.jar to <SOA Installation>/user_projects/domains/<DOMAIN_NAME>/lib directory.
7. Restart the managed Weblogic Server.
8. In the project to be deployed, the JMS jca file for the JMS Adapter might look like the following example.

   Note that value of DestinationName is TibcoQueue, which is the queue created using TIBCO Enterprise Message Service Administration Tool.

   Example - JMS jca File for JMS Adapter with Dynamically-Created Connection Factory

    <connection-factory UIJmsProvider="THIRDPARTY" 
    location="eis/tibjmsDirect/Queue" UIConnectionName="SOADEV"/> 
     <endpoint-interaction portType="Produce_Message_ptt" 
    operation="Produce_Message"> 
        <interaction-spec 
    className="oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec"> 
          <property name="TimeToLive" value="0"/> 
          <property name="PayloadType" value="TextMessage"/> 
          <property name="DeliveryMode" value="Persistent"/> 
          <property name="DestinationName" value="TibcoQueue"/> 
        </interaction-spec> 
      </endpoint-interaction> 
   

1. Create a certs directory under EMS_HOME/bin.
2. Copy server SSL certificates to the EMS_HOME/bin/certs directory. Tibco supplies, for the purposes of testing, a self-signed server certificate and private keys which you can find in EMS_HOME\bin\samples\certs.
3. In EMS_HOME/bin/tibemsd.conf, add the following lines:

       listen = ssl://localhost:7243 
       ssl_server_identity = certs/server.cert.pem 
       ssl_server_key = certs/server.key.pem 
       ssl_password = password 
       listen = tcp://localhost:7222 
   

   These lines explicitly set the TCP and SSL listen ports and specify the three required server-side SSL parameters: identity, private key, and password.

4. Save the file and stop the TIBCO Enterprise Message Service server.
5. Start the TIBCO EMS server with the -ssl_debug_trace option: tibemsd -ssl_debug_trace.
6. Verify server is listening on the SSL port in server console

    2014-04-29 16:14:20.997 Secure Socket Layer is enabled, using OpenSSL 0.9.8y5 
    Feb 2013 
    2014-04-29 16:14:20.998 Accepting connections on ssl://localhost/[::]:7243. 
    2014-04-29 16:14:20.998 Accepting connections on 
    ssl://localhost/0.0.0.0:7243. 
    2014-04-29 16:14:20.998 Accepting connections on tcp://localhost/[::]:7222. 
    2014-04-29 16:14:20.998 Accepting connections on 
    tcp://localhost/0.0.0.0:7222. 
   

7. Use the TIBCO Enterprise Message Service Administration Tool to create an SSL ConnectionFactory, disable host verification (do not disable host verification if you want to verify the client host), and create a queue:

    create factory SSLQueueConnectionFactory queue url=ssl://localhost:7243 
    setprop factory SSLQueueConnectionFactory ssl_verify_host=disabled 
    create queue TibcoQueue 
   

8. Open the Weblogic Administration Console to modify an existing connection pool for connection to Tibco Server. Navigate to Deployment->JmsAdapter->Configuration-> oracle.tip.adapter.jms.IJmsConnectionFactory->Outbound Connection Pools->eis/tibjms/Queue.
9. Set the ConnectionFactoryLocation to SSLQueueConnectionFactory. This is the name of the connection factory you created earlier using the TIBCO Enterprise Message Service Administration Tool.
10. Set the FactoryProperties to (separated into multiple lines for easy reading):

    java.naming.factory.initial=com.tibco.tibjms.naming.     TibjmsInitialContextFactory; 
     java.naming.provider.url=tibjmsnaming://localhost:7243; 
     java.naming.security.principal=<user name on Tibco server>; 
     java.naming.security.credentials=<password>;ThirdPartyJMSProvider=true; 
     com.tibco.tibjms.naming.security_protocol=ssl; 
     com.tibco.tibjms.naming.ssl_enable_verify_host=false; 
     com.tibco.tibjms.naming.ssl_vendor=j2se-default 
     

11. This enables the client to connect without a certificate. Save and update the deployed connection pool.
12. Copy the following jar files located in EMS_HOME\lib to <SOA Installation>/user_projects/domains/<DOMAIN_NAME>/lib directory:

    tibcrypt.jar 
    slf4j-api-1.4.2.jar 
    slf4j-simple-1.4.2.jar 
    tibjms.jar 
    

13. Restart Weblogic Server.
14. In the project to be deployed, the JMS jca file for the JMS adapter might look like the following example.

    Notice that value of DestinationName is TibcoQueue which is the queue created using TIBCO Enterprise Message Service Administration Tool.

    Example - JMS jca File for Prefconfigured TIBCO Connection Factory Scenario

    <connection-factory UIJmsProvider="THIRDPARTY" location="eis/tibjms/Queue" 
               UIConnectionName="SOADEV"/> 
      <endpoint-interaction portType="Produce_Message_ptt" 
           operation="Produce_Message"> 
         <interaction-spec 
             className="oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec"> 
           <property name="TimeToLive" value="0"/> 
           <property name="PayloadType" value="TextMessage"/> 
           <property name="DeliveryMode" value="Persistent"/> 
           <property name="DestinationName" value="TibcoQueue"/> 
         </interaction-spec> 
       </endpoint-interaction> 
    

15. To enable client certificate verification, you must modify EMS_HOME\bin\tibemsd.conf to add the CA certificate which was used to sign the client certificate, for example: ssl_server_trusted = certs/test_client_ca.pem, where test_client_ca.pem is a Tibco-supplied test CA certificate used to sign client certificate test_client_identity.p12. Both files can be found in EMS_HOME\bin\samples\certs. The modified EMS_HOME\bin\tibemsd.conf now looks like the following:

    listen = ssl://localhost:7243 
     ssl_server_identity = certs/server.cert.pem 
     ssl_server_key = certs/server.key.pem 
     ssl_password = password 
     ssl_server_ciphers = all 
     ssl_server_trusted = certs/test_client_ca.pem 
     listen = tcp://localhost:7222 
    

16. Start the TIBCO EMS server with the -ssl_debug_trace option: tibemsd -ssl_debug_trace
17. Modify the FactoryProperties (separated into multiple lines for easy reading):

    java.naming.factory.initial=com.tibco.tibjms.naming.   TibjmsInitialContextFactory; 
     java.naming.provider.url=tibjmsnaming://localhost:7243; 
     java.naming.security.principal=<user name on Tibco server>; 
     java.naming.security.credentials=<password>; 
     ThirdPartyJMSProvider=true; 
     com.tibco.tibjms.naming.security_protocol=ssl; 
     com.tibco.tibjms.naming.ssl_enable_verify_host=false; 
     com.tibco.tibjms.naming.ssl_vendor=j2se-default; 
     com.tibco.tibjms.naming.ssl_identity=<EMS_HOME>/bin/certs/     test_client_identity.p12; 
     com.tibco.tibjms.naming.ssl_trusted=<EMS_HOME>/bin/certs/test_client_ca.pem; 
     com.tibco.tibjms.naming.ssl_ciphers=all
     

18. With these changes, the client can connect to the server with a certificate as shown in the server console:

     2014-04-30 13:39:47.485 Peer certificate: 
     2014-04-30 13:39:47.485 Certificate=[/C=US/ST=California/L=us-english/O=Test 
     Company/OU=test_client 
     Unit/CN=test_client/emailAddress=test_clienttestcompany.com] 
     Issuer=[/C=US/ST=California/L=us-english/O=Test Company/OU=test_client_root 
     Unit/CN=test_client_root/emailAddress=test_client_roottestcompany.com] 
     2014-04-30 13:39:47.485 Peer certificate chain: 
     2014-04-30 13:39:47.485 Certificate=[/C=US/ST=California/L=us-english/O=Test 
     Company/OU=test_client_root 
     Unit/CN=test_client_root/emailAddress=test_client_roottestcompany.com] 
     Issuer=[/C=US/ST=California/L=us-english/O=Test Company/OU=test_client_root 
     Unit/CN=test_client_root/emailAddress=test_client_roottestcompany.com] 
     2014-04-30 13:39:47.485 SSL accepted cipher=RC4-SHA 
    

19. To limit the server to accept SSL connections only, add the following to EMS_HOME\bin\tibemsd.conf:

     ssl_require_client_cert = enable 
    

1. Copy the following files to the <SOAInstall_DIR>/user_projects/domains/<DOMAIN_NAME>/lib folder:

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar

2. Configure the connector factory by modifying the weblogic-ra.xml file in AS11gR1SOA/soa/connectors/JmsAdapter.rar, as shown in the following example:

   <connection-instance>
   <jndi-name>eis/webspheremq/Queue</jndi-name>
      <connection-properties>
         <properties>
            <property>
              <name>ConnectionFactoryLocation</name>
              <value>com.ibm.mq.jms.
                   MQQueueConnectionFactory</value>
            </property>
            <property>
               <name>FactoryProperties</name>
               <value>QueueManager=<QUEUEMANAGER>;
                       TransportType=1;HostName= 
                  <YOUR-HOST>;Port=<YOUR-PORT>;Channel=<CHANNEL>;
                     ThirdPartyJMSProvider=true      
   </value>
             </property>
             <property>
                 <name>AcknowledgeMode</name>
                 <value>AUTO_ACKNOWLEDGE</value>
             </property>
             <property>
                <name>IsTopic</name>
                <value>false</value>
             </property>
             <property>
                <name>IsTransacted</name>
                <value>true</value>
            </property>
            <property>
                <name>Username</name>
                <value><USERNAME></value>
            </property>
            <property>
               <name>Password</name>
               <value><PASSWORD></value>
           </property>
           </properties>
       </connection-properties>
   </connection-instance>
   

   Note that the default <USERNAME> and <PASSWORD> are MUSR_MQADMIN and password, respectively.

   Alternatively, to configure a new connection factory by using the Oracle WebLogic Server Administration Console, use the steps mentioned in Adding an Adapter Connection Factory.

1. Copy the following files to the <SOAInstall_DIR>/user_projects/domains/<DOMAIN_NAME>/lib folder:

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar

   • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar

   • com.ibm.mqetclient.jar

     This IBM-extended transactional client (com.ibm.mqetclient.jar) is required for MQ Series versions prior to version 7. Since version 7 of IBM MQ Series, this com.ibm.mqetclient.jar JAR file is not required to perform XA transactions. XA transactions work acceptably without this JAR file.

2. Configure the connector factory by modifying the weblogic-ra.xml file in AS11gR1SOA/soa/connectors/JmsAdapter.rar, as shown in the following example:

   <connection-instance>
   <jndi-name>eis/webspheremq/Queue</jndi-name>
      <connection-properties>
           <properties>
              <property>
                 <name>ConnectionFactoryLocation</name>
                 <value>com.ibm.mq.jms.                    MQXAQueueConnectionFactory</value>
              </property>
              <property>
                 <name>FactoryProperties</name>
                 <value>QueueManager=<QUEUEMANAGER>;                  TransportType=1; 
                    HostName=<YOUR-HOST>;
                          Port=<YOUR-PORT>;                  Channel=<CHANNEL>;    |            
                          ThirdPartyJMSProvider
                                 =true</value>
              </property
              <property>
                <name>AcknowledgeMode</name>
                <value>AUTO_ACKNOWLEDGE</value>
              </property>
              <property>
                <name>IsTopic</name>
                <value>false</value>
              </property
              <property>
                 <name>IsTransacted</name
                 <value>false</value>
              </property
              <property>
                 <name>Username</name>
                 <value><USERNAME></value>
              </property>
              <property>
                 <name>Password</name>
                 <value><PASSWORD></value>
               </property>
            </properties>
       </connection-properties>
   </connection-instance>
   

   Note that the default <USERNAME> and <PASSWORD> are MUSR_MQADMIN and password, respectively.

   Alternatively, to configure a new connection factory by using the Oracle WebLogic Server Administration Console, use the steps mentioned in Adding an Adapter Connection Factory.

You must complete the following prerequisites for the WebLogic Server JMS text message use case for Oracle BPEL PM.

• Creating Queues in the Oracle WebLogic Server Administration Console:

• Creating the Q2Qorders.xsd file

1. Open JDeveloper.
2. In the Application Navigator, click New Application. The New Gallery dialog is displayed.
3. Select SOA Application and click OK. Enter a name for the application in the Application Name field. For example, queue2queue.
4. Click Next.

   The Name your project page is displayed.

5. In the Project Name field, enter a descriptive name. For example, queue2queue.
6. Click Next. The Configure SOA settings page is displayed.
7. Select Composite With BPEL Process from the Composite Template list, and then click Finish.

   You have created a new application, and a SOA project.

   The Create BPEL Process page is displayed.

8. Enter a name for the BPEL process in the Name field. For example, queue2queue.
9. Select Define Interface Later in the Template list, and then click OK.

   You have created a BPEL process.

   The queue2queue application, queue2queue project, and the SOA composite appear in the design area.

10. Copy the Q2Qorders.xsd file to the XSD folder in your project.

1. Drag and drop JMS Adapter from the Service Adapters list to the Exposed Services swim lane in the composite.xml page. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter Inbound in the Service Name field, and click OK. The JMS Provider page is displayed.
3. Select Oracle Weblogic JMS in the Oracle Enterprise Messaging Service (OEMS) box, and click Next. The Service Connection page is displayed.

   Figure 8-14 The Adapter Configuration Wizard JMS Provider Page

   
   Description of "Figure 8-14 The Adapter Configuration Wizard JMS Provider Page"
4. Select the connection created in Creating an Application Server Connection, as shown in Figure 8-15.

   Figure 8-15 The Adapter Configuration Wizard Service Connection Page

   
   Description of "Figure 8-15 The Adapter Configuration Wizard Service Connection Page"
5. Click Next. The Adapter Interface page is displayed.
6. Select Define from operation and schema (specified later), and click Next. The Operation page is displayed.
7. Select Consume Message, as shown in Figure 8-16, and click Next. The Consume Operation Parameters page is displayed.

   Figure 8-16 The Adapter Configuration Wizard Operation Page

   
   Description of "Figure 8-16 The Adapter Configuration Wizard Operation Page"
8. Click Browse and select ReceiveQueue in the Destination field.

   The Consume Operation Parameters page is displayed.

9. Enter the parameters for the consume operation, and then click Next.

   The Messages page is displayed.

   Note:

   The value specified in the JNDI name should exist in the Oracle JMS Adapter weblogic-ra.xml file to ensure that the Adapter runs in managed mode.

10. Click Browse at the end of the URL field.

    The Type Chooser dialog is displayed.

11. Select Project Schema Files, Q2Qorders.xsd, and Items.

    Figure 8-17 The Type Chooser Dialog

    
    Description of "Figure 8-17 The Type Chooser Dialog"
12. Click Next. The Q2Qorders.xsd schema file is displayed in the URL in the Messages page.

    Figure 8-18 The Adapter Configuration Wizard - Message Page

    
    Description of "Figure 8-18 The Adapter Configuration Wizard - Message Page"
13. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
14. Click Next. The Finish page is displayed.
15. Click Finish. You have configured a JMS inbound adapter service.

1. Drag and drop JMS Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter Outbound in the Service Name field, and click OK. The JMS Provider page is displayed.
3. Select Oracle Weblogic JMS in the Oracle Enterprise Messaging Service (OEMS) box, and click Next. The Service Connection page is displayed.
4. Select the connection created in Creating an Application Server Connection, and click Next. The Adapter Interface page is displayed.
5. Select Define from operation and schema (specified later), and click Next. The Operation page is displayed.
6. Select Produce Message, and click Next. The Produce Operation Parameters page is displayed.
7. Click Browse and select SendQueue in the Destination field. The Produce Operation Parameters page is displayed.
8. Click Next. The Messages page is displayed.
9. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
10. Select Project Schema Files, Q2Qorders.xsd, and Items.
11. Click Next. The Q2Qorders.xsd schema file is displayed in the URL in the Message dialog.
12. Click Next. The Finish page is displayed.
13. Click Finish. You have configured the JMS adapter service, and the composite.xml page is displayed.

1. Drag the small triangle in the inbound Oracle JMS Adapter component in the Exposed Services area to the drop zone that appears as a green triangle in the BPEL process in the Components area.
2. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in the outbound Oracle JMS Adapter in the External References area.

   The JDeveloper Composite.xml is displayed, as shown in Figure 8-19.

   Figure 8-19 The JDeveloper - Composite.xml

   
   Description of "Figure 8-19 The JDeveloper - Composite.xml"
3. Click File, Save All.
4. Double-click queue2queue.

   The queue2queue.bpel page is displayed.

5. Drag and drop the Receive, Assign, and Invoke activities in the order mentioned from the Components window to the Components area, as shown in Figure 8-20.

   Figure 8-20 The queue2queue.bpel Page

   
   Description of "Figure 8-20 The queue2queue.bpel Page"
6. Double-click Receive.

   The Receive dialog is displayed.

7. Click the Browse Partner Links icon at the end of the Partner Link field.

   The Partner Link Chooser dialog is displayed.

8. Select Inbound, and then click OK.

   The Receive dialog is displayed with the Partner Link field populated with the value Inbound.

9. Click the Auto-Create Variable icon that is displayed at the end of the Variable field.

   The Create Variable dialog is displayed.

10. Accept the defaults, and click OK.
11. Select the Create Instance box, as shown in Figure 8-21, and click OK.

    Figure 8-21 The Receive Dialog

    
    Description of "Figure 8-21 The Receive Dialog"
12. Double-click the Invoke activity.

    The Invoke dialog is displayed.

13. Click the Browse Partner Links icon at the end of the Partner Link field.

    The Partner Link Chooser dialog is displayed.

14. Select Outbound, and then click OK.

    The Invoke dialog is displayed with the Partner Link field populated with the value Outbound.

15. Click the Automatically Create Input Variable icon that is displayed at the end of the Input Variable field.

    The Create Variable dialog is displayed.

16. Accept the defaults, and click OK.

    The Invoke dialog is displayed, as shown in Figure 8-22.

    Figure 8-22 The Invoke Dialog

    
    Description of "Figure 8-22 The Invoke Dialog"
17. Click OK.
18. Double-click the Assign activity.

    The Assign dialog is displayed.

19. Click the plus icon, and select Copy Operation. The Create Copy Operation dialog is displayed.
20. Select the variables, as shown in Figure 8-23, and click OK.

    Figure 8-23 The Create Copy Operation Dialog

    
    Description of "Figure 8-23 The Create Copy Operation Dialog"
21. Click OK in the Assign dialog.
22. Click File, Save All.

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em. The composite you deployed appears in the application navigator.
2. In the Last 5 Instances pane, there is an entry of a new instance. This is the instance that was triggered when you enqueued a message using queue2queue.java.
3. Click one of the instances. The Flow Trace page is displayed.
4. Click the TextMessage component instance. The Audit page is displayed.
5. Click the Flow-Debug tab to debug the instance.

The JMS Adapter enables you to interact with WebLogic Server JMS destination locations in a domain that are remote to the WebLogicServer domain where SOA is installed.

Two options are supported that enable you to access remote destinations using the JMS adapter:

• Direct access using specification of the FactoryProperties property in the weblogic-ra.xml file, with access parameters indicating the remote domain.

• Configuring the foreign server to access the remote domain.

For inbound use cases, both options are supported. For outbound use cases only, direct access is supported, but configuring the foreign server is not supported.

You can use the Adapter Configuration Wizard to model a process that enables the Oracle JMS Adapter to be used in a synchronous request reply interaction pattern. In this case, the Oracle JMS Adapter sends a request to the request queue and waits for a response from the reply queue before further execution continues.

Underneath, the Oracle JMS Adapter uses a new interaction pattern, JmsRequestReplyInteractionSpec. This interaction spec allows for a request and reply destination name to be configured.

A variation enables usage of a temporary destination as part of the reply queue. Basically, this pattern enables an Oracle JMS Adapter to send a message to a JMS destination. In turn, the Adapter sets the JMSReplyTo header to the reply destination.

This value is then used by a third-party client to send the message to the reply destination which is then dequeued by the Oracle JMS Adapter.

When using the Oracle JMS Adapter in a synchronous pattern, you can use an XA ConnectionFactory for JMS or BPEL incoming events, and set the connector factory isTransacted property to true in weblogic-ra.xml. However, if you are using a web service, ensure that you use a non-XA ConnectionFactory, and set the connector factory isTransacted property to true in weblogic-ra.xml.

When you use the Oracle JMS Adapter in a synchronous pattern with Oracle WebLogic Server JMS, the connection factory must be weblogic.jms.ConnectionFactory or any other non-XA connection factory. Also, if Oracle WebLogic Server JMS is running in the local JVM (the same JVM as the adapter), then you must ensure that the connector factory isTransacted property is set to false in weblogic-ra.xml.

You can use the Adapter Configuration Wizard to model a process that allows Oracle JMS Adapter to be used in an asynchronous request reply interaction pattern.

Basically this pattern allows an Oracle JMS Adapter to send a message to a JMS destination. When a message is received on the reply queue, the Oracle JMS Adapter can route messages to the correct composite or the component instance. The correlation is done based on the JMSMessageID of the request message, which becomes the JMSCorrelationID of the reply message, and the conversation ID of the underlying component.

In order for the Oracle JMS Adapter request reply to work correctly, the reply component must copy the received JMS message's JMSMessageID to the reply message's JMSCorrelationID. Also, in order for the Oracle Mediator Callback to work with the Oracle JMS Adapter request reply, the reply component must copy the received normalized message's tracking conversationId, InstanceId, CompositeSCAEntityId, and compositeInstanceId to the corresponding properties of the reply normalized message. The following BPEL example shows how to retrieve and copy the properties.

Suppose in BPEL there is a receive activity that receives the request JMS message and there is a reply activity that produces the reply JMS message:

<variables>
  <variable name="receiveInput_Consume_Message_InputVariable" messageType="ns1:Consume_Message_msg"/>
  <variable name="Invoke1_Produce_Message_InputVariable" messageType="ns3:Produce_Message_msg"/>
  <variable name="MessageID" type="xsd:string"/>
  <variable name="JMSReplyTo" type="xsd:string"/>
  <variable name="conversationId" type="xsd:string"/>
  <variable name="InstanceId" type="xsd:string"/>
  <variable name="CompositeSCAEntityId" type="xsd:string"/>
  <variable name="compositeInstanceId" type="xsd:string"/>
</variables>
<receive name="receiveInput" partnerLink="jmsService" portType="ns1:Consume_Message_ptt"
         operation="Consume_Message" variable="receiveInput_Consume_Message_InputVariable" createInstance="yes">
  <bpelx:fromProperties>
    <bpelx:fromProperty name="jca.jms.JMSMessageID" variable="MessageID"/>
    <bpelx:fromProperty name="jca.jms.JMSProperty.JCA_JMSReplyTo" variable="JMSReplyTo"/>
    <bpelx:fromProperty name="tracking.conversationId" variable="conversationId"/>
    <bpelx:fromProperty name="tracking.InstanceId" variable="InstanceId"/>
    <bpelx:fromProperty name="tracking.CompositeSCAEntityId" variable="CompositeSCAEntityId"/>
    <bpelx:fromProperty name="tracking.compositeInstanceId" variable="compositeInstanceId"/>
  </bpelx:fromProperties>
</receive>
<!-- process the received message and create a reply message-->

<if name="If1">
  <documentation>
    <![CDATA[need to check the JMSReplyTo variable to make sure it is not null and contains something like jms_server_name@queue_JNDI_name
            For asynchronous request/reply the received message's jca.jms.JMSProperty.JCA_JMSReplyTo is null]]>
  </documentation>
  <condition expressionLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
     contains($JMSReplyTo, '@')
  </condition>
  <invoke name="Invoke1" inputVariable="Invoke1_Produce_Message_InputVariable"
        partnerLink="jmsReference" portType="ns3:Produce_Message_ptt" operation="Produce_Message"
        bpelx:invokeAsDetail="no">
    <bpelx:toProperties>
      <bpelx:toProperty name="jca.jms.JMSCorrelationID" variable="MessageID"/>
      <bpelx:toProperty name="jca.jms.JMSDestinationName" variable="JMSReplyTo"/>
      <bpelx:toProperty name="tracking.InstanceId" variable="InstanceId"/>
      <bpelx:toProperty name="tracking.CompositeSCAEntityId" variable="CompositeSCAEntityId"/>
      <bpelx:toProperty name="tracking.compositeInstanceId" variable="compositeInstanceId"/>
      <bpelx:toProperty name="tracking.conversationId" variable="conversationId"/>
    </bpelx:toProperties>
  </invoke>
  <else>
    <invoke name="Invoke1" inputVariable="Invoke1_Produce_Message_InputVariable"
          partnerLink="jmsReference" portType="ns3:Produce_Message_ptt" operation="Produce_Message"
          bpelx:invokeAsDetail="no">
      <bpelx:toProperties>
        <bpelx:toProperty name="jca.jms.JMSCorrelationID" variable="MessageID"/>
        <bpelx:toProperty name="tracking.InstanceId" variable="InstanceId"/>
        <bpelx:toProperty name="tracking.CompositeSCAEntityId" variable="CompositeSCAEntityId"/>
        <bpelx:toProperty name="tracking.compositeInstanceId" variable="compositeInstanceId"/>
        <bpelx:toProperty name="tracking.conversationId" variable="conversationId"/>
      </bpelx:toProperties>
    </invoke>  
  </else>
</if>

1. Open JDeveloper.
2. In the Application Navigator, click New Application. The Create Generic Application - Name your Application dialog is displayed.
3. Enter a name for the application in the Application Name field. For example, AQQueue2Queue.
4. In the Application Template list, choose Generic Application.
5. Click Next.

   The Name your project page is displayed.

6. In the Project Name field, enter a descriptive name. For example, AQQueue2Queue.
7. In the Available list in the Project Technologies tab, double-click SOA to move it to the Selected list.
8. Click Next. The Create Generic Application - Configure SOA Settings page is displayed.
9. Select Composite With BPEL from the Composite Template list, and then click Finish.

   You have created a new application and a SOA project.

   The Create BPEL Process page is displayed.

10. Enter a name for the BPEL process in the Name field.
11. Select Define Interface Later in the Template list, and then click OK.

    You have created a BPEL process.

    The AQQueue2Queue application, the AQQueue2Queue project, and the SOA composite appear in the design area.

12. Create a file named expense.xsd in the XSD folder in your project:

    Contents of expense.xsd:

    <?xml version= '1.0' encoding= 'UTF-8' ?>
    <schema elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/pcbpel/samples/expense"
         xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://xmlns.oracle.com/pcbpel/samples/expense">
        <element name="ExpenseRecord">
            <complexType>
                <sequence>
                    <element name="EmpId" type="integer" minOccurs="0"/>
                    <element name="Item" type="string" minOccurs="0"/>
                    <element name="Count" type="integer" minOccurs="0"/>
                    <element name="Cost" type="double" minOccurs="0"/>
                </sequence>
            </complexType>
        </element>
    </schema>

1. Drag and drop JMS Adapter from the Service Adapters list into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter Inbound in the Service Name field, and click OK. The JMS Provider page is displayed.
3. Select Oracle Advanced Queueing in the Oracle Enterprise Messaging Service (OEMS) box, and click Next. The Service Connection page is displayed.
4. Select the connection created in Creating an Application Server Connection.
5. Click Next. The Adapter Interface page is displayed.
6. Select Define from operation and schema (specified later), and click Next. The Operation page is displayed.
7. Select Consume Message, and click Next. The Consume Operation Parameters page is displayed.
8. Click Browse and select testInQueue in the Destination field.
9. Click Next. The Messages page is displayed.
10. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
11. Select Project Schema Files and expense.xsd.
12. Click Next. The expenses.xsd schema file is displayed in the URL field in the Messages page.
13. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
14. Click Next. The Finish page is displayed.
15. Click Finish. You have configured a JMS inbound adapter service.

1. Drag and drop JMS Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter Outbound in the Service Name field, and click OK. The JMS Provider page is displayed.
3. Select Oracle Advanced Queueing in the Oracle Enterprise Messaging Service (OEMS) box, and click Next. The Service Connection page is displayed.
4. Select the connection created in Creating an Application Server Connection, and click Next. The Adapter Interface page is displayed.
5. Select Define from operation and schema (specified later), and click Next. The Operation page is displayed.
6. Select Produce Message, and click Next. The Produce Operation Parameters page is displayed.
7. Click Browse and select testOutQueue in the Destination field. The Produce Operation Parameters page is displayed.
8. Click Next. The Messages page is displayed.
9. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
10. Select Project Schema Files, expense.xsd.
11. Click Next. The expense.xsd schema file is displayed in the URL field in the Message dialog.
12. Click Next. The Finish page is displayed.
13. Click Finish. You have configured the JMS adapter service, and the composite.xml page is displayed.

1. Drag the small triangle in the inbound Oracle JMS Adapter component in the Exposed Services area to the drop zone that appears as a green triangle in the BPEL process in the Components area.
2. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in the outbound Oracle JMS Adapter in the External References area.

   The JDeveloper Composite.xml is displayed, as shown in Figure 8-24.

   Figure 8-24 JDeveloper - Composite.xml

   
   Description of "Figure 8-24 JDeveloper - Composite.xml"
3. Click File, Save All.
4. Double-click the BPEL process. The BPELProcess1.bpel page is displayed.
5. Drag and drop the Receive, Assign, and Invoke activities, in the order mentioned, from the Components window to the Components area.
6. Double-click the Receive activity.

   The Receive dialog is displayed.

7. Click the Browse Partner Links icon at the end of the Partner Link field.

   The Partner Link Chooser dialog is displayed.

8. Select Inbound, and then click OK.

   The Receive dialog is displayed with the Partner Link field populated with the value Outbound.

9. Click the Auto-Create Variable icon that is displayed at the end of the Variable field. The Create Variable dialog is displayed.
10. Accept the defaults, and click OK.
11. Check the Create Instance box.
12. Double-click the Invoke activity to Outbound.

    The Invoke dialog is displayed.

13. Click the Automatically Create Input Variable icon that is displayed at the end of the Input Variable field.
14. Click the Browse Partner Links icon at the end of the Partner Link field.

    The Partner Link Chooser dialog is displayed.

15. Select Outbound, and then click OK.

    The Invoke dialog is displayed with the Partner Link field populated with the value Outbound.

16. Accept the defaults, and click OK.
17. Click OK.
18. Double-click the Assign activity.

    The Assign dialog is displayed.

19. Click the plus icon, and select Copy Operation.

    The Create Copy Operation dialog is displayed.

20. Select the variables, and click OK.
21. Click OK in the Assign dialog.
22. Click File, Save All.

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em. The composite you deployed appears in the application navigator.
2. In the Last 5 Instances pane, there is an entry of a new instance. This is the instance that was triggered when you enqueued a message by using AQQueue2Queue.java.
3. Click one of the instances. The Flow Trace page is displayed.
4. Click the TextMessage component instance. The Audit page is displayed.
5. Click the Flow-Debug tab to debug the instance.

You use three FactoryProperty parameter values to provide adapter access to distributed topics, to specifically enable the Client ID to be shared by multiple connections, to enable the sharing of Durable subscriptions among multiple 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 cases, so typically you do not have to set it. See the following example:

  </property>
     <name>FactoryProperties</name>
  <value>ClientIDPolicy=UNRESTRICTED</value>
  
   </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 do not have to change the value.

   <property> 
      <name>FactoryProperties</name> 
      <value>SubscriptionSharingPolicy=
                 SHARABLE</value> 
   </property>
   

• TopicMessageDistributionAll

  See the section on Distributed Topics for more information on the TopicMessageDistributionAll FactoryProperties parameter. You can set it as in the following example:

  <property>
      <name>FactoryProperties</name>
      <value>TopicMessageDistributionAll=true</value>
  </property>
  

Specific inbound and outbound queue and error handling behaviors apply to the JMS Adapter with WebLogic Server 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.

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 follow.

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 must 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 the JMS Adapter.When using Replicated Distributed Topics, you must configure JMS adapter to use the unrestricted clientid and shared subscription policy, which are the default settings. In addition, you must specify the following message selector, NOT JMS_WL_DDForwarded when defining an activation spec.

To achieve better performance, you should use Partitioned Distributed Topics.

Refer to the following example, consisting of a snippet of a connection instance from the weblogic-ra.xml file for a local cluster:

<property>
    <name>FactoryProperties</name>
    <value>ClientID=SOAClient1;</value>
</property>

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 have 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, the 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 connection instance in the weblogic-ra.xml file.

An example usage (a snippet of a connection instance from a weblogic-ra.xml file for a local cluster) is:

<name>FactoryProperties</name>
<value>ClientID=SOAClient2;
       TopicMessageDistributionAll=true</value>
</property>

To achieve better performance, you should use Partitioned Distributed Topics.

When using Replicated Distributed Topics, 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, the 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 connection instance in weblogic-ra.xml. An example usage (snippet of connection instance from weblogic-ra.xml for a local cluster) is:

<name>FactoryProperties</name>
<value> ClientID=SOAClient2;
       TopicMessageDistributionAll=true</value>
</property>

In addition, you must specify the message selector, NOT JMS_WL_DDForwarded when defining an activation spec.

You can obtain user-specified value from the interaction spec instance.

All JMS message properties are available as Normalized Message properties. You can get the unit-of-order property by looking up the Normalized message property jca.jms.JMSProperty.JMS_BEA_UnitOfOrder on the delivered message.

1. On the JMS Adapter Configuration Wizard Screen, select Synchronous Consume Message.

   Figure 8-32 JMS Adapter Configuration Wizard Operation Screen, with Synchronous Consume Message Selected

   
   Description of "Figure 8-32 JMS Adapter Configuration Wizard Operation Screen, with Synchronous Consume Message Selected"
2. The JMS Adapter Configuration Wizard Synchronous Consume Parameters Screen appears, where you can enter parameters for the Synchronous Consume Screen. Enter a Message

   • Enter a Destination Name or Select Browse to open the Destination Browser.

   • Select a Message Body Type from the Chooser. Choices are:

     • TextMessage

     • BytesMessage

     • MapMessage

   • Enter a Message Selector.

     This field is optional. It filters messages based on header and property information. The message selector rule is a Boolean expression. If the expression is true, then the message is consumed. If the expression is false, then the message is rejected.

     Some examples are supplied on the screen. For other examples, you can enter logic, such as:

     • JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected.

     • JMSType = 'car' AND color = 'blue' AND weight > 2500

     • Country in ('UK', 'US', 'France')

   • Specify a JNDI name. This is also filled in when you select a Destination Name.

   Figure 8-33 The JMS Adapter Configuration Synchronous Consume Screen

   
   Description of "Figure 8-33 The JMS Adapter Configuration Synchronous Consume Screen"
3. If you selected Browse to open the Destination Browser, on this Browser:

   • Choose a Destination Type by selecting the Destination Type: All Types, Queues, or Topics.

   • Supply a Destination or click Search to search from those Destinations that populate the browser. Click Show All to show expand the list of Destinations.

   • Select a Destination, and click OK to use that Selection in the Synchronous Parameters page.

   Note:

   When using the Oracle JMS Adapter in a synchronous pattern, you can use an XA ConnectionFactory for JMS or BPEL incoming events, and set the connector factory isTransacted property to true in weblogic-ra.xml. However, if you are using a web service, ensure that you use a non-XA ConnectionFactory, and set the connector factory isTransacted property to true in weblogic-ra.xml.

   Figure 8-34 The JMS Adapter Configuration Wizard Select Destination Browser Screen

   
   Description of "Figure 8-34 The JMS Adapter Configuration Wizard Select Destination Browser Screen"
4. The JMS Adapter Configuration Wizard displays the JMS Adapter Messages Screen. On this screen, select Native Format is Not Required (Schema is Opaque) or browse to find a schema or open the Native Format Builder.