STEP 1: CREATE THE WEBLOGIC DOMAIN
WebLogic domain will require the following to configure
• Machine 1
• Admin Server*
• Managed Server 1
• Machine 2
• Managed Server 2
• Each WebLogic machine must be point to a unique running Node Manager instance .
• Each Managed Server must use a floating IP address for the host name. The floating IP address for Managed Server 1 & 2 must be unique.
• The Admin Server must have IP address for the host name if the manual Admin Server
Migration support is required.
The nodemanager.properties file for each Node Manager instance must be updated to indicate the netmask and network device name (interface) to be used throughout the server migratable cluster.
Below is an example of the specific Node Manager properties that are required for server migration configuration.
Sample Node Manager properties:
Interface=eth0
NetMask=255.255.255.0
UseMACBroadcast=true
The nodemanager.properties is in the location
FMW_HOME/wlserver_10.3/server/lib
STEP 3: SETUP THE LEASING PROCESS
There are two types of leasing configurations available:
• Consensus Leasing
• High-Availability Database Leasing
STEP 4: GRANT SUPERUSER PRIVILEGES TO THE WLSIFCONFIG SCRIPT
Ensure the PATH environment variable contains the following files:
• DOMAIN_HOME/bin/server_migration/wlsifconfig.sh
• WL_HOME/common/bin/wlscontrol.sh
• WL_HOME/common/nodemanager/nodemanager.domains
STEP 5: ENABLE SERVER MIGRATION
The following steps can be followed to enable “Server Migration” via the WebLogic Admin Server.
1. Configure the WebLogic cluster(s):
2. Under Candidate Machines For Migratable Servers select the machines you wish to be migration
3. Set the Migration Basis as required ("Consensus" or "Database"). If using "Database" for
4. Under Candidate Machines select the machines you wish to migrate to from the Available box and move them to the Chosen box
No comments:
Post a Comment