Configuring Server Migration for the WLS_OSB Servers
5.14.21 Configuring Server Migration for the WLS_OSB Servers
The high availability architecture for an OSB system uses server migration to protect some singleton services against failures. For more information on whole server migration, see Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server. The WLS_OSB1 managed server is configured to be restarted on OSBHOST2 in case of failure, and the WLS_OSB2 managed server is configured to be restarted on OSBHOST1 in case of failure. For this configuration the WLS_OSB1 and WLS_OSB2 servers listen on specific floating IPs that are failed over by WLS Server Migration. To configure server migration for the WLS_OSBn managed servers, follow these steps: Step 1 Set Up User and Tablespace for the Server Migration Leasing Table 1. Create a tablespace called leasing. Example: Log on to SQLPlus as the sysdba user and run the following command: SQL create tablespace leasing Note: On Windows, when you manually shut down multiple servers at the same time on the same machine and, on another machine, attempt to start one of the servers that you shut down, the IP bind may not work. This happens because the original machine still has claim to the IP address, even though netsh has reported that the IP address has been removed. To resolve this, you must check the network configuration either by using the ipconfig utility or Windows Network Configuration. Either of these may show that one of the virtualfloating IP addresses is still configured even though the servers have been shut down. You can then use Windows Network Configuration to remove the IP address using the following procedure: 1. From Windows Control Panel, select Network Connections. 2. Select the appropriate network interface, right-click, and select Properties . 3. Select Internet Protocol TCPIP and click the Properties button. 4. Select Advanced. 5. Select the appropriate IP address and click the Remove button. Note: After a server is migrated, to fail it back to its original nodemachine, stop the managed server from the Oracle WebLogic Administration Console and then start it again. The appropriate Node Manager will start the managed server on the machine to which it was originally assigned. Note: If a tablespace, schema multi data source, and data sources have already been set up for SOA as described in Section 5.14.20, Configuring Server Migration for the WLS_SOA Servers above, then the OSB Cluster can reuse the existing leasing schema and data source and Step 1 and Step 2 below are not required. Instead, simply target the data sources and multi data sources created for SOA to the OSB Cluster. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-187 logging datafile DB_HOMEsoradataorclleasing.dbf size 32m autoextend on next 32m maxsize 2048m extent management local; 2. 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; 3. Create the leasing table using the leasing.ddl script. a. Copy the leasing.ddl file, located in the WL_ HOMEserverdboracle817 or WL_HOMEserverdboracle920 directories, to your database node. b. Connect to the database as the leasing user. c. Run the leasing.ddl script in SQLPlus. SQL copy_locationleasing.ddl; Step 2 Create a Multi Data Source from Oracle WebLogic Server Administration Console 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 Oracle 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: ■ Ensure that this is a non-xa data source. ■ The names of the multi data sources are in the following format: MultiDS-rac0, MultiDS-rac1 ■ Use Oracle’s Driver Thin Version 9.0.1, 9.2.0, 10, 11. ■ Data sources do not require support for global transactions. Therefore, do not use any type of distributed transaction emulationparticipation algorithm for the data source do not choose the Supports Global Transactions option, or the Logging Last Resource , Emulate Two-Phase Commit, or One-Phase Commit options of the Supports Global Transactions option, and specify a service name for your database. ■ Target these data sources to the OSB cluster. ■ Make sure the datasources connection pool initial capacity is set to 0. To do this, select Services, JDBC, and then Datasources. In the Datasources screen, click the Datasource Name , then click the Connection Pool tab, and enter 0 in the Initial capacity field. To create a multi data source: 1. From the Domain Structure window in the Oracle WebLogic Server Administration Console, expand the Services node, then click Data Sources. The Summary of JDBC Data Sources page appears. 5-188 Oracle Fusion Middleware High Availability Guide2. In the Change Center, click Lock Edit.
3. Click New, then click Multi Data Sources. The Create a New JDBC Multi Data
Source page appears.4. Enter leasing as the Name.
5. Enter jdbcleasing as the JNDI name.
6. Select Failover as algorithm default.
7. Click Next.
8. Select non-XA driver the default.
9. Click Next.
10. Click Create New Data Source.
11. Enter leasing-rac0 as name. Enter jdbcleasing-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.12. Click Next.
13. Deselect Supports Global Transactions.
14. Click Next.
15. Enter the service name, database name this is actually the RAC Node instance name, for example: racdb1,racdb2, host port, and password for your leasing schema16. Click Next.
17. Click Test Configuration and verify the connection works.
18. Target the data source to the OSB cluster. 19. Select the data source and add it to the right screen.20. Click Create a New Data Source and repeat the steps for the second instance of
your Oracle RAC database. 21. Add the second data source to your multi data source. 22. Save and Activate the changes. Step 3 Edit the Node Manager’s Properties file For information on Node Manager and whole server migration, see Section 3.9, Whole Server Migration. The nodemanager.properties file is located in the WL_ HOMEcommonnodemanager directory. For server migration to work properly, you must add the properties listed in this section: ■ Interface=eth0 Note: Do not specify the sub interface, such as eth0:1 or eth0:2. This interface is to be used without the :0, or :1. The Node Manager’s scripts traverse the different :X enabled IPs to determine which to add or remove. For example, the valid values in Linux environments are eth0, eth1, or, eth2, eth3, ethn, depending on the number of interfaces configured. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-189 This property specifies the interface name for the floating IP eth0, for example, on Linux. Be sure that the interface provided is the public interface for this node. On multi home nodes, this interface should be the one on which the floating IP can be enabled. ■ NetMask=255.255.255.0 This property specifies the net mask for the interface for the floating IP. The netmask provided 255.255.255.0 is just an example. The actual value depends on your network. ■ UseMACBroadcast=true This property specifies whether or not to use a nodes MAC address when sending ARP packets, that is, whether or not to use the -b flag in the arping command. After starting Node Manager, 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 Linux or Interface=Local Area Connection Windows NetMask=255.255.255.0 UseMACBroadcast=true 1. Set the following property in the nodemanager.properties file. ■ StartScriptEnabled Set this property to true. 2. Start the Node Manager on OSBHOST1 and OSBHOST2 by running the startNodeManager.sh script located in the WL_HOMEserverbin directory. 3. Validate the changes to the nodemanager.properties file by checking the nodemanager.log file. Step 4 Set Environment and Superuser Privileges for the wlsifconfig.sh script 1. Grant sudo privilege to the WebLogic user oracle with No Password restriction, and grant execute privilege on sbinifconfig and sbinarping binaries. Note: For Windows, the Interface should be set to the Network Interface Name. For example: Interface=Local Area Connection. Note: The steps in this section are not required if the server properties start properties have been properly set and the Node Manager can start the servers remotely. Note: On Windows, the script is named wlsifconfig.cmd and it can be run by users with the administrator privilege. 5-190 Oracle Fusion Middleware High Availability Guide Make sure the script is executable by the WebLogic user oracle. The following is an example of an entry inside etcsudoers granting sudo execution privilege for oracle and also over the ifconfig and arping: Defaults:oracle requiretty oracle ALL=NOPASSWD: sbinifconfig,sbinarping Step 5 Configure Server Migration Targets Configuring Cluster Migration sets the DataSourceForAutomaticMigration property to true. Follow the steps in this section to configure cluster migration in a migration in a cluster: 1. Log into Oracle WebLogic Server Administration Console2. In the left pane, expand Environment and select Clusters.
3. Select the cluster for which you want to configure migration OSB_Cluster.
4. Click Migration.
5. In the Change Center, click Lock Edit.
6. In the Available field, select the machine to which to allow migration and click the
right arrow. In this case, select OSBHOST1 and OSBHOST2. 7. Select the data source to be used for automatic migration. In this case select the leasing data source.8. Click Save.
9. Set the Candidate Machines for Server Migration. This needs to be done for all the managed servers. To do this, follow these steps: a. In the left pane of Oracle WebLogic Server Administration Console, expand Environment and select Servers. b. Select the server for which you want to configure migration.c. Click the Migration tab.
Parts
» Oracle Fusion Middleware Online Documentation Library
» High Availability Problems High Availability Solutions
» High Availability Information in Other Documentation
» What Is the Administration Server? Understanding Managed Servers and Managed Server Clusters
» What Is a System Component Domain? What Is a Middleware Home? What Is a WebLogic Server Home?
» Oracle Fusion Middleware High Availability Terminology
» Server Load Balancing Oracle Fusion Middleware High Availability Technologies
» Local High Availability Active-Passive Deployment
» About Active-Active and Active-Passive Solutions
» Disaster Recovery Oracle Fusion Middleware High Availability Solutions
» Protection from Planned and Unplanned Down Time
» What Is a WebLogic Server Cluster? WebLogic Server Clusters and WebLogic Server Domains
» Application Failover Migration Key Capabilities of a Cluster
» Benefits of Clustering Types of Objects That Can Be Clustered
» Communications in a Cluster Cluster-Wide JNDI Naming Service
» Startup Process in a Cluster with Migratable Servers
» Administration Servers Role in Whole Server Migration Migratable Server Behavior in a Cluster
» Node Managers Role in Whole Server Migration Cluster Masters Role in Whole Server Migration
» Load Balancing Oracle Fusion Middleware Online Documentation Library
» Multi Data Sources Cluster Configuration and config.xml
» Java-Based Oracle Fusion Middleware Components Deployed to Oracle WebLogic Server
» Configuring Multi Data Sources for MDS Repositories
» Log on to SQLPlus as a system user, for example:
» Log on to SQLPlus as a user with sysdba privileges. For example:
» Configuring Multi Data Sources with Oracle RAC
» Oracle RAC Failover with WebLogic Server JDBC Clients
» Oracle Reports and Oracle Discoverer
» Troubleshooting Real Application Clusters
» SCAN Run Time Implications and Limitations
» Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior
» Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes
» Oracle BPEL Process Manager Request Flow and Recovery
» Oracle BPEL Process Manager Protection from Failures and Expected Behavior
» Oracle BPM Suite Component Characteristics
» Oracle BPM Suite Component Interaction
» Oracle BPMN Service Engine Single Instance Characteristics
» Oracle BPMN Service Engine High Availability Considerations
» Oracle Business Process Web Applications Single Instance Characteristics
» Oracle Business Process Analytics Single Instance Characteristics
» Oracle Mediator Component Characteristics Oracle Mediator Startup and Shutdown Lifecycle
» Oracle Mediator Request Flow
» Oracle Mediator Protection from Failures and Expected Behavior
» Troubleshooting Oracle Mediator High Availability
» Troubleshooting Oracle Human Workflow High Availability
» Oracle B2B Component Characteristics Oracle B2B Startup and Shutdown Lifecycle
» Oracle B2B Protection from Failures and Expected Behavior
» Oracle WSM Component Characteristics Oracle WSM Startup and Shutdown Lifecycle
» Oracle WSM Protection from Failures and Expected Behavior
» Oracle WSM Cluster-Wide Configuration Changes Configuring the Java Object Cache for Oracle WSM
» Configuring Distributed Notifications for the MDS Repository
» Oracle User Messaging Service Component Characteristics
» Oracle User Messaging Service Protection from Failures and Expected Behavior
» Oracle User Messaging Service Cluster-Wide Configuration Changes
» Oracle JCA Adapters Component Lifecycle
» Oracle JCA Adapters Reliability and Transactional Behavior
» Oracle JCA Adapters - Rejected Message Handling
» Oracle JCA Adapters High Availability Error Handling Oracle Database Adapters High Availability
» Oracle JMS Adapters High Availability
» Oracle JCA Adapters Log File Locations
» Oracle Business Activity Monitoring Component Characteristics
» Oracle Business Activity Monitoring Configuration Artifacts
» Oracle Business Activity Monitoring Protection from Failures and Expected Behavior
» Oracle Business Activity Monitoring Cluster-Wide Configuration Changes
» Oracle Service Bus Session State Oracle Service Bus External Dependencies
» Oracle Service Bus Configuration Artifacts Oracle Service Bus Deployment Artifacts
» Oracle Service Bus Protection from Failures and Expected Behavior
» Database Prerequisites VIP and IP Prerequisites Shared Storage Prerequisites
» Configuring Virtual Server Names and Ports for the Load Balancer
» Validating Oracle HTTP Server To verify that Oracle HTTP Server is set up
» Setting Connection Destination Identifiers for B2B Queues
» Starting Node Manager on SOAHOST2 Starting and Validating the WLS_SOA2 Managed Server
» Setting the Front End HTTP Host and Port
» Setting the WLS Cluster Address for Direct BindingRMI Invocations to Composites
» Deploying Applications Click Next.
» Configuring Server Migration for the WLS_SOA Servers
» Connect to the database as the leasing user. Run the leasing.ddl script in SQLPlus.
» Click Save. Oracle Fusion Middleware Online Documentation Library
» Enabling VIP1 and VIP3 in SOAHOST1 and VIP2 and VIP4 in SOAHOST2
» Configure Oracle Coherence for the Oracle Service Bus Result Cache
» Configuring a Default Persistent Store for Transaction Recovery Deploying Applications
» Configuring Server Migration for the WLS_OSB Servers
» Enabling VIP0 and VIP1 on BAMHOST1
» Oracle ADF Components Understanding Oracle ADF
» Oracle ADF Single Node Architecture Oracle ADF External Dependencies
» Oracle ADF Scope and Session State
» Oracle ADF Failover and Expected Behavior Oracle ADF Active Data Services
» Troubleshooting Oracle ADF Development Issues
» Deploying the ADF Application Validating Access through Oracle HTTP Server
» Select the Control tab. Select Environment Servers from the Administration Console. Select Clone.
» Oracle WebCenter Components Understanding Oracle WebCenter
» Oracle WebCenter Single-node Architecture Oracle WebCenter State and Configuration Persistence
» Oracle WebCenter External Dependencies
» Oracle WebCenter Configuration Considerations
» Oracle WebCenter Analytics Communications
» Oracle WebCenter State Replication Understanding the Distributed Java Object Cache
» Maintaining Configuration in a Clustered Environment
» Installing Oracle Fusion Middleware for Oracle WebCenter
» Enabling the Administration Server VIP
» Configuring a Virtual Host for Oracle Pagelet Producer and Sharepoint
» Configuring Activity Graph Click Start.
» Converting Discussions from Multicast to Unicast
» Configuring a Cluster for Oracle WebCenter Portal Applications
» Agent Startup and Shutdown Cycle Oracle Data Integrator External Dependencies
» Java EE Agent Configuration Standalone Agent Configuration
» Oracle Data Integrator Clustered Deployment
» WebLogic Server or Standalone Agent Crash Repository Database Failure
» About the 11g Oracle Identity Management Products
» Database Prerequisites Installing and Configuring the Database Repository
» Oracle Internet Directory Component Characteristics
» Oracle Internet Directory High Availability Architecture
» Protection from Failures and Expected Behavior
» Installing Oracle Fusion Middleware for Identity Management The next step is to
» Registering Oracle Internet Directory with a WebLogic Domain If you want to
» Creating boot.properties for the Administration Server on OIDHOST1 This section
» Configuring Oracle Internet Directory on OIDHOST2 Ensure that the Oracle Internet
» Validating Oracle Internet Directory High Availability
» Performing an Oracle Internet Directory Failover Performing an Oracle RAC Failover
» Troubleshooting Oracle Internet Directory High Availability
» Changing the Password of the ODS Schema Used by Oracle Internet Directory
» Oracle Virtual Directory Runtime Considerations Oracle Virtual Directory Component Characteristics
» Oracle Virtual Directory High Availability Architecture
» Configuring Oracle Virtual Directory on OVDHOST2 Follow these steps to configure
» Registering Oracle Virtual Directory with a WebLogic Domain It is recommended
» On the Installation Complete screen, click Finish to confirm your choice to exit.
» Troubleshooting LDAP Adapter Creation
» Oracle Directory Integration Platform Component Characteristics
» Oracle Directory Integration Platform High Availability Architecture
» Configuring Oracle HTTP Server for Oracle Directory Services Manager High
» If WebLogic Node Manager Fails to Start Operation Cannot Be Completed for Unknown Errors Message
» Oracle Directory Services Manager Component Characteristics
» Oracle Directory Services Manager High Availability Architecture
» Protection from Failures and Expected Behaviors
» Performing a WebLogic Server Instance Failover
» Using Oracle Directory Services Manager to Validate a Failover of a Managed Server
» Collocated Architecture Overview Troubleshooting Collocated Components Manager High Availability
» Additional Considerations for Collocated Components High Availability
» Oracle Access Manager Component Characteristics
» Oracle Access Manager High Availability Architecture
» Oracle Security Token Service High Availability Architecture
» Oracle Security Token Service Component Characteristics
» In the Customize Server and Cluster Configuration screen, select Yes, and click
» On the Configuration Summary screen, click Create to begin the creation process.
» Oracle Identity Manager Component Characteristics
» Runtime Processes Component and Process Lifecycle
» Starting and Stopping Oracle Identity Manager Configuration Artifacts External Dependencies
» Oracle Identity Manager High Availability Architecture
» On the Welcome screen, select Create a WebLogic Domain.
» Connect to the database as the leasing user.
» Select Environment - Servers from the Administration Console. Select Clone.
» Select the Automatic Server Migration Enabled option. This enables the Node Click Save.
» Click the OIMMSServerXXXXXX subdeployment. Add the new JMS Server
» Click Save. Authorization Policy Manager High Availability
» Oracle Adaptive Access Manager Component Characteristics
» Oracle Adaptive Access Manager High Availability Architecture
» On the Welcome screen, click Next.
» Oracle Identity Federation Component Characteristics
» High Availability Considerations for Integration with Oracle Access Manager
» Oracle Internet Directory Oracle Virtual Directory Oracle HTTP Server Node Manager
» WebLogic Administration Server Oracle Identity Manager
» Oracle Access Manager Managed Servers Oracle Adaptive Access Manager Managed Servers
» Oracle Identity Federation Starting and Stopping Oracle Identity Management Components
» Oracle HTTP Server and Oracle WebLogic Server
» Prerequisites Configuring Oracle HTTP Server for High Availability
» Install Oracle HTTP Server on WEBHOST2
» Oracle Web Cache Request Flow
» Oracle Web Cache Stateless Load Balancing
» Oracle Web Cache Backend Failover Oracle Web Cache Session Binding
» Oracle Web Cache Cluster-Wide Configuration Changes
» Oracle Web Cache as a Software Load Balancer
» From the Session Name list, select a session to enable binding for a specific
» Click Add. In the Component field, enter the name of the cache member.
» Adding a Node in Oracle Advanced Database Multimaster Replication
» Deleting a Node in Oracle Advanced Database Multimaster Replication
» Oracle IPM Component Characteristics
» Oracle IPM High Availability Architecture
» Creation of Oracle IPM Artifacts in a Cluster Troubleshooting Oracle IPM
» Oracle UCM Component Characteristics
» Oracle UCM High Availability Architecture
» Oracle UCM and Inbound Refinery High Availability Architecture
» Oracle URM High Availability Protection from Failure and Expected Behaviors
» Shared Storage Configuring the Oracle Database
» Installing Oracle ECM on ECMHOST1
» On the Welcome screen, select Create a new WebLogic domain.
» In the Select JMS Distributed Destination Type screen, select UDD from the
» Configuring Oracle HTTP Server on WEBHOST1
» Terminology for Directories and Directory Environment Variables
» Administration Server Topology 1 Transforming Oracle Fusion Middleware Infrastructure Components
» Administration Server Topology 2 Transforming Oracle Fusion Middleware Infrastructure Components
» Click Activate Changes. Choose Environment Servers. Click Control. Select WLS_EXMPL. Click Start.
» Transforming Oracle Internet Directory and Its Clients
» Select the Connect to a directory -- Create A New Connection link in the
» Click JDBC Connection under Data Sources.
» Click Administration. Click Scheduler Configuration under System Maintenance Click Apply.
» Database Instance Platform-Specific Considerations
» Example Topology 1 Example Topology 2
» Destination Topologies Cold Failover Cluster Transformation Procedure
» Introduction to Oracle Clusterware Cluster Ready Services and Oracle Fusion Middleware
» Upgrading Older Versions of ASCRS to the Current ASCRS Version Installing ASCRS
» Configuring ASCRS with Oracle Fusion Middleware
» Creating a Virtual IP Resource Creating a Shared Disk Resource
» Creating an Oracle Database Listener Resource Creating an Oracle Database Resource
» Creating a Middleware Resource
» Updating Resources Starting Up Resources Shutting Down Resources Resource Switchover
» Oracle Portal, Forms, Reports, and Discoverer Architecture
» Oracle Forms Runtime Considerations Oracle Forms Process Flow
» Oracle Forms Configuration Files Oracle Forms External Dependencies Oracle Forms Log Files
» Oracle Discoverer Runtime Considerations
» Preference Server Failover Session State Replication and Failover Performance Recommendation
» Dependencies Network Requirements Prerequisites
» Install Oracle WebLogic Server Install Oracle Portal, Forms, Reports, and Discoverer Validation
» Oracle BI EE Component Characteristics
» Oracle BI EE and EPM High Availability Architecture
» Shared Files and Directories
» Cluster-Wide Configuration Changes Oracle BI EE High Availability Concepts
» Oracle Essbase Component Characteristics
» Oracle Essbase High Availability Architecture Protection from Failures and Expected Behaviors
» Oracle Hyperion Provider Services Component Characteristics
» Oracle Hyperion Provider Services High Availability Architecture
» Workspace Component Characteristics Oracle EPM Workspace Component Architecture
» Workspace High Availability Architecture
» Oracle Hyperion Financial Reporting Component Characteristics
» Oracle BI Publisher Component Characteristics
» Oracle BI Publisher High Availability Architecture
» Oracle RTD Component Characteristics
» Oracle RTD High Availability Architecture
Show more