Basically this is true, but how you can create (officially supported way) those apps locally on SHC nodes? You cannot do it on CLI and GUI there isn't option for creating app in any SHC member! When...
See more...
Basically this is true, but how you can create (officially supported way) those apps locally on SHC nodes? You cannot do it on CLI and GUI there isn't option for creating app in any SHC member! When you are creating a new SHC, you must use empty nodes which cannot contains old apps from SH. If you need to migrate old SH into SHC then you must replicate those apps and other data via deployer. This means that you must create an empty app (just base structure like app_xx/bin, app_xx/default, app_xx/metadata, app_xx/lookups) on deployer and then push it into your SHC members. After you have done it this way, you can add other KOs like dashboards, reports, alerts etc. via GUI on any SHC members and those are replicated correctly between nodes. What will happen those files in SHC member app_xx/local folder (and default) is depending on your push settings like @kiran_panchavat already told. One notice your SHC size. It should always have odd number of members. RAFT protocol which are keeping your SHC up and running with correct captain needs this. Otherwise there are big possibility that it cannot elect a new captain after something has happened to old captain!