Changes for page Endpoint Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Calling a SOAP Web service
	1	+novice-file-based-connectivity-processing-a-file-per-line

Content

...	...	@@ -1,107 +1,70 @@
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.
	1	+{{container}}{{container layoutStyle="columns"}}(((
	2	+In this microlearning, we will learn how you can define a header line in which you specify the naming of the various columns. Some external systems require a header line when you supply them with data via a flat file that is placed somewhere.
3	3
4		-Should you have any questions, please contact academy@emagiz.com.
	4	+Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
6		-* Last update: April 1st, 2022
	6	+* Last update: May 28th, 2021
7	7	* Required reading time: 5 minutes
8	8
9	9	== 1. Prerequisites ==
	10	+
10	10	* Basic knowledge of the eMagiz platform
11	11
12	12	== 2. Key concepts ==
13		-This microlearning centers around calling a SOAP Webservice.
14	14
15		-With SOAP, we mean: A messaging protocol specification for exchanging structured information in the implementation of web services in computer networks.
	15	+This microlearning centers around learning how to place a header line on a flat-file output.
16	16
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 ==
	17	+By header line we mean: A line in the output that defines the naming of the various columns
26	26
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.
	19	+Some external parties require that the first line in the flat file output (i.e. CSV) is filled with column names (i.e. headers). In eMagiz, we call this line a header line.
28	28
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:
	21	+== 3. Header line ==
30	30
31		-* URL
32		-* Retry Advice
33		-* Error Handling
34		-* Authentication
	23	+In this microlearning, we will learn how you can define a header line in which you specify the naming of the various columns. Some external systems require a header line when you supply them with data via a flat file that is placed somewhere. The header line is the first line in the flat file output. Within this line, the various column names are specified for clarity.
35	35
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.
	25	+To add such a header line in eMagiz you need to navigate to the Create phase of eMagiz and open the exit flow in which you want to drop the file to a certain location. Within the context of this flow, we need to add functionality that will ensure that a header line is written to the output before any functional lines are added. To do so first enter "Start Editing" mode on flow level. After you have done so please add a file outbound channel adapter to the flow including an input channel. We will use this component to write our header line to the flat file output.
37	37
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:
	27	+Ensure that the directory to which you reference is the same as in your functional file outbound channel adapter.
39	39
40		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--exit-flow-starting-point.png]]
	29	+[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--file-outbound-channel-header-line.png]]
41	41
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.
	31	+Now it is time to turn our attention to the Advanced tab. For the Mode select Ignore. Select this option to ensure that the header line is only written down once when there is no output created yet and not somewhere in the middle, in the end, or every time. Furthermore, select the option Append New Line to ensure that the remainder of the information is not appended to the same line.
43	43
44		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component.png]]
	33	+[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--file-outbound-channel-header-line-advanced.png]]
45	45
46		-=== 3.1 URL ===
	35	+After you have done so we need to add a standard transformer that defines the various column names to be written to the flat file output. To do so add the standard transformer component to the canvas including an input channel. After you have done so define the relevant SpEL expression. In this case, we advise using a property value that represents a string of column names. The value of the property should be something as follows:
47	47
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.
	37	+'Header1;Header2;Header3;Header4'
49	49
50		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-url.png]]
	39	+Do note that the separator, in this case, needs to match the requirements of the external system. At the flow configuration level, the standard transformer should look as follows.
51	51
52		-=== 3.2 Retry Advice ===
	41	+[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--define-columns-names.png]]
53	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.
	43	+Our last step is to ensure that this piece of logic is tied to the main flow and is executed before writing the functional line(s) to the output file. To make that happen we need to add a wiretap to the flow. With the help of this functionality, you can define which part of the logic takes precedence over another part of the logic. To do so double click on the channel on which you want to place a wiretap, select the option wiretap and select the correct wiretap channel. After you have done this the result should be something as follows:
55	55
56		-[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-button.png]]
	45	+[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--wiretap-result.png]]
57	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
	47	+With these couple of steps, you have now successfully added logic to your flow that will ensure that a header line is added before any functional line(s) are written to the output file.
59	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		-
84	84	== 4. Assignment ==
85	85
86		-Build a flow within your project in which you do a call to an external party that hosts a SOAP web service.
	51	+Configure an exit in which you define and write a header line to a flat-file output before adding functional lines.
87	87	This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
88	88
89	89	== 5. Key takeaways ==
90	90
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
	56	+* The header line contains the names of the columns of the flat file output
	57	+* Use the Ignore mode to ensure the header line is created once
	58	+* Use the wiretap to ensure the header line is created first
98	98
99	99	== 6. Suggested Additional Readings ==
100	100
101		-If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
	62	+There are no suggested additional readings on this topic
102	102
103	103	== 7. Silent demonstration video ==
104	104
105		-{{video attachment="novice-soap-webservice-connectivity-calling-a-soap-webservice.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	66	+This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
106	106
	68	+{{video attachment="novice-file-based-connectivity-header-line.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
	69	+
107	107	)))((({{toc/}}))){{/container}}{{/container}}