Skip to Content
Last modified by Danniar Firdausy on 2024/09/30 17:12
From version 26.1
edited by Eva Torken
on 2023/08/25 11:31
Change comment: There is no comment for this version
To version 24.1
edited by Erik Bakker
on 2022/08/29 14:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.etorken
1 +XWiki.ebakker
Content
... ... @@ -38,7 +38,7 @@
38 38  * When you change something to the configuration of the backend operation (i.e. endpoint, parameter, system request/response) the change will **only** impact the specific exit gate
39 39  * When you change the gateway request/response message (with transformation) the change will impact **both** the all-entry and the specific exit gate
40 40  
41 -In some cases, version bumps are needed to confirm the change in Create. For exit gates, this process is identical to when you do a version bump of any messaging flow after updating for example a CDM message or message mapping. However, when you update something on the all-entry level what is needed differs. In case of a security change you need to reset the all-entry flow. To reset a flow simply access the context menu on flow level in Create (via a right-mouse click) and press Reset flow. In case of all other changes, no reset is needed, just a version bump.
41 +In all cases, you need a version bump of the flow to which you can relate the change. For exit gates, this process is identical to when you do a version bump of any messaging flow after updating for example a CDM message or message mapping. However, when you update something on the all-entry level this becomes less simple. Because eMagiz does not only pre-configure the resources for you in Create but the complete all-entry flow you **need** a reset of the all-entry to reflect these changes. To reset a flow simply access the context menu on flow level in Create (via a right-mouse click) and press Reset flow.
42 42  
43 43  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--reset-flow-context-menu.png]]
44 44  
... ... @@ -66,8 +66,13 @@
66 66  
67 67  As is the case with all new versions in Create the changes will only be effectuated when you deploy your solution via the Deploy phase of eMagiz.
68 68  
69 -== 4. Key takeaways ==
69 +== 4. Assignment ==
70 70  
71 +Think of three changes you want to apply to an API Gateway solution and see if you can determine which flow in Create needs an update.
72 +This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
73 +
74 +== 5. Key takeaways ==
75 +
71 71  * Updating can happen from Design
72 72  * Updating can happen from Create
73 73  * Both situations have a different impact
... ... @@ -75,9 +75,14 @@
75 75  * Updating from Create does not involve a reset
76 76  * Updating from Design involves a reset
77 77  
78 -== 5. Suggested Additional Readings ==
79 79  
84 +
85 +== 6. Suggested Additional Readings ==
86 +
80 80  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
81 81  
89 +== 7. Silent demonstration video ==
82 82  
91 +As this is a more theoretical microlearning we did not provide a video for this one.
92 +
83 83  )))((({{toc/}}))){{/container}}{{/container}}