Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version
To version 137.1
edited by Erik Bakker
on 2023/08/01 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +202 - New Equilibrium
Content
... ... @@ -2,39 +2,65 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 -== **3rd generation improvements and bug fixes** ==
7 +== **Release Properties** ==
8 +As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
10 +* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 +* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12 +* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13 +* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
11 11  
12 -{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
15 +{{info}}For more information, please check out the following microlearnings:
13 13  
14 -//__Improved efficiency in deploying a release__//
15 -This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
17 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 +* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
16 16  
17 -//__Removed specific dependencies between Deploy Architecture and Releases__//
18 -In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
19 19  
20 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
24 +== ** Manage - Next generation graphs improvements ** ==
25 +As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
22 22  
23 -//__Improved migration behavior__//
24 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25 -A smoother migration of your JMS (and backup JMS) process.
26 -Shortening of names that otherwise would be too long, additional feedback given to the user.
27 -Feedback when the migration process is finished.
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
28 28  
29 -//__Additional checks when deploying__//
30 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
29 +== **Feedback Items** ==
31 31  
31 +//__Improved editability when testing in eMagiz without Edit rights in Create__//
32 +Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
33 +
34 +//__Improved auditability on Deploy Architecture__//
35 +To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
36 +
37 +//__Test your own exported store content__//
38 +We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
39 +
40 +{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals. fundamental-magic-store.WebHome||target="blank"]]{{/info}}
41 +
42 +//__Improved comparison of flows in the releases overview__//
43 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
44 +
45 +== **Bug Fixes** ==
46 +
47 +//__Improved validation on XPath header enricher__//
48 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
49 +
50 +//__Cancel behavior on flow testing property overview fixed__//
51 +We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
52 +
53 +//__Cancel behavior on flow fragment level when exporting store content__//
54 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
55 +
56 +//__Adding numbers on containers in Deploy Architecture__//
57 +With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
58 +
32 32  == **Fancy Forum Answers** ==
33 33  
34 34  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
35 35  
36 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
38 38  
39 39  == **Key takeaways** ==
40 40