In this enterprise topology, you must configure server migration for the WLS_SOA1 and WLS_SOA2 managed servers. The WLS_SOA1 managed server is configured to restart on SOAHOST2 should a failure occur. The WLS_SOA2 managed server is configured to restart on SOAHOST1 should a failure occur. For this configuration, the WLS_SOA1 and WLS_SOA2 servers listen on specific floating IPs that are failed over by WLS Server Migration. Configuring server migration for the WLS_SOAn managed servers consists of the following steps:
Step 7: Testing the Server Migration
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;
leasing.ddl file located in either the
ORACLE_BASE/product/fmw/wlserver_10.3/server/db/oracle/817 or the
ORACLE_BASE/product/fmw/wlserver_10.3/server/db/oracle/920 directory to your database node.
Connect to the database as the
leasing.ddl script in SQL*Plus.
The second step is to create a multi-data source for the leasing table from the Oracle WebLogic Server Administration Console:
You create a data source to each of the RAC database instances during the process of setting up the multi-data source, both for these data sources and the global leasing multi-data source. When you create a data source:
Make sure that this is a non-xa data source
The names of the multi-data sources are in the format of <MultiDS>-rac0, <MultiDS>-rac1, and so on
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 SOA cluster
To create a multi-data source, complete these steps:
From Domain Structure window in the Oracle WebLogic Server Administration Console, expand the Services node, then expand the JDBC node.
Click Multi Data Sources. The Summary of JDBC Multi Data Source page appears.
Click Lock and Edit.
Click New. The Create a New JDBC Multi Data Source page appears.
Enter leasing as the Name
Enter jdbc/leasing as the JNDI name.
Select Failover as algorithm (default).
Select BAM_Cluster as the target.
Select non-XA driver (the default).
Click Create New Data Source.
Enter leasing-rac0 as name. Enter jdbc/leasing-rac0 as JNDI name. Enter oracle as the database type. For the driver type, enter Oracle Driver (Thin) for RAC server-Instance connection Version 10,11.
Note:When creating the multi-datasources for the leasing table, enter names in the format of <MultiDS>-rac0, <MultiDS>-rac1, and so on.
Deselect Supports Global Transactions.
Enter the service name, database name, host port, and password for your leasing schema.
Click Test Configuration and verify the connection works.
Target the data source to SOA_Cluster.
Select the data source and add it to the right screen.
Click Create a New Data Source for the first instance of your RAC database, target it to BAM_Cluster, and repeat the steps for the second instance of your RAC database.
Add the second data source to your multi-data source.
Click Activate Changes.
The third step is to create the appropriate certificates for host name verification between the Node Manager and the Administration Server. This procedure is described in Section 7.2, "Enabling Host Name Verification Certificates for Node Manager in SOAHOST1" and Section 7.4, "Enabling Host Name Verification Certificates for the Node Manager in SOAHOST2."
The fourth step is to edit the Node Manager's properties file. This file is called
nodemanager.properties and is located in the
ORACLE_BASE/product/fmw/wlserver_10.3/common/nodemanager directory. For server migration to work properly, you need to add the properties listed below:
This property specifies the interface name for the floating IP (for example, eth0).
This property specifies the net mask for the interface for the floating IP. The net mask should the same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
This property specifies whether or not to use a node's MAC address when sending ARP packets, that is, whether or not to use the -b flag in the
Verify in Node Manager's output (shell where Node Manager is started) that these properties are being used, or problems may arise during migration. You should see something like this in the Node Manager's output:
... StateCheckInterval=500 Interface=eth0 NetMask=255.255.255.0 ...
Note:The steps below are not required if the server properties (start properties) have been properly set and the Node Manager can start the servers remotely.
Set the following property in the
Set this property to
true. This is required for the shiphome to enable the Node Manager to start the managed servers.
Start the Node Manager on Node 1 and Node 2 by running the
startNodeManager.sh script located in the
Note:When running Node Manager from a shared storage installation, multiple nodes are started using the same
nodemanager.propertiesfile. However, each node may require different
Interfaceproperties. In this case, specify individual parameters on a per-node basis using environment variables. For example, to use a different interface (eth3) in SOAHOSTn, use the
Interfaceenvironment variable as follows:
SOAHOSTn> export JAVA_OPTIONS=-DInterface=eth3and start Node Manager after the varibale has been set in the shell.
The fifth step is to set environment and superuser privileges for the
Ensure that your PATH environment variable includes these files:
|File||Located in this directory|
Grant sudo configuration for the
Configure sudo to work without a password prompt.
For security reasons, sudo should be restricted to the subset of commands required to run the
wlsifconfig.sh script. For example, to set the environment and superuser privileges for the
wlsifconfig.sh script, complete these steps:
Grant sudo privilege to the WebLogic user ('oracle') with no password restriction, and grant execute privilege on the /sbin/ifconfig and /sbin/arping binaries.
Make sure the script is executable by the WebLogic user ('oracle'). The following is an example of an entry inside /etc/sudoers granting sudo execution privilege for
oracle and also over
oracle ALL=NOPASSWD: /sbin/ifconfig,/sbin/arping
Note:Ask the system adminsitrator for the sudo and system rights as appropriate to this step.
The sixth step is to configure server migration targets. Configuring Cluster Migration sets the
DataSourceForAutomaticMigration property to true. Follow the steps below to configure cluster migration in a migration in a cluster:
Log into the Oracle WebLogic Server Administration Console (
adminPort is 7001 by default).
In the Domain Structure window, expand Environment and select Clusters. The Summary of Clusters page appears.
Click the cluster for which you want to configure migration (SOA_Cluster) in the Name column of the table.
Click the Migration tab.
In the Available field, select the machine to which to allow migration and click the right arrow. In this case, select SOAHOST1 and SOAHOST2.
Select the data source to be used for automatic migration. In this case select the leasing data source.
Set the Candidate Machines for Server Migration. You must perform this task for all of the managed servers as follows:
In Domain Structure window of the Oracle WebLogic Server Administration Console, expand Environment and select Servers.
Select the server for which you want to configure migration.
Click the Migration tab.
In the Available field, located in the Migration Configuration section, select the machines to which to allow migration and click the right arrow. For WLS_SOA1, select SOAHOST2. For WLS_SOA2, select SOAHOST1.
Select Automatic Server Migration Enabled. This enables the Node Manager to start a failed server on the target node automatically.
Restart the Administration Server.
Tip:Click Customize this table in the Summary of Servers page, move Current Machine from the Available Window to the Chosen window to view the machine on which the server is running. This will be different from the configuration if the server gets migrated automatically.
The seventh and final step is to test the server migration. To verify that Server Migration is working properly, follow these steps:
From Node 1:
Stop the WLS_SOA1 managed server.
To do this, run this command:
SOAHOST1> kill -9 <pid>
pid specifies the process ID of the managed server. You can identify the pid in the node by running this command:
SOAHOST1> ps -ef | grep WLS_SOA1
Watch the Node Manager console: you should see a message indicating that WLS_SOA1's floating IP has been disabled.
Wait for the Node Manager to try a second restart of WLS_SOA1. Node Manager waits for a fence period of 30 seconds before trying this restart.
Once Node Manager restarts the server, stop it again. Now Node Manager should log a message indicating that the server will not be restarted again locally.
Watch the local Node Manager console. After 30 seconds since the last try to restart WLS_SOA1on Node 1, Node Manager on Node 2 should prompt that the floating IP for WLS_SOA1 is being brought up and that the server is being restarted in this node.
Access the soa-infra console in the same IP.
Migration can also be verified in the Administration Console:
Log into the Administration Console.
Click on Domain on the left console.
Click the Monitoring tab and then the Migration subtab.
The Migration Status table provides information on the status of the migration.