Connect to the database as the leasing user.
b. Connect to the database as the leasing user.
c. Run the leasing.ddl script in SQLPlus: SQL Copy_Locationleasing.ddl;8.9.3.11.2 Creating a Multi Data Source Using the Oracle WebLogic 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 format of MultiDS-rac0, MultiDS-rac1, and so on. ■ 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 OIM_CLUSTER and the SOA_CLUSTER. ■ Make sure the data source’s connection pool initial capacity is set to 0 zero. 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 zero in the Initial Capacity field. Creating a Multi Data Source Perform these steps to create a multi data source: 1. Log into the Oracle WebLogic Server Administration Console at http:oimhost1.mycompany.com:7001console using the Admin credentials. 2. In the Domain Structure window in the Oracle WebLogic Server Administration Console, expand the Services node, then expand the DataSource node. Configuring High Availability for Identity Management Components 8-1853. Click New. The Create a New JDBC Multi Data Source page opens.
4. Click Lock and Edit.
5. Click Multi Data Sources. The Summary of JDBC Multi Data Source page opens.
6. Enter leasing as the name. 7. Enter jdbcleasing as the JNDI name.8. Select Failover as algorithm default.
9. Click Next.
10. Select OIM_CLUSTER and SOA_CLUSTER as the targets.11. Click Next.
12. Select non-XA driver the default.
13. Click Next.
14. Click Create New Data Source.
15. Enter leasing-rac0 as the name. Enter jdbcleasing-rac0 as the JNDI name. Enter oracle as the database type. For the driver type, select Oracle Driver Thin for RAC server-Instance connection Version 10,11.16. Click Next.
17. Deselect Supports Global Transactions.
18. Click Next.
19. 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 schema.20. Click Next.
21. Click Test Configuration and verify that the connection works.
22. Click Next.
23. Target the data source to OIM_CLUSTER and SOA cluster. 24. Select the data source and add it to the right screen.25. Click Create a New Data Source for the second instance of your Oracle RAC
database, target it to the OIM_CLUSTER and SOA_CLUSTER, repeating the steps for the second instance of your Oracle RAC database. 26. Add the second data source to your multi data source.27. Click Activate Changes.
8.9.3.11.3 Editing Node Manager’s Properties File The third step is to edit Node Manager’s
properties file. This needs to be done for the Node Managers in both nodes OIMHOST1 and OIMHOST2 where server migration is being configured: Interface=eth0 NetMask=255.255.255.0 Note: When creating the multi data sources for the leasing table, enter names in the format of MultiDS-rac0, MultiDS-rac1, and so on. 8-186 Oracle Fusion Middleware High Availability Guide UseMACBroadcast=true ■ Interface: This property specifies the interface name for the floating IP for example, eth0. ■ NetMask: 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. ■ UseMACBroadcast: 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 arping command. 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 Node Manager’s output: ... StateCheckInterval=500 Interface=eth0 NetMask=255.255.255.0 ... 1. Set the following property in the nodemanager.properties file: ■ StartScriptEnabled: Set this property to ’true’. This is required to enable Node Manager to start the managed servers. 2. Start Node Manager on OIMHOST1 and OIMHOST2 by running the startNodeManager.sh script, which is located in the WL_HOMEserverbin directory. Note: Do not specify the sub-interface, such as eth0:1 or eth0:2. This interface is to be used without :0 or :1. 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, eth2, eth3, ethn, depending on the number of interfaces configured. Note: The steps below are not required if the server properties start properties have been properly set and Node Manager can start the servers remotely. Note: When running Node Manager from a shared storage installation, multiple nodes are started using the same nodemanager.properties file. However, each node may require different NetMask or Interface properties. In this case, specify individual parameters on a per-node basis using environment variables. For example, to use a different interface eth3 in HOSTn, use the Interface environment variable as follows: HOSTn export JAVA_OPTIONS=-DInterface=eth3 and start Node Manager after the variable has been set in the shell. Configuring High Availability for Identity Management Components 8-1878.9.3.11.4 Setting Environment and Superuser Privileges for the wlsifconfig.sh Script The
fourth step is to set environment and superuser privileges for the wlsifconfig.sh script: 1. Ensure that your PATH environment variable includes these files: 2. Grant sudo configuration for the wlsifconfig.sh script. ■ 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, perform the following steps to set the environment and superuser privileges for the wlsifconfig.sh script: ■ Grant sudo privilege to the WebLogic user ’oracle’ with no password restriction, and grant execute privilege on the sbinifconfig and sbinarping binaries. ■ 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 ifconfig and arping: oracle ALL=NOPASSWD: sbinifconfig,sbinarping8.9.3.11.5 Configuring Server Migration Targets The fifth step is to configure server
migration targets. You first assign all the available nodes for the cluster’s members and then specify candidate machines in order of preference for each server that is configured with server migration. Follow these steps to configure cluster migration in a migration in a cluster: 1. Log into the Oracle WebLogic Server Administration Console at http:oimhost1.mycompany.com:7001console using the Admin credentials.2. In the Domain Structure window, expand Environment and select Clusters. The
Summary of Clusters page is displayed. 3. Click the cluster for which you want to configure migration OIM_CLUSTER in the Name column of the table.4. Click the Migration tab.
5. Click Lock and Edit.
6. In the Available field, select the machine to which to allow migration and click the
right arrow. In this case, select OIMHOST1 and OIMHOST2. 7. Select the data source to be used for automatic migration. In this case, select the leasing data source. Table 8–9 Files Required for the PATH Environment Variable File Located in this directory wlsifconfig.sh DOMAIN_HOMEbinserver_migration wlscontrol.sh WL_HOMEcommonbin nodemanager.domains WL_HOMEcommon Note: Ask the system administrator for the sudo and system rights as appropriate to this step. 8-188 Oracle Fusion Middleware High Availability Guide8. Click Save.
9. Click Activate Changes.
10. Set the candidate machines for server migration. You must perform this task for all of the managed servers as follows: a. In the Domain Structure window of the 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