Wiki source code of Changing the default messaging format to XML
Version 7.1 by Bouke Reitsma on 2023/03/02 08:48
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| 2 | |||
| |
2.6 | 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, XML is more appropriate as default message format. In this microlearning, we focus on changing the default message format and show the impact this has on flows in Create. |
| |
1.1 | 4 | |
| 5 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 6 | |||
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Basic knowledge of the eMagiz platform | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| |
2.3 | 13 | There are no specific concepts to consider for now that require additional explanation. |
| |
1.1 | 14 | |
| |
2.3 | 15 | == 3. Changing the default messaging format == |
| |
1.1 | 16 | |
| |
2.6 | 17 | In our crash course on the API Gateway pattern, we have learned about setting up the API Gateway. By default, the messaging format selected for your gateway is JSON. However, you can change the default messaging format to XML in your project. This change can be made in Design -> Settings -> API Management. On the right side of this overview are the gateway settings. The last entry of this overview is the Default Format. By clicking on the Edit settings button, you enter the following overview |
| |
2.4 | 18 | |
| 19 | AFBEELDING 1 TOEVOEGEN | ||
| |
1.1 | 20 | |
| |
7.1 | 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~*. |
| |
2.4 | 22 | |
| |
5.1 | 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.{{/info}} |
| |
1.1 | 24 | |
| |
2.3 | 25 | == 4. Impact in Create == |
| |
1.1 | 26 | |
| |
6.1 | 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 support objects are required for this GET operation, since your gateway does not require a JSON response any more. |
| |
3.1 | 28 | |
| 29 | AFBEELDING 2 TOEVOEGEN | ||
| |
1.1 | 30 | |
| 31 | == 4. Assignment == | ||
| 32 | |||
| |
3.1 | 33 | Change the default messaging format to XML. |
| |
1.1 | 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 | |||
| |
2.6 | 38 | * The default messaging format can be changed to XML |
| 39 | * Updating this only affects new flows | ||
| |
3.1 | 40 | * Migrating existing operations can be done by resetting the exit flow |
| |
1.1 | 41 | |
| 42 | == 6. Suggested Additional Readings == | ||
| 43 | |||
| 44 | If you are interested in this topic and want more information on it please read the help text provided by eMagiz. | ||
| 45 | |||
| 46 | == 7. Silent demonstration video == | ||
| 47 | |||
| |
2.6 | 48 | To be recorded. |
| |
1.1 | 49 | |
| 50 | )))((({{toc/}}))){{/container}}{{/container}} |