| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ6 - Soap - Existing Web Service - Registering JMS Protocol |
« View previous topic :: View next topic » |
| Author |
Message
|
| catwood2 |
 Posted: Sat Sep 30, 2006 7:11 am Post subject: MQ6 - Soap - Existing Web Service - Registering JMS Protocol |
 |
|
Centurion
Joined: 17 May 2002
Posts: 108
|
I am new to web services/JMS and would appreciate some pointers.
I have installed MQSoap and run successfully the IVT tests on windows 2003. I have been reading the relevant redbooks and I am hitting a mental block in the area of existing web services. We have a help desk application with a set of web services being accessed via the http protocol. We want to hook into them using mq and I understand that the JMS protocol has to be registered with Axis as a valid transport for the Web services. This registration, as I am reading, is occuring during the deployment stage. So, this code is already deployed via the other application and we just want to be able to access via JMS protocol. I can see also that the MQListener process for the service is created by process of deployment. In a scenario where a service is deployed and you won't be deploying via mqsoap - what are the options?
1. Obtain the source code and redeploy? That seems counterintuitive and...well....wasteful - the service is already out there.
2. Determine some other process for registering the JMS protocol and creating a MQListener thru a different means?
3. ?
TIA for any thoughts.
catwood2 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Sep 30, 2006 7:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the service you want to invoke only supports the HTTP protocol... you will have to either invoke it using the HTTP protocol, or modify it to support JMS...
How that is done really depends on the service itself. If the service is built using AXIS, and AXIS lets you change what protocols a web service supports at deploytime... then, yes, I guess you will have to re-deploy your existing services. It may seem "wasteful", but you are really looking to CHANGE what it's doing - so you should expect to have to redeploy I think.
On the other hand, you can write a service Proxy that will receive JMS service invocations, and call out to an existing service over HTTP and then return the reply via JMS.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
