Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 458.1
edited by Erik Bakker
on 2024/04/09 16:30
Change comment: There is no comment for this version
To version 125.1
edited by Erik Bakker
on 2023/06/19 14:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +200 - Uncharted Territories
Content
... ... @@ -1,57 +1,66 @@
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!** In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
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.
7 7  
8 -== **Spring 6 Migration** ==
9 -As announced in our previous release blogs, 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 this release.
7 +== **Next generation improvements and bug fixes** ==
10 10  
11 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
12 -* JDBC BoneCP data source
13 -* SSL web service message sender
14 -* Web service outbound gateway
15 -* SFTP session factory
16 -* HTTP components message sender
17 -* Job manager
18 -* Credentials
19 -* Simple job launcher
20 -* Default SFTP session factory
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.
21 21  
22 -{{info}}In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
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}}
23 23  
24 -This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. {{/info}}
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.
25 25  
26 -{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
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}}
27 27  
28 -== **Feedback Items** ==
29 -//__Event streaming logging__//
30 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
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.
31 31  
32 -//__Root Cloud__//
33 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
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}}
34 34  
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 +
27 +== **Store Improvements** ==
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 +
32 +== **Bug Fixes** ==
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.
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.
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 +
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 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
49 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
43 43  
44 -== **Key Takeaways** ==
52 +== **Key takeaways** ==
45 45  
46 -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:
54 +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:
47 47  
48 48  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49 49  * If you have feedback or ideas for us, talk to the Platypus
50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
58 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 51  * Clear your browser cache (Ctrl + Shift + Del)
52 52  * Check out the release notes [here]
53 53  * Start thinking about how the license tracker can aid your development
54 54  * Start thinking about major, minor, and patch
63 +* Upgrade to the latest build number
55 55  * Keep making great integrations
56 56  
57 57  Let's stay in touch and till next time!
... ... @@ -59,11 +59,6 @@
59 59  {{info}}
60 60  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -{{/info}}
63 -)))
64 -
65 -(((
66 -{{toc/}}
67 -)))
71 +~*~* Indicates a GEN3-only feature.
72 +{{/info}})))((({{toc/}}))){{/container}}
68 68  {{/container}}
69 -{{/container}}