Skip to Content

Changes for page Endpoint Check

Last modified by Danniar Firdausy on 2024/09/04 10:26
From version 44.1
edited by Erik Bakker
on 2022/12/30 12:24
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2022/12/30 12:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,32 +51,8 @@
51 51  
52 52  [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]]
53 53  
54 -First, we navigate to the all entry we have created and open the Jetty component. The first segment of the Jetty Server talks about the server connector. In this part, the port is defined (either via a property or statically).
54 +=== 3.5 Verifying the WSDL location ===
55 55  
56 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--server-connector-settings.png]]
57 -
58 -If it is defined via a property you can search for the corresponding value under Deploy -> Properties by checking on the property name and filtering on runtime level to get to the port. If it is defined statically you can simply read it here. Note that the best practice is to use a property value as that allows you to use a different range for your port numbering between environments. In other words, it allows you to use the 9000 range for Test, the 8000 range for Acceptance, and the 9000 range for Production. This is also to safeguard against someone accidentally sending data to the wrong environment.
59 -
60 -=== 3.3 Context Path ===
61 -
62 -The first part of the static remainder of the endpoint is the context. By default, this is filled with /ws but you as a user can alter this. You can check the current value by opening the Jetty component again and looking at the context path that is filled in.
63 -
64 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--context-path.png]]
65 -
66 -=== 3.4 Path Specific Servlet Mapping ===
67 -
68 -The last part of our endpoint is determined by the path-specific servlet mapping. You can once again find the value (and change it if you want to) within the Jetty component. In this component, you can see the servlet mappings and see the path that belongs to that servlet. For SOAP Webservice the best practice is to have only one servlet-mapping and in 99% of the cases, the auto-generated value of eMagiz is more than fine.
69 -
70 -[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--path-specific-servlet-mapping.png]]
71 -
72 -Combining all of this, assuming we run in the eMagiz Cloud, will result in the following endpoint for our Test environment:
73 -* https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/
74 -
75 -Combining all of this, assuming we run locally on our laptop, will result in the following endpoint for our Test environment:
76 -* http://localhost:9091/ws/spwbsrv-connector/
77 -
78 -=== 3.5 Getting the WSDL name ===
79 -
80 80  To get to the WSDL to verify if it is available to be shared with external parties the last thing you need is the WSDL name. You can find this one, surprisingly enough, in the Jetty component. To get to the WSDL name double click on the servlet that is defined under the heading Servlets and navigate to the Advanced tab. Here you will see the name of the WSDL. If you have adhered to the default of eMagiz the name will mimic the name of your path-specific servlet mapping.
81 81  
82 82  [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--wsdl-name.png]]