Changes for page 210 - Deployment Delights

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

From 61.1 to 60.1 From 87.1 to 86.1

From version 86.1

edited by eMagiz
on 2023/02/28 11:57

Change comment: There is no comment for this version

To version 61.1

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

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 @@
--193 - Fan Out
++190 - Fast Forward

Author

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

Content

@@ -2,71 +2,117 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
++**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.
--== **REST XML for API Gateway** ==
++== **Queue Browser** ==
--{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
++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.
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
++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.
--Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
++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.
--==**Cloud Template update** ==
--
--===Cloud Template R23 - Single Lane ===
++* 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.
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
--===Cloud Template R6 - Single Lane ===
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++== **Message Redelivery ** ==
--===Cloud Template R6 - Double Lane===
++{{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}}
--This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--== **WS-Security on the 3rd generation runtime** ~*~* ==
++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).
--To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols.
++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.
--== **State Generation ~*~* ==
++On top of that we have added some additional functionality.
--With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
++* Search option
++  ** Original queue name
++  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
++* Save as test message
++  ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
++* Download
++  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
--{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
++== **3rd generation runtime bolstering** ==
++
++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.
++
++//__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.
++
++//__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 migration for JMS flows__//
++This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
++
++{{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}}
++
++//__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.
++
++//__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.
++
++//__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.
++
++//__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.
++
  == **Feedback items ** ==
--//__Removed OData as option for an API Gateway operation__//
--With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Changes in API Gateway operation paths is automatically updated in Create__//
--When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
++//__Improved naming convention on Store related pages__//
++We have improved various display names using the merge functionality within our store offering.
--{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
++//__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.
++//__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 ** ==
--//__Prevent endless loop in Deploy -> User Management__//
--With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
++//__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.
--{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
++//__Incorrect resource locations__//
++We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
--//__Update error handling during migration to the 3rd generation runtime__//
--As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
++//__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.
  == **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:
--* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
--* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
--* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||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** ==

Changes for page 210 - Deployment Delights

Summary

Details

Navigation