Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version
To version 245.1
edited by Danniar Firdausy
on 2023/11/06 13:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,47 +2,56 @@
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 worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
5 +**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can have a better overview of its implementation in your environment.
6 6  
7 -== **3rd generation improvements and bug fixes** ==
7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
9 +== **State Generation~*~*** ==
11 11  
12 -{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
11 +//__New Page__//
12 +The following page has been added:
13 +* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
13 13  
14 -//__Improved efficiency in deploying a release__//
15 -This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
15 +Added support for ... .
16 16  
17 -//__Removed specific dependencies between Deploy Architecture and Releases__//
18 -In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
17 +{{info}}The components are ... .{{/info}}
19 19  
20 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
19 +== **Metrics Storage Duration** ==
20 +We will ... .
22 22  
23 -//__Improved migration behavior__//
24 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25 -A smoother migration of your JMS (and backup JMS) process.
26 -Shortening of names that otherwise would be too long, additional feedback given to the user.
27 -Feedback when the migration process is finished.
22 +== **Feedback Items** ==
28 28  
29 -//__Additional checks when deploying__//
30 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
24 +//__Import from store__//
25 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
31 31  
27 +//__Import from store__//
28 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
29 +
30 +== **Bug Fixes** ==
31 +
32 +//__Topic and event-processor names__//
33 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
34 +
35 +//__Topic and event-processor names__//
36 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
37 +
32 32  == **Fancy Forum Answers** ==
33 33  
34 34  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:
35 35  
36 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
42 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
43 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
44 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
45 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
38 38  
47 +
39 39  == **Key takeaways** ==
40 40  
41 -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:
50 +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:
42 42  
43 43  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
44 44  * If you have feedback or ideas for us, talk to the Platypus
45 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
46 46  * Clear your browser cache (Ctrl + Shift + Del)
47 47  * Check out the release notes [here]
48 48  * Start thinking about how the license tracker can aid your development
... ... @@ -55,6 +55,6 @@
55 55  {{info}}
56 56  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  
58 -~*~* Indicates a GEN3-only feature.
67 +~*~* Indicates a next-generation-architecture only feature.
59 59  {{/info}})))((({{toc/}}))){{/container}}
60 60  {{/container}}