Databases Reference
In-Depth Information
How it works...
The uniqueness of the Listen Address field is an important configuration as it allows
the WebLogic cluster to provide the flexibility needed for high availability, and to use the
automatic/manual server and service migration. It also guarantees the independence and
decoupling of each of the WebLogic Managed Server configurations.
It's also a good practice to use a different Listen Port for the Managed Servers. Using
different
hostname:port
combinations should avoid possible port conflicts when two
Managed Servers would possibly listen for the same IP address if a migration situation arises.
As a rule of thumb, use a unique hostname for the Listen Address
field and a unique port for the Listen Port field. Also always use a fully
qualified domain name.
There's more...
Setting the Listen Address value can also be done using WLST.
Defining the Listen Address value using WLST
Carry out the following steps to change the Listen Address value:
1. Log in as a
wls
user to shell and start WLST:
[wls@prod01]$ $WL_HOME/common/bin/wlst.sh
2. Connect to the Administration Server using
wlsadmin
as the user,
<pwd>
as the
password and
t3://prod01.domain.local:7001
as the server URL:
wls:/offline> connect("wlsadmin","<pwd>","t3://prod01.domain.
local:7001")
3. Run the following WLST commands to create the cluster and the server instances:
edit()
startEdit()
cd('/Servers/PROD_Server01')
cmo.setListenAddress('prodsrv01.domain.local')
cd('/Servers/PROD_Server02')
cmo.setListenAddress('prodsrv02.domain.local')
cd('/Servers/PROD_Server03')
cmo.setListenAddress('prodsrv03.domain.local')
cd('/Servers/PROD_Server04')
Search WWH ::
Custom Search