Registering JMS Vendors with ION

You can register external JMS vendors in ION, to use the message queue connection point as a JMS client.

The ION JMS client connector is tested with these external vendors under their default installation conditions:

  • IBM WebSphere MQ 7.1.0
  • Tibco EMS 6.3.0 and 8.2
  • ActiveMQ 5.15.2
  • Oracle AQ 11.2.0.1

Additionally, you can also use ION to connect to another JMS vendor.

You can connect ION to any of the external JMS queues, you must register the client libraries of the external JMS vendors with ION. These Client libraries are usually not distributable. So, to connect to the queues of external vendors, you must have the client libraries. You must wrap these libraries into a bundle that you can deploy in ION. You can perform this bundle wrapping process on any machine. You must upload the final output to ION Service using the options in ION Desk.

Because the bundle wrapper program is run externally, the standard JAVA_HOME environment variable is used by ION. Therefore, a Java Software Developer's KIT, or JDK, is required that is installed and configured on the machine where you run the program. Ensure that you install JDK, not a Java Runtime Environment (JRE). The version of JDK you install must be supported by ION. For the current JDK version supported by ION, see the Infor ION Installation and Configuration Guide (U9854 US).

Note: The bundle wrapper registration process in ION requires technical knowledge of Java and JMS technologies.

You can create a Message queue connection point based on the any of the registered vendors. The list of properties in the connection point reflects the definition in the vendor specific class at that time and permanently remains fixed. When, altering the properties of an existing vendor specific class and you re-upload the driver. The older properties are still present in any previously defined connection points of that type. Therefore, if you change the list of properties in your driver you are required to recreate your connection point.

To have Active Connection point counters working for Tibco Vendor, you must use an admin user with at least "view-all" authorization. A non-admin user is not authorized to get Message Queue counts. This applies to all connectivity types such as TCP, SSL, and JNDI.