Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-193 - Fan Out
	1	+211 - Log Luminary

Author

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

Content

...	...	@@ -1,82 +1,78 @@
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 have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6	6
7		-== **REST XML for API Gateway** ==
	8	+== **Logging** ==
	9	+//__Missing log entries__//
	10	+We improved crash handling so that log messages clearly show when and why a container failed to start.
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}}
	12	+//__Runtime logging__//
	13	+We fixed a bug where no new log messages were showing up, even though they were produced by a container.
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.
	15	+//__Deployment execution error message__//
	16	+In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
	18	+== **Overviews** ==
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	+//__Runtime overview__//
	21	+We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
	23	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
18	18
19		-==**Cloud Template update** ==
	25	+//__Missing properties overview__//
	26	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
20	20
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 ====
	28	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
24	24
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"]]
	30	+//__Runtime restart or redeploy overview__//
	31	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
26	26
27		-====Cloud Template R6 - Single Lane ====
	33	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
28	28
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"]]
	35	+== **Feedback Items** ==
30	30
31		-====Cloud Template R6 - Double Lane====
	37	+//__Breaking changes pop-up__//
	38	+Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
32	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"]]
	40	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
34	34
35		-== **WS-Security on the 3rd generation runtime** ~*~* ==
	42	+//__External recipients emailaddress__//
	43	+The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
36	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.
	45	+//__Broker queue metrics dashboards__//
	46	+It is now possible to select the MQTT broker in the queue metrics dashboards.
38	38
39		-== **State Generation ~*~* ==
	48	+//__Runtime image version__//
	49	+The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
40	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	42
43		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
	52	+== **Bug Fixes** ==
44	44
45		-== **Feedback items ** ==
	54	+//__Message throughput__//
	55	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
46	46
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.
	57	+//__Cloud template upgrade unjust rollback__//
	58	+An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
49	49
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.
	60	+//__Next generation block__//
	61	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
52	52
53		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
54		-
55		-== **Bug fixes ** ==
56		-
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.
59		-
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}}
61		-
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		-
65	65	== **Fancy Forum Answers** ==
66	66
67	67	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:
68	68
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"]]
	67	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
72	72
73	73	== **Key takeaways** ==
74	74
75		-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:
	71	+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:
76	76
77	77	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78	* If you have feedback or ideas for us, talk to the Platypus
79		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	75	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80	80	* Clear your browser cache (Ctrl + Shift + Del)
81	81	* Check out the release notes [here]
82	82	* Start thinking about how the license tracker can aid your development
...	...	@@ -89,6 +89,12 @@
89	89	{{info}}
90	90	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91	91
92		-~*~* Indicates a GEN3-only feature.
93		-{{/info}})))((({{toc/}}))){{/container}}
	88	+~*~* Indicates a next-generation-architecture only feature.
	89	+{{/info}}
	90	+)))
	91	+
	92	+(((
	93	+{{toc/}}
	94	+)))
94	94	{{/container}}
	96	+{{/container}}