Changes for page Endpoint Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-novice-file-based-connectivity-processing-a-file-per-line
	1	+SOAP Headers

Content

...	...	@@ -1,70 +1,69 @@
1	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.
	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		-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 28th, 2021
	6	+* Last update: June 10th, 2021
7	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 SOAP Headers.
14	14
15		-This microlearning centers around learning how to place a header line on a flat-file output.
	15	+By SOAP Headers, we mean: headers within a SOAP Envelope that can be used to communicate metadata or authentication information between parties
16	16
17		-By header line we mean: A line in the output that defines the naming of the various columns
	17	+You can exchange data from:
	18	+* SOAP Header to Message Header
	19	+* Message Header to SOAP Header
18	18
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.
	21	+In both cases ensure that the correct information is exchanged.
	22	+
	23	+== 3. SOAP Headers ==
20	20
21		-== 3. Header line ==
	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.
22	22
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.
	27	+You can exchange data from:
	28	+* SOAP Header to Message Header
	29	+* Message Header to SOAP Header
24	24
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.
	31	+In both cases ensure that the correct information is exchanged.
26	26
27		-Ensure that the directory to which you reference is the same as in your functional file outbound channel adapter.
	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.
28	28
29		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--file-outbound-channel-header-line.png]]
	35	+In that microlearning, we also discussed the component that we need for this. The 'complex SOAP header mapper'.
30	30
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.
	37	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--complex-soap-header-mapper.png]]
32	32
33		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--file-outbound-channel-header-line-advanced.png]]
	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.
34	34
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:
	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:
36	36
37		-'Header1;Header2;Header3;Header4'
	43	+[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-soap-headers--mapping-from-message-header.png]]
38	38
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.
	45	+Once you are satisfied you can press Save and link the support object to the web service outbound gateway.
40	40
41		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--define-columns-names.png]]
	47	+With this information, you can place SOAP Headers on message headers and vice versa every time you need it.
42	42
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:
44		-
45		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-header-line--wiretap-result.png]]
46		-
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.
48		-
49	49	== 4. Assignment ==
50	50
51		-Configure an exit in which you define and write a header line to a flat-file output before adding functional lines.
	51	+Call an external web service and send along some SOAP Headers.
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		-* 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
	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
59	59
60	60	== 6. Suggested Additional Readings ==
61	61
62		-There are no suggested additional readings on this topic
	63	+If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
63	63
64	64	== 7. Silent demonstration video ==
65	65
66		-This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
	67	+{{video attachment="novice-soap-webservice-connectivity-soap-headers.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
67	67
68		-{{video attachment="novice-file-based-connectivity-header-line.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
69		-
70	70	)))((({{toc/}}))){{/container}}{{/container}}