Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 16.2
edited by Danniar Firdausy
on 2024/09/05 10:24
Change comment: There is no comment for this version
To version 9.2
edited by Bouke Reitsma
on 2023/03/03 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Changing the default messaging format
1 +Changing the default messaging format to XML
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.BoukeReitsma
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -In our [[crash course>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] on the API Gateway pattern, we have learned about setting up the API Gateway. By default, the message format chosen for your gateway is JSON. However, in some instances, other message formats are more appropriate as default. In this microlearning, we focus on changing the default message format and show the impact this has on flows in Create.
3 +In our crash course on the API Gateway pattern, we have learned about setting up the API Gateway. By default, the messaging format chosen for your gateway is JSON. However, in some instances, other message formats are more appropriate as default. In this microlearning, we focus on changing the default message format and show the impact this has on flows in Create.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -20,24 +20,32 @@
20 20  
21 21  The last option allows you to switch between JSON or XML as your default messaging format in the gateway. In order to apply your new default to your project, you must press "Apply settings" in Design -> Architecture to confirm your change~*.
22 22  
23 -{{info}}~* Note Changing the default messaging format does not affect existing operations in Create. Migrating these flows requires a reset of the exit flow. Additionally, the default response in Catalog has to be changed to application/xml. {{/info}}
23 +{{info}}~* Note Changing the default messaging format does not affect existing operations in Create. Migrating these flows requires a reset of the exit flow. Additionally, the default response in Catalog has to be changed to application/xml.
24 + {{/info}}
24 24  
25 -== 3.1 Impact in Create ==
26 +== 4. Impact in Create ==
26 26  
27 -After the flows are resetted in Create, the automatic flow creation in the Create phase is adapted to the new default setting. When changing the messaging format to XML, the components of newly generated flows are created with different names and settings. The image below shows an example of an API GET operation with XML as the default messaging format. Besides the changed naming of the transformation, no JSON factory support objects are required in your flow in comparison with a JSON messaging format.
28 +The automatic flow creation in the Create phase is adapted to the new default setting. When changing the messaging format to XML, the components of newly generated flows are created with different names and settings. The image below shows an example of an API GET operation with XML as the default messaging format. Besides the changed naming of the transformation, no support objects are required for this GET operation, since your gateway does not require a JSON response any more.
28 28  
29 29  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-changing-default-messaging-format--get-operation.png]]
30 30  
31 -== 4. Key takeaways ==
32 +== 4. Assignment ==
32 32  
34 +Change the default messaging format to XML.
35 +This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
36 +
37 +== 5. Key takeaways ==
38 +
33 33  * The default messaging format can be changed to XML
34 34  * Updating this only affects new flows
35 35  * Migrating existing operations can be done by resetting the exit flow
36 36  
37 -== 5. Suggested Additional Readings ==
43 +== 6. Suggested Additional Readings ==
38 38  
39 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-defining-a-message-format||target="blank"]]
40 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
41 -*** [[Defining a message format (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-defining-a-message-format||target="blank"]]
45 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
42 42  
47 +== 7. Silent demonstration video ==
48 +
49 +To be recorded.
50 +
43 43  )))((({{toc/}}))){{/container}}{{/container}}