Changes for page API Gateway - Introduction

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,9 +1,16 @@
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	+
2	2	= API Gateway * Introduction =
3	3
4	4	In this microlearning, we will introduce the key concepts of the API Gateway as eMagiz provides this capability.
5	5
6		-Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
	13	+Should you have any questions, please contact academy@emagiz.com.
7	7
8	8	* Last update: February 21st, 2021
9	9	* Required reading time: 5 minutes
...	...	@@ -20,7 +20,7 @@
20	20	A typical landscape could look like this.
21	21	The API Gateway is located in the secured eMagiz Cloud and provides the ability to access it from external application users. A client of ACME Ltd. could be sending in Sales Orders directly from their systems (incoming integration 1). The incoming Sales order is then delivered back to the back office system of ACME and could send a response back with successful delivery. Inside the ACME Ltd. organization, various development teams are processing the sales order further. One of the things that need to take place is to perform an external credit check of that specific client (integration 2). Service C might be responsible for that and is processing the request/response synchronously.
22	22
23		-[[image:Main.Images.Microlearning.WebHome@releasenote-apigw-1.png]]
	30	+<p align="center">[[image:releasenote-apigw-1.png||]]</p>
24	24
25	25	**Key considerations when to use the API Gateway integration pattern**
26	26
...	...	@@ -45,7 +45,7 @@
45	45
46	46	The API Gateway is fully embedded into the eMagiz Low-code Enterprise iPaaS so that users have a similar user experience when configuring the API Gateway, a Messaging integration, or an Event Stream. All the platform features in the different ILM phases can take into account the API Gateway configuration. What is important to realize is that the primary focus of the API Gateway configuration is to allow all configuration work to take place in the Design phase. You will find out that most or often all the Create models are automatically generated. Only in specific cases where specific customization is required, the created objects can be modified. Newly created Designs could result in the rework of the customization in the Create object.
47	47
48		-[[image:Main.Images.Microlearning.WebHome@releasenote-apigw-2.png]]
	55	+<p align="center">[[image:releasenote-apigw-2.png||]]</p>
49	49
50	50	**1. Capture your API Gateway**
51	51	In this phase, the regular operations or message types can be captured with all the necessary information of that specific operation. At the system level, you can indicate that the system acts as a backend service provider that has certain API's available
...	...	@@ -74,8 +74,8 @@
74	74	**5. Manage phase specific to the API Gateway**
75	75	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.
76	76
	84	+===== Practice =====
77	77
78		-
79	79	== 4. Assignment ==
80	80
81	81	Review the video below to ensure all concepts are clear
...	...	@@ -97,6 +97,10 @@
97	97
98	98	This video provides an introduction to the API Gateway of eMagiz
99	99
100		-<iframe width="1907" height="1073" src="https://www.youtube.com/embed/8TBXq9SVdL8" reference="Main.Videos.Microlearning.WebHome"/}}
	107	+<iframe width="1907" height="1073" src="https://www.youtube.com/embed/8TBXq9SVdL8" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
101	101
102		-)))((({{toc/}}))){{/container}}{{/container}}
	109	+</div>
	110	+</div>
	111	+</div>
	112	+
	113	+{{/html}}