> # Coherence Cluster: Configuration: Cache Configurations

> Column Display Related Tasks Related Topics

> This page displays all the cache configurations for a Coherence cluster.

> Cache configurations provide the ability to override the cache configuration file within a Grid Archive (GAR) with a different file. A cache configuration can be targeted at a Managed Server or a cluster. This allows an application to use of all the Coherence artifacts within a GAR, yet utilize a separate cache configuration file. An example of this would be to enable Proxy Service for Coherence*Extend connections to a cluster for a specific Managed Server or cluster.

> #### Column Display

> You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

> The following table lists all of the data points that you can display in columns on this page.

> Name | Description
> --- | ---
> Name | Name of this Coherence cluster Cache Configuration.
> Cache Configuration File | MBean Attribute: `CoherenceCacheConfigMBean.cacheConfigurationFile` Changes take effect after you redeploy the module or restart the server.
> JNDI Name | MBean Attribute: `CoherenceCacheConfigMBean.jndiName` Changes take effect after you redeploy the module or restart the server.
> Targets | MBean Attribute: `CoherenceCacheConfigMBean.targets` Changes take effect after you redeploy the module or restart the server.

> Related Tasks

> - Create cluster cache configurations
> - Import a custom cluster configuration
> - Configure Coherence clusters
> - Configure well known addresses
> - Configure Coherence logging

> Related Topics

> - Configuring and Managing Coherence Clusters
> - Using a Cluster Cache Configuration File
> - Developing Oracle Coherence Applications for Oracle WebLogic Server
> - Deploying Coherence Applications in WebLogic Server