Enable Cluster-Level Session Replication Enhancements
You can enable session replication enhancements for managed servers in a WebLogic
cluster to which you will deploy a web application at a later time.
Note -
If you are using Coherence*web, these session replication enhancements do not
apply. Skip these steps if you use the
dizzyworld.ear
application as described in Chapter 8, “Deploying a Sample Web Application
to and Oracle WebLogic Cluster” in the
Oracle
Fusion Middleware Exalogic Enterprise Deployment Guide at:
http://docs.oracle.com/cd/E18476_01/doc.220/e18479/deploy.htm
To enable session replication enhancements for Dept1_Cluster1,
complete the following steps:
-
Ensure that managed servers in the Dept1_Cluster1 cluster
are up and running.
Refer to Section 5.16 “Starting Managed Servers on ComputeNode1 and
ComputeNode2” of the Oracle® Fusion
Middleware Exalogic Enterprise Deployment Guide at: http://docs.oracle.com/cd/E18476_01/doc.220/e18479/create_domain.htm#BABEGAFB
-
Set replication ports for a managed server, such as WLS1.
-
Under Domain Structure, click Environment and Servers.
-
Click WLS1 on the list of servers.
-
Click the Cluster tab.
-
In the Replication Ports field, enter a range of ports for configuring
multiple replication channels.
For example, replication channels for managed servers in
Dept_1_Cluster1 can listen on ports starting from
7005 to 7015. To specify this range of ports, enter 7005-7015.
-
Create a custom network channel for each managed server in the cluster (for
example, WLS1).
-
Log in to the Oracle WebLogic Server Administration Console.
-
If you have not already done so, click Lock & Edit in the Change
Center.
-
In the left pane of the Console, expand Environment and select
Servers.
-
In the Servers table, click WLS1 Managed Server instance.
-
Select Protocols and then Channels.
-
Click New.
-
Enter ReplicationChannel as the name of the new network channel and
select t3 as the protocol, then click Next.
-
Enter the following information:
-
Click Next, and in the Network Channel Properties page, select Enabled
and Outbound Enabled.
-
Click Finish.
-
Under the Network Channels table, select ReplicationChannel, which is
the network channel you created for the WLS1 Managed Server.
-
Expand Advanced, and select Enable SDP Protocol.
-
Click Save.
-
To activate these changes, click Activate Changes in the Change Center
of the Administration Console.
-
Repeat Step 3 to create a network channel each for the remaining managed
servers in the Dept1_Cluster1 cluster. Enter the
required properties, as described in this table.
|
|
|
|
|
|
WLS2
|
ReplicationChannel
|
t3
|
10.0.0.2
|
7005
|
7006 to 7014
|
WLS3
|
ReplicationChannel
|
t3
|
10.0.0.3
|
7005
|
7006 to 7014
|
WLS4
|
ReplicationChannel
|
t3
|
10.0.0.4
|
7005
|
7006 to 7014
|
WLS5
|
ReplicationChannel
|
t3
|
10.0.0.5
|
7005
|
7006 to 7014
|
WLS6
|
ReplicationChannel
|
t3
|
10.0.0.6
|
7005
|
7006 to 7014
|
WLS7
|
ReplicationChannel
|
t3
|
10.0.0.7
|
7005
|
7006 to 7014
|
WLS8
|
ReplicationChannel
|
t3
|
10.0.0.8
|
7005
|
7006 to 7014
|
|
-
After creating the network channel for each of the managed servers in your
cluster, click Environment→ Clusters.
-
Click Dept1_Cluster1.
This is the example cluster where you will deploy a web application at a later
time.
-
Click the Replication tab.
-
In the Replication Channel field, ensure that Replication Channel is set as
the name of the channel to be used for replication traffic.
-
In the Advanced section, select the Enable One Way RMI for Replication option,
and click Save.
-
Activate changes, and restart the managed servers.
-
Manually add the system property
-Djava.net.preferIPv4Stack=true to the
startWebLogic.sh script, which is located in the
bin directory of base_domain, using a text editor as
follows:
-
Locate the following line in the startWebLogic.sh
script:
. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
-
Add the following property immediately after the preceding
entry:
JAVA_OPTIONS="${JAVA_OPTIONS}
-Djava.net.preferIPv4Stack=true"
-
Save and close the file.
-
Restart all managed servers.
-
In the administration console, click Environment → Servers.
-
Select a managed server, such as WLS1, by clicking WLS1.
-
Click the Control tab. Select WLS1 in the Server Status table. Click
Start.
-
Repeat Step 11 for each of the managed servers in the WebLogic
cluster.
-
Verify that multiple listening ports were opened in one of these ways:
-
Type the netstat -na command.
-
Check the managed server logs.