Developing web services with IBM MQ bridge for HTTP

Developing web services with IBM MQ bridge for HTTP

With IBM MQ bridge for HTTP, client applications can exchange messages with IBM MQ without the need to install an IBM MQ MQI client. We can call IBM MQ from any platform or language with HTTP capabilities.

Note: From IBM MQ Version 8.0, the IBM MQ bridge for HTTP is deprecated. The IBM messaging REST API provided from IBM MQ Version 9.0.4 should be used as an alternative.

Introduction to IBM MQ bridge for HTTP
The IBM MQ bridge for HTTP is a Java™, Enterprise Environment (JEE) Web application. HTTP clients can send POST, GET, and DELETE requests to it to put, browse and delete messages from IBM MQ queues. The IBM MQ bridge for HTTP is not suitable for use with messages, if assured delivery is required.
Install, configuring, and verifying IBM MQ bridge for HTTP
Obtain IBM MQ bridge for HTTP by installing Java Messaging and Web Services from either the IBM MQ MQI client or server installation materials. Deploy IBM MQ bridge for HTTP to a suitable application server.
Publish/subscribe using the IBM MQ bridge for HTTP
IBM MQ bridge for HTTP uses the IBM MQ classes for JMS publish/subscribe interface. HTTP POST creates a publication. HTTP DELETE creates a non-durable managed subscription. You must configure publish/subscribe for JMS before using the topic URI.
Running the IBM MQ bridge for HTTP samples
The IBM MQ bridge for HTTP samples are available for use on only the Windows operating system. The samples show you how to submit HTTP POST and HTTP DELETE commands to IBM MQ bridge for HTTP from Java programs.
Security considerations for IBM MQ bridge for HTTP
Standard web security considerations apply to authenticating a web browser client. Authorization to IBM MQ resources is at the level of the user running the IBM MQ bridge for HTTP servlet, and not the individual web browser client. Standard IBM MQ security consideration apply to IBM MQ.
Parent topic: Developing REST applications with IBM MQ