In previous blog entries we built a SOA/BPM cluster with associated Web Services Manager and BAM clusters and got those working. We now need to enable automatic migration of servers to ensure that no messages are lost or unnecessarily delayed.
First we need to create a migration leasing table. This is used to keep track of which machines are hosting which managed servers.
We can put this into its own tablespace to keep it separate from the SOA schemas. Using SQLPlus we create the new tablespace as shown below:
create tablespace leasing
logging datafile '/u01/oradata/rac/leasing.dbf'
size 32m autoextend on next 32m maxsize 2048m
extent management local;
This creates a tablespace leasing using the new file “leasing.dbf” in the same location as the other database files in our RAC cluster. This file is set to an initial size of 32m and will grow in 32m increments until it reaches a limit of 2G.
We can now create a user and schema in this tablespace using SQLPlus as follows:
grant create table, create session to leasing identified by welcome1;
alter user leasing default tablespace leasing;
alter user leasing quota unlimited on leasing;
This creates the user leasing and sets his default tablespace to be leasing.
We are now able to create our leasing table using the leasing.ddl script found in our WebLogic install at $WLS_HOME/server/db/oracle/920. We can copy this to our database server using scp and then execute it using SQLPlus as the leasing user as shown:
This will create a single table in the leasing schema to hold managed server lease details. (EDG)
Now that we have a leasing table we need to configure WebLogic with a data source that can access this table. This only needs to be able to support single phase commit because it will not be interacting with other transactional resources.
We will create a Multi-Data source to take advantage of our RAC cluster.
We now need to configure the node manager to manage IP addresses. On each machine we edit the nodemanager.properties file and add the following entries:
Note that we moved the node manager configuration to a non-shared location when we first set it up so the nodemanager.properties file should be found in /u01/oracle/admin/NodeManager.
We previously configured the machines to grant appropriate privileges to the oracle user to run the ifconfig and arping commands. These privileges are required by the wlsifconfig.sh script used by the node manager. (EDG and EDG)
Using the WebLogic console to set up server migration. First select the machines to be used for each cluster (BAM_Cluster and SOA_Cluster).
Navigate to Environment->Clusters and for the BAM and SOA clusters:
For BAM Server (BAM1) and all SOA Servers (SOA1, SOA2) then we need to configure their target migration servers by navigating to Environment->Servers in WebLogic console. Then for each server do the following:
We have now pretty much finished setting up our SOA and BAM cluster. We still need to test our environment but otherwise we are good to go. In a future blog entry I will extend the domain to support OSB.