B
Bill Wood
Guest
There are two related posts with my suggestions below: https://community.progress.com/technicalusers/f/19/t/12055.aspx (Sending Message to WebSphereMQ) https://community.progress.com/technicalusers/f/19/t/11853.aspx (OE to IBM WebSphereMQ) The real trick is setting up either an intermediary, or servlet on some webserver that acts as the REST Endpoint. You can write this yourself, or use something like Apache Camel. IBM has some intergration technologies in WebSphere as well to create REST or SOAP services (I have not found any direct REST/SOAP in WebSphereMQ directly.... but I am not a WebSphere expert, by any means. I have mostly dealt with alternative Message Buses). I also believe you can use the OpenEdge SonicMQ adapter which has a bridge to WebSphere via Aurea SonicESB.... but that is a direct JMS-JMS bridge and more than you may need.) For outbound REST to the endpoint, you would have to use OpenEdge sockets (There are some open source libraries on OpenEdge that add a REST layer.) Better would be to not use REST, but SOAP instead and then use the OpenEdge SOAP web service capability to call the SOAP endpoint. But the real decision is the first one.... what technology you have to implement the SOAP/REST endpoint that will be the gateway to WebSphere MQ.
Continue reading...
Continue reading...