Changes for page Multipart form-data

Last modified by Erik Bakker on 2024/06/17 11:39

From 8.1 to 7.1 From 23.2 to 23.1

From version 23.1

edited by Erik Bakker
on 2024/01/19 08:20

Change comment: There is no comment for this version

To version 8.1

edited by Erik Bakker
on 2022/07/26 12:49

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Multipart form-data
++Image Transformations

Content

@@ -1,5 +1,5 @@
  {{container}}{{container layoutStyle="columns"}}(((
--Sometimes when you call an external REST endpoint, they require you to send meta information and one or more "attachments" in one call to the REST endpoint. To make this possible, you need to send the information with the contentType called multipart/form-data. In this microlearning, we will discuss how you can configure a valid message within the eMagiz platform that allows you to send out messages with this contentType and have them accepted by the endpoint in question.
++In most cases, you will transform XML messages to other XML messages, or you will transform JSON or EDI messages in another of these formats. However, sometimes you want to perform an image transformation. With this image transformation you can transform images in certain formats to another format (i.e. png). This can come in handy when you want to standardize the image format before using it further downstream in your business application(s).
  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
@@ -9,73 +9,51 @@
  == 2. Key concepts ==
--This microlearning focuses on configuring a multipart/form-data message within eMagiz to ensure it is sent correctly to an endpoint.
++This microlearning focuses on performing image transformations in eMagiz.
--Key aspects are:
++With image transformation, we mean transforming the raw data that represents an image to another image format.
--* Defining the boundary that separates the parts of the message
--* Defining the content types of each part of the message
--* Construction of the complete message according to the specification
++* Read the helptext of the component to understand which formats are supported
++* Ensure the input image is supplied in the correct format
++* Ensure you wrap the output image in something if you want to do additional transformations on the data further downstream
--== 3. Multipart form-data ==
++== 3. Image Transformation ==
--Sometimes when you call an external REST endpoint, they require you to send meta information and one or more "attachments" in one call to the REST endpoint. To make this possible, you need to send the information with the contentType called multipart/form-data. In this microlearning, we will discuss how you can configure a valid message within the eMagiz platform that allows you to send out messages with this contentType and have them accepted by the endpoint in question.
++In most cases, you will transform XML messages to other XML messages, or you will transform JSON or EDI messages in another of these formats. However, sometimes you want to perform an image transformation. With this image transformation you can transform images in certain formats to another format (i.e. png). This can come in handy when you want to standardize the image format before using it further downstream in your business application(s).
--Key aspects are:
++Before we dive into the specifics of how to configure this let us first consider the following:
--* Defining the boundary that separates the parts of the message
--* Defining the content types of each part of the message
--* Construction of the complete message according to the specification
++* Read the helptext of the component to understand which formats are supported
++* Ensure the input image is supplied in the correct format
++* Ensure you wrap the output image in something if you want to do additional transformations on the data further downstream
--{{info}}
--The following criteria apply when utilizing the boundary functionality within the multipart/form-data construction:
--* The value of the Boundary must begin with a double horizontal bar –, this is called a leading hyphen
--* The value of the Boundary must not contain more than 70 characters in addition to the leading hyphen.
--* The value of the Boundary must not contain characters that are disabled by the HTTP protocol or the URL, such as the colon: etc.
--* A boundary within the request body must always be preceeded by a CRLF line. This means that when the request body **ends** with a CRLF line an **additional** CRLF line is needed **before** the boundary doubling the CRLF lines in that part of the request body.{{/info}}
++{{warning}}The focus of this microlearning lies on the image transformer component. Ensuring that the input is useful and the output fits the remainder of the process is highly depending on the use case and will therefore not be discussed in this microlearning{{/warning}}
--=== 3.1 Prepare the message ===
++When turning to the Create phase of eMagiz, we need to open the flow and enter "Start Editing" mode to add the component we need. For example, in the left panel, you can search for "Image". This will yield the following result.
--To construct the message, several steps are needed to make it work. Luckily, most of the steps necessary have to do with concepts we have already discussed in previous microlearnings. As you can imagine, based on what multipart/form-data entails, we need a way to both store the meta information and the file(s) we want to send to the external party. For example, put the metadata in one (or multiple) header(s) and use the file content as a payload. This you can achieve with a header enricher and standard transformer.
++[[image:Main.Images.Microlearning.WebHome@expert-create-your-transformations-image-transformation-image-transformation-component.png]]
--Once the file content is your payload, you must ensure that the data is "raw." So when you have a base64 encoded string, you should decode it before sending it to the endpoint.
++== 4. Assignment ==
--On top of that, we need to define the contentType header.
++Check out which of the XPaths we have discussed today can be found within your project.
++This assignment can be completed within the (Academy) project you created/used in the previous assignment.
--[[image:Main.Images.Microlearning.WebHome@expert-data-handling-multipart-form-data--content-type-header-config.png]]
++== 5. Key takeaways ==
--=== 3.2 Construct the message ===
++Some of the very complex XPath options are:
--After you have set the stage, you can use a standard transformer component to build your message correctly. To create it correctly, you need to take the following into account:
++* matches
++* replace
++* tokenize
--* Each part of the message needs to be separated by a boundary
--* The message needs to start with a boundary and finish with a boundary
--* Line breaks are needed to differentiate between the boundary and the text content
--* No line break is needed when the content is not text-based
++== 6. Suggested Additional Readings ==
--Given all this, you can write the following SpEL expression that will yield a desirable output:
++If you are interested in this topic and want more information on it, please read the help text provided by eMagiz and read more information on the following links:
--{{code}}'${multi-part-form-data.data-handling.boundary}' + headers.metaInfo + T(com.emagiz.util.Newline).CRLF.characters + '${multi-part-form-data.data-handling.boundary}' + T(com.emagiz.util.Newline).CRLF.characters + 'Content-Disposition: form-data; name="file"; filename="' + headers.filename + '"' + T(com.emagiz.util.Newline).CRLF.characters + 'Content-Type: application/pdf' + T(com.emagiz.util.Newline).CRLF.characters + T(com.emagiz.util.Newline).CRLF.characters + payload + '${multi-part-form-data.data-handling.boundary}'{{/code}}
++* http://www.xsltfunctions.com/xsl/fn_matches.html
++* http://www.xsltfunctions.com/xsl/fn_replace.html
++* http://www.xsltfunctions.com/xsl/fn_tokenize.html
--Putting this in a standard transformation gives you the following solution in the flow.
++== 7. Silent demonstration video ==
--[[image:Main.Images.Microlearning.WebHome@expert-data-handling-multipart-form-data--standard-transformer-config.png]]
--
--=== 3.3 Calling the endpoint ===
--
--Now that we have constructed our message correctly, the last thing to do is call the endpoint in question. Since we have prepared our message and accurately defined our contentType calling the endpoint does not require any additional configurations compared to what you are already used to when dealing with REST endpoints.
--
--== 4. Key takeaways ==
--
--* Make sure to define the boundary that separates the parts of the message
--* Make sure to define the content types of each part of the message
--* Make sure to define the content type that matches the specification for multipart/form-data
--* Construct the complete message according to the specification
--
--== 5. Suggested Additional Readings ==
--
--If you are interested in this topic, please read the help texts on the platform and read the following link:
--
--* [[Multipart form-data explained>>https://www.sobyte.net/post/2021-12/learn-about-http-multipart-form-data/||target="blank"]]
--
--)))((({{toc/}}))){{/container}}{{/container}}
++As this is more of theoretical microlearning, there is no video accompanying the microlearning.)))((({{toc/}}))){{/container}}{{/container}}

Changes for page Multipart form-data

Summary

Details

Navigation