Changes for page Exercise - Complete data model API gateway design
Last modified by Eva Torken on 2023/05/11 13:07
From version 7.1
edited by eMagiz
on 2023/03/31 15:34
on 2023/03/31 15:34
Change comment:
There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/05/10 13:13
on 2023/05/10 13:13
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - crashcourse-apigw-exercises-datamodelling1 +Exercise - Complete data model API gateway design - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to th eCrash CoursePlatform Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.2 +With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to this Crash Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it. 3 3 4 4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 ... ... @@ -10,7 +10,7 @@ 10 10 11 11 == 2. Exercise == 12 12 13 -Below the variousexercises tolearnmore13 +Below the exercises for this part of the crash course. 14 14 15 15 === 2.1 Data modeling OMS Carrier === 16 16 ... ... @@ -18,16 +18,14 @@ 18 18 19 19 * Import both definition to create the response definitions for the GET operation 20 20 * Ensure the proper reponse mapping is created 21 - 21 + 22 22 === 2.1 Data modeling OMS Order === 23 23 24 -Please implement the POS toperation for Order taking the following into account:24 +Please implement the POST operation for Order taking the following into account: 25 25 26 -* Import both definition to create the request definitions for the POST 27 -* Ensure the proper request mapping is created 26 +* Check the provided XSD definitions for the gateway request and response message and alter the API Gateway data model accordingly. 28 28 * Assumption is that the gateway and system messages are identical 29 - 28 + 30 30 == 3. Solution == 31 31 32 - 33 33 )))((({{toc/}}))){{/container}}{{/container}}