Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 320.1
edited by Carlijn Kokkeler
on 2023/12/21 14:51
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 -211 - Log Luminary
1 +189 - Private Eye
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,84 +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!**
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 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
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 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
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}}
14 14  
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
12 +== **3rd generation runtime bolstering** ==
17 17  
18 -== **Overviews** ==
19 -//__Runtime overview__//
20 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
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.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
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.
23 23  
24 -//__Missing properties overview__//
25 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
28 28  
29 -//__Runtime restart or redeploy overview__//
30 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
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}}
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
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.
33 33  
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.
34 34  
35 -== **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.
36 36  
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.
37 37  
38 -//__Breaking changes pop-up__//
39 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
39 +== **Feedback items ** ==
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
41 +We have also solved other feedback items besides the flow designer's critical updates.
42 42  
43 -//__External recipients emailaddress__//
44 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
43 +//__Improved naming convention on Store related pages__//
44 +We have improved various display names using the merge functionality within our store offering.
45 45  
46 -//__Broker queue metrics dashboards__//
47 -It is now possible to select the MQTT broker in the queue metrics dashboards.
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.
48 48  
49 -//__Runtime image version__//
50 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
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.
51 51  
52 52  
53 -== **Bug Fixes** ==
53 +== **Bug fixes ** ==
54 54  
55 -//__Message throughput__//
56 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
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.
57 57  
58 -//__Cloud template upgrade unjust rollback__//
59 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
58 +//__Incorrect resource locations__//
59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
60 60  
61 -//__Next generation block__//
62 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
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.
63 63  
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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:
67 67  
68 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
69 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
70 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
71 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
72 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||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"]]
73 73  
74 -
75 75  == **Key takeaways** ==
76 76  
77 -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:
78 78  
79 79  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
80 80  * If you have feedback or ideas for us, talk to the Platypus
81 -* 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.
82 82  * Clear your browser cache (Ctrl + Shift + Del)
83 83  * Check out the release notes [here]
84 84  * Start thinking about how the license tracker can aid your development
... ... @@ -91,12 +91,6 @@
91 91  {{info}}
92 92  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
93 93  
94 -~*~* Indicates a next-generation-architecture only feature.
95 -{{/info}}
96 -)))
97 -
98 -(((
99 -{{toc/}}
100 -)))
92 +~*~* Indicates a GEN3-only feature.
93 +{{/info}})))((({{toc/}}))){{/container}}
101 101  {{/container}}
102 -{{/container}}