Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create cluster cache configurations

Before you begin

Create and configure a Coherence cluster. See Create Coherence clusters and Configure Coherence clusters.

A Coherence cache configuration file defines the caches and services that are used by an application. Typically, a cache configuration file is included in a GAR module. A GAR is deployed to all managed Coherence servers in the data tier and can also be deployed as part of an EAR to the application tier. The GAR ensures that the cache configuration is available on every Oracle Coherence cluster member. However, there are use cases that require a different cache configuration file to be used on specific managed Coherence servers. For example, a proxy tier requires access to all artifacts in the GAR but needs a different cache configuration file that defines the proxy services to start..

You can use the Administration Console to define a cluster cache configuration. A cache configuration file can be associated with WebLogic clusters or Managed Coherence Servers at runtime. In this case, the cache configuration overrides the cache configuration file that is included in a GAR. You can also omit the cache configuration file from a GAR file and assign it at runtime. To override a cache configuration file at runtime, the cache configuration file must be bound to a JNDI name. The JNDI name is defined using the override-property attribute of the <cache-configuration-ref> element. The element is located in the coherence-application.xml file that is packaged in a GAR file. For details on the coherence-application.xml file, see Oracle Fusion Middleware Developing Oracle Coherence Applications for Oracle WebLogic Server. For more information on importing a cache configuration file, see Using a Cluster Cache Configuration File.

To configure a cluster cache configuration:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, expand Environment and select Coherence Clusters.
  3. Select the cluster for which you want to create a cluster cache configuration.
  4. Select the Configuration: Cache Configurations page, and click New.
  5. On the Create a Cache Configuration page, set the following cache configuration properties:
    1. Name: Enter the name of this cluster cache configuration.
    2. JNDI Name: Enter the JNDI name to which the cache configuration file is bound. This JNDI name is prefixed with cache-config/ and must match the value in the override-property of your cache-configuration-ref entry in coherence-application.xml. For example, JNDI name of ExamplesGAR must match override-property of cache-config/ExamplesGAR.
    3. Cache Configuration File: Enter the full path to the cache configuration file. Alternatively, you may specify a URL.
    4. Import Cache Configuration File: Select this option to import the cache configuration file from the specified location into the WebLogic Server directory structure.

      If you do not select this option, the cache configuration file is loaded directly from the specified location when the server is started.

  6. Click Save.
  7. Select the Targets page to select the WebLogic Server instances or clusters to which this cluster cache configuration is targeted. Click Save.
  8. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).


The cluster cache configuration is listed from the Configuration: Cache Configurations page of the Coherence cluster settings console page.

Back to Top