OE to IBM WebSphere

Posted by skevin.john on 07-Aug-2014 11:42

Hi,

Is it possible to post messages to IBM Webshpere MQ via RESTful webservice? If yes, please share the ways to do so..

Thanks,

Kevin Joe

OpenEdge Development - Forum
Posted by Bill Wood on 07-Aug-2014 11:55

I am not a WebSphereMQ expert, but the last time I recall looking, there is no native WebSphereMQ endpoint for REST.   That is the piece you need.  You need some Web Server (or something acting like a Web Server) that exposes a public REST or SOAP Endpoint for receiving messages.

If you have that, then you can use OpenEdge Web Services (for SOAP) or Sockets (for REST) to send messages to that endpoint.  (The fact that the endpoint itself does a WebSphere "send" is not really visible to the SOAP or REST endpoint.)

One issue that you may next ask is:  "Is it possible to RECEIVE messages from WebSphere into OE?".     The REST/SOAP won't work here (you can do a synchronous receive, but you can't do an async one.).      You could, however, take WebSphere server and have a MDB (Message Driven Bean) that listens to WebSphereMQ destinations and then used OpenEdge Open Client to call back to OE AppServer.

One more thought is this:

The architecture does have the following points to consider:

  • STOMP is NOT JMS, so the use of messaging in the ABL will need to change in small ways.  (e.g. there are fewer message types, and there are limitations on message size and QOS that are different from JMS generally and SonicMQ in particular.
  • The StompConnect service does need to be a running process that you connect to.  While it does not need to be local on every machine, Iwould generally try to keep it co-located with each AVM.

Posted by Bill Wood on 08-Mar-2016 08:29

BTW... Starting in OpenEdge 11.5.1,  Progress OpenEdge provides a generic Java Message Service (JMS) adapter for messaging. This generic JMS adapter can operate with any JMS-compliant vendor, including SonicMQ, IBM WebSphereMQ, and ActiveMQ.    

You can get more information in the product documentation, or look at the whitepaper on Community at

https://community.progress.com/community_groups/openedge_development/m/documents/1986

All Replies

Posted by Bill Wood on 07-Aug-2014 11:55

I am not a WebSphereMQ expert, but the last time I recall looking, there is no native WebSphereMQ endpoint for REST.   That is the piece you need.  You need some Web Server (or something acting like a Web Server) that exposes a public REST or SOAP Endpoint for receiving messages.

If you have that, then you can use OpenEdge Web Services (for SOAP) or Sockets (for REST) to send messages to that endpoint.  (The fact that the endpoint itself does a WebSphere "send" is not really visible to the SOAP or REST endpoint.)

One issue that you may next ask is:  "Is it possible to RECEIVE messages from WebSphere into OE?".     The REST/SOAP won't work here (you can do a synchronous receive, but you can't do an async one.).      You could, however, take WebSphere server and have a MDB (Message Driven Bean) that listens to WebSphereMQ destinations and then used OpenEdge Open Client to call back to OE AppServer.

One more thought is this:

The architecture does have the following points to consider:

  • STOMP is NOT JMS, so the use of messaging in the ABL will need to change in small ways.  (e.g. there are fewer message types, and there are limitations on message size and QOS that are different from JMS generally and SonicMQ in particular.
  • The StompConnect service does need to be a running process that you connect to.  While it does not need to be local on every machine, Iwould generally try to keep it co-located with each AVM.

Posted by skevin.john on 18-Aug-2014 11:11

Thanks Bill for the details.

I dont see any detailed steps for IBM Websphere in the portal.

Does anyone have detailed steps for this?

Posted by Bill Wood on 08-Mar-2016 08:29

BTW... Starting in OpenEdge 11.5.1,  Progress OpenEdge provides a generic Java Message Service (JMS) adapter for messaging. This generic JMS adapter can operate with any JMS-compliant vendor, including SonicMQ, IBM WebSphereMQ, and ActiveMQ.    

You can get more information in the product documentation, or look at the whitepaper on Community at

https://community.progress.com/community_groups/openedge_development/m/documents/1986

This thread is closed