Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 181.1
edited by Erik Bakker
on 2023/10/12 16:18
Change comment: There is no comment for this version
To version 58.1
edited by Erik Bakker
on 2023/01/18 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +190 - Fast Forward
Content
... ... @@ -2,120 +2,101 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
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 6  
7 -== **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
7 +== **Queue Browser** ==
9 9  
10 -== **Deployment Plan** ==
9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
11 11  
12 -//__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
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.
14 14  
15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
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.
16 16  
17 -//__Editing release properties__//
18 -With this release, it will be possible to change the description of a property by editing the property.
15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
19 19  
20 -//__Container memory settings__//
21 -A change in memory settings triggers redeployment of the container now.
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.
22 22  
23 -//__Properties tab__//
24 -We have removed the deprecated tab Properties in the Deploy phase.
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.
25 25  
26 -//__Cleanup old images__//
27 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
28 28  
29 -//__Performance improvements for loading releases__//
30 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
32 +== **3rd generation runtime bolstering** ==
31 31  
32 -== **Store Improvements** ==
34 +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.
33 33  
34 -//__Message definition elements order__//
35 -We fixed an issue that the order of message definition elements was changed after being imported.
36 +//__SOAP and REST web services migration, including splitting them__//
37 +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.
36 36  
37 -//__Importing a store item with synchronous message definitions__//
38 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
39 +//__Changing SSL settings for 3rd generation runtime models works__//
40 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
39 39  
40 -//__Importing store items containing static copies__//
41 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
42 +//__Improved migration for JMS flows__//
43 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
42 42  
43 -//__Importing store content__//
44 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
45 +{{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}}
45 45  
46 -//__Store disclaimer__//
47 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
47 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
48 +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.
48 48  
49 -== **Feedback Items** ==
50 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
51 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
50 50  
51 -//__Alerting manual pause__//
52 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
53 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
54 +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.
53 53  
54 -//__Ordering of graphs in Manage__//
55 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
56 +//__Added "Reset" functionality__//
57 +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.
56 56  
57 -//__UTC times in Grafana panels__//
58 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
59 +== **Feedback items ** ==
59 59  
60 -//__Update flow designer version__//
61 -The framework used in the flow designer has been updated to the latest version.
61 +We have also solved other feedback items besides the flow designer's critical updates.
62 62  
63 -//__Carwash track TLS versions in logging__//
64 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
63 +//__Improved naming convention on Store related pages__//
64 +We have improved various display names using the merge functionality within our store offering.
65 65  
66 -//__Moving channels in the flow designer__//
67 -Moving already attached channels in the flow designer has been made sligthly easier.
66 +//__Update security protocols for our internal architecture__//
67 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
68 68  
69 -//__Topic sizes description change__//
70 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
69 +//__Improved read-only description for "if exists" constructions in Transformations__//
70 +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.
71 71  
72 -//__Password change notification__//
73 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
74 74  
75 -//__Password comparison__//
76 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
73 +== **Bug fixes ** ==
77 77  
78 -//__Inactive user alerting__//
79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
75 +//__Decent validation feedback when not filling in the property value__//
76 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
80 80  
81 -//__Alphabetical sorting on user level in HTTP statistics__//
82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
78 +//__Incorrect resource locations__//
79 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
83 83  
84 -//__SOAP Web services path__//
85 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
81 +//__Apply to environment in User Management performance improvement__//
82 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
86 86  
87 -== **Bug Fixes** ==
88 -
89 -//__Flow designer styling__//
90 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
91 -
92 -//__Partial search for messages__//
93 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
94 -
95 -//__Disk usage after cloud template update__//
96 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
97 -
98 -//__Error handling migration__//
99 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
100 -
101 101  == **Fancy Forum Answers** ==
102 102  
103 103  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:
104 104  
105 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
106 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
107 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
108 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
109 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
88 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
89 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
90 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
91 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
110 110  
111 -
112 112  == **Key takeaways** ==
113 113  
114 -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:
95 +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:
115 115  
116 116  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
117 117  * If you have feedback or ideas for us, talk to the Platypus
118 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
99 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
119 119  * Clear your browser cache (Ctrl + Shift + Del)
120 120  * Check out the release notes [here]
121 121  * Start thinking about how the license tracker can aid your development
... ... @@ -128,6 +128,6 @@
128 128  {{info}}
129 129  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
130 130  
131 -~*~* Indicates a next-generation-architecture only feature.
112 +~*~* Indicates a GEN3-only feature.
132 132  {{/info}})))((({{toc/}}))){{/container}}
133 133  {{/container}}