Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 16.1
edited by eMagiz
on 2022/10/12 12:51
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get ready
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,51 +2,81 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
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 -==**Store additions**==
8 -We have released several Store items that can be used in the Design Store and which include complete data models and transformations. See the list below of the components that have these.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 3.png]]
7 +== **3rd generation runtime bolstering** ==
11 11  
12 -==**Audit trail User Management**==
13 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
14 -
15 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
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.
16 16  
17 -==**Next Generation Monitoring & Alerting engine**==
18 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
19 -
20 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
21 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
22 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
23 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
24 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
25 -
26 -
27 -=== **Improvements** ===
28 -
29 -* Performance Deployment plan
30 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
31 -
32 -* Flow Designer updates
33 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
34 -
35 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
36 -
37 -* Store
38 -We have fixed several smaller Store import issues to improve the user experience.
39 -
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 +
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 +
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
19 +
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.
22 +
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.
25 +
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.
28 +
29 +== **Exportable Release Audit** ~* ==
30 +
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.
32 +
33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
34 +
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Changes made on definition and transformation level are **not** restored
37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40 +
41 +== **Feedback items ** ==
42 +
43 +We have also solved other feedback items besides the flow designer's critical updates.
44 +
45 +//__Data Sink Refactor__//
46 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately.
47 +
48 +//__Improved naming convention on Store related pages__//
49 +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.
50 +
51 +//__Press "Enter" to search on multiple pages__//
52 +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.
53 +
54 +* Deploy → Deployment Plan
55 +* Deploy → Properties → History
56 +* Deploy → User Management → Roles
57 +* Manage → Error Messages → Error Messages
58 +* Manage → Error Messages → Flows with Error Messages
59 +* Manage → Error Messages → Exceptions of Error Messages
60 +* Manage → Log Entries
61 +* Manage → Alerts
62 +* Manage → Triggers
63 +* Manage → Tags – Cant find (only Gen2)
64 +* Manage → Notifications
65 +* Manage → Notification Settings
66 +* Manage → Data Usage → History
67 +* Manage → Code mappings → All tabs
68 +
40 40  == **Fancy Forum Answers** ==
41 41  
42 -As always, a gentle reminder to all 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:
71 +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:
43 43  
44 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
45 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
46 46  
47 47  == **Key takeaways** ==
48 48  
49 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
79 +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:
50 50  
51 51  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
52 52  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -57,12 +57,11 @@
57 57  * Start thinking about major, minor, and patch
58 58  * Upgrade to the latest build number
59 59  * Keep making great integrations
60 -* Check out the new documentation portal.
61 61  
62 62  Let's stay in touch and till next time!
63 63  
64 64  {{info}}
65 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  
67 67  ~*~* Indicates a GEN3-only feature.
68 68  {{/info}})))((({{toc/}}))){{/container}}