Databases Reference
In-Depth Information
Defining a network channel for cluster
communications
When configuring the Listen Address value with a hostname as in the previous recipes,
WebLogic Server instances use the specific network interface card (NIC) bound to the
hostname's IP address for network traffic. The traffic includes all inbound and outbound
requests and the Unicast cluster communications.
In a production environment with high network traffic, it is possible to improve network
utilization by adding an additional NIC to be used by the Unicast cluster communications,
segregating the application traffic, and the cluster communication traffic.
This recipe will create a new channel named
clusterChannel
and configure the
PROD_Cluster
cluster to use it.
Getting ready
This recipe assumes that all machines used by the cluster have two network interface cards.
The first NIC is
eth0
used by the default WebLogic channel. The second NIC is
eth1
and will
be used for the new WebLogic network channel.
All the Managed Server instances of the cluster must define a new channel with the same
name
clusterChannel
. The
clusterChannel
points to the IP address or hostname of
the NIC
eth1
of the machine that hosts the instance. The hostnames bound to the
eth1
for
the
PROD_Server01
,
PROD_Server02
,
PROD_Server03
, and
PROD_Server04
Managed
Servers are
channel01.domain.local
,
channel02.domain.local
,
channel03.
domain.local
, and
channel04.domain.local
respectively.
How to do it...
Carry out the following steps to create a new channel:
1. Access the Administration Console with your web browser at
http://prod01.
domain.local:7001/console
.
2. Click Expand the Environment tree on the left and click on Servers.
3. Click on the
PROD_Server01
link to navigate to General | Configuration of the first
Managed Server of the cluster.
Search WWH ::
Custom Search