Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-193 - Fan Out
	1	+218 - Sprightly Spring

Content

...	...	@@ -1,83 +1,57 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
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.
	6	+**Hi there, eMagiz developers!** In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
6	6
7		-== **REST XML for API Gateway** ==
	8	+== **Spring 6 Migration** ==
	9	+As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in this release.
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}}
	11	+Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
	12	+* JDBC BoneCP data source
	13	+* SSL web service message sender
	14	+* Web service outbound gateway
	15	+* SFTP session factory
	16	+* HTTP components message sender
	17	+* Job manager
	18	+* Credentials
	19	+* Simple job launcher
	20	+* Default SFTP session factory
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.
	22	+{{info}}In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
12	12
13		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
	24	+This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. {{/info}}
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.
	26	+{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
16	16
17		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
	28	+== **Feedback Items** ==
	29	+//__Event streaming logging__//
	30	+Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
18	18
19		-==**Cloud Template R23 - Single Lane** ==
	32	+//__Root Cloud__//
	33	+Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
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		-
23		-==**Cloud Template R6 - Single Lane** ==
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"]]
26		-
27		-==**Cloud Template R6 - Double Lane** ==
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"]]
30		-
31		-== **WS-Security on the 3rd generation runtime** ~*~* ==
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.
34		-
35		-== **State Generation ~*~* ==
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.
38		-
39		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
40		-
41		-== **Feedback items ** ==
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.
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"]]
	39	+* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
	40	+* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
	41	+* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
	42	+* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
68	68
69		-== **Key takeaways** ==
	44	+== **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:
	46	+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.
	50	+* 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
79	79	* Start thinking about major, minor, and patch
80		-* Upgrade to the latest build number
81	81	* Keep making great integrations
82	82
83	83	Let's stay in touch and till next time!
...	...	@@ -85,6 +85,11 @@
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		-{{/info}})))((({{toc/}}))){{/container}}
	62	+{{/info}}
	63	+)))
	64	+
	65	+(((
	66	+{{toc/}}
	67	+)))
90	90	{{/container}}
	69	+{{/container}}