Changes for page 213 - Joyful Journeys

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

From 57.1 to 58.1 From 200.1 to 201.1

From version 58.1

edited by Erik Bakker
on 2023/01/18 08:57

Change comment: There is no comment for this version

To version 200.1

edited by Carlijn Kokkeler
on 2023/10/24 09:06

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 @@
--190 - Fast Forward
++207 - Aligned State

Author

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

Content

@@ -2,101 +2,117 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
--== **Queue Browser** ==
++== **State Generation** ==
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++//__New components__//
++The following components have been added:
++* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
++* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
++* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
++* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
++* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
--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.
++//__SpEL functions & JSON__//
++Added SpEL functions for:
++* Encoding & decoding Base64, Hex and hmac.
++* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
++* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
--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.
++Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++Added support for `#JsonPath` usage in SpEL expressions.
--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.
++//__New image version 2.0.0__//
++The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
--* 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.
++//__Component pages__//
++Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++== **Metrics Storage Duration** ==
++We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
--== **3rd generation runtime bolstering** ==
++[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
--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.
++== **Feedback Items** ==
--//__SOAP and REST web services migration, including splitting them__//
--With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
++//__Import from store__//
++The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
--//__Changing SSL settings for 3rd generation runtime models works__//
--As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
++//__Save and cancel buttons placement__//
++The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
--//__Improved migration for JMS flows__//
--This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
++//__User session times__//
++The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
--{{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}}
++//__Cancel and next buttons order__//
++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.
--//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
--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.
++//__Data sink page__//
++The data sink page has been moved to the “Explore” tab.
--//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
--We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
++//__Unused images removal__//
++When a release is removed, the related unused images in the on-premises machines will be removed as well.
--//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
--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.
++//__Flow Designer performance__//
++Performance improvements for the Flow Designer have been implemented.
--//__Added "Reset" functionality__//
--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.
++//__Properties with special characters__//
++When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
--== **Feedback items ** ==
++//__Hidden flow fragements__//
++When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
--We have also solved other feedback items besides the flow designer's critical updates.
++//__Resources disappearances__//
++Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
--//__Improved naming convention on Store related pages__//
--We have improved various display names using the merge functionality within our store offering.
++//__Error channel for all inbounds__//
++If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
++We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
--//__Update security protocols for our internal architecture__//
--Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
++//__Highlighting resources__//
++The performance of highlighting resources of selected components is improved in Read only mode.
--//__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** ==
++//__Topic and event-processor names__//
++The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
--== **Bug fixes ** ==
++//__System alignment__//
++The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
--//__Decent validation feedback when not filling in the property value__//
--We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
++//__Error checking__//
++Besides checking error header, the error trigger is now configured to check if an error message contains a term.
--//__Incorrect resource locations__//
--We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
++//__Alerting__//
++For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
++For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
++The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
--//__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.
++//__Unused containers__//
++Containers are set inactive when they are unused and removed in Design.
++//__Error popups when promoting a release version__//
++We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
++
  == **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:
--* [[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"]]
++* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
++* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
++* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
++* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||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
@@ -109,6 +109,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 213 - Joyful Journeys

Summary

Details

Navigation