JMS connection: Generic JNDI
By enabling Generic JNDI, the JMS connector can connect to the Generic JNDI provider.
To enable Generic JNDI, upload the provider's 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.
Upload the JAR files into your Integration account library (Settings > Development Resources > Account Libraries). For more information, refer to 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.
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 Generic JNDI, then provide all the information to connect to a JMS provider via JNDI.
Connection Factory JNDI Lookup - JNDI name of the connection factory.
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 Generic JNDI server to.
JMS Properties - Any additional properties that need to be set on the initial context
