Master site

The master site is a central repository that other sites can reference for shared configuration information. Changes to interface objects are dynamically applied to the running Cloverleaf process. This is accomplished by reloading the cache on all running processes.

To support multiple environments on the same machine, you can reference multiple master sites for storage of configuration information. For example, test, dev, and QA environments.

Master site settings for individual sites are migrated forward during site promotion. Root master site settings are not migrated.

Master Site configuration is available through CLAPI.

In the IDE, the master site’s configurations are in italics.

If a master site configuration has a name conflict with the current site, then the IDE only shows one entry for the named resource. The one in the current site is the effective one.

The master site feature includes:

  • Root-level master site configuration:

    When defined in the Root Preferences dialog box, the root-level master site applies to all sites by default.

  • Site-level master site configuration:

    The site-level master site configuration can override the defined root-level master site.

  • Master site configuration purge/reload.
  • Master sites are only one level deep. There is no nesting.

The master site contain configuration objects that are shared between sites. Shared objects include:

  • Alerts
  • Engine output
  • Message format definitions
  • Tcl procs
  • Table configurations
  • Xlate configurations
  • SMAT database/error database auto-complete suggestions

In the Cloverleaf GUI, from Options > Root Preferences, you can select which master site all sites reference by default.

From Options > Site Preferences, you can select which master site the current site references for shared configuration data. This overrides the Root Preferences default.

Information on multiple master sites is also available. See: