| Author |
Message
|
| xzhou |
 Posted: Wed Dec 05, 2012 12:17 pm Post subject: SOAP Input node |
 |
|
Apprentice
Joined: 11 Apr 2008
Posts: 32
|
Hi
I uses WMB V8.0.0.1. soap input/output nodes are used in one flow. it works when I uses the SOAPUI as a testing tool.
I run a broker on my PC, and can retrieve a wsdl using IE or Firefox via url http://...../..service?wsdl on my PC as well.
But another PC on the same network can't access to wsdl although I turned off windows firewall on my PC. The error is "Get method is not supported".
It looks strange to me, and I am confused as well.
Did anyone run into same problem?
Thanks, XZ |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Dec 05, 2012 12:20 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
The listener port may be different. Check Windows Eventlog on the remote PC to see what the port number is.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| xzhou |
| Posted: Wed Dec 05, 2012 12:34 pm Post subject: |
|
|
Apprentice
Joined: 11 Apr 2008
Posts: 32
|
I don't think the port is a problem because the port # is in the url. Same url works on local, but not on remote.
Thanks, XZ |
|
| Back to top |
|
|
| Esa |
| Posted: Wed Dec 05, 2012 1:48 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
No, it's just that the Message Broker HTTP listener does not support HTTP Get method. Why not? Maybe because MEssage Broker is supposed to be an integration platform, not a portal or other user interface server.
You should use the Post method. If you just write the URL in the browsers address field, it will be called with Get. Tools like curl or SOAPUi can call with Post method.
The strange thing is that you could fetch the wsdl with a browser. Apparently the listener accepts Get from the local address?
Read about the HTTPListener in the InfoCenter. I cannot post you a link or check any closer details because the InfoCenter responds very slowly just now. Maybe IBM boots its web servers at this time of the day. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Dec 05, 2012 2:11 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| xzhou wrote: |
I don't think the port is a problem because the port # is in the url. Same url works on local, but not on remote.
Thanks, XZ |
Ports are dynamic by default in Broker. They are not guaranteed to be the same.
CHECK THE PORT NUMBER BEING LISTENED TO ON THE REMOTE SYSTEM. IT MAY BE DIFFERENT.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Dec 06, 2012 12:39 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| lancelotlinc wrote: |
CHECK THE PORT NUMBER BEING LISTENED TO ON THE REMOTE SYSTEM. IT MAY BE DIFFERENT. |
You mean that the port could be different for local and remote clients? I don't think you read the problem description carefully enough. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Dec 06, 2012 1:21 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Esa wrote: |
No, it's just that the Message Broker HTTP listener does not support HTTP Get method. Why not? Maybe because MEssage Broker is supposed to be an integration platform, not a portal or other user interface server.
|
Do you mean we cannot have flows implemented which can get HTTP GET requests or do you say we should not be doing that?
Because we have implemented flows which support HTTP GET requests. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Dec 06, 2012 1:21 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
CHECK THE PORT NUMBER BEING LISTENED TO ON THE REMOTE SYSTEM. IT MAY BE DIFFERENT. |
Eh?
I beg to differ unless you are having some sort of port forwarding between the remote system and the broker server.
For the benfit of the rest of us 'numbskulls' can you explain why/how you come up with that reason. I'd really like to know as it makes all the setting of SOAP Listener ports on an EG a complete waste of time.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Dec 06, 2012 1:41 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| kash3338 wrote: |
Do you mean we cannot have flows implemented which can get HTTP GET requests or do you say we should not be doing that?
|
Neither. I'm just saying that as far as I remember correctly Message Broker does not support GET method out of the box. I think that applies to the OP's caser where he has just taken the Broker out of the box without doing any specific configuration for enabling GET.
As a matter of fact, the (V7) InfoCenter says that you should use GET for obtaining the wsdl.
Maybe it does not work from the remote client because of some typo? A slash instead of the question mark?
@kash3338: I'm curious to know how you enabled HTTP GET for HTTPInput or SOAPInput nodes. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Dec 06, 2012 2:47 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| Esa wrote: |
Neither. I'm just saying that as far as I remember correctly Message Broker does not support GET method out of the box.
@kash3338: I'm curious to know how you enabled HTTP GET for HTTPInput or SOAPInput nodes. |
You drag the HTTPInput in, then you configure "Path suffix for URL*" (e.g. "/path/to/Service" and then you access (in a Browser (with HTTP-GET)): http://server:7800/path/to/Service")... [HTTP-GET] works wonderfully... nothing to configure additionally.
I have the same problem, actually:
| Quote: |
| http://server:7800/pathToService?wsdl |
results in:
| Quote: |
| Unsupported Method: GET. |
This must have to do with that SOAP-WebServices use POST (and not GET) for sending requests.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Dec 06, 2012 3:29 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqsiuser wrote: |
This must have to do with that SOAP-WebServices use POST (and not GET) for sending requests. |
Yes, that's what was confusing me. Thanks, mqsiuser. So it's just SOAPInput that does not support GET for anything else that capturing the wsdl. And seems to have some problems even with that... |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Dec 06, 2012 4:45 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| Esa wrote: |
| So it's just SOAPInput that does not support GET for anything else that capturing the wsdl. And seems to have some problems even with that... |
Actually SOAP 1.1 does not support HTTP GET. It was introduced in SOAP 1.2 to support HTTP GET.
By default the SOAPInput Node property "SOAP 1.1 actor" will have "Ultimate Destination (Ultimate Receiver)", I guess we need to configure some other value to make this support HTTP GET. (Not sure though).
| Esa wrote: |
| @kash3338: I'm curious to know how you enabled HTTP GET for HTTPInput or SOAPInput nodes. |
We used HTTPInput which does not need any separate configuration to support HTTP GET. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 06, 2012 4:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Esa |
| Posted: Thu Dec 06, 2012 5:09 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| mqjeff wrote: |
| http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ac56230_.htm |
If I interpret this correctly you are tryig to communicate us that you can use a flow with a SOAPInput node in gateway mode to convert HTTP GET into HTTP POST? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 06, 2012 5:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Esa wrote: |
| mqjeff wrote: |
| http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ac56230_.htm |
If I interpret this correctly you are tryig to communicate us that you can use a flow with a SOAPInput node in gateway mode to convert HTTP GET into HTTP POST? |
No. It's not really the link I meant to post.
I meant to post the link to the page that links to that page, which is to say the page on the SOAPInput node that describes the property of the node to allow the use of GET to support ?wsdl.
None of the discussion of GET vs POST has anything to do with the OP's problem, in that if it works from one machine it should work from another, provided the URL is the same.
If it doesn't work from some other machine with the same URL, then it's got naught to do with how the broker is configured. |
|
| Back to top |
|
|
|
|
