Changes for page eMagiz SFTP Connection guide

Summary

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

Details

Page properties

Content

...	...	@@ -14,50 +14,51 @@
14	14
15	15	* Basic knowledge of the eMagiz platform
16	16	* Understanding of the way in which an SFTP file pickup or drop is configured in eMagiz
	17	+* Reviewed microlearning :: TO ADD
	18	+
17	17
18		- bin/view/Main/eMagiz%20Academy/Microlearnings/Intermediate%20Level/File%20based%20connectivity/intermediate-file-based-connectivity-emagiz-sftp-connectivity/
19		-
20		- [[Connect Guide eMagiz SFTP>>doc:Main.eMagiz Academy.Microlearnings.WebHome]]
21		-
22	22	== 2. Key concepts ==
	21	+By the eMagiz SFTP, we mean: A specific SFTP offered by the eMagiz platform on which you can securely store and read messages. Considerations when connecting to the eMagiz SFTP
23	23
24		-This microlearning centers around determining the origin of log entries.
25		-By origin, in this context, we mean: Identifying which flow wrote an entry to the log that might be in need of analysis.
	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?
26	26
27		-* Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
28		- * In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant without your project.
29		-* This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
30		-* Double-clicking on a log entry provides you with the relevant details
31		-* Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
32		-* When you know the flow and the details you have determined the origin of the log entry
33	33
	28	+== 3. How to steps ==
34	34
	30	+=== 3.1 Obtain an SFTP User account ===
	31	+Make sure to get the access credentials from eMagiz Support. Ensure to obtain access credentials for all connected systems/applications that need to send or received files from the SFTP service. Every application team will get a specific user, and the eMagiz model will get it's own user. In this way, the data is securely provided to the ecosystem of the eMagiz model. For instance, in case there are 4 applications involved that need to get or send data to the SFTP service there will be 5 SFTP service users
35	35
36		-== 3. How to steps ==
	33	+=== 3.2 Create (agreed) folder structure ===
	34	+Once the integration is realized in eMagiz, the user will have chosen the folder structure for each receiving or sending user. On the SFTP folder structure there will be tst, accp and prod folder as well. That folder structure can be set by the eMagiz user as desired but needs to be known by eMagiz. Please see the next point
37	37
	36	+=== 3.3 Create script ===
	37	+For most implementations, external users or applications will send and receive files via the their own SFTP user. Each eMagiz integration model will have it's own SFTP user. To some use cases, files put on the eMagiz integration model SFTP user need to be synchronized with the external application SFTP user. On that case, a script needs to be provided to eMagiz Support. Please consult eMagiz Support to get help in case needed - samples are available.
	38	+
	39	+=== 3.4 Optimize SFTP user settings ===
	40	+Once the folder structure is fixed across test, accp and prod folders, a signal needs to be send to eMagiz Support. The eMagiz SFTP settings will be optimized accordingly using Event Notifications in AWS. Please ensure to transmit this signal as soon as possible to avoid misconfigured eMagiz SFTP settings for users.
	41	+
	42	+
	43	+
38	38	== 4. Assignment ==
39	39
40		-Determine the origin of at least five log entries that have been raised within your (Academy) project in the last two weeks. If your project has no log entries be creative in messing up stuff to create a log entry for which you can then determine the origin.
	46	+Take a moment to locate the Store component for eMagiz.
41	41
42	42	== 5. Key takeaways ==
43	43
44		-* Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
45		- * In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant without your project.
46		-* This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
47		-* Double-clicking on a log entry provides you with the relevant details
48		-* Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
49		-* When you know the flow and the details you have determined the origin of the log entry
	50	+* The eMagiz SFTP Service requires use of a specific Store component
	51	+* Please contact eMagiz Support to ensure the right configuration is created including the proper file paths inside the SFTP user folder
	52	+* Ensure to update eMagiz Support whenever the file path changes
50	50
51	51
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 when executing these actions.
	57	+None available
56	56
57	57	== 7. Silent demonstration video ==
58	58
59		-This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
60		-
	61	+None available
61	61	)))
62	62	((({{toc/}}))){{/container}}
63	63	{{/container}}