Changes for page Base64 encoding
Last modified by Danniar Firdausy on 2024/09/17 21:22
From version 19.3
edited by Danniar Firdausy
on 2024/09/17 21:19
on 2024/09/17 21:19
Change comment:
There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/08/28 15:20
on 2022/08/28 15:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,7 +1,6 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 -((( 4 -In many cases, the standard tools in eMagiz are sufficient for manipulating data to meet the needs of external parties. However, there are instances where more complex functionality is required. This microlearning session will guide you through the process of base64 encoding your input messages, which is essential when the receiving party requires encoded data. By the end of this microlearning, you will understand how to implement this feature and when it's most useful, especially when the message is not encoded, but you need to send the data encoded to the external party. 3 +(((Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party. 5 5 6 6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 7 7 ... ... @@ -12,8 +12,15 @@ 12 12 == 2. Key concepts == 13 13 14 14 This microlearning centers around base64 encoding. 15 - *With base64encoding, wemean:turning the string into an encoded string that the external party can handle.14 +We mean turning the string into an encoded string that the external party can handle. 16 16 16 +Essential characteristics of this functionality are: 17 + 18 +* Encoding (and decoding) of base64 strings take up additional memory (up to 33%) 19 +* Separate integration for the base64 strings apart from metadata is advisable 20 +* The component in eMagiz needs a base64 encoded string as input 21 +* Multiple times encoding and encoding in the same integration is **not** advisable 22 + 17 17 == 3. Base64 encoding == 18 18 19 19 Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party. ... ... @@ -23,9 +23,9 @@ 23 23 * Encoding (and decoding) of base64 strings take up additional memory (up to 33%) 24 24 * Separate integration for the base64 strings apart from metadata is advisable 25 25 * The component in eMagiz needs a base64 encoded string as input 26 -* Multiple times encoding and decoding in the same integration is **not** advisable32 +* Multiple times encoding and encoding in the same integration is **not** advisable 27 27 28 -The Base64 encode algorithm converts the original string into a base64 encoded string. Technically, it can be said that it converts eight-bit bytes into six-bit bytes. So when you have a string of ABC, you could manually convert this to an encoded format. You can find an excellent explanation of how it works [ [here>>https://base64.guru/learn/base64-algorithm/encode||target="blank"]]. Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper.34 +The Base64 encode algorithm converts the original string into a base64 encoded string. Technically, it can be said that it converts eight-bit bytes into six-bit bytes. So when you have a string of ABC, you could manually convert this to an encoded format. You can find an excellent explanation of how it works [here](https://base64.guru/learn/base64-algorithm/encode). Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper. 29 29 30 30 In the remainder of this microlearning, we will look at how you could implement this logic within the eMagiz tooling. 31 31 ... ... @@ -43,26 +43,32 @@ 43 43 44 44 Now that we know how to implement it, we can quickly look at possible use cases for this logic. We see this logic popping up mainly when dealing with attachments/files (i.e., pictures, pdf) within XML messages. 45 45 46 -== 4. Keytakeaways==52 +== 4. Assignment == 47 47 54 +Look for places where you could use this logic to aid your integration process within your (Academy) project. 55 +This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment. 56 + 57 +== 5. Key takeaways == 58 + 48 48 Essential characteristics of this functionality are: 49 49 50 50 * Encoding (and decoding) of base64 strings take up additional memory (up to 33%) 51 51 * Separate integration for the base64 strings apart from metadata is advisable 52 52 * The component in eMagiz needs a base64 encoded string as input 53 -* Multiple times encoding and decoding in the same integration is **not** advisable64 +* Multiple times encoding and encoding in the same integration is **not** advisable 54 54 55 -== 5. Suggested Additional Readings ==66 +== 6. Suggested Additional Readings == 56 56 57 57 If you are interested in this topic and want more information, please read the help text provided by eMagiz and the following links: 58 58 59 -* [[Advanced Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] 60 -** [[Risk Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Risk Management.WebHome||target="blank"]] 61 -*** [[Considering the impact of message size (Explanation)>>Main.eMagiz Academy.Microlearnings.Advanced Level.Risk Management.advanced-risk-management-considering-impact-of-message-size-on-stability-of-the-solution||target="blank"]] 62 -* [[Encode Base64 (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22encode+base64%22||target="blank"]] 63 -* [[Encode Algorithm (External)>>https://base64.guru/learn/base64-algorithm/encode||target="blank"]] 64 -* [[Base64 Encoding Online (External)>>https://www.base64encode.org/||target="blank"]] 65 -))) 70 +* https://base64.guru/learn/base64-algorithm/encode 71 +* https://www.base64encode.org/ 66 66 73 +== 7. Silent demonstration video == 74 + 75 +This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. 76 + 77 +{{video attachment="intermediate-data-handling-base64-encode.mp4" reference="Main.Videos.Microlearning.WebHome"/}}))) 78 + 67 67 ((({{toc/}}))){{/container}} 68 68 {{/container}}