# Configure and deploy Coherence deployment tiers

Before you begin

- Verify whether your domain's topology can support separate WebLogic Server clusters to represent Coherence deployment tiers. See Cluster Architectures in Administering Clusters for Oracle WebLogic Server.
- Create and package a Coherence Grid Archive (GAR) module for any application modules (Web application, EJB, etc.) that use Coherence. See Packaging Coherence Applications.

For optimal performance or scalability, Coherence is typically setup using WebLogic Server clusters. For example, a WebLogic Server cluster is used as a Coherence data tier and hosts one or more storage-enabled servers; a different WebLogic Server cluster is used as a Coherence application tier and hosts one or more applications; and lastly (if required) a different WebLogic Server cluster is used as a Coherence proxy tier and hosts one or more Coherence proxy servers. See Creating Coherence Deployment Tiers in Administering Clusters for Oracle WebLogic Server.

The main steps for configuring and deploying Coherence cluster tiers in WebLogic Server are:

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. Configure the Coherence cluster resources in your domain that will be associated with the corresponding WebLogic Server cluster tiers. See Create Coherence clusters
3. Configure a Coherence data tier. A data tier is a WebLogic Server cluster that is associated with a Coherence cluster and hosts any number of storage-enabled managed Coherence servers. Managed Coherence servers in the data tier store and distribute data (both primary and backup) on the cluster.
   1. Create a WebLogic Server cluster. See Configure clusters.
   2. Leave the default clustering mode (Unicast) and change the broadcast channel as required, or use the drop-down list and select Multicast and provide a different multicast address and port if required.
   3. Navigate to the Cluster > Coherence tab of the data tier cluster.
   4. Use the Coherence Cluster drop-down list and select a Coherence cluster to associate it with the WebLogic Server cluster. By default, the Managed Coherence Servers assigned to this WebLogic Server cluster will be storage-enabled coherence members (cache servers) as indicated by the Local Storage Enabled field.
4. Create managed Coherence servers for your data tier. See Create Managed Servers.
   1. Click the Yes option to add the server to an existing cluster, and use the drop-down list to select the data tier WebLogic Server cluster. The managed server inherits the Coherence settings from the data tier WebLogic Server cluster.
   2. Repeat this step to create additional managed servers as required.
5. Configure a Coherence application tier. An application tier is a WebLogic Server cluster that is associated with a Coherence cluster and hosts any number of storage-disabled managed Coherence servers. Managed Coherence servers in the application tier host applications (cache factory clients) and are Coherence cluster members.
   1. Configure a WebLogic Server cluster. Leave the default clustering mode (Unicast) and change the broadcast channel as required, or use the drop-down list and select Multicast and provide a different multicast address and port if required. See Configure clusters.
   2. Navigate to the Cluster > Coherence tab of the data tier cluster.
   3. Use the Coherence Cluster drop-down list and select a Coherence cluster to associate it with the WebLogic Server cluster. Disable storage on the application tier by clearing the Local Storage Enabled check box. The managed Coherence servers assigned to this WebLogic Server cluster will be storage-disabled Coherence members (clients). Servers in the application tier should never be used to store cache data.
6. Repeat step 4 to add managed Coherence servers to your application tier. However, use the Coherence Cluster drop-box to select the application tier WebLogic Server cluster, so the managed server inherits the Coherence settings from the application tier cluster. Repeat this step to create additional managed servers as required.
7. If necessary, configure a Coherence proxy tier. Managed Coherence proxy servers allow Coherence*Extend clients to use Coherence caches without being cluster members.
   1. Repeat step 5 to configure a Coherence proxy tier. Make sure to clear the Local Storage Enabled check box, so the managed Coherence servers assigned to this WebLogic Server cluster will be storage-disabled Coherence members (clients).
   2. Repeat step 4 to add managed Coherence servers to your proxy tier, using the Coherence Cluster drop-box to select the proxy tier WebLogic Server cluster, so the managed server inherits the Coherence settings from the proxy tier cluster.
   3. Repeat this step to create additional managed servers as required.
8. Deploy your Coherence GAR module to your WebLogic Server domain. Standalone GARs get deployed the same way as other JavaEE module. See Deploying Coherence Applications in WebLogic Server.

Related Tasks

- Cluster Architectures
- Overview of Coherence Clusters
- Developing Oracle Coherence Applications for Oracle WebLogic Server

Related Topics

- Administering Clusters for Oracle WebLogic Server
- Administering Node Manager for Oracle WebLogic Server