Changes for page 206 - Situational Deployment

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

From 68.1 to 67.1 From 172.1 to 171.1

From version 171.1

edited by Carlijn Kokkeler
on 2023/10/11 15:54

Change comment: There is no comment for this version

To version 68.1

edited by Erik Bakker
on 2023/01/18 10:37

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 @@
--206 - Situational Deployment
++190 - Fast Forward

Author

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

Content

@@ -2,110 +2,125 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**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.
--== **Deployment Plan** ==
++== **Queue Browser** ==
--//__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.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--//__Editing release properties__//
--With this release, it will be possible to change the description of a property by editing the property.
++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.
--//__JMS memory setting check__//
--A change in memory settings triggers redeployment of the container now.
++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 (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
--//__Properties tab__//
--We have removed the deprecated tab Properties in the Deploy phase.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
--//__Cleanup old images__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
++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.
--//__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.
++* 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 inadvertedly put a lot of messages on a queue.
++* Clear message from the wiretap queue (Wiretap option)
++  ** 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
++* Refresh messages list (both options)
++  ** 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
++* 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.
--== **Store Improvements** ==
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
--//__Message definition elements order__//
--We fixed an issue that the order of message definition elements was changed after being imported.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
--//__Importing 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.
++== **Message Redelivery ** ==
--//__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 you environment.{{/warning}}
--//__Importing Store content__//
--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.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--//__Store disclaimer__//
--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.
++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).
--== **Feedback Items** ==
++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.
--//__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.
++On top of that we have added some additional functionality.
--//__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).
++* 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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
--//__Update flow designer version__//
--The framework used in the flow designer has been updated to the latest version.
++== **3rd generation runtime bolstering** ==
--//__Carwash track TLS versions in logging__//
--A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
++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.
--//__Moving channels in the flow designer__//
--Moving already attached channels in the flow designer has been made sligthly easier.
++//__Define memory settings for on-premise runtimes from Deploy Architecture__//
++With this release, you are now able to 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.
--//__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.
++//__Empty runtime feedback when deploying a release (or setting the release as active)__//
++To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in 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.
--//__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.
++//__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.
--//__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.
++//__Updated H2 database setting__//
++As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
--//__Inactive user alerting__//
--Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
++{{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}}
--//__Alphabetical sorting on user level in HTTP statistics__//
--Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
++//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
++As a replacement of the current HTTP settings context menu we have 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.
--//__SOAP Web services path__//
--Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
++//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
++With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
--== **Bug Fixes** ==
++//__Performance improvement creating a release__//
++With this release, we have improved the performance of creating a release.
--//__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.
++== **Feedback items ** ==
--//__Partial search for messages__//
--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".
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Disk usage after cloud template update__//
--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.
++//__Sensitive information stored in properties is masked __//
++We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
--//__Error handling migration__//
--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.
++//__Confirmation pop-up displaying whether your topology changes in Deploy Architecture__//
++To give the user additional feedback of what will happen on the cloud slot when the user presses "Apply to environment" we have now added a confirmation pop-up that is shown when you migrate from the current runtime architecture to the 3rd generation runtime.
++//__Improved read-only description for "if exists" constructions in Transformations__//
++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.
++
++
++== **Bug fixes ** ==
++
++//__Fix 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 have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
++
++//__Apply to environment in User Management performance improvement__//
++We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
++
  == **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:
--* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
++* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
++* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
++* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
++* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
  == **Key takeaways** ==
--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:
++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:
  * 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
@@ -118,6 +118,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 next-generation-architecture only feature.
++~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 206 - Situational Deployment

Summary

Details

Navigation