Skip to Content

Changes for page Setting up exit gate

Last modified by Danniar Firdausy on 2024/09/04 16:15
From version 23.23
edited by Danniar Firdausy
on 2024/08/21 11:42
Change comment: There is no comment for this version
To version 26.1
edited by Danniar Firdausy
on 2024/09/04 16:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,11 +10,12 @@
10 10  == 2. Key concepts ==
11 11  
12 12  This microlearning centers around setting up the exit gate for the API Gateway solution of eMagiz.
13 -With exit gate, we mean: The piece of functionality that connects to the backend operation to execute the action on behalf of the client that is calling the API
14 -With API Gateway we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process
15 15  
14 +* With exit gate, we mean: The piece of functionality that connects to the backend operation to execute the action on behalf of the client that is calling the API
15 +* With API Gateway we mean: A collection of RESTful API operations that can be published to the outside world to give them access to applications that are linked to your business process
16 +
16 16  The exit gate is created by eMagiz based on the configuration in Design. In passthrough cases, you only need to add authentication.
17 -In cases of transformation, you need to specify the outbound component (i.e. HTTP, Web service, JDBC, SFTP, etc.) and the authentication.
18 +In cases of transformation, you need to specify the outbound component (e.g., HTTP, Web service, JDBC, SFTP, etc.) and the authentication.
18 18  
19 19  == 3. Setting up exit gate ==
20 20  
... ... @@ -40,12 +40,12 @@
40 40  
41 41  == 4. Key takeaways ==
42 42  
43 -* Each backend operation has a specific exit gate that will
44 - * Handle all incoming traffic destined for that backend operation
45 - * Connect to the backend operation
46 - * Send response back to the client that is calling the API
47 -* eMagiz will automatically build the biggest portion of the exit gate for you
48 -* Some manual changes are necessary
44 +* Each backend operation has a specific exit gate that:
45 +** Handles all incoming traffic destined for that backend operation
46 +** Connects to the backend operation to execute the requested action
47 +** Sends response back to the client that made the API call
48 +* eMagiz will automatically handle most of the setup for you, including the generation of the exit gate configuration.
49 +* Depending on your use cases, some manual changes might be necessary
49 49  
50 50  == 5. Suggested Additional Readings ==
51 51  
... ... @@ -63,8 +63,6 @@
63 63  * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
64 64  ** [[Testing API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing API Gateway.WebHome||target="blank"]]
65 65  *** [[Testing API Gateway (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing API Gateway.intermediate-testing-emagiz-api-gateway-testing-api-gateway||target="blank"]]
66 -** [[Release Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.WebHome||target="blank"]]
67 -*** [[Container management (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.intermediate-release-management-assigning-flows-2-containers.WebHome||target="blank"]]
68 68  * [[Advanced Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
69 69  ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
70 70  *** [[API Gateway Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-apigw-architecture.WebHome||target="blank"]]