Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 258.1
edited by Carlijn Kokkeler
on 2023/11/21 12:35
Change comment: There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +189 - Private Eye
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,80 +1,82 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
7 7  
8 -{{warning}}
9 -Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 -{{/warning}}
7 +== **Private Store** ==
8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
11 11  
12 -== **Quicker Deployment Plan** ==
10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
13 13  
14 -We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
12 +== **3rd generation runtime bolstering** ==
15 15  
16 -== **Next Generation Architecture Default** ==
14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
17 17  
18 -With this release, the next generation architecture will become the default. New models will use this generation as default.
16 +//__SOAP and REST web services migration, including splitting them__//
17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
19 +//__Changing SSL settings for 3rd generation runtime models works__//
20 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
23 23  
24 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
25 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
27 27  
28 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
29 29  
30 -== **Feedback Items** ==
33 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
31 31  
32 -//__Unused properties overview__//
33 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
36 +//__Added "Reset" functionality__//
37 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
34 34  
35 -* Not used by any runtime that is in the Create phase release.
36 -* Not required by a flow that is in the Create phase release.
37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
39 +== **Feedback items ** ==
38 38  
39 -//__Queue explorer milliseconds__//
40 -The queue browser now displays milliseconds in the timestamps.
41 +We have also solved other feedback items besides the flow designer's critical updates.
41 41  
42 -//__Cancel and next buttons order__//
43 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
43 +//__Improved naming convention on Store related pages__//
44 +We have improved various display names using the merge functionality within our store offering.
44 44  
45 -//__Unused images__//
46 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
46 +//__Update security protocols for our internal architecture__//
47 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
47 47  
48 -//__Carwash logging__//
49 -A new logging feature enabling us to make better choices in encryption standards will be released.
49 +//__Improved read-only description for "if exists" constructions in Transformations__//
50 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
50 50  
51 -//__Static alerts queue consumers__//
52 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
53 53  
54 -== **Bug Fixes** ==
53 +== **Bug fixes ** ==
55 55  
56 -//__Flow Designer connection line__//
57 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
55 +//__Decent validation feedback when not filling in the property value__//
56 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
58 58  
59 -//__Portal for migrated models__//
60 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
58 +//__Incorrect resource locations__//
59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
61 61  
62 -//__Error channel inbounds__//
63 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
61 +//__Apply to environment in User Management performance improvement__//
62 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
64 64  
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
68 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
70 70  
71 71  == **Key takeaways** ==
72 72  
73 -Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
75 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
74 74  
75 75  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 76  * If you have feedback or ideas for us, talk to the Platypus
77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 78  * Clear your browser cache (Ctrl + Shift + Del)
79 79  * Check out the release notes [here]
80 80  * Start thinking about how the license tracker can aid your development
... ... @@ -87,12 +87,6 @@
87 87  {{info}}
88 88  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89 89  
90 -~*~* Indicates a next-generation-architecture only feature.
91 -{{/info}}
92 -)))
93 -
94 -(((
95 -{{toc/}}
96 -)))
92 +~*~* Indicates a GEN3-only feature.
93 +{{/info}})))((({{toc/}}))){{/container}}
97 97  {{/container}}
98 -{{/container}}