Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 58.1
edited by Erik Bakker
on 2023/01/18 08:57
on 2023/01/18 08:57
Change comment:
There is no comment for this version
To version 157.1
edited by Carlijn Kokkeler
on 2023/10/10 14:06
on 2023/10/10 14:06
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 190 -FastForward1 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,101 +2,69 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** I t has beena whilesince ourlastdeploymenton the9th of December. Asa resultwe havefinishedup a lot ofnewimprovementsto our3rd generation runtimeofferingand fixedavarietyof annoyingbugs aswellassomesmall improvements.Thisreleaseischaracterizedbythe major stepswe tooktorelease several major features onour3rd generation runtimeamongwhicharethe queue browserand messageredeliveryfunctionality.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. 6 6 7 -== ** Queue Browser** ==7 +== **Deployment Plan** == 8 8 9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}} 9 +//__Improved deployment plan to make the process better and more predictable__// 10 +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. 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. 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 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. 15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]] 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 20 + 21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 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. 24 +== **Store Improvements** == 25 + 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. 27 +== **Feedback Items** == 29 29 30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] 29 +//__Alerting manual pause__// 30 +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. 31 31 32 -== **3rd generation runtime bolstering** == 32 +//__Ordering of graphs in Manage__// 33 +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). 33 33 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. 35 +//__UTC times in Grafana panels__// 36 +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. 35 35 36 -//__ SOAP andRESTwebservicesmigration, including splitting them__//37 - Withthisrelease,we havereleasedthe migrationprocessthatwill allowyou to migrate SOAP andREST webservices to the 3rdgenerationruntime. At the sametime, you can directlysplit theall-entry to eliminatethat construction.A specific migration path for thiswill be published in the documentation portal.38 +//__Update flow designer version__// 39 +The framework used in the flow designer has been updated to the latest version. 38 38 39 -//__C hanging SSLsettingsfor3rdgenerationruntimemodels works__//40 -A swiththecurrentruntimearchitecture,you canchangetheSSL settings ifneededfor a modelrunningin the 3rdgenerationruntime.41 +//__Carwash track TLS versions in logging__// 42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 41 41 42 -//__ Improved migrationforJMSflows__//43 - Thisrelease will improve themigrationofJMSflowswhen migratingo the3rd generation runtime.44 +//__Moving channels in the flow designer__// 45 +Moving already attached channels in the flow designer has been made sligthly easier. 44 44 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}} 47 +//__Topic sizes description change__// 48 +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. 46 46 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. 50 + 51 + 52 +== **Bug Fixes** == 49 49 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. 52 52 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. 55 - 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. 58 - 59 -== **Feedback items ** == 60 - 61 -We have also solved other feedback items besides the flow designer's critical updates. 62 - 63 -//__Improved naming convention on Store related pages__// 64 -We have improved various display names using the merge functionality within our store offering. 65 - 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 - 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 - 72 - 73 -== **Bug fixes ** == 74 - 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. 77 - 78 -//__Incorrect resource locations__// 79 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 80 - 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. 83 - 84 84 == **Fancy Forum Answers** == 85 85 86 86 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: 87 87 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"]] 59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 92 92 93 93 == **Key takeaways** == 94 94 95 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:63 +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: 96 96 97 97 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 98 98 * If you have feedback or ideas for us, talk to the Platypus 99 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 67 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 100 100 * Clear your browser cache (Ctrl + Shift + Del) 101 101 * Check out the release notes [here] 102 102 * Start thinking about how the license tracker can aid your development ... ... @@ -109,6 +109,6 @@ 109 109 {{info}} 110 110 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 111 111 112 -~*~* Indicates a GEN3-only feature.80 +~*~* Indicates a next-generation-architecture only feature. 113 113 {{/info}})))((({{toc/}}))){{/container}} 114 114 {{/container}}