http://www.grotal.

com/Hyderabad/Footwear-Manufacturers-C70/
WebLogic 12c Dynamic Clusters

A cluster that contains one or more generated (dynamic) server instances that are based on a
single shared server template. configured cluster. A cluster in which you manually configure
and add each server instance. dynamic server. A server instance that is generated
by WebLogic Server when creating a dynamic cluster.

A WebLogic Server cluster consists of multiple WebLogic Servers running simultaneously and working together. It
provides increased scalability and reliability.

WebLogic Server 12c has an exiting new feature called Dynamic Clustering. A dynamic cluster contains multiple
dynamic servers that is based on a single server template. This template will be the basis for all the servers in the
cluster so that each server does not need to be manually configured when expanding the cluster.

Dynamic clusters allow you to easily scale up the number of server instances in your domain. You specify the number
of server instances on a peak load, WebLogic Server then will create the specified number of server instances and
apply the calculated attribute values from the base template to each one. When additional server capacity is needed,
a new server instance can be added to the cluster without having to first manually configuration. In other words we no
longer configure managed servers individually. Instead configure a cluster with the number of server you want along
with the template. This will provide us dynamically scale up our cluster.

When we use a server template to create a dynamic cluster and specify the number of server instances we want,
WebLogic Server inherits and calculates necessary values from server template and then uses these calculated
values for the attributes. Some of these attributes are;

Managed Server Name: Server Name prefix appended with server id. For example, if the prefix is set to imc-
server-, then the dynamic servers will have the names imc-server-1, imc-server-2 and so on.

Network ports (Optional): Port value starting value is either the default or is based on the value in the server
template. Applies to listen port, SSL Listen port, Network access point and replication ports. If you explicitly
define a listen port in the server template or the cluster configuration itself, that value will be used for the first
generated server instance and appended by 1 for each additional server instance. If the default listen port is
indicated, WebLogic Server increments the "hundreds" digit by one and continue from there.

Machine mappings (Optional): The dynamic cluster CalculatedMachineNames and

MachineNameMatchExpression attributes control how server instances in a dynamic cluster are assigned to a
machine. This is important when using admin console/Node manager to start servers. Regular expression to
match the machine names. Managed server prefix + server id (numerical order in which the server is defined)

Creating Dynamic Clusters Example;

We can use WLST or WebLogic Console to create a Oracle WebLogic Dynamic Cluster. WebLogic Server Console
provides necessary wizard to easily create a dynamic clusters.It allows easily configure, manage, monitor the
dynamic clusters.When all steps completed the following components are created;

Cluster with Dynamic Servers

Server template
Machine mappings
Listen address and port mappings

First we navigate the Clusters page and click on to create Dynamic cluster.

On the next page we enter the cluster name and leave the rest as defaults.
The next page allows us to set the maximum number of server instances allowed in our dynamic cluster along with
the server name prefix. Server names are the specified prefix followed by the index number.

The next step allow us to control how server instances in a dynamic cluster are assigned to a machine. If we choose
any machine configured for this domain, then assignments will be made using a round robin algorithm.
The next page allows settings in the server template and the dynamic cluster configuration determines the listen ports
for the server instances in our dynamic cluster. This is where listen ports and machines assignments will be
calculated using a round-robin algorithm. Please note WebLogic Server calculates listen ports by default. This
calculation can also be disabled in the dynamic cluster configuration.

Finally we get the summary screen where we confirm to create the cluster with the attribute values we specified.
Now if we navigate the servers screen, we see that all the servers are created with the values we provided. We did
not manually/individually created Managed Servers. When creating a dynamic cluster in the Administration Console,
WebLogic Server creates the server template, dynamic cluster, and specified number of server instances for us. We
don't have to create them individually.

We can also navigate the Cluster Server template and modify the default values there. Below you can see a
screenshot where we can modify the default server log file names.
 Coherence Clusters
Coherence clusters consist of multiple managed Coherence server instances that distribute data in-
memory to increase application scalability, availability, and performance. An application interacts
with the data in a local cache and the distribution and backup of the data is automatically performed
across cluster members.

Coherence clusters are different than WebLogic Server clusters. They use different clustering
protocols and are configured separately. Multiple WebLogic Server clusters can be associated with a
Coherence cluster and a WebLogic Server domain typically contains a single Coherence cluster.
Managed servers that are configured as Coherence cluster members are referred to as managed
Coherence servers.
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
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.

Oracle Coherence is a highly scalable and fault-tolerant distributed cache engine. Coherence uses a
specialized scalable protocol and many inexpensive computers to create a cluster which can be
seamlessly expanded to add more memory, processing power or both. As a result, Coherence has
no single point of failure and transparently fails over if a cluster member fails. When a Coherence
server is added or removed the cluster automatically re-balances to share the workload. As a result,
Coherence provides a highly available and predictably horizontally scalable infrastructure for
managing application data
Corporate Office

USA
Branch Office
8 MEG WAY
Plot No. 1023-1026,
WINDSORLOCKS, CT 06096
4th Floor, Gurukul Society,
Madhapur - 500 081
Email : info@solventindia.com
TELEPHONE : +91 40 6461 0338
FAX : +91 40 6461 0338 SOUTH AFRICA
Email : info@solventindia.com
309 CORNER SCARLET STREET & 15TH
AVENUE
LAUDIUM 0037, GAUTENG
SOUTH AFRICA

UNITED KINGDOM

280A HIGH STREET

ORPINGTON, LONDON BR60ND
UNITED KINGDOM