This chapter describes how to monitor, control, and configure clusters. A WebLogic Server cluster consists of multiple WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability.
A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster's capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.
For more information on clusters, see Administering Clusters for Oracle WebLogic Server.
This chapter includes the following sections:
This section describes how to create new clusters. This section includes the following tasks:
A configured cluster is a cluster in which you manually configure and add each server instance.
To create a new configured cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
The Clusters table displays information about the clusters that have been configured in the current domain, such as:
Click Create, then select Cluster.
Define the configuration options for your new configured cluster on each of the following pages:
Click Create.
On the Cluster Properties page, define the general cluster properties for your new configured cluster:
Name: enter a unique name for your configured cluster.
Messaging Mode: select the messaging mode you want to use for this cluster.
Unicast Broadcast Channel: if you are using the unicast messaging mode, enter the unicast broadcast channel. This channel is used to transmit messages with the cluster. If you do not specify a channel, the default channel is used.
Multicast Address: if you are using the multicast messaging mode, enter the multicast address of the new configured cluster. A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255. The valid range is from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0. You should avoid using multicast addresses in the range x.0.0.1. This address must be unique to this cluster and should not be shared by other applications.
Multicast Port: if you are using the multicast messaging mode, enter the multicast port of the new configured cluster.The multicast port is used by cluster members to communicate with each other. Valid values are between 1 and 65535.
For more information about these fields, see Configuration Options.
On the Add Servers page, you can optionally add one or more servers to the new configured cluster by moving the servers from the Available column into the Chosen column.
For more information about these fields, see Configuration Options.
On the Review page, review the configuration for your new configured cluster.
For more information about these fields, see Configuration Options.
A dynamic cluster is a cluster that contains one or more generated (dynamic) server instances that are based on a single shared server template.
To create a new dynamic cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
The Clusters table displays information about the clusters that have been configured in the current domain, such as:
Click Create, then select Dynamic Cluster.
Define the configuration options for your new dynamic cluster on each of the following pages:
Click Create.
On the Cluster Properties page, define the general cluster properties for your new dynamic cluster:
Name: enter a unique name for your dynamic cluster.
Messaging Mode: select the messaging mode you want to use for this cluster.
Unicast Broadcast Channel: if you are using the unicast messaging mode, enter the unicast broadcast channel. This channel is used to transmit messages with the cluster. If you do not specify a channel, the default channel is used.
Multicast Address: if you are using the multicast messaging mode, enter the multicast address of the new dynamic cluster. A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255. The valid range is from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0. You should avoid using multicast addresses in the range x.0.0.1. This address must be unique to this cluster and should not be shared by other applications.
Multicast Port: if you are using the multicast messaging mode, enter the multicast port of the new configured cluster.The multicast port is used by cluster members to communicate with each other. Valid values are between 1 and 65535.
For more information about these fields, see Configuration Options.
On the Dynamic Server Properties page, define the dynamic server properties for your new dynamic cluster:
Dynamic Cluster Size: enter the number of dynamic server instances you want in your new dynamic cluster.
Max Dynamic Cluster Size: enter the maximum number of running dynamic server instances that can be assigned to this dynamic cluster.
Server Name Prefix: specify the naming convention you want to use for the dynamic servers in your dynamic cluster.
Select either Create a New Server Template Using Domain Defaults or Clone an Existing Server Template For This Cluster. If you choose to clone an existing template, select the template in Server Template to Clone. Server templates are used to configure the characteristics that are common to all the server instances in your dynamic cluster. If you do not have any server templates configured, one is automatically generated for you.
For more information about these fields, see Configuration Options.
On the Machine Bindings page, s elect the method you want to use to distribute the dynamic servers in your dynamic cluster across machines. Select Use any machine configured in this domain, Use a single machine for all dynamic servers, or Use a subset of machines in this domain. If you choose Use a single machine for all dynamic servers, select the machine you want to use from the Selected Machine dropdown menu. If you choose Use a subset of machines in this domain, enter the machine name match expression in Machine Name Match Expression.
For more information about these fields, see Configuration Options.
On the Listen Port Bindings page, select how the dynamic servers should be bound to listen ports. Listen ports for dynamic servers can be specified in a server template or can be dynamically generated to be unique.
Select Assign each dynamic server unique listen ports to create unique listen ports for each dynamic server. Enter the desired listen port and SSL listen port for the first dynamic server instance in Listen Port for First Server and SSL Listen Port for First Server.
Select Assign each dynamic server fixed listen ports to assign the same listen port and SSL listen port for all dynamic servers. Enter the desired listen port and SSL listen port in Listen Port and SSL Listen Port.
For more information about these fields, see Configuration Options.
On the Review page, review the configuration for your new dynamic cluster.
For more information about these fields, see Configuration Options.
This section describes how to monitor clusters. This section includes the following tasks:
To monitor the runtime status of all clusters configured in a domain:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
The Clusters table displays information about the clusters that have been configured in the current domain, such as:
Cluster Name
Status
Cluster Type
Servers
Cluster Address
Cluster Messaging Mode
Migration Basis
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
Select the name of the cluster for which you want to view configuration information, such as the cluster's default network communications.
To monitor the status of servers in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Summary.
The Summary table displays information about the status of all servers in a cluster, such as:
Name
State
Machine
Listen Address
Listen Port
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To monitor the health of a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Health.
The Health summary page allows you to monitor health information for the cluster and its subsystems.
For more information, see Configuration Options.
To monitor the server instances in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Servers.
The Servers table displays information about the servers in a cluster, such as:
Server
Type
Status
Cluster
Machine
State
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To monitor all deployments in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Deployments.
The Deployments table on the summary page displays information about all applications and modules deployed to the cluster, such as:
Name
State
Health
Type
Deployment Order
Targets
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
To monitor cluster deployment information, select the appropriate pages:
Web Applications: monitor Web applications deployed to your cluster; includes information about the application such as the machine and server instance on which the application is deployed and statistics about the servlets and sessions associated with the Web application
For more information, see Configuration Options.
Resource Adapters: monitor the status of inbound listeners and outbound connection pools
For more information, see Configuration Options.
EJBs: monitor statistics and information about stateless, stateful, entity, singleton, and message-driven EJBs
For more information, see Configuration Options.
Web Services: monitor all the Web services that are deployed to this cluster
For more information, see Configuration Options.
Web Service Clients: monitor all Web service clients in this cluster
For more information, see Configuration Options.
JAX-RS Applications: monitor all the JAX-RS applications that are running in this cluster
For more information, see Configuration Options.
Workload: monitor statistics for the Work Managers, constraints, and policies that are configured for application deployments in this cluster
For more information, see Configuration Options.
To monitor the JDBC data sources associated with a specific cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select JDBC Data Sources.
The JDBC data sources table displays information the status of all JDBC data sources, such as:
Name
Type
Resource
Scope
Server
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To monitor the status of JMS servers associated with a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Messaging.
To monitor messaging information for this cluster, select the appropriate pages:
JMS Servers: monitor the JMS servers that have been created in the current WebLogic Server cluster
For more information, see Configuration Options.
Store-and-Forward Agents: monitor SAF agent statistics and perform message management operations, such as pausing incoming requests to the agent
For more information, see Configuration Options.
JMS Resources: monitor all JMS resources that have been created for all the JMS system modules, including queue and topic destinations, connection factories, JMS templates, destination sort keys, destination quota, distributed destinations, foreign servers, and store-and-forward parameters
For more information, see Configuration Options.
JMS Modules: monitor the JMS modules created in this cluster
For more information, see Configuration Options.
Messaging Bridges: monitor the status of all messaging bridges configured on active servers in this cluster
For more information, see Configuration Options.
Optionally, select View to access the following table options on any of the pages:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To monitor failover information for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Failover.
The Failover summary page displays the following information:
Total primary sessions
Total session replicas
Total number of session updates to the backup cluster
The Failover table displays further failover and status information for the cluster, such as:
Server
Type
Machine
State
Backup Server
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To monitor the performance summary of a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Performance Summary.
The Performance Summary page displays general performance information, as well as performance information about the servlets, JSPs, and data sources associated with this cluster.
Click Show Metric Palette to select the metrics you want to view.
Select View to access table options.
Select Overlay to access additional table options.
Because some administrative tasks (such as deployments, service migrations, and attempts to start or stop Managed Servers) are completed immediately and others take varying amounts of time to complete, the Asynchronous Tasks summary page allows you to monitor the completion status of all tasks.
To monitor the status of asynchronous tasks in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Monitoring, then select Asynchronous Tasks.
The Asynchronous Tasks summary page allows you to monitor the completion status of all tasks by displaying information such as:
Description
Type
Status
Begin Time
End Time
Targets
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
This section describes how to control clusters. This section includes the following topics:
You can start, resume, suspend, or shutdown the server instances assigned to a cluster. For information on how the servers in a cluster transition from STANDBY or ADMIN to the RUNNING state, see "Understanding Server Life Cycle" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Before you begin:
Control operations on Managed Servers require starting the Node Manager. Starting Managed Servers in Standby mode requires the domain-wide administration port.
To control the server instances in the clusters configured in a domain:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
The Clusters table displays information about the clusters that have been configured in the current domain, such as:
Name
Status
Cluster Type
Servers
Cluster Address
Cluster Messaging Mode
Migration Basis
Default Load Algorithm
Replication Type
Cluster Broadcast Channel
For more information about these fields, see Configuration Options.
In the table, select the row for the cluster you want to manage, and then select one of the following control operations:
Start: moves server instances in the cluster from the SHUTDOWN state to RUNNING.
Resume: moves server instances in the cluster from the STANDBY or the ADMIN state to RUNNING.
Suspend: select an option to transition the server instances in the cluster from the RUNNING state to the ADMIN state:
When work completes: moves server instances in the cluster from the RUNNING state to the ADMIN state, allowing work in process to be handled gracefully. While in the SUSPENDING state, Work Managers complete in-flight processing for pending work in application threads.
Force shutdown now: immediately moves server instances in the cluster from the RUNNING state to the ADMIN state, without handling work in process gracefully.
Shutdown: select an option to shutdown the server instances in a cluster:
When work completes: gracefully stops server instances in the cluster. New requests are rejected but in-flight requests are completed before the server instance stops.
Force suspend now: immediately stops server instances in the cluster. In-flight requests are dropped, no new requests are accepted, and the server instance immediately stops.
Restart SSL: restarts the SSL listen sockets so that keystore changes take effect.
For more information, see Configuration Options.
Optionally, click Create to create a new cluster. For more information on creating clusters, see Create clusters.
To control on-demand scaling in a dynamic cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the dynamic cluster you want to configure.
An overview page displays information related to the dynamic cluster.
From the WebLogic Cluster dropdown menu, select Control, then select Scale Up or Scale Down.
From the Scale Up or Scale Down page you can view the following values:
Current Number of Running Servers
Current Cluster Size
Maximum Cluster Size
Minimum Cluster Size
In the Desired Server Count field, enter the desired number of running dynamic server instances you want in this cluster. Alternatively, you can use the arrows to change the value in this field.
Click Scale Up/Down.
For more information, see Configuration Options.
You can start, resume, suspend, or shutdown the server instances assigned to a cluster. For information on how the servers in a cluster transition from STANDBY or ADMIN to the RUNNING state, see "Understanding Server Life Cycle" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Before you begin:
Control operations on Managed Servers require starting the Node Manager. Starting Managed Servers in Standby mode requires the domain-wide administration port.
To control the server instances in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
The Clusters table displays information about the clusters that have been configured in the current domain.
In the Clusters table, select the name of the cluster you want to manage.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Control, then select Servers.
In the Servers (Control) table, select the row for the server instance you want to manage, and then select one of the following control operations:
Start: moves the server instance from the SHUTDOWN state to RUNNING.
Resume: moves the server instance from the STANDBY or the ADMIN state to RUNNING.
Suspend: select an option to transition the server instance from the RUNNING state to the ADMIN state:
When work completes: moves the server instance from the RUNNING state to the ADMIN state, allowing work in process to be handled gracefully. While in the SUSPENDING state, Work Managers complete in-flight processing for pending work in application threads.
Force shutdown now: immediately moves the server instance from the RUNNING state to the ADMIN state, without handling work in process gracefully.
Shutdown: select an option to shutdown the server instance.
When work completes: gracefully stops the server instance. New requests are rejected but in-flight requests are completed before the server instance stops.
Force suspend now: immediately stops the server instance. In-flight requests are dropped, no new requests are accepted, and the server instance immediately stops.
Restart SSL: restarts the SSL listen sockets so that keystore changes take effect.
For more information, see Configuration Options.
This section describes how to configure clusters. This section includes the following tasks:
To configure general settings for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select General Settings.
From the General Settings page you can define the general settings for a cluster, such as:
Name
Default Load Algorithm
Cluster Address
Number of Servers in Cluster Address
Enable Transaction Affinity
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced settings for this cluster.
Click Save.
To configure JTA for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Java Transaction API (JTA).
From the Java Transaction API (JTA) page you can define the JTA settings for a cluster, such as:
Timeout Seconds
Abandon Timeout Seconds
Before Completion Iteration Limit
Max Transactions
Max Unique Name Statistics
Checkpoint Interval Seconds
Forget Heuristics
Unregister Resource Grace Period
Execute XA Calls in Parallel
Enable Two Phase Commit
Enable Tightly Coupled Transactions
Enable Cluster-Wide Recovery
Write Recovery Logs When Determiners Configured
Determiners
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced settings for this cluster.
Click Save.
Clusters use messaging for sharing session, load balancing and failover, JMS, and other information between cluster members. Clusters can use either unicast or multicast messaging. Multicast is a simple broadcast technology that enables multiple applications to subscribe to a given IP address and port number and listen for messages, but requires hardware configuration and support. Unicast does not have these requirements.
To configure messaging for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Messaging.
From the Messaging page, you can define the messaging settings for your cluster, such as:
Messaging Mode
Unicast Broadcast Channel
Multicast Address
Multicast Port
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced settings for this cluster.
Click Save.
To configure server instances in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Servers.
From the Servers page, you can define settings for server instances in the cluster, such as:
Server Template
Current Cluster Size
Maximum Cluster Size
Minimum Cluster Size
Server Name Prefix
Enable Calculated Listen Ports
Enable Calculated Machine Associations
Machine Name Match Expression
For more information about these fields, see Configuration Options.
From the Servers page, you can also view information for the servers configured in the cluster, such as:
Name
Type
Machine
Listen Port
Listen Address
To add a new server instance to this cluster, click Add and select the server instance you want to add. To remove a server instance from this cluster, select the row for the server instance and click Remove.
Click Save.
To configure replication for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Replication.
From the Replication page, you can configure how WebLogic Server will replicate HTTP session state across a cluster, including settings such as:
Cross-cluster Replication Type
Remote Cluster Address
Replication Channel
Data Source for Session Persistence
Persist Sessions on Shutdown
Secure Replication Enabled
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced settings for this cluster.
Click Save.
If a clustered server fails, Node Manager can automatically restart the server instance and its services on another machine. You can specify the machines where Node Manager can restart migratable servers and also the data source used during server migration.
To configure server migration in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Migration.
From the Migration page, you can specify settings related to cluster migration, such:
Candidate Machines for Migratable Servers
Migration Basis
Data Source for Automatic Migration
Auto Migration Table Name
Member Death Detector Enabled
Member Discovery Timeout
Leader Heartbeat Period
Additional Migration Attempts
Pause Time Between Migration Attempts
For more information about these fields, see Configuration Options.
Click Save.
This section describes how to configure and control singleton services.
This section includes the following sections:
To configure general settings for a cluster singleton service:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Singleton Services.
In the Singleton Services table, select the singleton service you want to configure.
Select Configuration, then select General.
From the General page, you can define settings for the class associations of this singleton service, such as:
Name
Class Name
Additional Migration Attempts
Sleep Time Between Attempts
For more information about these fields, see Configuration Options.
Click Save.
To configure migration for a cluster singleton service:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Singleton Services.
In the Singleton Services table, select the singleton service you want to configure.
Select Configuration, then select Migration.
From the Migration page, you can define migration settings for this singleton service, such as:
Name
User Preferred Server
Constrained Candidate Servers
For more information about these fields, see Configuration Options.
Click Save.
To create notes for a singleton service:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Singleton Services.
In the Singleton Services table, select the singleton service you want to configure.
Select Notes.
On the Notes page, enter your notes.
For more information about these fields, see Configuration Options.
Click Save.
To migrate a cluster singleton service:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Singleton Services.
The Singleton Services table displays information about the singleton services, such as:
Name
Class Name
Cluster Name
Preferred Server
Candidate Servers
Constrained Candidate Servers
For more information about these fields, see Configuration Options.
In the table, select the singleton service you want to migrate.
Select the Control page. In the table, select the row of the singleton service you want to migrate.
For more information, see Configuration Options.
Click Migrate.
On the Migrate Singleton Services page, select a hosting server from the New Hosting Server menu.
Click OK.
Job scheduling makes Java CommonJ timers cluster-aware and provides the ability to execute jobs periodically anywhere in a cluster without dependency on a particular server instance.
To configure job scheduling in a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Scheduling.
From the Scheduling page, you can define configuration settings that specify how information is shared across servers in a cluster.
In the Data Source for Job Scheduler field, select the data source to use.
In the Job Scheduler Table Name field, enter a table name to use for storing timers active with the job scheduler.
Click Save.
For more information, see Configuration Options.
To configure overload for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Overload.
From the Overload page, you can configure the cluster-wide defaults that control how WebLogic Server instances in this cluster should react in the case of an overload or failure condition. The settings you can define include:
Shared Capacity for Work Managers
Failure Action
Panic Action
Free Memory Percent High Threshold
Free Memory Percent Low Threshold
Max Stuck Thread Time
Stuck Thread Count
For more information about these fields, see Configuration Options.
Click Save.
WebLogic Server provides a self-health monitoring capability to improve the reliability and availability of servers in a WebLogic Server domain. Selected subsystems within each server instance monitor their health status based on criteria specific to the subsystem
To configure health monitoring characteristics for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Health Monitoring.
From the Health Monitoring page, you can configure health monitoring characteristics for this cluster, such as:
Inter-Cluster Comm Link Health Check Interval
Health Check Interval
Health Check Periods Until Fencing
Fencing Grace Period
For more information about these fields, see Configuration Options.
Click Save.
To configure HTTP settings for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select HTTP.
From the HTTP page, you can define the HTTP settings for this cluster, such as:
Frontend Host
Frontend HTTP Port
Frontend HTTPS Port
For more information about these fields, see Configuration Options.
Click Save.
To configure Coherence settings for a cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster you want to configure.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Administration, then select Coherence.
From the Coherence page, you can select the Coherence cluster you want to use for this cluster and define settings such as:
Local Storage Enabled
Coherence Web Local Storage Enabled
For more information about these fields, see Configuration Options.
Click Save.
To create notes for cluster configuration:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, click the name of the cluster for which you want to create notes.
An overview page displays information related to the server.
From the WebLogic Cluster dropdown menu, select Administration, then select Notes.
On the Notes page, enter your notes.
Click Save.
For more information, see Configuration Options.
To configure on-demand scaling for a dynamic cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the row of the dynamic cluster you want to scale up or down.
Click Scale Up/Down.
On the Scale Up/Down page, use the arrows in the Desired Server Count field to select the number of running server instances you want in your dynamic cluster.
Click Scale Up/Down.
Elasticity enables the automatic scaling of dynamic clusters and re-provisioning of associated resources based on demand. Enable elasticity by constructing policies to monitor resource usage and set actions to enable specific scaling or other administrative actions according to those policies. You can configure elasticity to provide on-demand scaling, calendar based scaling, or policy based scaling.
This section includes the following tasks
An elasticity policy monitors resource utilization in a dynamic cluster to determine scaling decisions, or other administrative actions, such as adding servers to a dynamic cluster or adjusting the size of a JDBC connection pool. When an elasticity policy evaluates to true, the one or more actions associated with that policy are executed.
To monitor the elastic policies configured in a dynamic cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the dynamic cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Elasticity, then select Policies.
The Policies table displays information on the elastic policies configured in this dynamic cluster, such as:
Name
Scale Type
Action Name
Diagnostic Module
Enabled
Alarm Type
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options on any of the pages:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
For more information on creating and configuring policies, see Create a new policy and Configure a policy.
To monitor the elastic actions configured in a dynamic cluster:
From the WebLogic Domain dropdown menu, select Environment, then select Clusters.
In the Clusters table, select the name of the dynamic cluster you want to monitor.
An overview page displays information related to the cluster.
From the WebLogic Cluster dropdown menu, select Elasticity, then select Actions.
The Actions table displays information on the elastic actions configured in this dynamic cluster, such as:
Name
Type
Enabled
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options on any of the pages:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
For more information on creating and configuring actions, see Create a new action and Configure an action.