Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

From 72.1 to 73.1 From 163.1 to 164.1

From version 73.1

edited by Erik Bakker
on 2023/01/31 12:16

Change comment: There is no comment for this version

To version 163.1

edited by Carlijn Kokkeler
on 2023/10/11 10:57

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--191 - Fifty Fifty
++206 - Situational Deployment

Author

@@ -1,1 +1,1 @@
--XWiki.ebakker
++XWiki.CarlijnKokkeler

Content

@@ -2,131 +2,98 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
++**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.
--== **Dynamic Alerts** ~*~* ==
++== **Deployment Plan** ==
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++//__Improved deployment plan to make the process better and more predictable__//
++The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
--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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
++//__Editing release properties__//
++With this release, it will be possible to change the description of a property by editing the property.
--To do so, we offer two options within this functionality. First, 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 the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
++//__JMS memory setting check__//
++A change in memory settings triggers redeployment of the container now.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++//__Properties tab__//
++We have removed the deprecated tab Properties in the Deploy phase.
--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.
++//__Cleanup old images__//
++When a release is removed, the related unused images in the on-premises machines will be removed as well.
--* Delete the message from the queue (Explore option)
--  ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
--* Clear message from the wiretap queue (Wiretap option)
--  ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
--* Refresh messages list (both options)
--  ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
--* Save as test message
--  ** 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.
--* Download
--  ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
++//__Performance improvements for loading releases__//
++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.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++== **Store Improvements** ==
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
++//__Message definition elements order__//
++We fixed an issue that the order of message definition elements was changed after being imported.
--{{info}}The following restrictions apply to this functionality:
--  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
--  * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
--    ** After five minutes the wiretap functionality will be shutdown automatically under water.
--    ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
++//__Improting a store item with synchronous message definitions__//
++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.
--== **Debugger ** ~*~* ~* ==
++//__Importing store items containing static copies__//
++We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
++== **Feedback Items** ==
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
++//__Alerting manual pause__//
++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.
--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 under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
++//__Ordering of graphs in Manage__//
++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).
--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.
++//__UTC times in Grafana panels__//
++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.
--On top of that, we have added some additional functionality.
++//__Update flow designer version__//
++The framework used in the flow designer has been updated to the latest version.
--* Search option
--  ** Original queue name
--  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
--* Save as test message
--  ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
--* Download
--  ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
++//__Carwash track TLS versions in logging__//
++A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
++//__Moving channels in the flow designer__//
++Moving already attached channels in the flow designer has been made sligthly easier.
--== **3rd generation runtime bolstering** ==
++//__Topic sizes description change__//
++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.
--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.
++//__Password change notification__//
++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.
--//__Define memory settings for on-premise runtimes from Deploy Architecture__//
--With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
++//__Password comparison__//
++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.
--//__Empty runtime feedback when deploying a release (or setting the release as active)__//
--To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
++//__Inactive user alerting__//
++Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--//__Auto-fill namespaces for SOAP hosted webservices__//
--Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
++//__Alphabetical sorting on user level in HTTP statistics__//
++Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--//__Updated H2 database setting__//
--As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
++== **Bug Fixes** ==
--{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
++//__Flow designer styling__//
++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.
--//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
--As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
++//__Partial search for messages__//
++It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
--//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
--With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
++//__Disk usage after cloud template update__//
++Several accounts showed significantly more disk usage after the last cloud template update, this has been resolved.
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
--
--== **Feedback items ** ==
--
--We have also solved other feedback items besides the flow designer's critical updates.
--
--//__Sensitive information stored in properties is masked __//
--We have made how we display sensitive information across the portal similar for various parts of the portal.
--
--//__Importing "Private" store content to which you do not have access__//
--We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
--
--
--== **Bug fixes ** ==
--
--//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
--We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
--
--//__Synchronization of Event Streaming topic states__//
--We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
--
--//__Copy and paste default support objects__//
--With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
--
--//__Fix editability of properties when importing store items__//
--With this release, you can once again change property names upon importing a store item.
--
  == **Fancy Forum Answers** ==
  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:
--* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
--* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
--* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
--* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
++* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
  == **Key takeaways** ==
--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:
++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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
--* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
++* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
@@ -139,6 +139,6 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a GEN3-only feature.
++~*~* Indicates a next-generation-architecture only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 212 - Failover Fiesta

Summary

Details

Navigation