Skip to main content
Feedback

JMS v2 connection: Oracle AQ (WebLogic)

By enabling Oracle AQ (WebLogic), the JMS v2 connector can connect to the Oracle AQ (WebLogic) provider.

Use the JMS Oracle AQ (WebLogic) connection component to connect to Oracle AQ via WebLogic. Use the JMS Oracle AQ connection component to connect with Oracle AQ directly when you do not want to maintain a WebLogic instance.

To enable Oracle AQ (WebLogic) messaging, upload the following JAR files into your Integration account library (Setup > Account Libraries). For more information, see the topics Creating a Custom Library component, and Custom library deployment considerations to deploy the appropriate basic runtime, runtime cluster, runtime cloud, or environment. Uploaded or imported files first pass through a virus scanner. The upload or import results in an error if it detects a virus, and then rejects the file. If an error persists, contact Boomi Support.

  • wljmsclient.jar

  • wlthint3client.jar

caution

Boomi does not recommend manually copying the wljmsclient.jar and wlthint3client.jar JAR files to the lib and userlib installation directories for basic runtimes, runtime clusters, and runtime clouds.

Communications Options tab

JMS Server Type - Select Oracle AQ (WebLogic) to see default settings specific to Oracle AQ (WebLogic).

Connection Factory JNDI Lookup - The default is blank.

Initial Context Factory - A text field where users can input their JNDI initial context factory object into.

Provider URL - A text field where users can input the URL to point to your Oracle AQ (WebLogic) server to.

JMS Properties - (Optional) Used to add JMS property names and values.

On this Page