Wiki source code of What is Lifecycle Management

Last modified by Eva Torken on 2023/06/16 08:20
Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 In this microlearning, we will focus on the concepts of lifecycle management. This we do to introduce a concept we will build upon in further microlearnings.
3
4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5
6 == 1. Prerequisites ==
7
8 * Basic knowledge of the eMagiz platform
9 * Basic knowledge of the build number component within the eMagiz Platform
10
11 == 2. Key concepts ==
12
13 This microlearning centers around the concepts of lifecycle management.
14
15 By lifecycle management we mean: A way to stay in control of the integration landscape we are developing alongside our customers
16
17 Lifecycle management is characterized by:
18
19 * Tools to stay in control of your integration landscape.
20 * A way to keep up to date with the latest developments within the eMagiz portal.
21 * Everyone should be involved
22
23 == 3. What is Lifecycle Management ==
24
25 In this microlearning, we will focus on the concepts of lifecycle management. This we do to introduce a concept we will build upon in further microlearnings.
26
27 Lifecycle management is characterized by:
28
29 * Tools to stay in control of your integration landscape.
30 * A way to keep up to date with the latest developments within the eMagiz portal.
31 * Everyone should be involved
32
33 In this microlearning, we will look at the concepts of lifecycle management. In the remainder of this course and other courses on the topic, we will zoom in on parts of lifecycle management. From a conceptual standpoint, Life Cycle Management does not only entail deleting flows and information when a certain integration has reached its end of life but also keeping your integration landscape up to date with new features and developments as made by the eMagiz product development team. Life Cycle Management should be a conscious part of everyday life for everyone that plays a part within a team, project, or program. This way the team, and not the individual, will add the most value to the process.
34
35 === 3.1 Best practices ===
36
37 * Remove flows as part of completing your production deployment (after a grace period in which you confirm that everything works as expected). This to avoid a backlog of delete actions. A standard grace period would be two weeks. One could deviate from this standard if they have discussed this with the business owner.
38 * Remove flows only after written approval of the business owner of the process
39 * Remove flows from back to front. In other words, start in Manage and end in Capture.
40 * Regularly update your flows in Test and Acceptance so you can test new functionality released by eMagiz
41 * Updating flows to the latest build numbers can be done in two ways
42 ** Deploy with each production deployment a certain number of extra flows for which nothing has changed but the build number
43 ** Use a separate deployment moment to upgrade all flows, without functional changes, to the newest build number
44
45 == 4. Key takeaways ==
46
47 * Lifecycle management is characterized by:
48 ** Tools to stay in control of your integration landscape.
49 ** A way to keep up to date with the latest developments within the eMagiz portal.
50 ** Everyone should be involved
51
52 == 5. Suggested Additional Readings ==
53
54 If you are interested in this topic and want more information on the conceptual ideas behind it please read the following links:
55
56 * [[What is application lifecycle management>>https://www.redhat.com/en/topics/devops/what-is-application-lifecycle-management-alm||target="blank"]]
57 * [[Application lifecycle management explained>>https://tms-outsource.com/blog/posts/application-lifecycle-management/||target="blank"]]
58
59 )))((({{toc/}}))){{/container}}{{/container}}