Master Configuration
Master configuration, also referred to as master copy, is the complete set of configuration provisioned by the portal engine to the gateway cluster for a subscription. If the local configuration of one or more gateway instances is out-of-sync, they can be fully re-provisioned with the master configuration.
The master configuration for a gateway cluster is composed of two parts: base and access.
The base configuration is set by the portal administrator, also referred to as the API provider, and does not change when application developers push updates from the portal. Base configuration is not environment specific.
The access configuration is updated when API subscriptions are created, and used by partners and applications. It contains information controlling the access to an API by certain organizations, users, and applications, which are environment-specific entities.
To use the master configuration for the first time, copy the entire set of the cluster configuration to ASG_CONFIG_HOME/environments/<env_name>/<gateway_name>/<project_name>. After that, any change to the base configuration must be made on both the master configuration and the gateway instances' local configuration.
When moving the gateway configuration from a development environment to a production environment, move the base configuration manually. Do not move the access configuration in the development environment because it might differ from the configuration in the production environment.
Use the tool, asg-tools, provided by API Exchange Gateway to export or import the base configuration from the development environment and then import it into the production environment. Access configurations in each environment remain unaffected. See TIBCO API Exchange Gateway Release Notes for details on using the tool asg-tools.
By default, the master copy is not maintained on the portal engine. This is not advisable for a development environment.
For a production environment, you can choose to maintain the master copy in the portal engine by enabling master configuration from the gateway configuration UI > Portal Engine Properties.