Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/04/18 13:04
From version 430.1
edited by Erik Bakker
on 2024/03/12 14:43
Change comment: There is no comment for this version
To version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,136 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
6 +**Hi there, eMagiz developers!** This release...
7 7  
8 -== **Announcement - TLS versions deprecated** ==
9 -
10 -As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
11 -
12 -* TLSv1.0
13 -* TLSv1.1
14 -
15 -{{info}}Should you have concerns whether any of the external systems called from your eMagiz model only support the older TLS versions we suggest checking this via either [[OpenSSL>>attach:Main.Images.Release Blog.WebHome@openssl.pdf||target="blank"]] or by calling the endpoint via SOAP UI (version 5.7.0 or higher). {{/info}}
16 -
17 -== **Announcement - Spring 6** ==
18 -
19 -We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture in our release that will be released on April 11th, 2024. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
20 -
21 -{{warning}}
22 -* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting.
23 -* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
24 -** Simple job launcher (data pipelines)
25 -** Job explorer (data pipelines)
26 -** HTTP components message sender (support object)
27 -** Web service outbound gateway (with a 'message sender' attribute specified)
28 -** SFTP session factory (support object)
29 -** API gateways with OAuth2 as security mechanism.
30 -* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
31 -** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
32 -* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
33 -
34 -== **Infra flow selection** ==
35 -
36 -This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually. This means that the platform and/or system will color light blue to signify this change in the infra version.
37 -
38 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
39 -
40 -In edit mode, you can select a new version via the right-click option, which you already use for other flows.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
43 -
44 -We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release.
45 -
46 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
47 -
48 -== **Memory configuration machine** ==
49 -
50 -To improve the configuration of memory settings on the runtime level and especially the impact of that change on the overall health of the machine, we have made several changes to this process. Most noteworthy, we now keep track of the total amount of memory assigned to all runtimes running on a machine to compare this to the available amount of memory on the machine. To access the overview you need to select the "Details" option on machine level in Deploy Architecture and select the tab called "Runtime".
51 -
52 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--runtime-overview-healthy.png]]
53 -
54 -When you exceed the available memory, eMagiz will notify you and block you from continuing to avoid unstable behavior.
55 -
56 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--runtime-overview-unhealthy.png]]
57 -
58 -== **Multiple environments selection** ==
59 -
60 -{{warning}}The following is only applicable under the following conditions:
61 - * Windows 2022 server
62 - * At least one port opened (as a consequence of a hosted web service){{/warning}}
63 -
64 -When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
65 -
66 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
67 -
68 68  == **Feedback Items** ==
69 -//__Easier component selection in flow designer__//
70 -The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
71 71  
72 -//__Improved handling of optionality in JSON on lists__//
73 -Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties.
10 +//__Failover setup__//
11 +New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]
74 74  
75 -With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired.
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
76 76  
77 -//__Loading bar when searching for log entries__//
78 -To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.
15 +//__External recipients emailaddress__//
16 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
79 79  
80 -//__Improved feedback when deleting elements from Capture__//
81 -To better specify to the user which integration or system the user intends to delete, we have improved the text in the confirmation pop-up. This way, we can provide more information to the user to avoid mistakes.
18 +//__Broker queue metrics dashboards__//
19 +It is now possible to select the MQTT broker in the queue metrics dashboards.
82 82  
83 -//__Enhanced filter options in Manage__//
84 -With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
21 +//__Runtime image version__//
22 +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.
85 85  
86 -//__Copy property names from Create__//
87 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
88 88  
89 -//__Improved feedback during migration to the current runtime architecture__//
90 -Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order.
91 -
92 -//__Block user from making changes to their cloud while another upgrade is still in progress__//
93 -We now block users from changing their cloud configuration when another upgrade is ongoing.
94 -
95 -//__Cron trigger validation__//
96 -We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
97 -
98 98  == **Bug Fixes** ==
99 -//__Making Edit (and View) the default action when configuring parameters__//
100 -We have made the Edit (and View) button the default action when configuring parameters in a transformation.
101 101  
102 -//__Property configuration pop-up resized__//
103 -We have resized the property configuration overviews to make the property value better readable.
27 +//__Message throughput__//
28 +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.
104 104  
105 -//__Alphabetically sorted components in the flow designer__//
106 -As of this release, we now sort the components alphabetically in the flow designer.
30 +//__Cloud template upgrade incorrect rollback__//
31 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
107 107  
108 -//__Improved sorting on runtime overview__//
109 -As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
33 +//__Next generation block__//
34 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
110 110  
111 -//__Improved sorting on catalog overview__//
112 -As of this release, we now sort the topics in the catalog by name.
113 -
114 -//__Styling fix on rich text editors__//
115 -Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
116 -
117 -//__Styling fix on release edit__//
118 -As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
119 -
120 -//__Removed false-positive alerts on transformations__//
121 -When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation.
122 -
123 -//__Event Streaming Graphs - view thirty days back__//
124 -Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further.
125 -
126 -//__Improved helptext__//
127 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
128 -
129 129  == **Fancy Forum Answers** ==
130 130  
131 131  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:
132 132  
133 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
40 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
134 134  
135 -== **Key Takeaways** ==
42 +== **Key takeaways** ==
136 136  
137 137  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:
138 138