Author |
Message
|
MQWizard |
Posted: Wed Oct 18, 2006 6:00 am Post subject: WSDL JMS request/reply operation |
|
|
Novice
Joined: 14 Sep 2006 Posts: 13
|
Hi Everyone,
thanks in advance for the reply.
I am using MB V5 fix pack 5. I dont have jmsinput node and jmsoutput node on my broker.
My first need is -I have to define a wsdl for jms sync (reqest/reply operation).
I defined it using the categories and have generated the wsdl definition. i am not sure how it will work. It looks like for both input and output it will use the same queue. So I am confused.
Pls help me understand how it will work and what do I need to do in a flow for this request/reply JMS service to work?
My second need is-I want to use a single envelope structure for both request and reply in the above scenario. My envelope wraps my request and response structure.
Issue-Looks like once selected a particular message definition file for a wsdl Kind, the toolkit does not allow to select the same message definition file for another wsdl kind within the same message category file.
How can I acheive this.
I appreciate your time and help.
thanks. _________________ Wizard Leads the way |
|
Back to top |
|
 |
MQWizard |
Posted: Wed Oct 18, 2006 10:02 am Post subject: |
|
|
Novice
Joined: 14 Sep 2006 Posts: 13
|
I did not get any replies so I will try to add more words, may that will help me.
My first question is-
In JMS WSDL, I have the JMS address in the Service wsdl. this jms address has only one jndi connection factory name and one jndidestination name. To me it is equivalient to one queue manager and one queue name for One JMS Webservice request/reply service.
How does this work with message broker. How does a message flow pick up a message from the input queue and post a reply into the output queue? I can understand if they are different queues but I am not able to understand with a single queue.
Can someone pls explain to me. _________________ Wizard Leads the way |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Oct 18, 2006 10:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Ask the people who produced the WSDL.
It doesn't seem to be a good idea, that they are expecting to put the response back to the same queue that they receive the request from.
I suspect that they mean that the Response will go back to the JMSReplyTo on the Request. That would be the equivalent of the ReplyToQueue of the message - and you could handle in WMB by using either another MQInput node or the MQGet node. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Oct 18, 2006 1:55 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Is the MQReply node not available in his version? _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Oct 18, 2006 2:21 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
fjb_saper wrote: |
Is the MQReply node not available in his version? |
That would send a reply, not receive one. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Oct 18, 2006 2:24 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
MQ Wizard wrote: |
How does a message flow pick up a message from the input queue and post a reply into the output queue |
I believe this was his question...
So the answer would be:
Use the MQInput node to pickup the message from the input queue and the MQReply node to send the reply.... _________________ MQ & Broker admin |
|
Back to top |
|
 |
mgk |
Posted: Thu Oct 19, 2006 12:20 am Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1642
|
Could you post the WSDL? _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
MQWizard |
Posted: Thu Oct 19, 2006 5:21 am Post subject: |
|
|
Novice
Joined: 14 Sep 2006 Posts: 13
|
thanks guys for the replies. I appreciate
I understood my first issue and the problem I was facing. Let me elaborate.
I was familar with using Http webservice with broker and with other app environments.
In http webservice, wsdl definition, location attribute in the soap:address element helps to define the transport/ transport url
for both input and for output (in other words for both request and reply from the service).
In Jms service, jms:address element allows to define only one Jndidestination, which is one queue.
If I map what I have with http webservice wsdl, the definition for both request and reply queue should exist within
the same wsdl file.
But with what I have read and have understood, for JMS, wsdl defines only the transport (queue
names for request) and does not define transport for the response.
response protocol is pretty much open and it is expected that at runtime it be handled by the server and client implementation.
My understanding is replytoq and CorrelationID parameter need to be defined in request message JMS header by the
webservice jms client and jms server uses this to route/ respond back with a reply.
pls correct me if you feel, I have misunderstood or not have understood the concept completely.
Also, if you can pls refer me to any documentation, which lists down the JMS field names, their locations and the values expected for JMS Request/reply operation.
Finally my second issue still remains.Toolkit does not allow to select the same msg definition file for wsdl:input and wsdl:output in the category file. My message definition file is a wrapper and wraps both request and reply.
thanks in advance for your advice. _________________ Wizard Leads the way |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Oct 19, 2006 12:34 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
|
Back to top |
|
 |
MQWizard |
Posted: Fri Oct 20, 2006 6:29 am Post subject: |
|
|
Novice
Joined: 14 Sep 2006 Posts: 13
|
thankyou.
I got the answer for my first issue. thanks.
Any inputs on second issue?? _________________ Wizard Leads the way |
|
Back to top |
|
 |
|