Skip to Content
Last modified by Eva Torken on 2023/05/11 13:07
From version 15.1
edited by Eva Torken
on 2023/05/11 10:59
Change comment: There is no comment for this version
To version 8.1
edited by eMagiz
on 2023/03/31 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Exercise - Complete data model API gateway design
1 +Exercise - Complete data modeling
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.etorken
1 +XWiki.eMagiz
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 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.
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 the Crash Course Platform 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,22 +10,24 @@
10 10  
11 11  == 2. Exercise ==
12 12  
13 -Below the exercises for this part of the crash course.
13 +Below the various exercises to learn more
14 14  
15 15  === 2.1 Data modeling OMS Carrier ===
16 16  
17 17  Please implement the GET operation for Carrier taking the following into account:
18 18  
19 -* Import both definitions to create the response definitions for the GET operation
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 POST operation for Order taking the following into account:
24 +Please implement the POSt operation for Order taking the following into account:
25 25  
26 -* Check the provided XSD definitions for the gateway request and response message and alter the API Gateway data model accordingly.
26 +* Import both definition to create the request definitions for the POST
27 +* Ensure the proper request mapping is created
27 27  * Assumption is that the gateway and system messages are identical
28 -
29 +
29 29  == 3. Solution ==
30 30  
32 +
31 31  )))((({{toc/}}))){{/container}}{{/container}}