Changes for page Change Detection - State Generation
Last modified by Carlijn Kokkeler on 2024/06/07 15:27
From version 17.1
edited by Erik Bakker
on 2022/05/02 10:01
on 2022/05/02 10:01
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - BasicAuth - Check1 +Active/Passive Failover - Content
-
... ... @@ -2,18 +2,20 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 - Withthe help of this storecomponent,youcanvalidateif the basicauthenticationprovidedbyone single entity is conformedtohatyouwould haveexpected.Incasethatis not true,eMagizwill return'Unauthorized'to theclient.5 +This store item can easily add the required configuration to your infra flow to make the active/passive failover functionality possible within the runtime context. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 -With the help of this store component, you canvalidateifthebasicauthentication providedby one singleentity is conformed to whatouwould haveexpected. In case thatisnottrue,eMagiz willreturn'Unauthorized'toheclient.10 +With the help of this store item, you can make the active/passive failover functionality possible within the runtime context. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that this functionality can only validate one specific set of credentials. If multiple clients call your endpoint you should change the groovy script accordingly. 15 -* Any custom additions that are needed for your specific use cases need to be created by you and eMagiz will not create it for you. 16 -* Please check out the following link to learn a bit more about Groovy: https://www.tutorialspoint.com/groovy/index.htm 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. 17 17 18 18 ==== 3. License Information==== 19 19 Part of the standard license agreement as agreed upon when using the store for the first time. ... ... @@ -20,9 +20,10 @@ 20 20 21 21 ==== 4. Relevant eMagiz Academy Microlearnings==== 22 22 23 -None 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"]] 24 24 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/?]])))28 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]))) 26 26 27 27 28 28