Last modified by Erik Bakker on 2023/01/24 14:59

From version 14.1
edited by Erik Bakker
on 2022/08/08 12:58
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/08/08 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,14 +18,13 @@
18 18  
19 19  Below are the things to consider when implementing eMagiz for a new integration. These are things to discuss in the triangle business, eMagiz Developer and Architect.
20 20  
21 -
22 -1. Test
21 +* Data providers & consumers - The first thing to discuss who will provide data and who will consume the data. The properties of these systems are important to take into consideration such as whether these are online all the time, what development teams are involved, and the capability to push or pull.
23 23  
24 -2. Definitions - The exact definition of the data elements to be exchanged is to be retrieved so that an understanding is created around the format of the data packets as well as the specific mappings/transformation required. The definitions require a business perspective around the interpretation and use in the business process at hand.
23 +* Definitions - The exact definition of the data elements to be exchanged is to be retrieved so that an understanding is created around the format of the data packets as well as the specific mappings/transformation required. The definitions require a business perspective around the interpretation and use in the business process at hand.
25 25  
26 -3. Frequency & size - The size of data packets is relevant to ensure the right solution is created including the right architecture in terms of Cloud formation. Frequency is similarly important to ensure the right solution and architecture are created.
25 +* Frequency & size - The size of data packets is relevant to ensure the right solution is created including the right architecture in terms of Cloud formation. Frequency is similarly important to ensure the right solution and architecture are created.
27 27  
28 -4. Connectivity - What are the involved connectivity constraints involved? Consider items such as VPNs into the client infrastructure, security considerations, involved parties, and their maturity level to easily connect or provide details.
27 +* Connectivity - What are the involved connectivity constraints involved? Consider items such as VPNs into the client infrastructure, security considerations, involved parties, and their maturity level to easily connect or provide details.
29 29  
30 30  == 4. Assignment ==
31 31