Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 181.1
edited by Erik Bakker
on 2023/10/12 16:18
Change comment: There is no comment for this version
To version 242.1
edited by Carlijn Kokkeler
on 2023/11/21 11:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,111 +2,67 @@
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!** We have done .....
6 6  
7 -== **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
7 +== **Next Generation Architecture Default** ==
8 +With this release, the next generation architecture will become the default. New models will use this generation as default.
9 9  
10 -== **Deployment Plan** ==
10 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
11 11  
12 -//__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
12 +== **Cloud Template R11 - Single Lane** ==
13 +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 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
15 +== **Cloud Template R13 - Double Lane** ==
16 16  
17 -//__Editing release properties__//
18 -With this release, it will be possible to change the description of a property by editing the property.
19 19  
20 -//__Container memory settings__//
21 -A change in memory settings triggers redeployment of the container now.
22 -
23 -//__Properties tab__//
24 -We have removed the deprecated tab Properties in the Deploy phase.
25 -
26 -//__Cleanup old images__//
27 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
28 -
29 -//__Performance improvements for loading releases__//
30 -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.
31 -
32 -== **Store Improvements** ==
33 -
34 -//__Message definition elements order__//
35 -We fixed an issue that the order of message definition elements was changed after being imported.
36 -
37 -//__Importing a store item with synchronous message definitions__//
38 -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.
39 -
40 -//__Importing store items containing static copies__//
41 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
42 -
43 -//__Importing store content__//
44 -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.
45 -
46 -//__Store disclaimer__//
47 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
48 -
49 49  == **Feedback Items** ==
50 50  
51 -//__Alerting manual pause__//
52 -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.
20 +//__Unused properties overview__//
21 +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:
22 +* Not used by any runtime that is in the Create phase release.
23 +* Not required by a flow that is in the Create phase release.
24 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
53 53  
54 -//__Ordering of graphs in Manage__//
55 -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).
26 +//__Send build requests asynchronously__//
27 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
56 56  
57 -//__UTC times in Grafana panels__//
58 -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.
29 +//__Queue explorer milliseconds__//
30 +The queue browser now displays milliseconds in the timestamps.
59 59  
60 -//__Update flow designer version__//
61 -The framework used in the flow designer has been updated to the latest version.
32 +//__Cancel and next buttons order__//
33 +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.
62 62  
63 -//__Carwash track TLS versions in logging__//
64 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
35 +//__Unused images__//
36 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
65 65  
66 -//__Moving channels in the flow designer__//
67 -Moving already attached channels in the flow designer has been made sligthly easier.
38 +//__Carwash logging__//
39 +A new logging feature enabling us to make better choices in encryption standards will be released.
68 68  
69 -//__Topic sizes description change__//
70 -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.
41 +//__Static alerts queue consumers__//
42 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
71 71  
72 -//__Password change notification__//
73 -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.
74 -
75 -//__Password comparison__//
76 -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.
77 -
78 -//__Inactive user alerting__//
79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
80 -
81 -//__Alphabetical sorting on user level in HTTP statistics__//
82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
83 -
84 -//__SOAP Web services path__//
85 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
86 -
87 87  == **Bug Fixes** ==
88 88  
89 -//__Flow designer styling__//
90 -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.
46 +//__Images rebuild__//
47 +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.
91 91  
92 -//__Partial search for messages__//
93 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
49 +//__Flow Designer connection line__//
50 +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.
94 94  
95 -//__Disk usage after cloud template update__//
96 -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.
52 +//__Portal for migrated models__//
53 +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.
97 97  
98 -//__Error handling migration__//
99 -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.
55 +//__Error channel inbounds__//
56 +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.
100 100  
101 101  == **Fancy Forum Answers** ==
102 102  
103 103  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:
104 104  
105 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
106 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
107 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
108 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
109 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
62 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
63 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
64 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
65 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
110 110  
111 111  
112 112  == **Key takeaways** ==