Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 85.1
edited by Erik Bakker
on 2023/02/28 09:44
Change comment: There is no comment for this version
To version 244.1
edited by Carlijn Kokkeler
on 2023/11/21 11:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,77 +2,78 @@
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!** We have done .....
6 6  
7 -== **REST XML for API Gateway** ==
7 +{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead 5:00 AM UTC. {{/warning}}
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 +== **Next Generation Architecture Default** ==
10 +With this release, the next generation architecture will become the default. New models will use this generation as default.
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.
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
14 +== **Cloud Template R11 - Single Lane** ==
15 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here
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.
17 +== **Cloud Template R13 - Double Lane** ==
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
18 18  
19 -==**Cloud Template R23 - Single Lane** ==
20 +== **Feedback Items** ==
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"]]
22 +//__Unused properties overview__//
23 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
24 +* Not used by any runtime that is in the Create phase release.
25 +* Not required by a flow that is in the Create phase release.
26 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
22 22  
23 -==**Cloud Template R6 - Single Lane** ==
28 +//__Send build requests asynchronously__//
29 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
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"]]
31 +//__Queue explorer milliseconds__//
32 +The queue browser now displays milliseconds in the timestamps.
26 26  
27 -==**Cloud Template R6 - Double Lane** ==
34 +//__Cancel and next buttons order__//
35 +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.
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"]]
37 +//__Unused images__//
38 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
30 30  
31 -== **WS-Security on the 3rd generation runtime** ~*~* ==
40 +//__Carwash logging__//
41 +A new logging feature enabling us to make better choices in encryption standards will be released.
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.
43 +//__Static alerts queue consumers__//
44 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
34 34  
35 -== **State Generation ~*~* ==
46 +== **Bug Fixes** ==
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.
48 +//__Images rebuild__//
49 +We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
38 38  
39 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
51 +//__Flow Designer connection line__//
52 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
40 40  
41 -== **Feedback items ** ==
54 +//__Portal for migrated models__//
55 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
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.
57 +//__Error channel inbounds__//
58 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
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.
48 -
49 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
50 -
51 -== **Bug fixes ** ==
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.
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}}
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.
60 -
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"]]
64 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
68 68  
69 +
69 69  == **Key takeaways** ==
70 70  
71 -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:
72 +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:
72 72  
73 73  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76 76  * Clear your browser cache (Ctrl + Shift + Del)
77 77  * Check out the release notes [here]
78 78  * Start thinking about how the license tracker can aid your development
... ... @@ -85,6 +85,6 @@
85 85  {{info}}
86 86  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87 87  
88 -~*~* Indicates a GEN3-only feature.
89 +~*~* Indicates a next-generation-architecture only feature.
89 89  {{/info}})))((({{toc/}}))){{/container}}
90 90  {{/container}}