Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
on 2023/02/14 15:33
Change comment:
There is no comment for this version
To version 437.1
edited by CarlijnKokkeler
on 2024/04/08 11:20
on 2024/04/08 11:20
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 - 192 - SmallStep1 +218 - Sprightly Spring - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,70 +1,79 @@ 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!** In the last couple of weeks, we worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Start/Stop Flows** ~*~* == 8 8 9 -{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}} 9 +== **Spring 6 Migration** == 10 +As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release. 10 10 11 -To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option. 12 +Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 13 +* JDBC BoneCP data source 14 +* SSL web service message sender 15 +* Web service outbound gateway 16 +* SFTP session factory 17 +* HTTP components message sender 18 +* Job manager 19 +* Credentials 20 +* Simple job launcher 21 +* Default SFTP session factory 12 12 13 - [[image:Main.Images.ReleaseBlog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. 14 14 15 - Afterselecting the option,eMagiz will opena pop-up whereyou canstop andstartthe startingpointof eachflow deployed onthatruntime.Thiseffectis thattheflowwillprocessnonewmessages,but the flowwillstillprocessallremaining messages afterstoppingtheflow. Topreventaflow, youselecta flow andpress the Stop button.To startit again,press Start.25 +In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration||target="blank"]]. 16 16 17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 27 +== **Feedback Items** == 28 +//__Dynamic trigger__// 29 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger. 18 18 19 - {{info}}Only in "Start Editing"modecanyoustartandstop specific flows{{/info}}31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 20 20 21 -== **Manage overview Event Streaming** ~*~* == 33 +//__Copy to clipboard buttons__// 34 +Copy to clipboard buttons have been added to various pages: 22 22 23 -To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data. 36 + * Deploy agent pop-up 37 + * Create - Flow designer: Properties 38 + * Deploy - Property releases: Property details 24 24 25 -[[image:Main.Images.Release Blog.WebHome@ 192-release-blog--event-streaming-overview-manage.png]]40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 26 26 27 -== **Feedback items ** == 42 +//__Reset H2 database__// 43 +For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. 28 28 29 - Wehave also solvedotherfeedback items besides the flowdesigner's critical updates.45 +{{info}}Please note the following: 30 30 31 -//__Topic configuration calculation__// 32 -With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics. 47 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 48 +* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. 49 +* For on-premise runtimes, only a reset of the runtime is needed. 33 33 34 -//__Make preparation step in deployment plan visible__// 35 -For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan. 51 +For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}} 36 36 37 - {{warning}}Makesureto updateyour deployment plan accordingly toensurethat thepreparation step isnot forgotten{{/warning}}53 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 38 38 39 -//__3rd generation runtime debugger feedback__// 40 -We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality. 55 +== **Bug Fixes** == 56 +//__Runtime overview improvements__// 57 +The runtime overview has been improved regarding checks on the runtime version. 41 41 42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__// 43 -As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows. 44 - 45 -//__User Management synchronization now happens in one step__// 46 -With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized. 47 - 48 48 == **Fancy Forum Answers** == 49 49 50 50 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: 51 51 52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]] 54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]] 63 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 64 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 55 55 56 -== **Key takeaways** ==66 +== **Key Takeaways** == 57 57 58 -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:68 +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: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 64 * Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development 66 66 * Start thinking about major, minor, and patch 67 -* Upgrade to the latest build number 68 68 * Keep making great integrations 69 69 70 70 Let's stay in touch and till next time! ... ... @@ -72,6 +72,11 @@ 72 72 {{info}} 73 73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 75 -~*~* Indicates a GEN3-only feature. 76 -{{/info}})))((({{toc/}}))){{/container}} 84 +{{/info}} 85 +))) 86 + 87 +((( 88 +{{toc/}} 89 +))) 77 77 {{/container}} 91 +{{/container}}