Skip to Content

Changes for page 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
From version 92.1
edited by Erik Bakker
on 2023/03/14 08:25
Change comment: There is no comment for this version
To version 88.1
edited by eMagiz
on 2023/02/28 13:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Big Leap
1 +193 - Fan Out
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -2,65 +2,73 @@
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 have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
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.
6 6  
7 -== **3rd generation improvements** ==
7 +== **REST XML for API Gateway** ==
8 8  
9 -//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 -We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
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}}
11 11  
12 -//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 -We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
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.
14 14  
15 -//__Improved Manage Dashboard__//
16 -This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
13 +[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
17 17  
18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 -When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
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.
20 20  
21 -//__Improved process of deploy preparation__//
22 -With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
17 +[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
23 23  
24 -//__Improved migration of Streaming container__//
25 -When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
19 +==**Cloud Template update** ==
26 26  
27 -//__Add History to Notifications in Manage__//
28 -To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
21 +We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set).
22 +
23 +====Cloud Template R23 - Single Lane ====
29 29  
30 -//__Improved Manage phase for Event Streaming__//
31 -Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
25 +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"]]
32 32  
33 -//__Improved help text for network volumes__//
34 -With this release we have improved the help text that explains network volumes and how to use them within our solution.
27 +====Cloud Template R6 - Single Lane ====
35 35  
36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
29 +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"]]
37 37  
31 +====Cloud Template R6 - Double Lane====
32 +
33 +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"]]
34 +
35 +== **WS-Security on the 3rd generation runtime** ~*~* ==
36 +
37 +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. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
38 +
39 +== **State Generation ~*~* ==
40 +
41 +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.
42 +
43 +{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
44 +
38 38  == **Feedback items ** ==
39 39  
40 -//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 -With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
47 +//__Removed OData as option for an API Gateway operation__//
48 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
42 42  
43 -//__User Roles are sorted alphabetically__//
44 -All user roles under User Management are now also sorted alphabetically.
50 +//__Changes in API Gateway operation paths is automatically updated in Create__//
51 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
45 45  
46 -//__Name of keystore for user management now includes the environment__//
47 -To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename.
53 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
48 48  
49 49  == **Bug fixes ** ==
50 50  
51 -//__Consolidated upgrade process cloud template__//
52 -With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud.
57 +//__Prevent endless loop in Deploy -> User Management__//
58 +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.
53 53  
54 -//__Ensure users can deploy release on environments they have edit rights on__//
55 -As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so.
60 +{{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}}
56 56  
62 +//__Update error handling during migration to the 3rd generation runtime__//
63 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
64 +
57 57  == **Fancy Forum Answers** ==
58 58  
59 59  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:
60 60  
61 -* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62 -* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63 -* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
69 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
70 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
71 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
64 64  
65 65  == **Key takeaways** ==
66 66