Automatically sharing configurations among replicas

You can configure one collective controller server.xml include file in a replica set and automatically update the configuration of other replicas in the set. Automatic sharing of configurations means that you do not need to manually update the configurations of other replicas. Automatic sharing of configurations is especially useful for collectives that use auto scaling.

1. Create a configDropins directory for the controller with the configuration you want to share among replicas.

   If the controller of the replica set does not already have the configDropins/defaults directory, create the $WLP_USER_DIR/servers/server_name/configDropins/defaults directory for the controller.

   Note: For information about precedence among files in configDropins subdirectories, see Using the configuration dropins folder to specify server configuration. The topic mentions both the configDropins/defaults directory and a configDropins/overrides directory. Controller configurations dropped into a configDropins/overrides directory are not shared among replicas. To share configurations among replicas, you must use the configDropins/defaults directory.
2. Share the controller configuration with other replicas in the replica set.
   Note: When sharing controller configuration with other replicas, the <collectiveHostAuthInfo> element must be configured with specific SSH key paths or a SAF keyring configuration.

   • Drop the configuration of the replica set controller into its configDropins/defaults directory.

     For example, copy the server.xml include file of the controller to its configDropins/defaults directory.

   • Use ControllerConfigMBean operations to list, add, or remove the shared configuration files of a collective controller.

     Configuration files are stored in the $WLP_USER_DIR/servers/server_name/configDropins/defaults directory of the controllers and are shared with the configDropins/defaults directory of the replicas.

     Use Jython scripts or a Java client such a JConsole to perform the following collective controller ControllerConfigMBean operations:

     listSharedConfig

     The listSharedConfig operation lists the files in the shared configuration directory of the replica.

     addSharedConfig

     The addSharedConfig operation adds a configuration to a file and stores the file in the configDropins/defaults directory of each replica. You must specify two parameters for the operation:

     fileName

     The file name of the controller configuration to share. If you specify a file name that exists in the shared configuration directory, the existing file is overwritten. (String)

     config

     The content of a valid server.xml include file. (String)

     For example:

     <?xml version="1.0" encoding="UTF-8" ?>
     <server>
       <logging traceSpecification="com.ibm.ws.collective.repository.internal.SharedConfigManager=all"/>
     </server>

     removeSharedConfig

     The removeSharedConfig operation removes a file from the configDropins/defaults directory of each replica. You must specify a parameter for the operation:

     fileName

     The file name of the controller configuration to delete from the shared configuration directory of each replica. (String)

   • When sharing controller configuration with other replicas, the <collectiveHostAuthInfo> element must be configured with specific SSH key paths or a SAF keyring configuration.

   The controller configuration automatically synchronizes with the configuration dropins directories of every other replica in the replica set. When you add a replica to a controller that automatically shares its configuration, the content of the configDropins/defaults directory of the controller is replicated to the new replica. Any changes that you make to scaling policy definitions for one controller automatically synchronize with configurations in the configuration dropins directories of the other replicas.

   If the controller configuration does not automatically synchronize with the configuration of other replicas, check the controller and replica logs. Also, if you used the configDropins/defaults directory to share the controller configuration, ensure that configuration monitoring is not turned off. By default, configuration monitoring is enabled. If configuration monitoring is unavailable, you can use the FileNotificationMBean to inform the controller of configuration changes, and then the changes are shared with the replicas. Configurations stored by ControllerConfigMBean operations are automatically shared among replicas whether configuration monitoring is enabled or not. See Controlling dynamic updates.