Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 61.1
edited by Erik Bakker
on 2023/01/18 09:52
Change comment: There is no comment for this version
To version 448.1
edited by CarlijnKokkeler
on 2024/04/08 14:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +218 - Sprightly Spring
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,131 +1,58 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
6 +**Hi there, eMagiz developers!**
7 +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>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||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.
6 6  
7 -== **Queue Browser** ==
9 +== **Spring 6 Migration** ==
10 +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 our release that will be released on April 11th, 2024, which is this release.
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
12 +Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 +* JDBC BoneCP data source
14 +* SSL web service message sender
15 +* Web service outbound gateway
16 +* SFTP session factory
17 +* HTTP components message sender
18 +* Job manager
19 +* Credentials
20 +* Simple job launcher
21 +* Default SFTP session factory
10 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
12 12  
13 -To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
25 +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"]].
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
27 +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"]].
16 16  
17 -After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
29 +== **Feedback Items** ==
30 +//__Event streaming logging__//
31 +Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
18 18  
19 -* Delete the message from the queue (Explore option)
20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21 -* Clear message from the wiretap queue (Wiretap option)
22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23 -* Refresh messages list (both options)
24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 -* Save as test message
26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27 -* Download
28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
33 +//__Root Cloud__//
34 +Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
31 -
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
33 -
34 -== **Message Redelivery ** ==
35 -
36 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
37 -
38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
39 -
40 -Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
41 -
42 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
43 -
44 -On top of that we have added some additional functionality.
45 -
46 -* Search option
47 - ** Original queue name
48 - ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49 -* Save as test message
50 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
51 -* Download
52 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
53 -
54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
55 -
56 -== **3rd generation runtime bolstering** ==
57 -
58 -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.
59 -
60 -//__SOAP and REST web services migration, including splitting them__//
61 -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.
62 -
63 -//__Changing SSL settings for 3rd generation runtime models works__//
64 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
65 -
66 -//__Improved migration for JMS flows__//
67 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
68 -
69 -{{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}}
70 -
71 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
72 -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.
73 -
74 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
75 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
76 -
77 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
78 -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.
79 -
80 -//__Added "Reset" functionality__//
81 -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.
82 -
83 -== **Feedback items ** ==
84 -
85 -We have also solved other feedback items besides the flow designer's critical updates.
86 -
87 -//__Improved naming convention on Store related pages__//
88 -We have improved various display names using the merge functionality within our store offering.
89 -
90 -//__Update security protocols for our internal architecture__//
91 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
92 -
93 -//__Improved read-only description for "if exists" constructions in Transformations__//
94 -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.
95 -
96 -
97 -== **Bug fixes ** ==
98 -
99 -//__Decent validation feedback when not filling in the property value__//
100 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
101 -
102 -//__Incorrect resource locations__//
103 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
104 -
105 -//__Apply to environment in User Management performance improvement__//
106 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
107 -
108 108  == **Fancy Forum Answers** ==
109 109  
110 110  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:
111 111  
112 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
113 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
114 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
115 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
40 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
41 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
42 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
43 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
116 116  
117 -== **Key takeaways** ==
45 +== **Key Takeaways** ==
118 118  
119 -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 +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:
120 120  
121 121  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
122 122  * If you have feedback or ideas for us, talk to the Platypus
123 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
124 124  * Clear your browser cache (Ctrl + Shift + Del)
125 125  * Check out the release notes [here]
126 126  * Start thinking about how the license tracker can aid your development
127 127  * Start thinking about major, minor, and patch
128 -* Upgrade to the latest build number
129 129  * Keep making great integrations
130 130  
131 131  Let's stay in touch and till next time!
... ... @@ -133,6 +133,11 @@
133 133  {{info}}
134 134  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
135 135  
136 -~*~* Indicates a GEN3-only feature.
137 -{{/info}})))((({{toc/}}))){{/container}}
63 +{{/info}}
64 +)))
65 +
66 +(((
67 +{{toc/}}
68 +)))
138 138  {{/container}}
70 +{{/container}}