Skip to Content
Last modified by Danniar Firdausy on 2024/09/02 16:51
From version 12.1
edited by eMagiz
on 2022/06/13 10:55
Change comment: There is no comment for this version
To version 11.1
edited by eMagiz
on 2022/06/13 10:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,17 +55,20 @@
55 55  
56 56  For transformations, the request & reply system messages can be created visually like in the platform. The same goes for the gateway model that can be created visually as well. There is no concept of a CDM message as in the Messaging pattern. The transformation & Enrichment can take place in the standard mapping tooling available. So the concepts of a Request message, Response message, Mapping are available via right-click options in the platform.
57 57  Other transformations to reach SOAP/XML-based backend operations are also possible by selecting what format the operation has in the backend operation. This will then automatically ensure the transformation considers the JSON to XML transformation. For other protocol transformations, the XML variant can be used and custom influenced in the Create phase.
58 - * Create phase for the API gateway
58 +
59 +3. Create phase for the API gateway
59 59  In the Create phase, integrations with backend operations can be added to the Create model as usual. The result is that the specific components are created automatically. Via the Create * API Gateway section, the components are listed for now. In the upcoming releases, the Create phase will be updated to embed the API Gateway components in the complete view.
60 - * Deploy the API Gateway
61 +
62 +4. Deploy the API Gateway
61 61  In the Deploy Phase the application users can be registered, the API key is generated automatically, and access to the specific backend operations where that application user should have access granted. Furthermore, the components of the API Gateway are the following:
62 62  
63 -** Gateway infra
64 -** All entry (later replaced with single entries per operation)
65 -** Exit gate (contains a connection to backend provider)
65 +* Gateway infra
66 +* All entry (later replaced with single entries per operation)
67 +* Exit gate (contains a connection to backend provider)
66 66  
67 67  These components can be made part of the Release and Deployment plans. The Deploy Architecture will contain the Cloud architecture to be deployed and can be applied with the Design Architecture. The API Gateway runs in the eMagiz Cloud exclusively for now.
68 - * Manage phase specific to the API Gateway
70 +
71 +5. Manage phase specific to the API Gateway
69 69  In this phase, everything works as usual. Error messages of eMagiz will be routed in the Error messages, and the queue statistics are available as a separate entry in the left-hand menu.
70 70  
71 71  == 4. Assignment ==