Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 60.1
edited by Erik Bakker
on 2023/01/18 09:30
Change comment: There is no comment for this version
To version 258.1
edited by Carlijn Kokkeler
on 2023/11/21 12:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,118 +1,80 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
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.
6 6  
7 -== **Queue Browser** ==
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}}
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
12 +== **Quicker Deployment Plan** ==
10 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
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 12  
13 -To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
16 +== **Next Generation Architecture Default** ==
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
18 +With this release, the next generation architecture will become the default. New models will use this generation as default.
16 16  
17 -After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
18 18  
19 -* Delete the message from the queue (Explore option)
20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21 -* Clear message from the wiretap queue (Wiretap option)
22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23 -* Refresh messages list (both options)
24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 -* Save as test message
26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27 -* Download
28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
22 +== **Cloud Template R11 Docker - Single Lane** ==
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
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"]].
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
26 +== **Cloud Template R13 Docker - Double Lane** ==
33 33  
34 -== **Message Redelivery ** ==
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"]].
35 35  
36 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
30 +== **Feedback Items** ==
37 37  
38 -Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
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:
39 39  
40 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
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.
41 41  
42 -On top of that we have added some additional functionality.
39 +//__Queue explorer milliseconds__//
40 +The queue browser now displays milliseconds in the timestamps.
43 43  
44 -* Search option
45 - ** Original queue name
46 - ** Original message ID (which can be found as a header called jms_messageid in the error message view)
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.
47 47  
48 -== **3rd generation runtime bolstering** ==
45 +//__Unused images__//
46 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
49 49  
50 -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.
48 +//__Carwash logging__//
49 +A new logging feature enabling us to make better choices in encryption standards will be released.
51 51  
52 -//__SOAP and REST web services migration, including splitting them__//
53 -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.
51 +//__Static alerts queue consumers__//
52 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
54 54  
55 -//__Changing SSL settings for 3rd generation runtime models works__//
56 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
54 +== **Bug Fixes** ==
57 57  
58 -//__Improved migration for JMS flows__//
59 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
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.
60 60  
61 -{{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}}
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.
62 62  
63 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
64 -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.
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.
65 65  
66 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
67 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
68 -
69 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
70 -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.
71 -
72 -//__Added "Reset" functionality__//
73 -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.
74 -
75 -== **Feedback items ** ==
76 -
77 -We have also solved other feedback items besides the flow designer's critical updates.
78 -
79 -//__Improved naming convention on Store related pages__//
80 -We have improved various display names using the merge functionality within our store offering.
81 -
82 -//__Update security protocols for our internal architecture__//
83 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
84 -
85 -//__Improved read-only description for "if exists" constructions in Transformations__//
86 -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.
87 -
88 -
89 -== **Bug fixes ** ==
90 -
91 -//__Decent validation feedback when not filling in the property value__//
92 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
93 -
94 -//__Incorrect resource locations__//
95 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
96 -
97 -//__Apply to environment in User Management performance improvement__//
98 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
99 -
100 100  == **Fancy Forum Answers** ==
101 101  
102 102  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:
103 103  
104 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
105 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
106 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
107 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
69 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
108 108  
109 109  == **Key takeaways** ==
110 110  
111 -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:
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:
112 112  
113 113  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
114 114  * If you have feedback or ideas for us, talk to the Platypus
115 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
116 116  * Clear your browser cache (Ctrl + Shift + Del)
117 117  * Check out the release notes [here]
118 118  * Start thinking about how the license tracker can aid your development
... ... @@ -125,6 +125,12 @@
125 125  {{info}}
126 126  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
127 127  
128 -~*~* Indicates a GEN3-only feature.
129 -{{/info}})))((({{toc/}}))){{/container}}
90 +~*~* Indicates a next-generation-architecture only feature.
91 +{{/info}}
92 +)))
93 +
94 +(((
95 +{{toc/}}
96 +)))
130 130  {{/container}}
98 +{{/container}}