Changes for page 190 - Fast Forward
Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 65.1
edited by Erik Bakker
on 2023/01/18 10:25
on 2023/01/18 10:25
Change comment:
There is no comment for this version
To version 63.1
edited by Erik Bakker
on 2023/01/18 10:13
on 2023/01/18 10:13
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -66,16 +66,16 @@ 66 66 //__Auto-fill namespaces for SOAP hosted webservices__// 67 67 Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages. 68 68 69 -//__Updated H2 database setting__// 70 -As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down. 69 +{{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}} 71 71 72 -{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}} 71 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 72 +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. 73 73 74 -//__ Runtimesettingsoptionadded tocontextmenuon runtimelevel Deploy Architecture__//75 - AsareplacementofthecurrentHTTP settingscontextmenu wehaveaddedaewmenuitemcalledruntimesettings.On topf being abletoconfigureyour HTTP settings (whichyouneedto defineforhostedweb service) younow also can define whetherthecontrol bus needs to work forthisruntime.74 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 75 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 76 76 77 -//__ DeployAgentoptionadded tocontextmenuonmachinelevelDeployArchitecture__//78 -With this release, wehaveadded a contextmenu item thatallows userto deploy the agent thatisneededto runyour3rd generationarchitecture on-premise.Formoreinformationon howto install this pleasecheckoutthis [[microlearning>>doc:Main.eMagizAcademy.Microlearnings.ExpertLevel.SolutionArchitectureStore.expert-solution-architecture-onpremises-installguide||target="blank"]]77 +//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__// 78 +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. 79 79 80 80 //__Added "Reset" functionality__// 81 81 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.