Changes for page Change Detection - State Generation
Last modified by Carlijn Kokkeler on 2024/06/07 15:27
From version 21.1
edited by Erik Bakker
on 2024/03/29 13:56
on 2024/03/29 13:56
Change comment:
There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2022/05/02 09:44
on 2022/05/02 09:44
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 -A ctive/PassiveFailover1 +Add Namespace - Content
-
... ... @@ -2,30 +2,27 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 - Thisstore item can easily addtherequiredconfigurationtoyourinfra flow tomaketheactive/passivefailoverfunctionalitypossible within theuntimecontext.5 +With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 -With the help of this store item, you canmaketheactive/passivefailover functionalitypossible within theuntimecontext.10 +With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that you also need to define the correct settings in each flow to group flows together that need to use the active/passive failover functionality. 15 -* When using this configuration you can only create groups within the context of a single runtime. So for each runtime for which you want this functionality you need to add this store item to the Infra flow. 16 -* Each container needs a different port to communicate through. 17 -* Each container needs their own cluster. 18 -* From Deploy you can control the failover functionality. 14 +* Note that this is a custom XSLT that is designed for a specific cause. 15 +* Always try to understand the context before you implement this transformation. 16 +* Note that you need to define your specific namespace yourself when you want to implement this solution within your model. 19 19 20 20 ==== 3. License Information==== 21 - Part ofthestandard license agreementasagreeduponwhenusing the storeforthefirst time.19 +To use this store item you need to secure an additional license on the eMagiz platform. If you are interested in such a license please contact us at productmanagement@emagiz.com. 22 22 23 23 ==== 4. Relevant eMagiz Academy Microlearnings==== 24 24 25 -* [[Flow Configuration>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]] 26 -* [[Deploy Possibilities>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]] 23 +None 27 27 28 - //Would you please consult the privacy policy of eMagiz at the following[[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))25 +Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]]))) 29 29 30 30 31 31