Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 67.1
edited by Erik Bakker
on 2023/01/18 10:25
on 2023/01/18 10:25
Change comment:
There is no comment for this version
To version 258.1
edited by Carlijn Kokkeler
on 2023/11/21 12:35
on 2023/11/21 12:35
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 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,126 +1,80 @@ 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!** Ithasbeena whilesince ourlastdeploymenton the9thf December. As a resultwehavefinished upalot ofnewimprovementstoour3rdgenerationruntime offering and fixedavarietyofannoyingbugsas wellassome smallimprovements.Thisrelease ischaracterizedby the majorstepswe tooktoreleaseseveralmajor featureson our 3rdgenerationruntimeamong which arethequeuebrowserandmessage redeliveryfunctionality.6 +**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default. 6 6 7 -== **Queue Browser** == 8 +{{warning}} 9 +Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. 10 +{{/warning}} 8 8 9 - {{warning}}Notethat this functionality only works when yourJMS server is runningon the3rd generationruntime{{/warning}}12 +== **Quicker Deployment Plan** == 10 10 11 - Toenhancethe observabilityofyourtegration landscapewhilerunninginthe3rd generation runtime architecturewehaveaddedanew featureto our Managephase called the"Queuebrowser". You canaccessthisfunctionalityviathe"Explore"menu optioninManage.Withthehelpfthequeuebrowseryoucan,as thenamesuggests,browseyourqueue.14 +We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now! 12 12 13 - Todo so, weoffertwooptions within this functionality. Wehave the Explore function and wehave the Wiretap function.When selecting a queue and opting forthe Explore option you get a live view of what data iscurrently present on the queue. When selectingtheWiretap functionality youautomatically wiretapyour queue and are presented with copies (on a special queue) ofyouractualmessagethatpass through the queue from the moment you pressed the Wiretap button.16 +== **Next Generation Architecture Default** == 14 14 15 - [[image:Main.Images.ReleaseBlog.WebHome@190-release-blog--queue-browser-overview.png]]18 +With this release, the next generation architecture will become the default. New models will use this generation as default. 16 16 17 - After selecting the queueand choosingtheoption eMagiz will show you the list ofmessages(oldest first) that arecurrentlyon thequeue(Exploreoption) or that passed the queue since the moment you activateheoption(Wiretap option).For each message you have various options at your disposal.20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]] 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. 22 +== **Cloud Template R11 Docker - Single Lane** == 29 29 30 - [[image:Main.Images.ReleaseBlog.WebHome@190-release-blog--queue-browser-explore-overview.png]]24 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]]. 31 31 32 - [[image:Main.Images.ReleaseBlog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]26 +== **Cloud Template R13 Docker - Double Lane** == 33 33 34 - ==**MessageRedelivery**==28 +This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 35 35 36 - {{warning}}Notethat this functionality only works when your JMS server is running on the 3rdgenerationruntimeand the functionality isenabled for you environment.{{/warning}}30 +== **Feedback Items** == 37 37 38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]] 32 +//__Unused properties overview__// 33 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 39 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). 35 +* Not used by any runtime that is in the Create phase release. 36 +* Not required by a flow that is in the Create phase release. 37 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 41 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. 39 +//__Queue explorer milliseconds__// 40 +The queue browser now displays milliseconds in the timestamps. 43 43 44 -On top of that we have added some additional functionality. 42 +//__Cancel and next buttons order__// 43 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 45 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. 45 +//__Unused images__// 46 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 53 53 54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 48 +//__Carwash logging__// 49 +A new logging feature enabling us to make better choices in encryption standards will be released. 55 55 56 -== **3rd generation runtime bolstering** == 51 +//__Static alerts queue consumers__// 52 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 57 57 58 - Thisrelease will introduce various improvements for our 3rd generation runtime.Below youwill find the most noteworthy enhancements we made to the 3rdgenerationruntimeand itsinteraction with the portal.54 +== **Bug Fixes** == 59 59 60 -//__De finememorysettings for on-premise runtimes fromDeploy Architecture__//61 - Withthis release,you are nowableto definethe memorysettings (andthereforethememorylimits) ofyour on-premise runtimesinthesame manner ascloud runtimes. Inall casesyoucan nowdefineandchangethememorysettings via DeployArchitecture. In contrast tohow these values are actualizedforcloud runtimes youneedto create anew release and deploy ittoactualize the changeson-premise.56 +//__Flow Designer connection line__// 57 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 62 62 63 -//__ Emptyruntime feedback when deployinga release (orsettingherelease as active)__//64 - Topreventthatyouarenot beingableto deploy areleaseto yourenvironmentduetoa mismatch between whatisinyoureleaseandin Deploy Architecturewe havenowaddeda feedbackpop-upwhendeployingareleasethatnotifiesyoufor whichruntimesthereis a mismatchbetweenyour release andDeploy Architecture.59 +//__Portal for migrated models__// 60 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 65 65 66 -//__ Auto-fill namespaces forSOAPhostedwebservices__//67 - Basedonyour configurationinDesign eMagizwill nowauto-fillthenamespacewhenyouhostaSOAP webservice.Thisavoidsanypotentialproblems invalidatingmessages.62 +//__Error channel inbounds__// 63 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 68 68 69 -//__Updated H2 database setting__// 70 -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. 71 - 72 -{{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}} 73 - 74 -//__Runtime settings option added to context menu on runtime level Deploy Architecture__// 75 -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. 76 - 77 -//__Deploy Agent option added to context menu on machine level Deploy Architecture__// 78 -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"]] 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"]] 69 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 116 116 117 117 == **Key takeaways** == 118 118 119 -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:73 +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. 77 +* 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 ... ... @@ -133,6 +133,12 @@ 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}} 90 +~*~* Indicates a next-generation-architecture only feature. 91 +{{/info}} 92 +))) 93 + 94 +((( 95 +{{toc/}} 96 +))) 138 138 {{/container}} 98 +{{/container}}