Changes for page Endpoint Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-novice-soap-webservice-connectivity-configure-your-soap-webservice
	1	+Calling a SOAP Web service

Content

...	...	@@ -1,67 +1,107 @@
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.
	1	+{{container}}{{container layoutStyle="columns"}}(((
	2	+When talking to external parties via a SOAP web service you need to define in eMagiz that you want to call a SOAP web service so eMagiz will form a correct SOAP message. On top of the call there is a support object in eMagiz that will help you with the analysis of your problems when calling the SOAP web service. In this microlearning, we will learn how to call a SOAP web service from eMagiz.
3	3
4		-Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	4	+Should you have any questions, please contact academy@emagiz.com.
5	5
6		-* Last update: May 31th, 2021
7		-* Required reading time: 7 minutes
	6	+* Last update: April 1st, 2022
	7	+* Required reading time: 5 minutes
8	8
9	9	== 1. Prerequisites ==
10		-
11	11	* Basic knowledge of the eMagiz platform
12	12
13	13	== 2. Key concepts ==
	13	+This microlearning centers around calling a SOAP Webservice.
14	14
15		-This microlearning centers around learning how to define the character set to ensure that eMagiz processes the information correctly.
	15	+With SOAP, we mean: A messaging protocol specification for exchanging structured information in the implementation of web services in computer networks.
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.
	17	+* To call a REST Webservice you need either:
	18	+ ** A Web Service Outbound Gateway
	19	+* Critical information when configuring this component:
	20	+ ** URL
	21	+ ** Retry Advice
	22	+ ** Error Handling
	23	+ ** Authentication
	24	+
	25	+== 3. Calling a SOAP Webservice ==
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)
	27	+When talking to external parties via a SOAP web service you need to define in eMagiz that you want to call a SOAP web service so eMagiz will form a correct SOAP message. On top of the call there is a support object in eMagiz that will help you with the analysis of your problems when calling the SOAP web service. In this microlearning, we will learn how to call a SOAP web service from eMagiz.
22	22
23		-== 3. Character set ==
	29	+Calling a SOAP Webservice within eMagiz can be done with the help of a Web Service Outbound Gateway. To correctly configure this component you need to consider the following elements:
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.
	31	+* URL
	32	+* Retry Advice
	33	+* Error Handling
	34	+* Authentication
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:
	36	+We will discuss the first three items in this list in this microlearning. In the microlearnings that will follow this microlearning, we will delve deeper into various authentication possibilities.
28	28
29		-- File to string transformer
30		-- Flat file to XML transformer
31		-- File outbound channel adapter
	38	+Before we delve into the configuration of the component let us first move to Create and open an exit flow in which we want to call the SOAP Webservice. When you open the exit flow it will look similar to this:
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.
	40	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--exit-flow-starting-point.png]]
34	34
35		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-characterset--characterset-configuration.png]]
	42	+Now that we have opened the flow and are in "Start Editing" mode we need to add the web service outbound gateway to start with.
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.
	44	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component.png]]
38	38
39		-Congratulations you have successfully learned how to specify the character set.
	46	+=== 3.1 URL ===
40	40
	48	+Now that we have added the correct component to the canvas it has become time to configure the component correctly. The first thing to configure when calling a SOAP Webservice is determining and registering the endpoint (URL) eMagiz should call to deliver the message too. As always in scenarios where an information element can change between environments, you should use a property reference and determine the correct value on a per-environment basis.
	49	+
	50	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-url.png]]
	51	+
	52	+=== 3.2 Retry Advice ===
	53	+
	54	+The second setting we need to configure is the retry advice. With retry advice, you can guard your solution against temporary connection losses between eMagiz and the external party. As this can happen from time to time the best practice is to configure such a Retry Advice on every Web Service Outbound component. To add the Retry Advice move to the Advanced tab and move down to the Request handler advice chain segment. Within this segment, you will see a button called Retry Advice.
	55	+
	56	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-button.png]]
	57	+
	58	+When you click on the Retry Advice button you will be prompted with a pop-up. In here you need to configure the exact settings
	59	+
	60	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-pop-up-empty.png]]
	61	+
	62	+The best practice for this configuration is as follows for asynchronous solutions:
	63	+* Select the option called Simple Retry Policy
	64	+* Set the max attempts at 6
	65	+* Select the Fixed back off policy
	66	+* Set the backoff period at 5000 (ms)
	67	+
	68	+When you have done so the configuration should look as follows. The only thing left is to press Save to save your Retry Advice configuration
	69	+
	70	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-pop-up-filled-in.png]]
	71	+
	72	+=== 3.3 Error Handling ===
	73	+
	74	+When calling a SOAP Web service with the configuration we have defined up till here you could suffer from cryptic error response you get back when the SOAP web service call fails. To improve the error handling to make your life easier when analyzing the problem you need to add a support object to the canvas and link it to the web service outbound gateway. This support object is named "Detailed SOAP Fault Message Resolver".
	75	+
	76	+To link the support object to your web service outbound gateway you open the web service outbound gateway, navigate to the Advanced tab, and select the Fault message resolver. Afterward press Save to save the link between the components.
	77	+
	78	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-fault-message-resolver.png]]
	79	+
	80	+Now that we have configured the HTTP Outbound component to our liking we can press Save on the component level to store our changes. As a result the flow will look as follows:
	81	+
	82	+[[image:Main.Images.Microlearning.WebHome@microlearning/novice-soap-webservice-connectivity-calling-a-soap-webservice--flow-result.png]]
	83	+
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.
	86	+Build a flow within your project in which you do a call to an external party that hosts a SOAP web service.
44	44	This assignment can be completed with the help of the (Academy) project that you have 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
	91	+* eMagiz will create a valid SOAP message when using this component
	92	+* eMagiz provides a support object for better error handling of SOAP faults
	93	+* There are four key configuration elements:
	94	+ ** URL
	95	+ ** Retry Advice
	96	+ ** Error Handling
	97	+ ** Authentication
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:
	101	+If you are interested in this topic and want more information on it 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.
	105	+{{video attachment="novice-soap-webservice-connectivity-calling-a-soap-webservice.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}}