Skip to Content

Changes for page 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
From version 84.1
edited by Erik Bakker
on 2023/02/27 16:23
Change comment: There is no comment for this version
To version 70.1
edited by Erik Bakker
on 2023/01/18 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +190 - Fast Forward
Content
... ... @@ -2,69 +2,117 @@
2 2  {{container layoutStyle="columns"}}(((
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 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.
5 +**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.
6 6  
7 -== **REST XML for API Gateway** ~*~* ==
7 +== **Queue Browser** ~*~* ==
8 8  
9 -{{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}}
9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -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.
11 +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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
13 +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 (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
14 14  
15 -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.
15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
17 +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.
18 18  
19 -==**Cloud Template R23 - Single Lane** ==
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.
20 20  
21 -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"]]
30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
22 22  
23 -==**Cloud Template R6 - Single Lane** ==
32 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
24 24  
25 -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"]]
34 +== **Message Redelivery ** ~*~* ==
26 26  
27 -==**Cloud Template R6 - Double Lane** ==
36 +{{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}}
28 28  
29 -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"]]
38 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
30 30  
31 -== **WS-Security on the 3rd generation runtime** ~*~* ==
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).
32 32  
33 -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.
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.
34 34  
35 -== **State Generation ~*~* ==
44 +On top of that we have added some additional functionality.
36 36  
37 -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.
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.
38 38  
39 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
54 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
40 40  
56 +== **3rd generation runtime bolstering** ==
57 +
58 +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.
59 +
60 +//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61 +With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise.
62 +
63 +//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64 +To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
65 +
66 +//__Auto-fill namespaces for SOAP hosted webservices__//
67 +Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
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 +//__Performance improvement creating a release__//
81 +With this release, we have improved the performance of creating a release.
82 +
41 41  == **Feedback items ** ==
42 42  
43 -//__Removed OData as option for an API Gateway operation__//
44 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
85 +We have also solved other feedback items besides the flow designer's critical updates.
45 45  
46 -//__Changes in API Gateway operation paths is automatically updated in Create__//
47 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
87 +//__Sensitive information stored in properties is masked __//
88 +We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
48 48  
49 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
90 +//__Importing "Private" store content to which you do not have access__//
91 +We have improved the user feedback a user will get when trying to import a "Private" store item that is not available to the user.
50 50  
93 +
51 51  == **Bug fixes ** ==
52 52  
53 -//__Prevent endless loop in Deploy -> User Management__//
54 -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.
96 +//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97 +We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
55 55  
56 -{{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}}
99 +//__Synchronization of Event Streaming topic states__//
100 +We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
57 57  
58 -//__Update error handling during migration to the 3rd generation runtime__//
59 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
102 +//__Copy and paste default support objects__//
103 +With this release you can now copy and paste components without having to worry that additional support objects that already exist in your target flow are copied over and over into the same flow.
60 60  
105 +//__Fix editability of properties when importing store items__//
106 +With this release you can once again change property names upon importing a store item.
107 +
61 61  == **Fancy Forum Answers** ==
62 62  
63 63  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:
64 64  
65 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
66 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
67 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
112 +* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113 +* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114 +* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
68 68  
69 69  == **Key takeaways** ==
70 70