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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.dfirdausy
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
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.
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.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -22,29 +22,22 @@
22 22  
23 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}}
24 24  
25 -== 4. Impact in Create ==
25 +== 3.1 Impact in Create ==
26 26  
27 -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.
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 28  
29 29  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-changing-default-messaging-format--get-operation.png]]
30 30  
31 -== 4. Assignment ==
31 +== 4. Key takeaways ==
32 32  
33 -Change the default messaging format to XML.
34 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
35 -
36 -== 5. Key takeaways ==
37 -
38 38  * The default messaging format can be changed to XML
39 39  * Updating this only affects new flows
40 40  * Migrating existing operations can be done by resetting the exit flow
41 41  
42 -== 6. Suggested Additional Readings ==
37 +== 5. Suggested Additional Readings ==
43 43  
44 -If you are interested in this topic and want more information on it, please read the help text provided by eMagiz.
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 45  
46 -== 7. Silent demonstration video ==
47 -
48 -To be recorded.
49 -
50 50  )))((({{toc/}}))){{/container}}{{/container}}