Changes for page Endpoint Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-SOAP Headers
	1	+novice-soap-webservice-connectivity-soap-headers

Content

...	...	@@ -1,62 +1,113 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
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.
	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. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
3	3
4	4	Should you have any questions, please contact academy@emagiz.com.
5	5
6	6	* Last update: June 10th, 2021
7		-* Required reading time: 5 minutes
	7	+* Required reading time: 7 minutes
8	8
9	9	== 1. Prerequisites ==
10	10	* Basic knowledge of the eMagiz platform
11	11
12	12	== 2. Key concepts ==
13		-This microlearning centers around SOAP Headers.
	13	+This microlearning centers around configuring your SOAP web service.
14	14
15		-By SOAP Headers, we mean: headers within a SOAP Envelope that can be used to communicate metadata or authentication information between parties
	15	+By configuring, we mean: Designing and determining the characteristics of the SOAP web service
16	16
17		-You can exchange data from:
18		-* SOAP Header to Message Header
19		-* Message Header to SOAP Header
	17	+Crucial parts in the configuration are:
	18	+* Operation Name
	19	+* SOAP Webservice Namespace
	20	+* Validation
	21	+* Authentication
20	20
21		-In both cases ensure that the correct information is exchanged.
	23	+Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning.
22	22
23		-== 3. SOAP Headers ==
	25	+== 3. Validate Incoming Messages ==
24	24
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.
	27	+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. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
26	26
27		-You can exchange data from:
28		-* SOAP Header to Message Header
29		-* Message Header to SOAP Header
	29	+Crucial parts in the configuration are:
	30	+* Operation Name
	31	+* SOAP Webservice Namespace
	32	+* Validation
	33	+* Authentication
30	30
31		-In both cases ensure that the correct information is exchanged.
	35	+Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning. The SOAP Webservice serves as a point of entry where people with the rights credentials (security) and the right answers (validation) are allowed to enter and perform their actions. In the next microlearning, we will talk about the security part. In this microlearning, we talk about the validation part.
32	32
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	+As you have learned from the crash course you can validate an XML message with the help of an XSD. This XSD describes dataTypes, order, associations, and length of attributes. You can use such an XSD for the validation of what your clients send you. eMagiz will automatically define a WSDL based on the XSD that you provide that stores metainformation and stores the XSD for validation purposes. This way you can communicate the WSDL (location) to external parties as a reference document upon which they can build their solution. If you keep the eMagiz defaults you can access the WSDL via http://host:port/ws/ws-name/ws-name.wsdl. Note that you need to all values (except for the ws and .wsdl part) with actual values.
34	34
35		-In that microlearning, we also discussed the component that we need for this. The 'complex SOAP header mapper'.
	39	+What eMagiz does need from you is the correct XSD for validation. As a starting point you should download the XSD that eMagiz has generated based on the system message(s) you have defined in the Design phase. Once you have that you can structure the XSD correctly. A valid XSD start with a schema segment. In this segment you need to define your SOAP WS namespace:
36	36
37		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--complex-soap-header-mapper.png]]
	41	+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
	42	+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	43	+ xmlns="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/"
	44	+ attributeFormDefault="unqualified" elementFormDefault="unqualified"
	45	+ targetNamespace="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/">
38	38
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.
	47	+Once you have that you need to copy all complex and simple types from the XSD that you downloaded and paste them below the lines you have created:
40	40
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:
	49	+<xs:complexType name="Input">
	50	+ <xs:sequence>
	51	+ <xs:element name="String" type="nonEmptyString"/>
	52	+ <xs:element minOccurs="0" name="Decimal" type="xs:decimal"/>
	53	+ <xs:element name="Enum" type="Enum"/>
	54	+ <xs:element name="Integer" type="xs:long"/>
	55	+ <xs:element name="Boolean" type="xs:boolean"/>
	56	+ <xs:element minOccurs="0" name="DateTime" type="xs:dateTime"/>
	57	+ </xs:sequence>
	58	+ </xs:complexType>
	59	+ <xs:simpleType name="nonEmptyString">
	60	+ <xs:restriction base="xs:string">
	61	+ <xs:minLength value="1"/>
	62	+ </xs:restriction>
	63	+ </xs:simpleType>
	64	+ <xs:simpleType name="Enum">
	65	+ <xs:restriction base="xs:string">
	66	+ <xs:enumeration value="URGENT"/>
	67	+ <xs:enumeration value="HIGH"/>
	68	+ <xs:enumeration value="MEDIUM"/>
	69	+ <xs:enumeration value="LOW"/>
	70	+ <xs:enumeration value="PLANNING"/>
	71	+ </xs:restriction>
	72	+ </xs:simpleType>
42	42
43		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--mapping-from-message-header.png]]
	74	+To wrap things up you need to define your Request and Response element and close the schema:
44	44
45		-Once you are satisfied you can press Save and link the support object to the web service outbound gateway.
	76	+<xs:element name="SendNptRequest">
	77	+ <xs:complexType>
	78	+ <xs:sequence>
	79	+ <xs:element name="Input" type="Input"/>
	80	+ </xs:sequence>
	81	+ </xs:complexType>
	82	+ </xs:element>
	83	+ <xs:element name="SendNptResponse">
	84	+ <xs:complexType/>
	85	+ </xs:element>
	86	+ </xs:schema>
46	46
47		-With this information, you can place SOAP Headers on message headers and vice versa every time you need it.
	88	+Combining this will result in a valid XSD for my example. In your case, you will need to enter other values. When you are done with the creation of the XSD save it with a name such as spwbsrv-connector.xsd and upload it to the flow. After you have uploaded the XSD link it to the connector-xsd support object in your entry.
48	48
	90	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--uploaded-file.png]]
	91	+
	92	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--file-linked-to-xsd-component.png]]
	93	+
	94	+With this done you have successfully added validation to your SOAP web service.
	95	+
49	49	== 4. Assignment ==
50	50
51		-Call an external web service and send along some SOAP Headers.
	98	+Add validation to the SOAP Webservice we have been configuring.
52	52	This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
53	53
54	54	== 5. Key takeaways ==
55	55
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
	103	+* Crucial parts in the configuration are:
	104	+ ** Operation Name
	105	+ ** SOAP Webservice Namespace
	106	+ ** Validation
	107	+ ** Authentication
	108	+* Validation is done with the help of an XSD
	109	+* The WSDL is used for external documentation
	110	+* Use the XSD generated by eMagiz based on the system message as a starting point
60	60
61	61	== 6. Suggested Additional Readings ==
62	62
...	...	@@ -64,6 +64,6 @@
64	64
65	65	== 7. Silent demonstration video ==
66	66
67		-{{video attachment="novice-soap-webservice-connectivity-soap-headers.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	118	+{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
68	68
69	69	)))((({{toc/}}))){{/container}}{{/container}}