Forum Discussion
danielrose01
12 years agoOccasional Contributor
OK, I think I spotted the problem.
I am going to try and attach some files that show a few differences.
In the TEST WSDL Code Part 02 of 03 file note that the SOAP ADDRESS LOCATION item in the WSDL points a different URL and PORT then what is used for the ADDRESS of the WebService. The WebService page is in the file called TEST Webservice Page file.
I included the PROD WebService and PROD WSDL Code Page for reference.
The big clue here is that:
I am able to use SoapUI to connect and communicate with the WDL in our PROD environment. However it fails in TEST.
I believe that this ADDRESS LOCATION item is the issue. The value in the PROD environment seem to point directly to the same URL and Port as found in the ADDRESS reference on the WebService page. The similar components in TEST environment point to different URLs and Ports. The similar components in TEST are the ADDRESS LOCATION ITEM in the WSDL code and the ADDRESS reference in the WebService Page.
I am going to try and attach some files that show a few differences.
In the TEST WSDL Code Part 02 of 03 file note that the SOAP ADDRESS LOCATION item in the WSDL points a different URL and PORT then what is used for the ADDRESS of the WebService. The WebService page is in the file called TEST Webservice Page file.
I included the PROD WebService and PROD WSDL Code Page for reference.
The big clue here is that:
I am able to use SoapUI to connect and communicate with the WDL in our PROD environment. However it fails in TEST.
I believe that this ADDRESS LOCATION item is the issue. The value in the PROD environment seem to point directly to the same URL and Port as found in the ADDRESS reference on the WebService page. The similar components in TEST environment point to different URLs and Ports. The similar components in TEST are the ADDRESS LOCATION ITEM in the WSDL code and the ADDRESS reference in the WebService Page.