Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 124.1
edited by Erik Bakker
on 2023/06/19 14:21
Change comment: There is no comment for this version
To version 52.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +188 - Close Encounters
Content
... ... @@ -2,52 +2,73 @@
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 a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **Next generation improvements and bug fixes** ==
7 +== **3rd generation runtime bolstering** ==
8 8  
9 -//__Enhanced right-hand view within Deployment Plan context__//
10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
9 +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.
11 11  
12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
13 13  
14 -//__Improved timeout settings when deploying__//
15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
16 16  
17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
18 18  
19 -//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
21 21  
22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
23 23  
24 -//__Improved loading speed of Manage Dashboard__//
25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
26 26  
27 -== **Store Improvements** ==
29 +== **Exportable Release Audit** ~* ==
28 28  
29 -//__Importing in Design is improved__//
30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
31 31  
32 -== **Bug Fixes** ==
33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
33 33  
34 -//__Deprecated reminder pop-up removed__//
35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Works **only** for releases that are promoted and made active on **Production**
37 + * You will **only** see changes made during the **current** calendar year
38 + * On the first of April all objects of the **last** calendar year will be **removed**{{/warning}}
36 36  
37 -//__Improved selection area in Flow Designer__//
38 -When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
40 +== **Feedback items ** ==
39 39  
40 -//__Improved Kafka settings_//
41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
42 +We have also solved other feedback items besides the flow designer's critical updates.
42 42  
43 -{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
44 +//__Improved naming convention on Store related pages__//
45 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
44 44  
47 +//__Press "Enter" to search on multiple pages__//
48 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
49 +
50 +* Deploy → Deployment Plan
51 +* Deploy → Properties → History
52 +* Deploy → User Management → Roles
53 +* Manage → Error Messages → Error Messages
54 +* Manage → Error Messages → Flows with Error Messages
55 +* Manage → Error Messages → Exceptions of Error Messages
56 +* Manage → Log Entries
57 +* Manage → Alerts
58 +* Manage → Triggers
59 +* Manage → Tags – Cant find (only Gen2)
60 +* Manage → Notifications
61 +* Manage → Notification Settings
62 +* Manage → Data Usage → History
63 +* Manage → Code mappings → All tabs
64 +
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
50 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
69 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
70 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
71 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
51 51  
52 52  == **Key takeaways** ==
53 53