JMS V2 connection: SonicMQ
By enabling SonicMQ, the JMS V2 connector can connect to the SonicMQ provider.
To enable SonicMQ messaging, upload the following JAR files into your account library (Settings > Development Resources > Account Libraries), add those files to a Custom Library component, and deploy the component to the appropriate basic runtime, runtime cluster, runtime cloud, or environment.
-
sonic_XA.jar -
sonic_Crypto.jar -
sonic_Client.jar -
sonic_ASPI.jar -
mfcontext.jar
Upload the JAR files into your Integration account library (Settings > Development Resources > Account Libraries). For more information, refer to 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.
Uploaded or imported files pass through a virus scanner first. If the scan detects a virus, you receive an error message, and the scan rejects the file. If an error persists, contact Boomi Support.
Communication Options tab
JMS Server Type - Select SonicMQ to see some default settings specific to SonicMQ.
Connection Factory JNDI Lookup - Set to the name of the connection factory you created earlier.
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 SonicMQ Classic server to.
JMS Properties - (Optional) Used to add JMS property names and values.
