About queued message exchange for integrations via Messaging
Axway Integrator supplies services for transforming, enhancing, validating and routing the files and messages that transit in your network.
Axway Messaging provides Messaging-Oriented Middleware services. It enables independent and potentially non-concurrent applications installed in a distributed system to communicate with each other via managed message queues.
Integrator can use the services of Messaging for queued reception and distribution of messages.
Integrator exchanges messages with Messaging via JMS. The Integrator JMS Connector supplies the services that permit this interconnection. On the Messaging Server side, a JMS API handles deposit and read queue events using the JMS standards.
The topics in this book describe how to combine the services of Integrator and Messaging to create a system of queued message handling.
To provide queued messaging services for messages that transit Integrator, you require the following Axway products:
You can install these products on different machines and/or different platforms.
In the case of an installation on the same machine, it is possible to use either the same or a different user for the installation.
You create the connection between Integrator and Messaging via the JMS (Java Message Service) Connector of Integrator. This Connector can also be used to connect Integrator to any JMS provider, such as WebLogic, WebSphere or OpenJMS.
The following figure illustrates the connection architecture described in this document.
For the example described in this document, the installation of the products has the following characteristics:
Objects to create in Composer:
Integration connectivity via Messaging: General procedure