Changes for page Configure A Backend Operation
Last modified by Erik Bakker on 2024/08/23 11:32
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,0 @@ 1 -Configure a backend operation - Parent
-
... ... @@ -1,1 +1,0 @@ 1 -WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.marijn - Content
-
... ... @@ -1,8 +1,17 @@ 1 -{{container}}{{container layoutStyle="columns"}}((( 1 +{{html wiki="true"}} 2 +<div class="ez-academy"> 3 + <div class="ez-academy_body"> 4 + 5 +<div class="doc"> 6 + 7 + 8 + 9 += Configure a backend operation = 10 + 2 2 In this microlearning, we will focus on learning about how you can correctly configure the backend operations. 3 3 A crucial part of setting up your (API) Gateway with the help of RESTful services is knowing which backend operations you want to expose with the help of the API Gateway. 4 4 5 -Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].14 +Should you have any questions, please contact academy@emagiz.com. 6 6 7 7 * Last update: April 14th, 2021 8 8 * Required reading time: 6 minutes ... ... @@ -19,6 +19,8 @@ 19 19 20 20 When setting up your API Gateway integration the process of doing things is to start at the backend operation and based on that expose an operation in the API Gateway. 21 21 31 + 32 + 22 22 == 3. Configure a backend operation == 23 23 24 24 When you look at the conceptual idea of the API Gateway, exposing backend operations via a centralized location to the outside world ... ... @@ -26,7 +26,7 @@ 26 26 27 27 Configuring backend operations is done in the Design phase of eMagiz. When you are in the Design overview you can double click on the backend system that holds the operation(s). This action will show you the following pop-up 28 28 29 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--system-edit.png]]40 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--system-edit.png||]]</p> 30 30 31 31 In here you need to fill in the technical name, just as with any other system. Furthermore, you have two decisions to make: 32 32 ... ... @@ -38,7 +38,7 @@ 38 38 39 39 In case the answer to the first decision is XML you should switch the default format to XML and unselect the OpenAPI 3.0 spec. The result should be something like this. 40 40 41 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--system-edit-xml-result.png]]52 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--system-edit-xml-result.png||]]</p> 42 42 43 43 === 3.1 Importing a specification === 44 44 ... ... @@ -45,16 +45,16 @@ 45 45 If the external party can provide you with an OpenAPI 3.0 specification you can manage your backend system by pressing the Import button 46 46 when you are editing the system (double click on the system in question) 47 47 48 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--system-edit-manage.png]]59 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--system-edit-manage.png||]]</p> 49 49 50 50 After you have pressed the Import button you enter the following pop-up. Here you can select the OpenAPI 3.0 JSON file to be imported in eMagiz. 51 51 52 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--import-open-api-pop-up.png]]63 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--import-open-api-pop-up.png||]]</p> 53 53 54 54 Press Import and let eMagiz do the heavy lifting for you. eMagiz will now import all backend operations that are specified in the OpenAPI 3.0 JSON file you have selected. 55 55 A result of such an import could be as follows. 56 56 57 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--import-open-api-result.png]]68 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--import-open-api-result.png||]]</p> 58 58 59 59 Congratulations you have successfully imported your OpenAPI 3.0 specification. 60 60 ... ... @@ -65,24 +65,24 @@ 65 65 66 66 In all these cases you can manage your backend system by pressing the Manage button when you are editing the system (double click on the system in question) 67 67 68 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend-operations--system-edit-manage.png]]79 +<p align="center">[[image:crashcourse-api-gateway-configure-backend-operations--system-edit-manage.png||]]</p> 69 69 70 70 When you select the option Manage you will be presented with the following pop-up. The first time this pop-up will be empty. All other times it should contain at least one backend operation. 71 71 72 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend--manage-pop-up.png]]83 +<p align="center">[[image:crashcourse-api-gateway-configure-backend--manage-pop-up.png||]]</p> 73 73 74 74 Let us manually fill a simple GET call to retrieve all HTTP methods. So we start at the top left of the screen in the resource section and press New. 75 75 In the pop-up that follows we enter the resource path that is defined in the specification and press Save. The result will be as follows. 76 76 77 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend--manage-pop-up-resource-filled-in.png]]88 +<p align="center">[[image:crashcourse-api-gateway-configure-backend--manage-pop-up-resource-filled-in.png||]]</p> 78 78 79 79 The next step will be to add an operation via the option New under Operations in the middle of your screen. The result of that action will be something as follows. 80 80 81 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend--manage-pop-up-operation-filled-in.png]]92 +<p align="center">[[image:crashcourse-api-gateway-configure-backend--manage-pop-up-operation-filled-in.png||]]</p> 82 82 83 83 As there are no parameters in this case you have now successfully configured your first backend operation. When you close this screen you will see the results on system level 84 84 85 - [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-configure-backend--pop-up-result.png]]96 +<p align="center">[[image:crashcourse-api-gateway-configure-backend--pop-up-result.png||]]</p> 86 86 87 87 Now you can Save or add another operation to add to your specification. 88 88 ... ... @@ -91,6 +91,8 @@ 91 91 After you have correctly configured your backend operation you can start to think about how you can best expose the operations via the API Gateway. 92 92 In the next three microlearnings, we will delve deeper into the various components and also learn how you can quickly expose these backend operations in your API Gateway. 93 93 105 +===== Practice ===== 106 + 94 94 == 4. Assignment == 95 95 96 96 Manually configure a GET operation with the resource path /httpmethods in an API Gateway system. ... ... @@ -104,6 +104,8 @@ 104 104 * Manually configure based on other specification 105 105 * Other cases such as connecting to XML based systems will be discussed later on 106 106 120 + 121 + 107 107 == 6. Suggested Additional Readings == 108 108 109 109 If you are interested in this topic and want more information on it please read the help text provided by eMagiz. ... ... @@ -112,6 +112,10 @@ 112 112 113 113 This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. Disclaimer, you only see the eMagiz part but if you follow the above steps you are good to go! 114 114 115 - {{videoattachment="crashcourse-api-gateway-configure-backend-operation.mp4" reference="Main.Videos.Microlearning.WebHome"/}}130 +<iframe width="1280" height="720" src="../../vid/microlearning/crashcourse-api-gateway-configure-backend-operation.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> 116 116 117 -)))((({{toc/}}))){{/container}}{{/container}} 132 +</div> 133 +</div> 134 +</div> 135 + 136 +{{/html}}