| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Do I change the WSDL <soap:address> location before im |
« View previous topic :: View next topic » |
| Author |
Message
|
| rmbowma |
 Posted: Wed Feb 10, 2010 5:38 am Post subject: Do I change the WSDL <soap:address> location before im |
 |
|
Apprentice
Joined: 24 Mar 2005
Posts: 28
|
I have a .wsdl file that was generated by somebody else that I want to use to create a Message Definition. Here is the WSDL port:
<wsdl:port name="AA_Soap_Binding" binding="tns:AA_Soap_BindingBinding">
<soap:address location="http://XXXXXXXX:80/aWebService"/>
</wsdl:port>
o As you can see in the <soap:address location> Element, the host name is XXXXXXXX and port is 80. Before I import this WSDL into my Toolkit to create my Message Definition, don't I have to change the host name value to the host name where my Broker is running, that is, Broker is not going to be running on host XXXXXXXX but another host whose name I don't know yet? Also, don't I have to change the port number from 80 to the port number that will be used by the Execution Group's httplistener where my flow will be running?
I think I have to change both of these values but I don't know for sure. A web service requestor will know the correct host name and port number to use when invoking my web service message flow but don't the host name and port in the <soap:address location> have to match what the web service requestor specifies in his http request? Note that an IP sprayer will NOT be sitting in front of Broker. Web service requestor clients will be sending their http requests directly to the Execution Group where my flow is running, that is, the clients will know the correct host name and port to specify in their http request.
o If I am correct above about having to change the host name and port number in the WSDL prior to importing the WSDL, this will be a message flow/WSDL management nightmare. If I want my message flow to execute in separate development, QA, and production environments, that means for each environment I will have to manually change the host name and port in the WSDL and re-import the WSDL to re-create my Message Definition for each environment.
o Or I wonder........Maybe the host name and port in <soap:address location> doesn't matter? If a http web service request arrives at an Execution Group's httplistener, then if the path suffix for the URL in the http request matches the 'Path suffix for URL' Property in HTTP Transport Tab of the SOAP Input Node, will my message flow running in that Execution Group will be invoked? |
|
| Back to top |
|
 |
| mgk |
| Posted: Thu Feb 11, 2010 4:41 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| Maybe the host name and port in <soap:address location> doesn't matter? |
Correct, at import time, they are not used. They are also not used by the SOAP Input node as the only piece of the URL from the address in the WSDL that is used is in the SOAP Input node is the "path" in the URL, and even that can be changed on the node itself. For the SOAP Request node the full URL (hostname, port and path) is used to populate the "request url" property on the node. However, you can change this directly on the Request node (or override dynamically at runtime in the LocalEnvironment instead or as well). Look at the Samples for webservices that come with the product as they should show you how this works...
Regards,
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
