Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:39
From version 45.1
edited by Erik Bakker
on 2022/12/30 12:12
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/12/30 12:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -45,10 +45,6 @@
45 45  
46 46  {{warning}}Note that when you make changes to the system message after the integration is already in Create, or when you add a new integration to Create, you need to create a new version of your infra flow to be able to deploy the changes to your WSDL.{{/warning}}
47 47  
48 -In this same support object, you also see the default location of the hosted SOAP endpoint, which is http://localhost:${entry.connector.ws.port}/ws/{soap WS name}/. Based on this, you can find the WSDL by adding {soap WS name}.wsdl to the URI. In this example, when hosting the SOAP web service on-premise, a valid URI would be "http://localhost:8099/ws/soapgn3-connector/soapgn3-connector.wsdl".
49 -
50 -{{info}}Note that when running your web service in the eMagiz cloud, the first part (the host part) will change depending on your configuration in Deploy Architecture and the cloud slot on which you are running. An example URI, in that case, would be "https://soap-test-cloud0000.emagizcloud.com/ws/soapgn3-connector/soapgn3-connector.wsdl"{{/info}}
51 -
52 52  With this done, you have successfully added validation to your SOAP web service.
53 53  
54 54  == 4. Assignment ==