From the Coherence Cluster Members section, click to select the managed Coherence servers or WebLogic Server clusters that are to be part of the Coherence cluster or skip this section if managed Coherence servers and WebLogic Clusters are yet to be defined.

For details on configuring the clustering mode, see Configure Cluster Communication. The default cluster listen port (7574) does not need to be changed for most clusters.

From the Coherence Cluster Addressing section, select the clustering mode or keep the default settings.

From the Create a Coherence Cluster Configuration page, enter a name for the cluster in the Name field and click Next.

From the Summary of Coherence Clusters page, click New.

From the WebLogic Server Administration Console Domain Structure pane, expand Environment and click Coherence Clusters.

Managed Coherence servers are typically setup in tiers that are based on their type: a data tier for storing data, an application tier for hosting applications, and a proxy tier that allows external clients to access caches.įigure 12-1 shows a conceptual view of a Coherence cluster in a WebLogic Server domain. Managed Coherence servers can be explicitly associated with a Coherence cluster or they can be associated with a WebLogic Server cluster that is associated with a Coherence cluster. Managed servers configured as Coherence cluster members are referred to as managed Coherence servers.

Multiple WebLogic Server clusters can be associated with a Coherence cluster and a WebLogic Server domain typically contains a single Coherence cluster. They use different clustering protocols and are configured separately. The commands are automatically available when connected to an Administration Server domain runtime MBean server.Ĭoherence clusters are different than WebLogic Server clusters. WLST includes a set of commands that can be used to persist and recover cached data from disk. When running Coherence within WebLogic Server in a managed Coherence Servers environment, WebLogic Server domain runtime MBean server collects JMX information from the management proxy and this information is accessible by using WLST. Accessing Coherence MBeans by Using WLST.The WLST is a command-line interface that you can use to automate domain configuration tasks, including configuring and managing Coherence clusters.

Managed Coherence servers expose several cluster member settings that can be configured for a specific domain.Ī single-server cluster is a cluster that is constrained to run on a single managed server instance and does not access the network. A CoherenceClusterSystemResource instance is created using the WebLogic Server Administration Console or WLST.Ĭoherence supports different topologies within a WebLogic Server domain to provide varying levels of performance, scalability, and ease of use.Ī Coherence cluster resource exposes several cluster settings that can be configured for a specific domain. The cluster is represented as a single system-level resource (CoherenceClusterSystemResource). An application interacts with the data in a local cache and the distribution and backup of the data is performed automatically across cluster members.Ī WebLogic Server domain typically contains a single Coherence cluster. Coherence clusters consist of multiple Managed Coherence server instances that distribute data in-memory to increase application scalability, availability, and performance.

Oracle coherence web