Click Activate Changes. Choose Environment Servers. Click Control. Select WLS_EXMPL. Click Start.
12.2.2.4.1 Transforming an Oracle WebLogic Managed Server using the Fusion Middleware
Administration Console For this procedure, the WebLogic Server Administration Console must be running. In the following example, cfcvip.mycompany.com is the virtual IP used for the Cold Failover Cluster, and WLS_EXMPL is the managed server to be transformed. 1. Log into the WebLogic Server Administration Console. 2. Create a machine for the virtual host:a. Select Environment Machines.
b. In the Change Center, click Lock Edit.
c. Click New.
d. For the Name field, enter cfcvip.mycompany.com
e. For the Machine OS field, select the appropriate operating system.
f. Click OK.
g. Click the newly created Machine.h. Click Node Manager tab.
i. Update Listen Address: cfcvip.mycompany.com.
j. Click Save.
k. Click Activate Changes.
3. Stop the WLS_EXMPL Managed server:a. Choose Environment Servers.
b. Click Control.
c. Select WLS_EXMPL.
d. Select Force Shutdown Now in the Shutdown drop-down menu.
4. Associate the WLS_EXMPL Managed Server with the VirtualHost Machine:a. Choose Environment Servers.
b. In the Change Center, click Lock Edit.
c. Click Configuration.
d. Select WLS_EXMPL.
e. For Machine, assign the newly created Machine by assigning it from the pull down menu.f. For Listen Address, enter cfcvip.mycompany.com.
g. Click Save.
h. Click Activate Changes.
5. Start the WLS_EXMPL Managed Server: Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-17a. Choose Environment Servers.
b. Click Control.
c. Select WLS_EXMPL.
d. Click Start.
12.2.2.4.2 Transforming an Oracle WebLogic Managed Server using the WLST Command Line
You can transform an Oracle WebLogic managed server using WLST commands as well. Oracle recommends shutting down the managed server you are transforming before performing these steps. To transform a Managed Server using the WLST command line in online mode with the WebLogic Server Administration Server up: 1. In the command line, enter: WL_HOME serverbinsetWLSEnv.sh WL_HOME commonbinwlst.sh 2. In WLST, enter the following commands: wls:offlineconnectusername,password,AdminServer location For example: wls:offlineconnectWebLogic, welcome1, t3:admin.mycompany.com:7001 wls:DomainNameserverConfig edit wls:DomainNameedit startEdit wls:DomainNameedit createcfcvip.mycompany.com,Machine wls:DomainNameedit cdMachinescfcvip.mycompany.comNodeManagercfcvip.mycompany.com wls:DomainNameedit setListenAddress, cfcvip.mycompany.com wls:DomainNameedit cd Servers wls:DomainNameeditServers cd WLS_EXMPL wls:DomainNameeditServersWLS_EXMPL setMachine, cfcvip.mycompany.com wls:DomainNameeditServersWLS_EXMPL setListenAddress, cfcvip.mycompany.com wls:DomainNameeditServersWLS_EXMPL save wls:DomainNameeditServersWLS_EXMPL activate wls:DomainNameeditServersWLS_EXMPL exit Stop if not already down and start the Managed server. Once the Managed server transformation is completed, all references to it should use the new Listen Address - cfcvip.mycompany.com. If Oracle HTTP Server serves as a front end to this Managed server, then any mod_wls_ohs configuration with mount points referring to applications in this Managed server should be changed to route to the new listening end point.12.2.2.5 Transforming Node Manager
Node Manager can be used in a Cold Failover Cluster environment. The possible configurations are: ■ Using a Node Manager that listens on the virtual IP as well and fails over with the rest of the Cold Failover Cluster stack. With ASCRS based deployments, the Node Manager must be part of the same Middleware Home as where the Cold Failover 12-18 Oracle Fusion Middleware High Availability Guide Cluster Fusion Middleware instance is running. This Node Manager is assumed to be dedicated for this Fusion Middleware instance. In this case, Oracle recommends having additional Network Channels listening on the localhost configured. Other Node Managers may co-exist on the box listening on other ports. For more details, see Chapter 13, Using Oracle Cluster Ready Services. ■ A Node Manager that does not failover with the rest of the Cold Failover Cluster stack. In this case, Node Manager is not configured for Cold Failover Cluster and listens on all IPs on the machine, and not specifically on the virtual IP for Cold Failover Cluster. The failover nodes also have a similarly configured Node Manager already available and configured. The Machine associated with the WebLogic instance communicates with the Node Manager on the localhost. For more details, see the Oracle Fusion Middleware Node Manager Administrator’s Guide for Oracle WebLogic Server. For Cold Failover Cluster in general, port usage should be planned so that there are no port conflicts when failover occurs. To convert the Node Manager to Cold Failover Cluster: 1. If Node Manager is running, stop it. The nodemanager.properties file is created only after the first start of Node Manager. Restart the Node Manager if necessary. 2. In the nodemanager.properties file located in the WL_ HOMEcommonnodemanager directory, set the ListenAddress to the virtual IP. For example: ListenAddress=cfcvip.mycompany.com 3. Restart the Node Manager using the StartNodeManager.sh file, located in the WL_HOMEserverbin directory. For ASCRS based deployment, the Node Manager is started using WL_HOMEserverbincfcStartNodemanager.sh. See Chapter 13, Using Oracle Cluster Ready Services. for more details.12.2.2.6 Transforming Oracle Process Management and Notification Server
Oracle Process Management and Notification Server OPMN is used for Process Management of system components and is part of the application server instance. Note: If needed, start the Node Manager only using the cfcStartNodemanager.sh script instead of the startNodeManager.sh script. Note: For WebLogic Managed Servers and Administration Servers, hostname verification may be enabled or disabled in a given installation. For CFC installation where hostname verification is enabled and Node Manager is managing these instances, the hostname verification step should use certificates for the virtual IP cfcvip.mycompany.com as part of these steps. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-19 Oracle recommends keeping the default OPMN configuration in a Cold Failover Cluster environment. No further steps are necessary for Cold Failover Cluster transformation of the OPMN process itself. If you are transforming an Oracle Instance for Cold Failover Cluster and it has already been registered with an Administration Server, make the following changes in these files: 1. In the topology.xml file in the DOMAIN_HOMEopmn directory of the Administration Server domain, change host name entries for this specific Oracle instance being transformed to Cold Failover Cluster to cfcvip.mycompany.com. For example, for an Oracle HTTP Server instance transformed to Cold Failover Cluster, set the following in the topology.xml file property name=HTTPMachine value=cfcvip.mycompany.com For the instance itself: ias-instance id=asinst instance-home=11gr1as3MWasinst host=cfcvip.mycompany.com port=6701 2. In the opmn.xml file in the INSTANCE_HOMEconfigOPMNopmn directory, replace the physicalhostname with cfcvip.mycompany.com: ias-componentias-component id=ReportsServer_physicalhostname_asinst_2 process-set id=ReportsServer_physicalhostname_asinst_2 restart-on-death=true numprocs=1 3. In the instance.properties file in the INSTANCE_HOMEconfigOPMNopmn directory, change adminHost=physical hostname to adminHost=cfcvip.mycompany.com.12.2.2.7 Transforming Oracle Enterprise Manager for an Oracle Instance
When an Oracle instance such as Oracle Internet Directory, Oracle Virtual Directory, Web Tier components, and Oracle Portal, Forms, Reports, and Discoverer components is transformed to Cold Failover Cluster, the Enterprise Manager agent that is part of this Oracle instance must be transformed to Cold Failover Cluster as well. To transform the Enterprise Manager agent: 1. Stop the Enterprise Manager agent using the following command: cd INSTANCE_HOMEEMAGENTemagent_dirbin .emctl stop agent 2. Set the directory to ORACLE_INSTANCEEMAGENTemagent_instance namesysmanconfig. 3. In the emd.properties file, change node1.mycompany.com to cfcvip.mycompany.com for the emd_url attribute. 4. Change the targets.xml file on the agent side: cd INSTANCE_HOMEEMAGENTemagent_dircp targets.xml targets.xml.org Modify targets.xml so that it has only targets related to the host and oracle_emd. Remove all other entries. For example: Targets AGENT_TOKEN=ad4e5899e7341bfe8c36ac4459a4d569ddbf03bc Target TYPE=oracle_emd NAME=cfcvip.mycompany.com:port Target TYPE=host NAME=cfcvip.mycompany.com DISPLAY_ 12-20 Oracle Fusion Middleware High Availability Guide NAME=cfcvip.mycompany.com Targets 5. Stop and restart the agent cd INSTANCE_HOMEEMAGENTemagent_dirbin .emctl start agent Make the following changes for the Enterprise Manager server in the Administration Server domain directory: 1. Set your directory to MW_HOMEuser_projectsdomainsdomain_ namesysmanstate. 2. In the targets.xml file, located in MW_HOMEuser_projectsdomainsdomain_ namesysmanstate directory, modify the hostname from node1.mycompany.com to cfcvip.mycompany.com12.2.2.8 Transforming Web Tier Components and Clients
The Web tier is made up of two primary components, Oracle HTTP Server and Oracle Web Cache. The next two sections describe how to transform Oracle HTTP Server and Oracle Web Cache for Cold Failover Cluster.12.2.2.8.1 Transforming Oracle HTTP Server To transform Oracle HTTP Server for Cold
Failover Cluster: In INSTANCE_HOMEconfigOHScomponent_namehttpd.conf, change the following attributes Listen cfcvip.mycompany.com:port OHS_LISTEN_PORT Listen cfcvip.mycompany.com:port OHS_PROXY_PORT ServerName cfcvip.mycompany.com Also, perform a single sign-on reregistration, as described in Section 12.2.3.14, Single Sign-On Re-registration If required. Clients of Oracle HTTP Server If an Oracle Web Cache instance is routing to Oracle HTTP Server that has been transformed to Cold Failover Cluster, in INSTANCE_ HOMEconfigWebCachecomponent_namewebcache.xml, change the following attributes: Change node1.mycompany.com to cfcvip.mycompany.com, where node1.mycompany.com is the previous address of the Oracle HTTP server before transformation. HOST ID=h1 NAME=cfcvip.mycompany.com PORT=8888 LOADLIMIT=100 OSSTATE=ON HOST ID=h2 NAME=cfcvip.mycompany.com PORT=8890 LOADLIMIT=100 OSSTATE=ON SSLENABLED=SSL12.2.2.8.2 Transforming Oracle Web Cache To transform an Oracle Web Cache for Cold
Failover Cluster: 1. Set up an alias to the physical hostname on both nodes of the cluster in etchosts. This is an alias to the IP address of the node. Set this in etchosts for Linux and Windows location for Windows. The alias name is wcprfx.mycompany.com For example, On node Node1, the etchosts file on UNIX, the entry would be n.n.n.n node1 node1.mycompany.com wcprfx wcprfx.mycompany.comParts
» 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