Changes for page Endpoint Check

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.etorken

Content

...	...	@@ -45,19 +45,14 @@
45	45
46	46	Whether or not the port needs to be defined to get to the endpoint is once again determined by the location. If the endpoint is hosted in the eMagiz Cloud the port is *not* part of the endpoint. However, when you host your endpoint locally the endpoint becomes part of your endpoint. Note that to make this piece work in the eMagiz Cloud you should set up your Route properly. More on that in our Cloud Management courses. You can determine the port, for the endpoint or the route, by navigating to the infra flow of the runtime through which you host your SOAP web service. In the infra flow you can also find the remainder of the path to get to the WSDL location.
47	47
48		-In the infra flow there is a support object of the type "Dynamic WSDL". In here you 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 {Id}.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".
	48	+In the infra flow there is a support object of the type "Dynamic WSDL". In here you 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 {Id}.wsdl to the URI. In this example, when hosting the SOAP web service on-premise, a valid URI would be {{code}}http://localhost:8099/ws/soapgn3-connector/soapgn3-connector.wsdl{{/code}}.
49	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}}
	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 {{code}}https://soap-test-cloud0000.emagizcloud.com/ws/soapgn3-connector/soapgn3-connector.wsdl{{/code}}{{/info}}
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		-== 4. Assignment ==
	54	+== 4. Key takeaways ==
55	55
56		-Determine the endpoint of your SOAP Webservice and retrieve the WSDL.
57		-This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
58		-
59		-== 5. Key takeaways ==
60		-
61	61	* The endpoint consists of the following elements:
62	62	** Starts with https:// or http://
63	63	** Second part is the host (i.e. where is the endpoint running)
...	...	@@ -67,12 +67,8 @@
67	67	** If you want to get to the WSDL simply add the name of the WSDL (which is defined by the Id given to the "Dynamic WSDL" support object) and the .wsdl extension to the endpoint when viewing it in the browser
68	68	* The relevant information can be derived from the "Dynamic WSDL" support object and by determining where the endpoint is hosted
69	69
70		-== 6. Suggested Additional Readings ==
	65	+== 5. Suggested Additional Readings ==
71	71
72	72	If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
73	73
74		-== 7. Silent demonstration video ==
75		-
76		-{{video attachment="novice-soap-webservice-connectivity-endpoint-check-gen3.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
77		-
78	78	)))((({{toc/}}))){{/container}}{{/container}}