# Change a blade's configuration

## Change configuration of a Caplin-supplied blade

Some blades supplied by Caplin come with configuration overrides that are defined in blade subdirectories of _global_config/overrides_. You can override the configuration of these blades by editing the files in these subdirectories.

For example, Caplin supplies a RefinerService blade for the Transformer. When this blade is deployed for the first time, the deploy command (`./dfw deploy`) copies the _RefinerService/Transformer/etc_ directory to the overrides directory _global_config/overrides/RefinerService_. You can then override the configuration of the RefinerService blade by editing the configuration files in _global_config/overrides/RefinerService_.

**💡 TIP**\
You don’t normally need to customize _built-in_ Config blades, other than to change port numbers (see [Check port numbers](cdf-change-server-specific-configuration.md#check-port-numbers) in How can I... [Change server-specific configuration](cdf-change-server-specific-configuration.md)).

**💡 TIP**\
When you’ve changed the configuration of a production system, we recommend that you run the [`dump`](cdf-the-deployment-framework-command-utility-dfw.md#dump) command immediately, before restarting the system. The most up-to-date configuration data will then be readily available if Caplin Support need it to help fix a problem with your running system. If you don’t run `dump` before restarting, you’ll have to stop the running system to get the configuration needed to diagnose a fault, or copy the configuration manually from the various directories where it’s located.

## Check and merge blade configuration overrides

If a blade is already deployed with configuration overrides, when a new kit for that blade is deployed, the new kit doesn’t remove or modify the existing overrides. However, when you deploy the new kit, the Deployment Framework does warn you when the new kit contains configuration overrides that clash with your existing overrides and details the clashes.

If there are clashes, you should compare the configuration overrides in the new blade kit against the existing overrides for the blade as defined in _global_config/overrides_, and merge any differences.

**💡 TIP**\
The release note for the blade will detail any changes to configuration overrides in the blade kit.

---

**See also:**

* [DataSource For C Configuration Syntax Reference](../datasource/datasource-configuration-syntax.md) (Explains the syntax of Caplin Platform blade configuration.)