Changes for page eMagiz SFTP Connectivity

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-eMagiz SFTP Connectivity
	1	+intermediate-file-based-connectivity-emaigz-sftp-connectivity

Content

...	...	@@ -1,11 +1,11 @@
1	1	{{container}}
2	2	{{container layoutStyle="columns"}}
3	3	(((
4		-In some cases, there is no communication possible with a local file directory. Or there is a requirement from the external party to place the files somewhere else. Mainly the somewhere else is either an FTP or an SFTP. This microlearning will look at the eMagiz SFTP and learn how to set up the connection between eMagiz and the eMagiz SFTP. In the following microlearning, we will take a more general approach and look how to connect to other SFTP hosts via eMagiz.
	4	+In this microlearning, we will learn what you should consider determining the impact of business logic within your integration solution. An eMagiz model is most useful when exchanging data between systems while taking care of data and protocol transformations. For example, an eMagiz model is generally less suited for incorporating business logic as these rules cannot be defined dynamically and are relatively complex. Filling your eMagiz model with a lot of business logic opens you up for a continuous discussion about data and interpretations of business rules. As that is not the core goal of an eMagiz model, you should always ask yourself what the most suitable place is to incorporate pieces of logic.
5	5
6	6	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7	7
8		-* Last update: June 2nd, 2022
	8	+* Last update: April 6th, 2021
9	9	* Required reading time: 4 minutes
10	10
11	11	== 1. Prerequisites ==
...	...	@@ -14,54 +14,55 @@
14	14
15	15	== 2. Key concepts ==
16	16
17		-This microlearning is about the eMagiz SFTP (connectivity).
	17	+This microlearning centers around considering the impact of business logic
18	18
19		-By the eMagiz SFTP, we mean: A specific SFTP offered by the eMagiz platform on which you can securely store and read messages.
	19	+By business logic, we mean: Rules that determine what should happen to a message
20	20
21		-Considerations when connecting to the eMagiz SFTP
	21	+The most interesting point when talking about business logic is:
22	22
23		-* Did you read the connect guide and made sure that all requirements are met?
24		-* Did you use the store component made available in the eMagiz store to set up the connection?
25		-* Did you verify that the indicator for temporary file name is set to false?
	23	+* Where to draw the line?
26	26
27		-== 3. eMagiz SFTP Connectivity ==
	25	+== 3. Considering the impact of business logic ==
28	28
29		-In some cases, there is no communication possible with a local file directory. Or there is a requirement from the external party to place the files somewhere else. Mainly the somewhere else is either an FTP or an SFTP. This microlearning will look at the eMagiz SFTP and learn how to set up the connection between eMagiz and the eMagiz SFTP. In the following microlearning, we will take a more general approach and look how to connect to other SFTP hosts via eMagiz.
30		-
31		-Considerations when connecting to the eMagiz SFTP
	27	+In this microlearning, we will learn what you should consider determining the impact of business logic within your integration solution. An eMagiz model is most useful when exchanging data between systems while taking care of data and protocol transformations. For example, an eMagiz model is generally less suited for incorporating business logic as these rules cannot be defined dynamically and are relatively complex. Filling your eMagiz model with a lot of business logic opens you up for a continuous discussion about data and interpretations of business rules. As that is not the core goal of an eMagiz model, you should always ask yourself what the most suitable place is to incorporate pieces of logic.
32	32
33		-* Did you read the connect guide and made sure that all requirements are met?
34		-* Did you use the store component made available in the eMagiz store to set up the connection?
35		-* Did you verify that the indicator for temporary file name is set to false?
	29	+(% class="wikigeneratedid" %)
	30	+[[Invalid check>>image:advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png||alt="Figure one" id="Iadvanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png"]]
36	36
37		-To connect to the eMagiz SFTP eMagiz offers multiple options in the eMagiz store. Depending on whether you want to read or write data you need to select the SFTP Inbound Connectivity or the SFTP Outbound Connectivity option in the store.
	32	+The most exciting point when talking about business logic is:
38	38
39		-(% class="wikigeneratedid" %)
40		-[[Invalid check>>image:intermediate-file-based-connectivity-emagiz-sftp-connectivity--store-alternatives.png||alt="Store components" id="Iintermediate-file-based-connectivity-emagiz-sftp-connectivity--store-alternatives.png"]]
	34	+* Where to draw the line?
41	41
42		-Within each of the options you can select between the default connection or the caching connection. Depending on the frequency with which you want to connect to the SFTP you need to select the default or the caching variant. In cases were you have a lot of interaction with the SFTP we advise to use the caching variant. In cases were there is infrequent interaction with the SFTP we advise to use the default variant.
	36	+What is acceptable and what is not acceptable in eMagiz then quickly becomes the question. You could argue that any business rule is too much in eMagiz. However, that is a bit too strict of a definition as there are scenarios in which it is pretty helpful to manipulate the destination of messages while transporting them between systems. One example of this would be logic in the asynchronous routing that allows you to develop functionality within the routing and ensure that each piece of the functionality comes with an on/off switch. This way, you reduce problems when deploying and make it clear to all that data can be sent (or not sent) to certain offramps.
43	43
44		-(% class="wikigeneratedid" %)
45		-[[Invalid check>>image:intermediate-file-based-connectivity-emagiz-sftp-connectivity--store-options.png||alt="Store alternatives" id="Iintermediate-file-based-connectivity-emagiz-sftp-connectivity--store-alternatives.png"]]
46	46
	39	+Another valid scenario would be to filter messages based on a single criterion to reduce the data load sent to specific systems. For example, when you have one system that sends out employee information that needs to be sent to ten different systems, you could use the messaging pattern and filter out the relevant information in the offramp. However, you could also publish all employee information on a topic, let all those systems consume from it, and do the filtering themselves. Both are possible. The most interesting question in this scenario would be whether it can hurt if all systems access all employee information. If that is the case, then filtering in eMagiz becomes highly relevant suddenly.
	40	+
	41	+
	42	+On the flip side, you should not implement business logic in eMagiz if the rules consist of multiple criteria and are dependent on other (tables of) information. So gathering all that and making the decision will become so complex that you should consider moving the logic to the business application itself. That way, you reduce the complexity of the integration. This reduces the risks of things going wrong and reduces the time needed to develop and maintain the integration.
	43	+
	44	+
	45	+The main takeaway should be that adding business logic comes at a price. Depending on the specific requirements, you have to decide whether the pros outweigh the cons. The most crucial part of using business logic is proper documentation. That way, it is clear what the business logic does, why it is there, and how it can be controlled.
	46	+
47	47	== 4. Assignment ==
48	48
49		-Configure an exit that holds the logic needed to write a file to the eMagiz SFTP. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
	49	+See if you can determine which business logic is implemented in your project and whether that was a wise decision. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
50	50
51	51	== 5. Key takeaways ==
52	52
53		-* Did you read the connect guide and made sure that all requirements are met?
54		-* Did you use the store component made available in the eMagiz store to set up the connection?
55		-* Did you verify that the indicator for temporary file name is set to false?
	53	+* Check out the pros and cons to determine whether business logic in eMagiz makes sense
	54	+* Documentation is key
56	56
57	57	== 6. Suggested Additional Readings ==
58	58
59		-* [[Connect Guide eMagiz SFTP>>doc:Main.eMagiz Academy.Microlearnings.WebHome]]
	58	+* [[Asynchronous Routing>>doc:Main.eMagiz Academy.Microlearnings.WebHome]]
60	60
61	61
62	62	== 7. Silent demonstration video ==
63	63
64		-{{video attachment="intermediate-file-based-connectivity-emagiz-sftp-connectivity.mp4"/}})))
	63	+There is no video for this microlearning.
65	65
	65	+{{video attachment="advanced-active-monitoring-determining-cause-of-log-entry.mp4"/}})))
	66	+
66	66	((({{toc/}}))){{/container}}
67	67	{{/container}}

advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ebakker

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.0 KB

Content