Changes for page API Gateway - Introduction

Summary

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

Details

Page properties

Content

...	...	@@ -20,7 +20,7 @@
20	20
21	21	[[image:Main.Images.Microlearning.WebHome@releasenote-apigw-1.png]]
22	22
23		-**Key considerations when to use the API Gateway integration pattern**
	23	+Key considerations when to use the API Gateway integration pattern
24	24
25	25	Below is the list of considerations when to use the API Gateway.
26	26
...	...	@@ -45,11 +45,11 @@
45	45
46	46	[[image:Main.Images.Microlearning.WebHome@releasenote-apigw-2.png]]
47	47
48		-
49		-**1. Capture your API Gateway**
	48	+(% style="list-style-type: lower-roman" %)
	49	+1. Capture your API Gateway
50	50	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
51	51
52		-**2. Design an API Gateway**
	52	+2. Design an API Gateway
53	53	This is the central phase in the configuration of the API Gateway. The main idea is that the entire Gateway should be configured from the Design phase The front-end Gateway is the part where the external application user(s) can access the specific operation published and where the application user is authorized for. Specific operations can be configured and documented including parameters and response types. In the backend operation provider (an eMagiz system), the actual link to the backend operations can be registered including parameters. Frontend and backend operations can be connected at the moment an operation is exposed in the eMagiz API Gateway. Integrations or message types connected to a backend operation providing system are now able to have operations as child objects to get a better overview of what operations are available. Operations are still the integrations reported in the various parts of eMagiz * the message type becomes more of a group object.
54	54
55	55	* In case the backend service provider has an OpenAPI 3.0 specification available, this can be imported to have everything directly configured. Documentation of what OpenAPI statements are supported can be found in the help texts.
...	...	@@ -58,10 +58,10 @@
58	58	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.
59	59	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.
60	60
61		-**3. Create phase for the API gateway**
	61	+3. Create phase for the API gateway
62	62	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.
63		-
64		-**4. Deploy the API Gateway**
	63	+
	64	+4. Deploy the API Gateway
65	65	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:
66	66
67	67	* Gateway infra
...	...	@@ -70,11 +70,9 @@
70	70
71	71	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.
72	72
73		-**5. Manage phase specific to the API Gateway**
	73	+5. Manage phase specific to the API Gateway
74	74	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.
75	75
76		-
77		-
78	78	== 4. Assignment ==
79	79
80	80	Review the video below to ensure all concepts are clear