z/VSE Access to MQ server via REST
Ingolf24 120000DRN3 Visits (1731)
The WebSphere MQ Server for z/VSE is no longer in service since September 2015. If you are dependent on messaging, you can use the WebSphere MQ Client for VSE and MQ Trigger Monitor on z/VSE as a replacement and connect to a MQ server on a supported MQ platform. More information and the downloads are in the IBM Knowledge Center at z/VSE 6.2 topic "Using the z/VSE MQ Client Trigger Monitor for Asynchronous Inter-Program Communication" - here.
We also prepared a white paper "Migrating from MQ Server on z/VSE to MQ Client using the z/VSE MQ Client Trigger Monitor" - here.
z/VSE 6.2 introduces Representational State Transfer (REST) support, see my related blog entry. In z/VSE you may use REST to send and receive information between CICS programs and other modules over the internet via RESTful web services.
More details are described in the z/VSE e-business Connectors User's Guide, Chapter 25 Using REST for Inter-Program Communication. This book can be downloaded from the z/VSE 6.2 PDF Library in the IBM Knowledge Center - here.
Since some time IBM MQ for Multiplatforms supports REST APIs. That is instead of the MQ client you may also use z/VSE's REST support to connect to the MQ Server on a non-z/VSE platform.
The messaging REST API comes as standard with IBM MQ from IBM MQ Version 9.0.4 and is enabled by default. You can use the messaging REST API to send and receive IBM MQ messages in plain text form
Developing REST applications with IBM MQ" is described in the IBM Knowledge Center - here.
A few weeks ago IBM MQ announced enhancements to their IBM MQ V9.1.2 for Multiplatforms product.
The MQ V9.1 LTSR (Long Term Service Release) delivered the ability to call MQ messaging functions through REST API calls. Lightweight and simple applications can use a subset of MQ functions quickly and easily without requiring an MQ client library to be bound with the applications.
Have a good weekend.