Technical detail
IBM WebSphere MQ Bridge for HTTP
This new SupportPac provides a simple way to access data on WebSphere MQ for applications that use HTTP. It bridges between MQ resources – both queues and publish-subscribe topics - and HTTP or HTTPS networks. This SupportPac requires a J2EE Application Server to provide the HTTP server-side stack and is offered without support.
Visit the WebSphere MQ SupportPac site to download and install it:
Uses for the Bridge
The WebSphere MQ Bridge for HTTP can provide simple access for Web 2.0, Web services and applications that don't require MQ clients.
Large client environments
For those who deal with large numbers of applications that require only very simple access to WebSphere MQ, the Bridge for HTTP offers a way to connect these applications without first installing WebSphere MQ clients: "zero-client" access. This can provide:
Simplified deployment and maintenance of large scale distributed applications
No need to install and set-up WebSphere MQ clients
No WebSphere MQ client footprint
Web 2.0
For those who want to create a rich Web experience with AJAX and REST, the Bridge for HTTP offers a simple to way to access business data from core applications to present to Web users as well as to collect data from Web applications.
Speeds and eases integration of new Web apps with enterprise applications and data
Helps deliver richer content to Web users
Provides a publish/subscribe data movement model for Web applications
No MQ skills needed to access data on MQ
Simple MQ Access
Simple AJAX commands provide a REST (Representational State Transfer) style of access to message data on WebSphere MQ queues and to topics for publishing and subscribing. The following examples show how easy it is to access MQ using AJAX (Asynchronous JavaScript and XML) commands.
Examples
| Sample AJAX code and URIs | resource = Queue | resource = Topic | WebSphere MQ API equivalent |
|---|---|---|---|
| this.XMLHttpRequest.open('GET', "http://host/msg/queue/resource"); | Reads next message from Queue | Reads next message on that topic | MQGET with browse |
| this.XMLHttpRequest.open('POST', "http://host/msg/queue/resource"); | Added data as message to Queue | Publishes data on that topic | MQPUT |
| this.XMLHttpRequest.open('DELETE', "http://host/msg/queue/resource"); | Retrieves and removes next message from Queue | Reads subscription and deletes message | MQGET |
