Overview of IBM WebSphere Message Queue |
Posted: March 2, 2018 |
IntroductionIBM MQ is robust messaging middleware that simplifies and accelerates the integration of diverse applications and business data across multiple platforms. IBM MQ facilitates the assured, secure and reliable exchange of information between applications, systems, services and file by sending and receiving message data via messaging queues, thereby simplifying the creation and maintenance of business applications. It delivers Universal Messaging with a broad set of offerings to meet enterprise-wide messaging needs, as well as connectivity for the internet of things and mobile devices. IBM MQ Advanced for Developers is available at no-charge for development purposes for Windows and Linux platforms. There is also a no-charge, 90-day trial for all platforms. IBM MQ provides: Rapid, seamless connectivity of information with a single, robust and trusted messaging backbone for dynamic heterogeneous environments. Rapid, seamless connectivity of information** Provides a comprehensive, secure and reliable messaging solution to support conventional and emerging messaging needs. Secure, reliable message delivery>> Assures delivery of information – once and only once – with the highest quality of service. High performance and scalable message transfer** Flexible solution that allows rapid response to changes, reducing the need to modify code in the applications. Simplified management and control>> Integrates capabilities of IBM MQ with IBM Managed File Transfer, IBM Advanced Message Security and IBM MQ Telemetry in a single offering – IBM MQ Advanced. Lower cost of ownership** Reduces the cost and effort associated with managing multiple solutions using a unified messaging solution. Basic MQ architectureWhen integrating with IBM WebSphere MQ system, a DataPower service performs messaging system bridging from variety of protocols to the MQ protocol or from the MQ protocol to a variety of protocols. The service also supports message traffic from the MQ protocol to the MQ protocol and provides transformation, security, authorization, routing, logging and customization services. 1. A DataPower service connects an HTTP-based messaging system to a back-end WebSphere MQ system In both of these architectures, the DataPower service acts as a WebSphere MQ client only. The service does not act as a WebSphere MQ queue manager. Figure 1 illustrates the basic architecture implemented when a DataPower service is used to connect an HTTP-based messaging system (typical of a Web Services architecture) to a WebSphere MQ-based system inside the enterprise. The figure illustrates the primary configuration objects created on the appliance as well as the configuration of the MQ Queue Manager to which the service connects and exchanges messages.
The Front Side Handler object implements HTTP transport connectivity on the client, or front, side of the service. On the back end, the Multi-Protocol Gateway employs MQ-based URLs to determine the WebSphere MQ queue to which requests are forwarded, and also from which replies are pulled. Conversely, Figure 2 illustrates a DataPower service being used to extend a WebSphere MQ-based messaging system out to a Web Services architecture. Here, the Front Side Handler object polls a WebSphere MQ queue for request messages and places replies from the back-end services on another WebSphere MQ queue. The Front Side Queue Manager object might optionally place messages in an error queue on the WebSphere MQ queue manager. On the back end, a standard HTTP URL is used to determine the destination to which requests are forwarded, and from which answers are received in accordance with the HTTP specification.
|
|||||||||||||||||||||||||||||||||||||||||||
|