Message queue connection points

You can use connectivity through message queues.

In ION Desk you can create a connection point to read or write a message queue. ION uses JMS (Java Messaging Standard) queues. This enables you to send or receive messages to or from ION.

The Message Queue Connector of ION acts either as a JMS server or as a JMS client. When the connection point is configured as a JMS Server, the required message queues are generated and hosted by ION. ActiveMQ is used. If your application can read or write JMS message queues without using JMS, you can connect through ION.

If you are already using JMS queues from another server, you must implement a bridge. This bridge reads the JMS messages from your own queue and writes them to the ION queue or the other way around.

A connection point that is configured as a JMS Client, enables ION to directly connect to external JMS queues that are provided by other vendors. Messages are transported back and forth.

Regardless of using the connection point as a server or a client, you can use complete BODs as messages, or use any XML message. In the latter case,ION ensures that your XML message is packed as a BOD in the ION Service. In this way, your data can be handled and monitored in ION like any other BOD. For example, you can use mapping or content-based routing on your messages, trigger alerts and workflows. Consequently, you can use message queue connection points in a document flow like any other type of connection point.

A message queue connection point specifies:

  • The standard properties for any connection point, such as name and tenant. Note that for message queue connection points the logical ID type is fixed ('jms'), the logical ID is lid://infor.jms. followed by the converted name.
  • What queue(s) to use and how to connect to these queues.
  • Which documents can be sent and received and how the BODs must be translated to JMS messages or the other way around.

For an explanation about the connection properties for Message queue connection point that are used as a JMS client, see the Connection properties.

For configuring Message queue connection point as a JMS Server see Configuring a message queue connection point as a JMS server.

Note: The option of using the Message queue connection point as a JMS provider is deprecated and placed on maintenance mode. When you use this option, consider switching to the JMS client option or use the IMS connector for an API based approach. This also provides you with a proactive migration path to move to the ION cloud edition.