Академический Документы
Профессиональный Документы
Культура Документы
Copyright 2013,
Page 1
Table of Contents
1.
INTRODUCTION .................................................................................................................................................................. 3
2.
ASSUMPTIONS ................................................................................................................................................................... 3
3.
REQUIREMENTS .................................................................................................................................................................. 4
4.
5.
6.
7.
Copyright 2013,
Page 2
1. INTRODUCTION
The Purpose of this document is introduce the concept of weblogic server migration
Most services in weblogic server cluster are deployed across all the managed servers in the cluster enabling
transparent failover. However for services like JMS and JTA transactions recovery systems are targeted at
individual managed server instances in a cluster, hence failover is not the appropriate solution. For services like
these weblogic recovery with migration is used instead of failover
Managed server migration is a process of moving the instance of the weblogic managed server elsewhere if a
failure occurs. The whole managed server instance is migrated to a different physical server upon failure (system
hangs, network failure, host system fails). This provides all the services including the JMS and JTA transaction
systems to be highly available.
Upon failure, a migratable managed server automatically restarts on the same system if possible. If the
migratable server cannot restart on the system it failed on, it is migrated to another system. In addition, an
administrator can manually initiate migration of a server instance.
ifconfig - Enable your network to register the new location of the virtual IP
arping - Enable your network to register the new location of the virtual IP.
2. ASSUMPTIONS
Base domain is installed using the virtual host name
Administration Server installed on SOA_HOST1 using soa-as.comany.com as the host name
Managed Server 1(MS1) is installed on SOA_HOS1 using soa_ms1.company.com
Managed Server 1(MS1) is installed on SOA_HOS1 using soa_ms2.company.com
Copyright 2013,
Page 3
3. REQUIREMENTS
Network Requirements
IP Address
XXX.XXX.XXX.XXX
YYY.YYY.YYY.YYY
Host Name
SOA_HOST1
SOA_HOST2
Ethernet
Interface/Index
Eth0-0
Eth0-1
Eth0-2
HOST
Status
SOA_HOST1
SOA_HOST1
SOA_HOST1
soa-as.compnay.com
soa-ms1.compnay.com
soa-ms1.compnay.com
Up
Up
Down
Status
soa-as.company.com
soa-ms1.company.com
soa-ms2.company.com
Ethernet
Interface/Index
HOST
Page 4
AAA.AAA.AAA.AAA
BBB.BBB.BBB.BBB
CCC.CCC.CCC.CCC
Eth0-0
Eth0-1
Eth0-2
SOA_HOST1
SOA_HOST1
SOA_HOST1
soa-as.compnay.com
soa-ms1.compnay.com
soa-ms1.compnay.com
Up
Up
Down
soa-as.company.com
soa-ms1.company.com
soa-ms2.company.com
Copyright 2013,
Page 5
Application Host 1
1. Start Cluster
Application Host 2
VIP 1
VIP 3
4. Obtain Configuration
VIP 2
Managed Server 1
(Migratable)
2. Contact NM
Weblogic Cluster
Admin Server
Leasing Table
FMW DB
Managed Server 1
(Migratable)
5. Cache Config
5. Cache Config
7. Renew lease
7. Renew lease
Virtual IP
VIP 1
aaa.aaa.aaa.aaa
Soa-as.company.com
Soa-as.company.com
aaa.aaa.aaa.aaa
VIP 2
bbb.bbb.bbb.bbb
Soa-ms1.company.com
Soa-ms1.company.com
bbb.bbb.bbb.bbb
ccc.ccc.ccc.ccc
Soa-ms2.company.com
Soa-ms2.company.com
ccc.ccc.ccc.ccc
Prepared By
Rakesh B
Gujjarlapudi
Copyright 2013,
Page 6
Copyright 2013,
Page 7
6. SERVER MIGRATION
In this enterprise topology, you must configure server migration for the MS1 and MS2 managed servers.
The MS1 managed server is configured to restart on SOA_HOST2 should a failure occur.
The MS2 managed server is configured to restart on SOA_HOST1 should a failure occur.
For this configuration, the MS1 and MS2 servers listen on specific floating IPs that is failed over by WLS Server
Migration.
Step 1 - Setting Up a User and Tablespace for the Server Migration Leasing Table
The first step is to set up a user and tablespace for the server migration leasing table:
Create a tablespace called leasing. For example, log on to SQL*Plus as the sysdba user and run the following
command:
SQL> create tablespace leasing logging datafile 'DB_HOME/oradata/orcl/leasing.dbf' size 32m autoextend on
next 32m maxsize 2048m extent
management local;
Create a user named leasing and assign to it the leasing tablespace.
SQL> create user leasing identified by welcome1;
SQL> grant create table to leasing;
SQL> grant create session to leasing;
SQL> alter user leasing default tablespace leasing;
SQL> alter user leasing quota unlimited on LEASING;
Create the leasing table using the leasing.ddl script.
Copy the leasing.ddl file located in either the
ORACLE_BASE/product/osbmw/wlserver_10.3/server/db/oracle/920 directory to your database node.
Connect to the database as the leasing user.
Run the leasing.ddl script in SQL*Plus.
SQL> @copy_location/leasing.ddl;
Step 2: Creating a Multi-Data Source Using the Oracle WebLogic Server Administration Console for the leasing
table
Create a data source to each of database instances
Make sure that this is a non-xa data source
Use Oracle's Driver (Thin) Version 9.0.1, 9.2.0, 10, 11
Use Supports Global Transactions, One-Phase Commit, and specify a service name for your database
Target these data sources to the cluster
Copyright 2013,
Page 8
9. In Domain Structure window of the Oracle WebLogic Server Administration Console, expand
Environment and select Servers.
10. Select the server for which you want to configure migration.
11. Click the Migration tab.
12. In the Available field, located in the Migration Configuration section, select the machines to which to
allow migration and click the right arrow. For MS1, select SOA_HOST2. For MS2, select SOA_HOST1.
13. Select Automatic Server Migration Enabled. This enables the Node Manager to start a failed server on
the target node automatically.
14. Click Save.
15. Restart the Administration Server
Copyright 2013,
Page 9
Copyright 2013,
Page 10
Copyright 2013,
Page 11
Copyright 2013,
Page 12