Skip to Content
Last modified by Erik Bakker on 2024/08/23 11:32
From version 32.3
edited by Danniar Firdausy
on 2024/08/21 11:03
Change comment: There is no comment for this version
To version 33.1
edited by Danniar Firdausy
on 2024/08/21 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,7 +19,7 @@
19 19  
20 20  == 3. Configure a backend operation ==
21 21  
22 -The core concept of an API Gateway is to serve as an interface that centralizes and exposes backend operations to the outside world. It is then logical that, when you set up your API Gateway (i.e., the front-end facing part), you first start with the backend operation you want to expose.
22 +The core concept of an API Gateway is to serve as an interface that centralizes and exposes backend operations to the outside world. It is then logical that, when you set up your API Gateway (i.e., the frontend facing part), you first start with the backend operation you want to expose.
23 23  
24 24  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:
25 25  
... ... @@ -27,7 +27,7 @@
27 27  
28 28  In here you need to fill in the technical name, just as with any other system. Furthermore, you have two decisions to make:
29 29  
30 -* Does the system talk JSON or XML (i.e. which message format)
30 +* Does the system talk JSON or XML (i.e., which message format)
31 31  * Can you specify the backend operations either via an import of the OpenAPI 3.0 spec or via a manual action
32 32  
33 33  If the answer to the above decisions is JSON and yes the default settings are correct you should continue to either import the OpenAPI 3.0 spec or manually configure at least one backend operation.