Configure a Foreign Server using a Databases JDBC URL Limitations when using Stand-alone WebLogic AQ JMS Clients

Interoperating with Oracle AQ JMS 7-15 ojdbc6.jar, orai18n.jar and one of the following WebLogic client jars: wlthint3client.jar, wlclient.jar, or wlfullclient.jar. For applications running outside the WebLogic Servers JVM: ■ A configured WebLogic JMS Foreign Server references the databases URL, as well as other JDBC driver configurations. See Section 7.4.3.1, Configure a Foreign Server using a Databases JDBC URL. ■ Local JNDI names are defined for AQ JMS connection factories and destinations as part of the WebLogic JMS Foreign Server configuration. These JNDI names are configured to map to existing AQ connection factories and destinations. ■ Stand-alone clients reference local JNDI names. Unlike applications that run on WebLogic Server, stand-alone clients need to ensure that the driver and AQ client are on the classpath.

7.4.3.1 Configure a Foreign Server using a Databases JDBC URL

Specify the db_url, java.naming.security.principal JNDI properties and a password in jndi-properties-credentials. For Example: foreign-server initial-context-factoryoracle.jms.AQjmsInitialContextFactoryinitial-context-fa ctory jndi-properties-credential-encrypted{3DES}g8yFFu1AhP8=jndi-properties-credenti al-encrypted jndi-property keyjava.naming.security.principalkey valuej2eevalue jndi-property jndi-property keydb_urlkey valuejdbc:oracle:thin:{hostname}:{port}:{sid}value jndi-property foreign-server where: ■ The value of the db_url JNDI property is the JDBC URL used to connect to the AQ JMS Oracle database. ■ The value of the java.naming.security.principal is the database user name AQ JMS uses to connect to the database. ■ jndi-properties-credentials contains the database password. No other configuration properties are required.

7.4.3.2 Limitations when using Stand-alone WebLogic AQ JMS Clients

The following section provides limitations to consider when creating and using stand-alone WebLogic JMS clients. This release does not support: ■ Use of a WebLogic AQ JMS stand-alone client to automatically participate in global transactions managed by WLS. 7-16 Configuring and Managing JMS for Oracle WebLogic Server ■ Connection pooling for WebLogic AQ JMS stand-alone clients. ■ Looking up JMS objects defined by an AQ JMS foreign server using a data source.

7.5 Related Documentation

The following section provides links to related documentation: ■ Oracle Streams Advanced Queuing Users Guide ■ Performance and Tuning for Oracle WebLogic Server ■ FAQs: Integrating Remote JMS Providers in Programming JMS for Oracle WebLogic Server ■ Configuring and Managing JMS for Oracle WebLogic Server ■ Programming Stand-alone Clients for Oracle WebLogic Server