Wiki source code of eMagiz SFTP Connection guide
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | = How to connect with the eMagiz SFTP Service = | ||
| 5 | |||
| 6 | In this microlearning, we will provide short guide that will help eMagiz users how to connect to the eMagiz SFTP service. Allthough this is a regular SFTP service, there are some specific steps involved to allow an optimal configuration of the integration. | ||
| 7 | |||
| 8 | Should you have any questions, please contact academy@emagiz.com. | ||
| 9 | |||
| 10 | * Last update: June 2nd, 2022 | ||
| 11 | * Required reading time: 5 minutes | ||
| 12 | |||
| 13 | == 1. Prerequisites == | ||
| 14 | |||
| 15 | * Basic knowledge of the eMagiz platform | ||
| 16 | * Understanding of the way in which an SFTP file pickup or drop is configured in eMagiz | ||
| 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 | == 2. Key concepts == | ||
| 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. | ||
| 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 | |||
| 34 | |||
| 35 | |||
| 36 | == 3. How to steps == | ||
| 37 | |||
| 38 | == 4. Assignment == | ||
| 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. | ||
| 41 | |||
| 42 | == 5. Key takeaways == | ||
| 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 | |||
| 51 | |||
| 52 | |||
| 53 | == 6. Suggested Additional Readings == | ||
| 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. | ||
| 56 | |||
| 57 | == 7. Silent demonstration video == | ||
| 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 | ))) | ||
| 62 | ((({{toc/}}))){{/container}} | ||
| 63 | {{/container}} |