Messaging and Queuing provides asynchronous capabilities. The employment of messaging and queuing (a traditionally peer-to-peer transport mechanism) for use in a client/server processing model makes the server a uniquely flexible tool. The server now provides a fully asynchronous connector, which can access data on multiple platforms using standard commercial messaging software products (IBM's MQSeries) as a vehicle.
The components of Messaging are:
An application can create requests intended for servers without any live direct connection to those servers and without any connection to a network service. Local requests (Units of Work) are safe stored on the local queuing mechanism until access is available to the XML Transformation Engine's queues. The Message Hub processes Units of Work from many connectors by creating synchronous connections to servers in a multi-threaded processing environment. It then passes any results it receives from these Units of Work back to the original connector requester.
In the connector, the server's messaging-capable API is available. For more information, see Messaging and Queuing.
| iWay Software |