Skip to Content

Changes for page Endpoint Check

Last modified by Erik Bakker on 2024/02/21 21:35
From version 45.1
edited by Erik Bakker
on 2023/01/23 08:31
Change comment: There is no comment for this version
To version 40.1
edited by Erik Bakker
on 2022/06/12 09:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -3,6 +3,9 @@
3 3  
4 4  Should you have any questions, please contact academy@emagiz.com.
5 5  
6 +* Last update: June 11th, 2021
7 +* Required reading time: 7 minutes
8 +
6 6  == 1. Prerequisites ==
7 7  * Basic knowledge of the eMagiz platform
8 8  
... ... @@ -18,10 +18,10 @@
18 18  * These three things combined make up the first part of our endpoint that will vary per environment
19 19  * Following that we have a static remainder of the endpoint that is build up as follows: /ws/{path-specific-servlet-mapping}/
20 20  * If you want to get to the WSDL simply add the name of the WSDL and the .wsdl extension to the endpoint when viewing it in the browser
21 -
24 +
22 22  == 3. Endpoint Check ==
23 23  
24 -When setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. One last check to perform before you can communicate with the external parties that the endpoint is available to receive messages and up and running. In this microlearning, we will learn how you can perform such a check.
27 +hen setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. One last check to perform before you can communicate with the external parties that the endpoint is available to receive messages and up and running. In this microlearning, we will learn how you can perform such a check.
25 25  
26 26  The endpoint consists of the following elements:
27 27  * Starts with https:// or http://
... ... @@ -62,10 +62,10 @@
62 62  [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--path-specific-servlet-mapping.png]]
63 63  
64 64  Combining all of this, assuming we run in the eMagiz Cloud, will result in the following endpoint for our Test environment:
65 -* {{code}}https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/{{/code}}
68 +* https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/
66 66  
67 67  Combining all of this, assuming we run locally on our laptop, will result in the following endpoint for our Test environment:
68 -* {{code}}http://localhost:9091/ws/spwbsrv-connector/{{/code}}
71 +* http://localhost:9091/ws/spwbsrv-connector/
69 69  
70 70  === 3.5 Getting the WSDL name ===
71 71  
... ... @@ -74,10 +74,10 @@
74 74  [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--wsdl-name.png]]
75 75  
76 76  With this information we could reach the WSDL via the following endpoint, assuming we run in the eMagiz Cloud:
77 -* {{code}}https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/spwbsrv-connector.wsdl{{/code}}
80 +* https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/spwbsrv-connector.wsdl
78 78  
79 79  With this information we could reach the WSDL via the following endpoint, assuming we run locally on our laptop:
80 -* {{code}}http://localhost:9091/ws/spwbsrv-connector/spwbsrv-connector.wsdl{{/code}}
83 +* http://localhost:9091/ws/spwbsrv-connector/spwbsrv-connector.wsdl
81 81  
82 82  With this information, you should be able to access the WSDL and communicate both the endpoint as well as the WSDL to your external parties.
83 83