Changes for page 202 - New Equilibrium

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-193 - Fan Out
	1	+202 - New Equilibrium

Author

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

Content

...	...	@@ -1,72 +1,74 @@
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 the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **REST XML for API Gateway** ~*~* ==
	8	+== **Release Properties** ==
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}}
	10	+As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
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	+* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
	13	+* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
	14	+* When adding or editing a property, you can **now** select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
	15	+* A, for most, new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
	17	+{{info}}
	18	+For more information, please check out the following microlearnings:
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.
	20	+* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	21	+* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
	22	+* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
16	16
17		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
	24	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	25	+{{/info}}
18	18
19		-==**Cloud Template R23 - Single Lane** ==
	27	+== ** Manage - Graphs improvements ~*~* ** ==
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"]]
	29	+As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
22	22
23		-==**Cloud Template R6 - Single Lane** ==
	31	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.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"]]
	33	+== **Feedback Items** ==
26	26
27		-==**Cloud Template R6 - Double Lane** ==
	35	+//__Improved editability when testing in eMagiz without Edit rights in Create__//
	36	+Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
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	+//__Improved auditability on Deploy Architecture__//
	39	+To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
30	30
31		-== **WS-Security on the 3rd generation runtime** ~*~* ==
	41	+//__Test your own exported store content__//
	42	+We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
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.
	44	+{{info}}
	45	+In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]
	46	+{{/info}}
34	34
35		-== **State Generation ~*~* ==
	48	+//__Improved comparison of flows in the releases overview__//
	49	+We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
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.
	51	+== **Bug Fixes** ==
38	38
39		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
	53	+//__Improved validation on XPath header enricher__//
	54	+To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
40	40
41		-== **Feedback items ** ==
	56	+//__Cancel behavior on flow testing property overview fixed__//
	57	+We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
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.
	59	+//__Cancel behavior on flow fragment level when exporting store content__//
	60	+We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
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.
	62	+//__Adding numbers on containers in Deploy Architecture__//
	63	+With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
48	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"]]
	69	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
68	68
69		-== **Key takeaways** ==
	71	+== **Key Takeaways** ==
70	70
71	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	72
...	...	@@ -74,7 +74,7 @@
74	74	* If you have feedback or ideas for us, talk to the Platypus
75	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	76	* Clear your browser cache (Ctrl + Shift + Del)
77		-* Check out the release notes [here]
	79	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]]
78	78	* Start thinking about how the license tracker can aid your development
79	79	* Start thinking about major, minor, and patch
80	80	* Upgrade to the latest build number
...	...	@@ -85,6 +85,12 @@
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}}
	90	+~*~* Indicates a next-generation-architecture only feature.
	91	+{{/info}}
	92	+)))
	93	+
	94	+(((
	95	+{{toc/}}
	96	+)))
90	90	{{/container}}
	98	+{{/container}}