Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
on 2023/05/22 15:07
Change comment:
There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
on 2022/12/06 15:57
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 98 -Great Migration1 +189 - Private Eye - Content
-
... ... @@ -2,39 +2,73 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Inthetfewweeks,we haveworkedhard onmprovingthemigrationards ournext-generationarchitectureandthegeneralbehaviorwhen runningonthenext-generation architecture.Furthermore,severalimprovementshavebeen madeto our infrastructuretonsure thatall dataflowingviathisinfrastructurenowthat moreandmorecustomersaremigratingcan behandledas well,if notbetter,asbefore.5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -== **3rd generation improvements and bug fixes** == 7 +== **Private Store** == 8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 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. 10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 11 11 12 - {{info}}Notethat this fix is partof anewruntime image forthe karaf-based runtimes.The impact of this canbe read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}12 +== **3rd generation runtime bolstering** == 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. 14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 16 16 17 -//__Re movedspecificdependencies betweenDeploy Architecture andReleases__//18 - Inthis release, we have removedseveralexplicitdependencies thatconfusedthefunctionalityintheDeployArchitecture overviewcomparedtothefunctionality linkedtoae,specificallythe deploymentfarelease.16 +//__SOAP and REST web services migration, including splitting them__// 17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal. 19 19 20 -//__ Improved validationerrorson the invalidconfigurationof HTTP outboundcomponents__//21 - Thisrelease fixesandre-introducestheoptiontoexecute youractionson the eMagizper zone or allatoncewhenrunning inadouble-laneDockersetup.19 +//__Changing SSL settings for 3rd generation runtime models works__// 20 +As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime. 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 +//__Improved migration for JMS flows__// 23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 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. 25 +{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}} 31 31 27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 +As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow. 29 + 30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 32 + 33 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__// 34 +With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image. 35 + 36 +//__Added "Reset" functionality__// 37 +With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime. 38 + 39 +== **Feedback items ** == 40 + 41 +We have also solved other feedback items besides the flow designer's critical updates. 42 + 43 +//__Improved naming convention on Store related pages__// 44 +We have improved various display names using the merge functionality within our store offering. 45 + 46 +//__Update security protocols for our internal architecture__// 47 +Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards. 48 + 49 +//__Improved read-only description for "if exists" constructions in Transformations__// 50 +To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does. 51 + 52 + 53 +== **Bug fixes ** == 54 + 55 +//__Decent validation feedback when not filling in the property value__// 56 +We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality. 57 + 58 +//__Incorrect resource locations__// 59 +We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 60 + 61 +//__Apply to environment in User Management performance improvement__// 62 +We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 63 + 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"]] 68 +* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 69 +* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 70 +* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 71 +* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 38 38 39 39 == **Key takeaways** == 40 40