4.5 Synchronizing Configurations Between the Administration Server and Nodes

When you create a configuration, the configuration files—server.xml and vs_name-obj.conf—are created in the configuration store on the administration server.

When you create instances of the configuration, the configuration files are copied from the configuration store to the instance-specific configuration directories on the nodes, as in the following examples:

INSTANCE_HOME/net-soa.example.com/config
INSTANCE_HOME/net-dev.example.com/config

So the configuration files in the instance-specific configuration directories are usually identical to the configuration files stored in the configuration store on the administration server. In the following situations, a configuration stored on the administration server can be different from that of its instances.

• You modified a configuration on the administration server, by using the administration console or CLI, but have not yet deployed the modified configuration to its instances.

  You can rectify this out-of-sync situation by deploying the configuration as described in Section 4.3, "Deploying a Configuration."

• You changed the configuration of an instance manually, by editing a configuration file directly in the instance's config directory.

If you change the configuration of an instance manually by editing a configuration file—server.xml or vs_name-obj.conf in the INSTANCE_HOME/net-config_name/config directory, the next time you log in to the administration console and view the configuration, the alert Instance Configuration Modified is displayed. The alert indicates that the configuration stored on the administration server is different from the current configuration settings of one or more instances. The alert continues to be displayed till you synchronize the configuration stored on the administration server with that of all its instances, by doing one of the following:

• Pull the modified configuration from one of the modified instances back into the configuration store of the administration server.

• Discard the instance-specific configurations by redeploying the configuration from the administration server to the modified instances.

You can synchronize a configuration on the administration server with its instances by using either the administration console or the CLI.

Note:

The CLI examples in this section are shown in shell mode (tadm>). For information about invoking the CLI shell, see Section 2.3.1, "Accessing the Command-Line Interface."

Synchronizing Configurations on the Administration Server and Administration Nodes Using the Administration Console

To synchronize a configuration stored on the administration server with that of its instances by using the administration console, do the following:

1. Log in to the administration console, as described in Section 2.3.2, "Accessing the Administration Console."

2. Click the Configurations button that is situated at the upper left corner of the page.

   A list of the available configurations is displayed.

3. Select the configuration for which one or more instances have been modified. You can identify the configuration from its status, which would be Instance Configuration Modified.

   The Instances page of the configuration is displayed, with the Instance Configuration Modified button at the top of the main pane.

4. Click the Instance Configuration Modified button.

   The Deploy Configuration dialog box is displayed.

   • If you want to discard all of the instance-specific configurations and deploy the configuration that is currently stored on the administration server to all the instances, select the Discard Instance Changes option.

   • If you want to pull the configuration of a modified instance to the administration server, select Pull and Deploy Configuration from Node, and select the appropriate administration node.

     For each administration node, you can review the names of the configuration files that are different from the configuration store on the administration server, by clicking View Details.

5. Click OK.

   A message is displayed confirming that the configuration was successfully deployed.

6. Click Close.

Synchronizing Configurations on the Administration Server and Administration Nodes Using the CLI

To discard the instance-specific configurations and deploy the configuration that is currently stored on the administration server to all the instances, run the following command:

tadm> deploy-config -- force config_name

To pull configuration files from an instance to the configuration store on the administration server, run the following commands:

tadm> pull-config --config=config_name node

tadm> deploy-config config_name

For more information about the CLI commands mentioned in this section, see the Oracle Traffic Director Command-Line Reference or run the commands with the --help option.