I am using WebMethods 7.1.2.
I generated a consumer WSD in my development environment against a webservice being parallel developed on another integration server. I configured the client IS to use webservice endpoint alias.
I then proceeded to migrated the WSD and all reference components to our test environment. Once the target webservice was in test, I configured an endpoint alias on the client test IS to point to the webservice test region.
When the client invoks the webservice in test, I get a “host not found” error. This is because the pub.client.soapClient service appears to be validating the WSDL against the original development WSD endpoint I created it with. I should point out that our IS’s are all behind CSS switches so we can use IP aliasing to access our webMethods environments. By design, our test environment cannot get to development endpoint of the webservice.
I can lock the webservice adapter flow service and change the hard coded “address” parameter, but that defeats the whole point of having an webservice alias doesn’t it? I shouldn’t have to change the code.
If I was to migrate my client code to production, that would mean that the webservice client would be validating against the development WSDL before invoking the production webservice. Not good!
Does this seem like a bug? Has anyone run into this before?