Skip to Content
Last modified by Erik Bakker on 2024/09/05 14:00
From version 18.1
edited by Erik Bakker
on 2023/04/13 14:16
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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Communication between models
1 +Image Transformations
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -When your integration landscape grows through time, you might decide to split functional business processes into multiple eMagiz models. In those cases, the question of connecting these models easily, stable, and securely could arise. This microlearning will focus on that question and provide an answer based on our vision and best practices when dealing with the platform.
2 +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).
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,48 +9,51 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
12 -This microlearning focuses on communication between two eMagiz models. When communicating to any external party (from the view of a specific model), you should always consider the following:
12 +This microlearning focuses on performing image transformations in eMagiz.
13 13  
14 -* Security
15 -* Loose coupling
16 -* Maintainability
17 -* Clarity
14 +With image transformation, we mean transforming the raw data that represents an image to another image format.
18 18  
19 -== 3. Communication between models ==
16 +* Read the helptext of the component to understand which formats are supported
17 +* Ensure the input image is supplied in the correct format
18 +* Ensure you wrap the output image in something if you want to do additional transformations on the data further downstream
20 20  
21 -Most users would think that communication via queues to connect two separate eMagiz models is a bright idea. However, this is something that we do not encourage. We discourage this for several practical and technical reasons alike.
20 +== 3. Image Transformation ==
22 22  
23 -When looking at the practical side of things getting it configured correctly is time-consuming and an error-prone action (as is evident by the question). Furthermore, it can lead to unexpected situations where you make a typo to listen to a queue on which no messages are provided. This queue will, however, be registered on the JMS level (when you activate the flow in question with the custom configuration), which can lead to confusing queue statistics and even more troublesome false-positive alerting based on missing queue metrics or missing consumers.
22 +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).
24 24  
25 -On top of that, when you allow one model to write and read from queues registered in another model, maintaining both models will become very complex. This holds for the ones working on the project at the moment but also for those working on it at a later stage and does that need to provide (incidental) support on the environments.
24 +Before we dive into the specifics of how to configure this let us first consider the following:
26 26  
27 -Another practical reason for not wanting this is that we do not actively support this use case from eMagiz. This means that when we update our technical infrastructure, we will not consider this scenario. This could lead to additional work in the future and reduced stability of your solution.
26 +* Read the helptext of the component to understand which formats are supported
27 +* Ensure the input image is supplied in the correct format
28 +* Ensure you wrap the output image in something if you want to do additional transformations on the data further downstream
28 28  
29 -From the technical point of view, the consequence of this construction is that both models need to know each other certificates and credentials, which are not considered secure. On top of that, because you, theoretically, can exchange data from any queue to any queue, you could create a situation in which updates in one model trigger changes in the other model (i.e., when using the same data model) that are unexpected (and frankly unwanted).
30 +{{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}}
30 30  
31 -We advise using functionality that makes it explicit that both models function independently of each other. From eMagiz, we consider two valid alternatives for this:
32 -- Using a web service as a communication layer between the two models. This web service can be REST or SOAP and has been implemented before
33 -- Using the Event Streaming functionality of eMagiz to write and read from topics.
32 +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.
34 34  
35 -Both alternatives have the benefit that the security can be tight and explicit (i.e., only model A can write/post data to model B). Furthermore, managing the solution becomes much easier as it uses the standard functionality within the platform. Therefore, we have no plans to support this approach in the product.
34 +[[image:Main.Images.Microlearning.WebHome@expert-create-your-transformations-image-transformation-image-transformation-component.png]]
36 36  
37 37  == 4. Assignment ==
38 38  
39 -Consider what your criteria are when communicating between models and compare them to our criteria.
40 -This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
38 +Check out which of the XPaths we have discussed today can be found within your project.
39 +This assignment can be completed within the (Academy) project you created/used in the previous assignment.
41 41  
42 42  == 5. Key takeaways ==
43 43  
44 -* Consider the following when communication between two models
45 -** Security
46 -** Loose coupling
47 -** Maintainability
48 -** Clarity
43 +Some of the very complex XPath options are:
49 49  
45 +* matches
46 +* replace
47 +* tokenize
48 +
50 50  == 6. Suggested Additional Readings ==
51 51  
52 -If you are interested in this topic and want more information, please consult us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]]
51 +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:
53 53  
53 +* http://www.xsltfunctions.com/xsl/fn_matches.html
54 +* http://www.xsltfunctions.com/xsl/fn_replace.html
55 +* http://www.xsltfunctions.com/xsl/fn_tokenize.html
56 +
54 54  == 7. Silent demonstration video ==
55 55  
56 56  As this is more of theoretical microlearning, there is no video accompanying the microlearning.)))((({{toc/}}))){{/container}}{{/container}}