Skip to Content

Changes for page Discovery

Last modified by Danniar Firdausy on 2024/08/20 15:09
From version 22.1
edited by Carlijn Kokkeler
on 2023/09/22 13:32
Change comment: There is no comment for this version
To version 21.1
edited by Carlijn Kokkeler
on 2023/09/08 14:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,11 +33,6 @@
33 33  * What should each system be called?
34 34  * What should be the default integration pattern for each system?
35 35  
36 -In case you would like to add systems to your existing integration landscape, you need to ask yourself several questions as well:
37 -* How does this system fit into my existing landscape?
38 -* Does this system have similarities with existing systems?
39 -* How should this system interact with existing systems?
40 -
41 41  Some more documentation may be relevant, and can be filled out easily while configuring a system. More information on how to configure a system can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]] microlearning.
42 42  
43 43  When you want to create an integration, you need to ask yourself the following questions:
... ... @@ -50,7 +50,7 @@
50 50  
51 51  == 5. Design ==
52 52  
53 -After the Capture phase, you can proceed to the Design phase. In the Design phase, the system message definitions are created, and the transformation mappings are drawn. A message definition is a visual representation of how the elements are related to each other, whether they are mandatory and the data types they have that can be used in the message mapping. The client infrastructure is also determined in the Design phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
48 +After the Capture phase, you can proceed to the Design phase. In the Design phase, the system message definitions are created, and the transformation mappings are drawn. A message definition is a visual representation of how the elements are related to each other, whether they are mandatory and the data types they have that can be used in the message mapping. The client infrastructure is also determined in the Capture phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
54 54  * What should my data model look like?
55 55  * What message definitions are needed?
56 56  * Which message formats are required?
... ... @@ -58,11 +58,6 @@
58 58  * What should the architecture (incl. instances, machine sizes, etc.) be like?
59 59  * What metadata needs to be stored?
60 60  
61 -In case you would like to expand your existing integration landscape, you need to ask yourself several questions as well:
62 -* How does my addition to the data model fit into the current data model?
63 -* Which entities in the current data model have overlap with the entities I wish to add?
64 -* Are there any overlapping system messages if I add this system message?
65 -
66 66  Several more questions may be relevant. Documentation on how to develop in the Design phase can be found in the [[Platform Crash Courses>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.||target="blank"]].
67 67  
68 68  == 6. Key takeaways ==