Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04

From 60.1 to 59.1 From 424.1 to 423.1

From version 423.1

edited by Erik Bakker
on 2024/03/12 14:01

Change comment: There is no comment for this version

To version 60.1

edited by Erik Bakker
on 2023/01/18 09:30

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--216 - Hack Heaven
++190 - Fast Forward

Content

@@ -1,138 +1,123 @@
  {{container}}
--{{container layoutStyle="columns"}}
--(((
++{{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that, we launch new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
++**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.
--== ** Announcement - TLS versions deprecated** ==
++== **Queue Browser** ==
--As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--* TLSv1.0
--* TLSv1.1
++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.
--{{info}}Text{{/info}}
++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.
--== **Announcement - Spring 6** ==
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
--We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]]** architecture in our release that will be released on April 11th, 2024. This image moves the eMagiz stack from Java 8 to Java 17 and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
++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.
--{{warning}}
--* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting.
--* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
--** Simple job launcher (data pipelines)
--** Job explorer (data pipelines)
--** HTTP components message sender (support object)
--** Web service outbound gateway (with a 'message sender' attribute specified)
--** SFTP session factory (support object)
--** API gateways with OAuth2 as security mechanism.
--* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, this may affect the availability of the libraries on the classpath and, therefore, the validity of import statements. You can already test the Groovy script using the flow testing functionality, as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
--** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
--* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production. {{/warning}}
++* 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.
--== **Infra flow selection** ==
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
--This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
++== **Message Redelivery ** ==
--In edit mode, you can select a new version via the right-click option, which you already use for other flows.
++{{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}}
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
++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).
--We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release.
++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.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
++On top of that we have added some additional functionality.
--== **Multiple environments selection** ==
++* Search option
++  ** Original queue name
++  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
--{{warning}}The following is only applicable under the following conditions:
--  * Windows 2022 server
--  * At least one port opened (as a consequence of a hosted web service){{/warning}}
++== **3rd generation runtime bolstering** ==
--When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
++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.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
++//__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.
--== **Feedback Items** ==
--//__Easier component selection in flow designer__//
--The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
++//__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.
--//__Improved handling of optionality in JSON on lists__//
--Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties.
++//__Improved migration for JMS flows__//
++This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
--With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired.
++{{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}}
--//__Loading bar when searching for log entries__//
--To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.
++//__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.
--//__Improved feedback when deleting elements from Capture__//
--To better specify to the user which integration or system the user intends to delete, we have improved the text in the confirmation pop-up. This way, we can provide more information to the user to avoid mistakes.
++//__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.
--//__Enhanced filter options in Manage__//
--With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
++//__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.
--//__Copy property names from Create__//
--This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
++//__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.
--//__Improved feedback during migration to the current runtime architecture__//
--Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order.
++== **Feedback items ** ==
--//__Block user from making changes to their cloud while another upgrade is still in progress__//
--We now block users from changing their cloud configuration when another upgrade is ongoing.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Cron trigger validation__//
--We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
++//__Improved naming convention on Store related pages__//
++We have improved various display names using the merge functionality within our store offering.
--== **Bug Fixes** ==
--//__Making Edit (and View) the default action when configuring parameters__//
--We have made the Edit (and View) button the default action when configuring parameters in a transformation.
++//__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.
--//__Property configuration pop-up resized__//
--We have resized the property configuration overviews to make the property value better readable.
++//__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.
--//__Alphabetically sorted components in the flow designer__//
--As of this release, we now sort the components alphabetically in the flow designer.
--//__Improved sorting on runtime overview__//
--As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
++== **Bug fixes ** ==
--//__Improved sorting on catalog overview__//
--As of this release, we now sort the topics in the catalog by name.
++//__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.
--//__Styling fix on rich text editors__//
--Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
++//__Incorrect resource locations__//
++We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
--//__Styling fix on release edit__//
--As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
++//__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.
--//__Removed false-positive alerts on transformations__//
--When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation.
--
--//__Event Streaming Graphs - view thirty days back__//
--Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further.
--
--//__Improved helptext__//
--We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
--
  == **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:
--* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||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** ==
++== **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
  * Start thinking about major, minor, and patch
++* Upgrade to the latest build number
  * Keep making great integrations
  Let's stay in touch and till next time!
@@ -140,11 +140,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]]
--{{/info}}
--)))
--
--(((
--{{toc/}}
--)))
++~*~* Indicates a GEN3-only feature.
++{{/info}})))((({{toc/}}))){{/container}}
  {{/container}}
--{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation