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

Summary

Details

Page properties
Content
... ... @@ -10,9 +10,7 @@
10 10  == 2. Key concepts ==
11 11  
12 12  This microlearning centers around configuring a backend operation with the API Gateway solution of eMagiz.
13 -
14 14  With backend operation we mean: Any action that is available to be executed on an internal system that you want to make publicly available via the API Gateway.
15 -
16 16  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.
17 17  
18 18  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.
... ... @@ -19,7 +19,8 @@
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 frontend facing part), you first start with the backend operation you want to expose.
20 +When you look at the conceptual idea of the API Gateway, exposing backend operations via a centralized location to the outside world.
21 +It stands to reason that when you set up your API Gateway (i.e. the front-end facing part) you 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