Skip to Content

Changes for page 198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 104.1
edited by Erik Bakker
on 2023/04/13 14:30
Change comment: There is no comment for this version
To version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +198 - Great Migration
Content
... ... @@ -2,98 +2,46 @@
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 focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
6 6  
7 -== **Release properties** ==**
7 +== **3rd generation improvements and bug fixes** ==
8 8  
9 -With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
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 10  
11 -As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
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}}
12 12  
13 -{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
14 +//__Removed certain dependencies between Deploy Architecture and Releases__//
15 +In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
14 14  
15 -{{info}}The following considerations need to be taken into account when using this functionality:
16 -* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
17 -* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
18 -* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
19 -* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
20 -* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
21 -* There is a maximum of twenty-six ‘property’ releases. (twenty-six letters of the alphabet)
22 -* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
17 +//__Improved validation errors on invalid configuration of HTTP outbound components__//
18 +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.
23 23  
24 -== **API improvements** ==
20 +//__Improved migration behavior__//
21 +This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
25 25  
26 -//__Improved auto-generated error handling__//
27 -When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
23 +//__Improved auto-healing when running in a hybrid situation__//
24 +In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
28 28  
29 -//__Switch default message format__//
30 -We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
26 +//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
27 +To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
31 31  
32 -//__Re-using elements in gateway message__//
33 -This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
29 +{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
34 34  
35 -//__Improved naming of API operations when adding integrations to Create__//
36 -Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
37 -
38 -== **3rd generation improvements** ==
39 -
40 -//__Update of the static alerting engine__//
41 -In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
42 -
43 -//__Add "Data pipeline" functionality__//
44 -This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
45 -
46 -//__Fix related to the debugger__//
47 -This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
48 -
49 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
50 -
51 -//__Improved migration process__//
52 -This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
53 -
54 -//__Deployment plan change__//
55 -In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
56 -
57 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
58 -
59 59  == **Feedback items ** ==
60 60  
61 -//__License Tracker improvements__//
62 -With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
33 +//__Make sure the message format can be viewed without "Start editing"__//
34 +With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
63 63  
64 -//__Ability to view the message definition for a topic__//
65 -Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
36 +//__Various styling improvements in the flow testing functionality__//
37 +Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
66 66  
67 -//__Restricted access for uploading custom certificates to endpoints__//
68 -To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
69 -
70 -== **Bug fixes ** ==
71 -
72 -//__Improved deletion behavior for enumerations__//
73 -To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
74 -
75 -//__Prevent "async" api operations__//
76 -With this release, we have removed the ability to select the "async" option when the default message format is API Management.
77 -
78 -//__Importing a response definition broke the request definition__//
79 -Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
80 -
81 -//__Removing a flow does not update the API "all-entry" anymore__//
82 -When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
83 -
84 -//__Stop deployment plan when a property is missing__//
85 -Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
86 -
87 -//__Cap stack trace of error messages and log entries__//
88 -To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
89 -
90 90  == **Fancy Forum Answers** ==
91 91  
92 92  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:
93 93  
94 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
95 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
96 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
43 +* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
44 +* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
97 97  
98 98  == **Key takeaways** ==
99 99