Changes for page Validate Incoming Messages

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-novice-soap-webservice-connectivity-configure-your-soap-webservice
	1	+Validate Incoming Messages

Parent

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

Default language

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

Content

...	...	@@ -1,67 +1,75 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In some cases, the input you receive or the output that you need to send to an external party cannot handle all characters or the input or output is written with the help of a character set. In this microlearning, we will learn how you can define the character set for file-based connectivity to ensure that you can process and deliver files according to the specifications.
	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 to host 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		-Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	4	+If you have any questions, don't hesitate to contact academy@emagiz.com.
5	5
6		-* Last update: May 31th, 2021
7		-* Required reading time: 7 minutes
8		-
9	9	== 1. Prerequisites ==
10		-
11	11	* Basic knowledge of the eMagiz platform
12	12
13	13	== 2. Key concepts ==
	10	+This microlearning centers around configuring your SOAP web service.
14	14
15		-This microlearning centers around learning how to define the character set to ensure that eMagiz processes the information correctly.
	12	+By configuring, we mean: Designing and determining the characteristics of the SOAP web service.
16	16
17		-By character set, we mean: The composite number of different characters that are being used and supported by computer software and hardware. It consists of codes, bit patterns, or natural numbers used in defining some particular character.
	14	+Crucial parts in the configuration are:
	15	+* Operation Name
	16	+* SOAP Webservice Namespace
	17	+* Validation
	18	+* Authentication
18	18
19		-* Some external system talk in a different character set
20		-* eMagiz talks in default UTF-8 as a character set and assumes everyone else also does this
21		-* In cases of mismatch correct is at the point where you talk with the other system (i.e. entry or exit)
	20	+Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning.
22	22
23		-== 3. Character set ==
	22	+== 3. Validate Incoming Messages ==
24	24
25		-In some cases, the input you receive or the output that you need to send to an external party cannot handle all characters or the input or output is written with the help of a character set. In this microlearning, we will learn how you can define the character set for file-based connectivity to ensure that you can process and deliver files according to the specifications.
	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 to host 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		-Sometimes external systems only talk in a specific character set. To ensure that all the data is properly communicated between eMagiz and the other system we need to make sure that we define which character set that is so we can tell it to eMagiz via a component. That way eMagiz will deviate from its default (i.e. UTF-8) and will process the file according to that different character set. In practice, we mainly see windows-1252 as an alternative that pops up once in a while. In various components that deal with file handling, you can define the character set on which eMagiz should act. Examples of such components are:
	26	+Crucial parts in the configuration are:
	27	+* Operation Name
	28	+* SOAP Webservice Namespace
	29	+* Validation
	30	+* Authentication
28	28
29		-- File to string transformer
30		-- Flat file to XML transformer
31		-- File outbound channel adapter
	32	+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 proper credentials (security) and the correct answers (validation) can enter and perform their actions. In the previous microlearning, we talked about the security part. In this microlearning, we talk about the validation part.
32	32
33		-In all these components you have the option to define the character set within the Advanced tab of the component. In this microlearning, we will use the File to string transformer to illustrate how that will look.
	34	+=== 3.1 Configuration on system message level in Design ===
34	34
35		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-characterset--characterset-configuration.png]]
	36	+As you have learned from the crash course, you can validate an XML message with the help of an XSD. This XSD describes data types, order, associations, and length of attributes. You can use such an XSD to validate what your clients send you. eMagiz will automatically define a WSDL based on the combination of system messages you provide for each operation you want to host. To ensure that the WSDL is created correctly, don't forget to add an entity called "Send{givenname}Request" to the (request) system message and an entity called "Send{givenname}Response" in case you have a response system message. An example of how this needs to be configured in Design is shown below.
36	36
37		-In this field, you can define the character set of your choice. To make this work in eMagiz you need to navigate to the Create phase of eMagiz and open the entry flow in which you want to retrieve the file to a certain location. Within the context of this flow, we need to add functionality that will ensure that the correct character set is used. To do so first enter "Start Editing" mode on flow level. After that open, the File to string transformer, navigate to the Advanced tab, and fill in the correct character set. After you have defined the correct character set the only thing left to do is to Save the component. See the suggested additional readings section on the complete list of character sets that are supported by Java 8.
	38	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--root-entity-for-wsdl.png]]
38	38
39		-Congratulations you have successfully learned how to specify the character set.
	40	+=== 3.2 Effect in Create ===
40	40
	42	+In the infra flow, eMagiz automatically adds a support object of the "Dynamic WSDL" type. In this support object, the link is made between the system message definitions and the WSDL that will be created based on this.
	43	+
	44	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]]
	45	+
	46	+{{warning}}Note that when you make changes to the system message after the integration is already in Create, or when you add a new integration to Create, you need to create a new version of your infra flow to be able to deploy the changes to your WSDL.{{/warning}}
	47	+
	48	+With this done, you have successfully added validation to your SOAP web service.
	49	+
41	41	== 4. Assignment ==
42	42
43		-Configure an entry in which you define the component and configuration needed to process a file on a per-line basis.
44		-This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
	52	+Add validation to the SOAP Webservice we have been configuring.
	53	+This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
45	45
46	46	== 5. Key takeaways ==
47	47
48		-* Some external system talk in a different character set
49		-* eMagiz talks in default UTF-8 as a character set and assumes everyone else also does this
50		-* In cases of mismatch correct is at the point where you talk with the other system (i.e. entry or exit)
51		-* eMagiz provides several components within which you can define the character set
	57	+* Crucial parts in the configuration are:
	58	+ ** Operation Name
	59	+ ** SOAP Webservice Namespace
	60	+ ** validationvalidation
	61	+ ** Authentication
	62	+* Validation is done with the help of an XSD
	63	+* The WSDL is used for external documentation
	64	+* eMagiz will automatically generate the WSDL for you based on your system messages
	65	+** Do not forget to add the correct root entity to your system message to make the WSDL work
52	52
53	53	== 6. Suggested Additional Readings ==
54	54
55		-If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
	69	+If you are interested in this topic and want more information, please read the help text provided by eMagiz.
56	56
57		-* https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html
58		-* https://www.techopedia.com/definition/941/character-set
59		-* https://www.smashingmagazine.com/2012/06/all-about-unicode-utf8-character-sets/
60		-
61	61	== 7. Silent demonstration video ==
62	62
63		-This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
	73	+{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages-gen3.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
64	64
65		-{{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
66		-
67	67	)))((({{toc/}}))){{/container}}{{/container}}