Author |
Message
|
ashritha |
Posted: Wed Dec 01, 2010 3:09 pm Post subject: Could not open WSDL in IE for message flow |
|
|
Voyager
Joined: 25 Jul 2005 Posts: 85
|
Hi,
I have developed a message flow that is exposed as a webservice. I could test the service by importing the wsdl in a soapUI. I could import the WSDL into the soapUI(free tool for testing webservices) and could send requests, receive responses from the broker service.
The client that would use this service is a Datastage job. Before i give the WSDL to the datastage team, I was trying to open the wsdl in a web browser. here is the url that i gave in the address bar
http://ussp-mbsd01.sjm.com:7800/MaterialMaster
"ussp-mbsd01.sjm.com:7800" is the system/port where the service is deployed. I have used the same url from the SOAPUI to send the requests and could do it successfully. However, when i am trying to open the wsdl from an internet explorer by giving the url in the address bar, it gives me a "HTTP 405 Method Not Allowed" exception. Typically, for any webservice that is exposed, we should be able to see the wsdl on the internet explorer if we give the soap address location. I was trying to do the same here and failed. Is there something that i am missing here?
Do we have this option of seeing the wsdl on the internet explorer when the webservice(message flow) is deployed on the broker?
Any insight on this is greatly appreciated.
Thanks. |
|
Back to top |
|
 |
harish_td |
Posted: Wed Dec 01, 2010 6:12 pm Post subject: |
|
|
Master
Joined: 13 Feb 2006 Posts: 236
|
If you are running Message Broker version 7.0.0.1 AND
You have checked the *Enable support for ? wsdl* check-box on a SOAPInput node you would be able to open the WSDL via the HTTP GET method(which is what the browser is trying to do)
"HTTP 405 Method Not Allowed" is telling you that GET on this web-service is not supported
soapUI by default uses the HTTP Post Method, which is supported by the deployed message flow. |
|
Back to top |
|
 |
ashritha |
Posted: Thu Dec 02, 2010 8:50 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005 Posts: 85
|
Hi,
Thanks much for the reply. I do have message broker version 7.0.0.1 installed. However, my toolkit version is still 7.0.0. So, I am not able to view the check-box for SOAPInput node you have mentioned in your reply.
I assume, I have to install 7.0.0.1 version of the toolkit as well to be able to view these options. I will try to update it.
If my understanding is incorrect, please let me know. |
|
Back to top |
|
 |
ashritha |
Posted: Thu Dec 02, 2010 1:37 pm Post subject: |
|
|
Voyager
Joined: 25 Jul 2005 Posts: 85
|
Thanks for the solution. It worked. Fixpack 1 gives the ability to chose the option to see the wsdl in the browser.
Thanks so much. |
|
Back to top |
|
 |
Gama |
Posted: Wed Jan 19, 2011 7:18 am Post subject: |
|
|
 Centurion
Joined: 11 Jan 2005 Posts: 103 Location: Portugal
|
Hi,
I have the same problem, but in my case i don't have the possibility to enable the option "Enable support for ?wsdl", because we are using the WMB6.1.
Exist any way to make the WSDL available to the apllication or browser?
Ex.
(http://myURL?wsdl)
Many thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 19, 2011 7:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Gama wrote: |
Hi,
I have the same problem, but in my case i don't have the possibility to enable the option "Enable support for ?wsdl", because we are using the WMB6.1.
Exist any way to make the WSDL available to the apllication or browser? |
Yes- manually. But not through any function of Message Broker 6.1. The only support for this that is available in message broker is at 7.0.0.1. |
|
Back to top |
|
 |
Gama |
Posted: Wed Jan 19, 2011 8:16 am Post subject: |
|
|
 Centurion
Joined: 11 Jan 2005 Posts: 103 Location: Portugal
|
Quote: |
Yes- manually. But not through any function of Message Broker 6.1. The only support for this that is available in message broker is at 7.0.0.1. |
Could you please detail a little more? |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 19, 2011 8:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Gama wrote: |
Quote: |
Yes- manually. But not through any function of Message Broker 6.1. The only support for this that is available in message broker is at 7.0.0.1. |
Could you please detail a little more? |
Broker 6.1 will do absolutely nothing to make any of the WSDLs that are deployed to it accessible via HTTP.
If you want them available via HTTP, you must manually put them somewhere that they will be available via HTTP.
Broker 6.1 does not provide any mechanism to make any random files available via HTTP. |
|
Back to top |
|
 |
Gama |
Posted: Wed Jan 19, 2011 9:07 am Post subject: |
|
|
 Centurion
Joined: 11 Jan 2005 Posts: 103 Location: Portugal
|
Thanks for the clarification.
Action to do is upgrade to WMB7.
 |
|
Back to top |
|
 |
ajit1981 |
Posted: Wed Feb 02, 2011 10:03 pm Post subject: |
|
|
Apprentice
Joined: 09 Apr 2010 Posts: 41 Location: Bangalore, Inida
|
Hi mqjeff,
I have upgrade my toolkit to WMB7.0.0.1. And I deployed the flow with *Enable support for ? wsdl* option. But from IE browser its publish only deployable wsdl which I have created from original wsdl, which dosn't include the XSD, for publish the XSD we need to open the another browser , and need to give the XSD url(url?xsd=xsd0) which published in *url?wsdl*.
I want to publish the original WSDL from which I have created the deployable wsdl in Messageset. Is there is anyway to Publish the Original wsdl ?
Thanks in advance. _________________ Regards,
Ajit |
|
Back to top |
|
 |
Gama |
Posted: Thu Feb 03, 2011 1:22 am Post subject: |
|
|
 Centurion
Joined: 11 Jan 2005 Posts: 103 Location: Portugal
|
|
Back to top |
|
 |
ajit1981 |
Posted: Thu Feb 03, 2011 1:48 am Post subject: |
|
|
Apprentice
Joined: 09 Apr 2010 Posts: 41 Location: Bangalore, Inida
|
Hi Gama,
Thanks for the response and link.
Yes I have upgrade the broker and toolkit to 7.0.0.2. I am able to publish the wsdl too by using the *url?wsdl*.
But Its publishing in IE only deployable wsdl contain which we create from original wsdl. I want to publish the actual wsdl contain.
Just wondering weather there is any option which print the original wsdl contain also ? _________________ Regards,
Ajit |
|
Back to top |
|
 |
balu2608 |
Posted: Tue Mar 26, 2013 6:44 am Post subject: |
|
|
 Apprentice
Joined: 18 May 2012 Posts: 39
|
If you are running Message Broker version 7.0.0.1 AND
You have checked the *Enable support for ? wsdl* check-box on a SOAPInput node you would be able to open the WSDL via the HTTP GET method(which is what the browser is trying to do)
"HTTP 405 Method Not Allowed" is telling you that GET on this web-service is not supported
soapUI by default uses the HTTP Post Method, which is supported by the deployed message flow.
Quote: |
Hi ,
Even i have the same problem but in this case i have upgraded to fixpack 5 but it doesnt make any changes ,is it particular to fixpack 1 only can you please suggest me ....... |
|
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Mar 26, 2013 6:50 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
balu2608 wrote: |
If you are running Message Broker version 7.0.0.1 AND
You have checked the *Enable support for ? wsdl* check-box on a SOAPInput node you would be able to open the WSDL via the HTTP GET method(which is what the browser is trying to do)
"HTTP 405 Method Not Allowed" is telling you that GET on this web-service is not supported
soapUI by default uses the HTTP Post Method, which is supported by the deployed message flow.
Quote: |
Hi ,
Even i have the same problem but in this case i have upgraded to fixpack 5 but it doesnt make any changes ,is it particular to fixpack 1 only can you please suggest me ....... |
|
?wsdl feature not available until 7.0.0.2. What is your EFFECTIVE LEVEL on your runtime? _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
balu2608 |
Posted: Tue Mar 26, 2013 10:03 pm Post subject: |
|
|
 Apprentice
Joined: 18 May 2012 Posts: 39
|
Thanks for your reply lancelotlinc,
Actually we are using 7.0.0 ,but in our case the client is trying the wsdl url by removing the ?wsdl is their any property that we have to enable or disable ,so that it works from the internet explorer by removing ?wsdl from the url path |
|
Back to top |
|
 |
|