'Unknown Host' error when setting up outbound SOAP service
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-11-2016 12:33 PM
Hi Everyone, first time trying to set up an outbound web service in the system. Ultimately, what I want to do is to sent some information from a business rule to a web server where I have an .asmx service hosted. First step I took was to create a new Outbound SOAP Message. Attempting to download the WSDL resulted in an exception. This was the information used (This is a test service that was created just for this test);
- WSDL - https://kpmtest.kmtl.com:4443/webservices/projectservicejson.asmx?WSDL
- Result - Unable to load WSDL: java.lang.RuntimeException: java.net.UnknownHostException: kpmtest.kmtl.com:java.net.UnknownHostException: kpmtest.kmtl.com
To alleviate this issue, I copy and pasted the WSDL XML manually. This allowed me to generate the SOAP Message Functions. At this point, if I try and refresh one of these functions - I receive the same issue. Running a test on this function results in a response that contains 'Unknown Host'. I should mention that this particular service has been setup to accept requests from outside the domain and has been confirmed to be working and accessible from another one of our cloud partners.
If I recall correctly, I think I remember seeing that to use an outbound service, that service cannot be behind a firewall? Am I correct in that assumption? Thanks.
- Labels:
-
Integrations
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-11-2016 01:12 PM
Hi Zac,
You are correct. If your service is behind a firewall, you need to look at using MID server to gain access. I just tried from my browser and cannot access that system so it verifies your findings from your instance.
Reference:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-26-2018 12:39 AM
HI Zac,
In my case, I updated the SOAP endpoint, its worked.