Deploying the JMS vendor

After the preparation is complete, you can deploy the JMS vendor in ION.

To deploy a specific JMS driver in ION:

  1. Ensure that the custom jar is placed into the JMSClientBundleWrapper\OriginalJar folder.
  2. Ensure that the VendorSpecificJmsImpl.java file is properly implemented and placed into the JMSClientBundleWrapper\OriginalJar folder.
  3. Ensure that the properties.txt file reflects the vendor specifics and is placed in the /JMSClientBundleWrapper folder.
  4. Run the build.bat script. These results are possible:
    • The BUILD SUCCESSFUL message is displayed. A zip file is created (OSGi bundle) in the /JMSClientBundleWrapper folder. This file is required to start up the bundle.
    • The execution of build.bat fails because of insufficient write privileges or because of lack of correct jar files. A relevant detail error message is displayed. Take corrective action based on the error and retry.
  5. Complete these steps:
    1. In ION Desk, select Configure > ION Service. Then click the Configuration Files tab.
    2. In the Custom JMS Client libraries section, click Upload.
    3. Upload the zip file.
    4. If this is a replacement of an already active driver, then the ION service must restart. Click Yes and wait for a few minutes until the ION service is running again
    If the upload is successful, a message that the file is uploaded is displayed. The entry is displayed in the list of Custom JMS Client Libraries.
Now you can model your Message queue connection point as a client using the new JMS client registered..