Changes for page Exercise - Complete data model API gateway design
Last modified by Eva Torken on 2023/05/11 13:07
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - ExerciseComplete1 +crashcourse-apigw-exercises-datamodelling - 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 isCrash 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,19 @@ 10 10 11 11 == 2. Exercise == 12 12 13 -Below the exercises forthis partofthecrashcourse.13 +Below the various exercises to learn more 14 14 15 -=== 2.1 Data modeling OMS Carrier === 15 +=== 2.1 Data modelling OMS Carrier === 16 16 17 17 Please implement the GET operation for Carrier taking the following into account: 18 - 19 -* Import both definition to create the response definitions for the GET operation 20 -* Ensure the proper reponse mapping is created 21 21 22 -=== 2.1 Data modeling OMS Order === 19 +* Gateway reponse message: click here to download 20 +* System response message: click here to download 21 +* No path or query parameters are required 22 +* The endpoint to retrieve the Carriers: https://order-tracking.p.rapidapi.com/carriers 23 +* This endpoint is an REST/JSON based endpoint 24 + 23 23 24 -Please implement the POSt operation for Order taking the following into account: 25 - 26 -* Import both definition to create the request definitions for the POST 27 -* Ensure the proper request mapping is created 28 -* Assumption is that the gateway and system messages are identical 29 29 30 30 == 3. Solution == 31 31