| Author |
Message
|
| vvanherk |
 Posted: Tue Oct 07, 2003 10:34 am Post subject: MQSI and WebServices / SOAP |
 |
|
Newbie
Joined: 07 Oct 2003
Posts: 4
|
Hey.
Does anyone have any input on using MQSI and WebServices. I would like to be able to use WebServices/SOAP to send and recieve messages to the Broker.
Any input would be greatly appreciated. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 07, 2003 11:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Move to WBIMB, v5. There are HTTP/HTTPS SOAP input and output nodes.
Or use WAS/J2EE to write an interface that turns a soap request into a request/reply WMQI process using standard queues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vvanherk |
| Posted: Tue Oct 07, 2003 12:16 pm Post subject: |
|
|
Newbie
Joined: 07 Oct 2003
Posts: 4
|
Thanks for the info.
Are you aware of any upgrade issues in doing so? We are on Integrator Broker version 2.1
I know these releases are not too far apart, but could be too many implications to go down this path.
Regards, |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 07, 2003 12:53 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| vvanherk wrote: |
Thanks for the info.
Are you aware of any upgrade issues in doing so? We are on Integrator Broker version 2.1
I know these releases are not too far apart, but could be too many implications to go down this path. |
Yes. You can't exactly "upgrade". You have to convert all your message flows and message sets to the new version.
It's not a simple process. But you're going to have to do it at some point, and it may be cheaper than building your own SOAP/Web Services infrastructure until you do have to move. You'll have to evaluate those costs yourself, though.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kolban |
| Posted: Tue Oct 07, 2003 1:45 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
|
| Back to top |
|
|
| vvanherk |
| Posted: Wed Oct 08, 2003 9:43 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2003
Posts: 4
|
Hey.
Thank you both for your replies.
The current situation situation is this:
Client has an existing application where requests come in via Servlet to EJB to MQ.
They are not happy with the EJB as the guy who wrote it is gone. It also does not really need to be an EJB, but the guy that left had a hammer, and everything looked like a nail. They also want to utilize MQSI where possible, as they now have it and want MQ requests to go through it. The servlet that get's initial request is outside of scope, so needs to remain as part of the architecture.
So, I was thinking WebServices would be perfect for what they are doing. In the event that we cannot upgrade soon to the latest and greatest, what would be the best way to abstract that out and use WebServices anyway. Is it best to go Servlet - WebServices - J2EE - MQSI? If so, any particalur approaches for using WebServices - J2EE together that are better then any others.
Getting WebServices in now would also enable us to pull J2EE layer when we do upgrade....just route webservies directly to Broker SOAP nodes.
Any thoughts would be appreciated.
Regards, |
|
| Back to top |
|
|
|
|
