Changes for page Endpoint Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Endpoint Check
	1	+SOAP Headers

Parent

...	...	@@ -1,1 +1,1 @@
1		-Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome
	1	+WebHome

Author

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

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

...	...	@@ -1,69 +1,69 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-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.
	2	+When communicating via SOAP web service calls it can happen that an exchange of data needs to happen between the message headers on your message and the SOAP headers. In this microlearning, we will learn about this exchange in both directions. SOAP Headers are headers within a SOAP Envelope that can be used to communicate metadata or authentication information between parties.
3	3
4	4	Should you have any questions, please contact academy@emagiz.com.
5	5
	6	+* Last update: June 10th, 2021
	7	+* Required reading time: 5 minutes
	8	+
6	6	== 1. Prerequisites ==
7	7	* Basic knowledge of the eMagiz platform
8	8
9	9	== 2. Key concepts ==
10		-This microlearning centers around the endpoint check.
	13	+This microlearning centers around SOAP Headers.
11	11
12		-By endpoint check, we mean: determine whether the WSDL is accessible on the correct endpoint so we can forward the URL to the WSDL + the URL to call to our external parties
	15	+By SOAP Headers, we mean: headers within a SOAP Envelope that can be used to communicate metadata or authentication information between parties
13	13
14		-* The endpoint consists of the following elements:
15		- ** Starts with https:// or http://
16		- ** Second part is the host (i.e. where is the endpoint running)
17		- ** Third part is the port on which the incoming traffic is accepted
18		- ** These three things combined make up the first part of our endpoint that will vary per environment
19		- ** Following that we have a static remainder of the endpoint that is build up as follows: /{soap WS name}/{Id}/
20		- ** 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
	17	+You can exchange data from:
	18	+* SOAP Header to Message Header
	19	+* Message Header to SOAP Header
21	21
22		-== 3. Endpoint Check ==
	21	+In both cases ensure that the correct information is exchanged.
	22	+
	23	+== 3. SOAP Headers ==
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.
	25	+When communicating via SOAP web service calls it can happen that an exchange of data needs to happen between the message headers on your message and the SOAP headers. In this microlearning, we will learn about this exchange in both directions. SOAP Headers are headers within a SOAP Envelope that can be used to communicate metadata or authentication information between parties.
25	25
26		-* The endpoint consists of the following elements:
27		- ** Starts with https:// or http://
28		- ** Second part is the host (i.e. where is the endpoint running)
29		- ** Third part is the port on which the incoming traffic is accepted
30		- ** These three things combined make up the first part of our endpoint that will vary per environment
31		- ** Following that we have a static remainder of the endpoint that is build up as follows: /{soap WS name}/{Id}/
32		- ** 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
	27	+You can exchange data from:
	28	+* SOAP Header to Message Header
	29	+* Message Header to SOAP Header
33	33
34		-As you can see the endpoint can be divided into two parts. One part is dynamic across environments and one part is static across environments. Let us first determine how we can find out the first part of our endpoint.
	31	+In both cases ensure that the correct information is exchanged.
35	35
36		-=== 3.1 HTTPS or HTTP ===
	33	+In a previous microlearning, we already discussed one aspect of this. As you probably recall from our microlearning on [Securing your SOAP Webservice](novice-soap-web service-connectivity-securing-your-soap-webservice.md) we needed to exchange data between the SOAP header that our client was sending and a message header on the message so we could check whether or not the client was authorized to call the operation.
37	37
38		-We start at the top with the determination of HTTPS or HTTP. A simple rule of thumb is that when running in the eMagiz Cloud the endpoint starts with https:// and when the endpoint is running locally (i.e. on-premise) the endpoint starts with http:// (unless you secure it yourself, more on that later).
	35	+In that microlearning, we also discussed the component that we need for this. The 'complex SOAP header mapper'.
39	39
40		-=== 3.2 Host ===
	37	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--complex-soap-header-mapper.png]]
41	41
42		-The next part of the endpoint is the host. The host is effectively the (virtual) machine on which the endpoint is running. When hosting an endpoint in the eMagiz cloud the host part is the combination between the DNS left-most label on Route level and the cloudslot on which your environment is running. The first part of the equation can be found under Deploy -> Architecture. The second part can be found under Deploy -> Properties by looking for the {technicalnameproject}.amqp01.host. You need to combine the two elements via a dash -. An example of this would then be spwbsrv-test-cloud0001.emagizcloud.com. In case of an on-premise installation, you should ask your customer what the IP address or DNS name is to connect to the machine on which your runtime is running. If the runtime is running locally on your laptop the host equals localhost.
	39	+As you can see you can map from and to message headers with regards to the SOAP Headers. As we already discussed the first scenario in an earlier microlearning I will for now continue with the other scenario. This scenario is mainly needed when eMagiz calls a SOAP web service that is hosted by an external party. Since we would normally do this in an exit (gate/flow) let us open such an exit in eMagiz and enter "Start Editing" mode.
43	43
44		-=== 3.3 Port and Path ===
	41	+The first step we need to take is to ensure that the information that we need to send to the SOAP web service in question (in this a unique reference number) is available in a message header. This can be done by verifying in all steps that preceded before the message entered the exit whether or not this piece of information was already added to a message header. In this case, we assume that this is the case since we want to focus on the 'complex SOAP header mapper' component and its relation to the web services outbound gateway. To correctly exchange data from a message header to a SOAP header we need to define a valid SpEL expression. See the help text of the component for a suggestion of what a valid SpEL expression is. The key part in this is knowing how the external party wants to receive the header(s) and how you (or one of your colleagues) has named the message header. When you have those two information elements you can write the correct expression. The result should be something as follows:
45	45
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.
	43	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--mapping-from-message-header.png]]
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 {{code}}http://localhost:8099/ws/soapgn3-connector/soapgn3-connector.wsdl{{/code}}.
	45	+Once you are satisfied you can press Save and link the support object to the web service outbound gateway.
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 {{code}}https://soap-test-cloud0000.emagizcloud.com/ws/soapgn3-connector/soapgn3-connector.wsdl{{/code}}{{/info}}
	47	+With this information, you can place SOAP Headers on message headers and vice versa every time you need it.
51	51
52		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]]
	49	+== 4. Assignment ==
53	53
54		-== 4. Key takeaways ==
	51	+Call an external web service and send along some SOAP Headers.
	52	+This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
55	55
56		-* The endpoint consists of the following elements:
57		- ** Starts with https:// or http://
58		- ** Second part is the host (i.e. where is the endpoint running)
59		- ** Third part is the port on which the incoming traffic is accepted
60		- ** These three things combined make up the first part of our endpoint that will vary per environment
61		- ** Following that we have a static remainder of the endpoint that is build up as follows: /{soap WS name}/{Id}/
62		- ** 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
63		-* The relevant information can be derived from the "Dynamic WSDL" support object and by determining where the endpoint is hosted
	54	+== 5. Key takeaways ==
64	64
65		-== 5. Suggested Additional Readings ==
	56	+* You can exchange data from:
	57	+ ** SOAP Header to Message Header
	58	+ ** Message Header to SOAP Header
	59	+* You need the SOAP structure and the message header name to make it work
66	66
	61	+== 6. Suggested Additional Readings ==
	62	+
67	67	If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
68	68
	65	+== 7. Silent demonstration video ==
	66	+
	67	+{{video attachment="novice-soap-webservice-connectivity-soap-headers.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	68	+
69	69	)))((({{toc/}}))){{/container}}{{/container}}