Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+192 - Small Step

Author

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

Content

...	...	@@ -2,108 +2,64 @@
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 few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
	5	+**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6	6
7		-== **Deployment Plan** ==
	7	+== **Start/Stop Flows** ~*~* ==
8	8
9		-//__Improved deployment plan to make the process better and more predictable__//
10		-The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
	9	+{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
11	11
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
	11	+To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
14	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	13	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
17	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	15	+After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
20	20
21		-//__Cleanup old images__//
22		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	17	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
23	23
24		-//__Performance improvements for loading releases__//
25		-Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
	19	+{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
26	26
27		-== **Store Improvements** ==
	21	+== **Manage overview Event Streaming** ~*~* ==
28	28
29		-//__Message definition elements order__//
30		-We fixed an issue that the order of message definition elements was changed after being imported.
	23	+To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
31	31
32		-//__Improting a store item with synchronous message definitions__//
33		-We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
	25	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
34	34
35		-//__Importing store items containing static copies__//
36		-We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
	27	+== **Feedback items ** ==
37	37
38		-//__Importing Store content__//
39		-We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
	29	+We have also solved other feedback items besides the flow designer's critical updates.
40	40
41		-== **Feedback Items** ==
	31	+//__Topic configuration calculation__//
	32	+With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
42	42
43		-//__Alerting manual pause__//
44		-A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
	34	+//__Make preparation step in deployment plan visible__//
	35	+For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
45	45
46		-//__Ordering of graphs in Manage__//
47		-The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
	37	+{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
48	48
49		-//__UTC times in Grafana panels__//
50		-All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
	39	+//__3rd generation runtime debugger feedback__//
	40	+We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
51	51
52		-//__Update flow designer version__//
53		-The framework used in the flow designer has been updated to the latest version.
	42	+//__No "Shift key" needed anymore to select multiple items in the flow designer__//
	43	+As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
54	54
55		-//__Carwash track TLS versions in logging__//
56		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
	45	+//__User Management synchronization now happens in one step__//
	46	+With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
57	57
58		-//__Moving channels in the flow designer__//
59		-Moving already attached channels in the flow designer has been made sligthly easier.
60		-
61		-//__Topic sizes description change__//
62		-In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
63		-
64		-//__Password change notification__//
65		-When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
66		-
67		-//__Password comparison__//
68		-When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
69		-
70		-//__Inactive user alerting__//
71		-Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
72		-
73		-//__Alphabetical sorting on user level in HTTP statistics__//
74		-Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
75		-
76		-//__SOAP Web services path__//
77		-Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
78		-
79		-== **Bug Fixes** ==
80		-
81		-//__Flow designer styling__//
82		-The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
83		-
84		-//__Partial search for messages__//
85		-It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
86		-
87		-//__Disk usage after cloud template update__//
88		-In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
89		-
90		-//__Error handling migration__//
91		-If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
92		-
93		-
94	94	== **Fancy Forum Answers** ==
95	95
96	96	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:
97	97
98		-* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
	52	+* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	53	+* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
	54	+* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
99	99
100	100	== **Key takeaways** ==
101	101
102		-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:
	58	+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:
103	103
104	104	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
105	105	* If you have feedback or ideas for us, talk to the Platypus
106		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	62	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
107	107	* Clear your browser cache (Ctrl + Shift + Del)
108	108	* Check out the release notes [here]
109	109	* Start thinking about how the license tracker can aid your development
...	...	@@ -116,6 +116,6 @@
116	116	{{info}}
117	117	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
118	118
119		-~*~* Indicates a next-generation-architecture only feature.
	75	+~*~* Indicates a GEN3-only feature.
120	120	{{/info}})))((({{toc/}}))){{/container}}
121	121	{{/container}}