Select Configure all data sources as RAC multi data sources in the next Click Next. In the Driver drop-down list, select Oracles Driver Thin for RAC Enter the Service name. Enter the Prefix_Username for Oracle WebCenter schemas. Click Servers. Open the Co
4. Enter the Domain Name, Domain Location, and Application Location and click
Next . 5. In the Configure Administrator Username and Password screen, enter the username and password to be used for the domains administrator, and click Next. 6. In the Configure Server Start Mode and JDK screen, make the following selections: ■ WebLogic Domain Startup Mode: select Production Mode ■ JDK Selection: select Oracle JRockit 1.6.0_14 SDK. Click Next.7. In the Configure JDBC Data Sources screen. select Configure selected component
schemas as RAC multi data source schemas in the next pane . The Repository Creation Utility creates the necessary schemas in the Oracle database. You provide a custom prefix for these schemas. Table 6–10 lists the data sources, the schemas used and the managed servers to which they are assigned. a. Ensure that the following data source appears on the screen.b. Select Configure all data sources as RAC multi data sources in the next
panel .c. Click Next.
8. In the Configure RAC Multi Data Source Component Schema screen, click the Add
button to add the Host name, Instance name, and Listen port of both Oracle RAC nodes. Table 6–10 Oracle WebCenter Data Sources Data Source Schema Name ActivitiesDS wcedg_activities DiscussionsDS wcedg_discussions PersonalizationDS wcedg_webcenter PortletDS wcedg_portlet WebCenterDS wcedg_webcenter WebCenterMDS wcedg_mds Configuring High Availability for Oracle ADF and WebCenter Applications 6-55 Figure 6–6 Configure RAC Multi Data Source Component Schema Screen Leave one schema checked and uncheck the other schemas.a. In the Driver drop-down list, select Oracles Driver Thin for RAC
Service-Instance connections .b. Enter the Service name.
c. Enter the Prefix_Username for Oracle WebCenter schemas.
d. Enter the Password for the schemas.
e. Click Add to enter the details for the first Oracle RAC instance. f. Update each multi data source schema by selecting one data source at a time and adding the appropriate details. Click Next. 9. In the Test JDBC Data Sources screen, the connections are tested automatically. The Status column shows the results. Ensure that all connections were successful. If not, click Previous to return to the previous screen and correct your entries. Click Next when all the connections are successful. 10. In the Select Optional Configuration screen, select the following: ■ Administration Server ■ Managed Servers, Clusters and Machines 11. In the Customize Server and Cluster Configuration screen, select Yes, and click Next . 12. In the Configure the Administration Server screen, enter the following values: ■ Name: AdminServer ■ Listen Address: Enter the VIP address used in Section 6.4.4 . 6-56 Oracle Fusion Middleware High Availability Guide ■ Listen Port: 7001 ■ SSL listen port: NA ■ SSL enabled: leave unchecked Click Next. 13. In the Configure Managed Servers screen, add the following managed servers: Click Next. 14. In the Configure Clusters screen, add the following clusters Portlet_Cluster ■ Name: Portlet_Cluster ■ Cluster Messaging Mode: unicast ■ Cluster Address Enabled: leave blank Spaces_Cluster ■ Name: Spaces_Cluster ■ Cluster Messaging Mode: unicast ■ Cluster Address Enabled: leave blank Collaboration_Cluster ■ Name: Collaboration_Cluster ■ Cluster Messaging Mode: unicast ■ Cluster Address Enabled: leave blank Utilities_Cluster ■ Name: Utilities_Cluster Table 6–11 Configuring Managed Servers Name Listen Address Listen Port SSL Listen Port SSL Enabled WC_Portlet Hostname of APPHOST1 8889 na unchecked WC_Portlet2 Hostname of APPHOST2 8889 na unchecked WC_Spaces1 Hostname of APPHOST1 8888 na unchecked WC_Spaces2 Hostname of APPHOST2 8888 na unchecked WC_ Collaboration1 Hostname of APPHOST1 8890 na unchecked WC_ Collaboration2 Hostname of APPHOST2 8890 na unchecked WC_Utilities1 Hostname of APPHOST1 8891 na unchecked WC_Utilities2 Hostname of APPHOST2 8891 na unchecked Note: By default, each Oracle WebCenter cluster is configured as unicast. To configure your Oracle WebCenter cluster for multicast, see Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server. Configuring High Availability for Oracle ADF and WebCenter Applications 6-57 ■ Cluster Messaging Mode: unicast ■ Cluster Address Enabled: leave blank Click Next. 15. In the Assign Servers to Clusters screen, assign the following servers to clusters: ■ Spaces_Cluster WC_Spaces1 WC_Spaces2 ■ Portlet_Cluster WC_Portlet1 WC_Portlet2 ■ Collaboration_Cluster WC_Collaboration1 WC_Collaboration2 ■ Utilities_Cluster WC_Utilities1 WC_Utilities2 Click Next. 16. In the Configure Machines screen: ■ Delete the LocalMachine that appears by default. ■ Click the Unix Machine tab, and add the following machines: Click Next. 17. In the Assign Servers to Machines screen, assign servers to machines as follows: Table 6–12 Configuring Machines Name Node Manager Listen Address APPHOST1 Hostname of APPHOST1 APPHOST2 Hostname of APPHOST2 6-58 Oracle Fusion Middleware High Availability Guide Figure 6–7 Assign Servers to Machines Screen ■ APPHOST1: WC_Spaces1, WC_Portlet1, WC_Collaboration1, WC_Utilities1 ■ APPHOST2: WC_Spaces2, WC_Portlet2, WC_Collaboration2, WC_Utilities2 Click Next.18. In the Configuration Summary screen, click Create.
19. In the Creating Domain screen, click Done.
6.4.6 Creating boot.properties for the Administration Server and for Managed Servers on APPHOST1
This is an optional step for enabling the Administration Server to start without prompting you for the administrator username and password. Create a boot.properties file for the Administration Server and for the managed servers on APPHOST1. For the Administration Server: 1. Create the following directory: APPHOST1 mkdir -p MW_HOMEuser_ projectsdomainswcdomainserversAdminServersecurity 2. Use a text editor to create a file called boot.properties in the directory created in the previous step, and enter the following lines in the file: username=adminuser password=password Configuring High Availability for Oracle ADF and WebCenter Applications 6-59 For the WC_Spaces1 managed server: 1. Create the following directories: APPHOST1 mkdir ORACLE_BASEproductfmwuser_ projectsdomainswcdomainserversWC_Spaces1security 2. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file: username=adminuser password=password 3. Repeat Steps 2 and 3 for the WC_Portlet1 and WC_Collaboration1 Managed Servers on APPHOST1.6.4.7 Starting the System in APPHOST1
This section describes procedures for starting the system in APPHOST16.4.7.1 Starting the Administration Server on APPHOST1
To Start the Administration Server on APPHOST1 run the following commands: APPHOST1 cd ORACLE_BASEproductfmwuser_projectsdomainswcdomainbin APPHOST1 .startWebLogic.sh6.4.7.2 Validating the Administration Server
To verify that the Administration Server is properly configured: 1. In a browser, go to http:VIP1:7001console. 2. Log in as the administrator. 3. Verify that all the managed servers WC_Spaces1, WC_Spaces2, and so on are listed. 4. Verify that all Clusters are listed. 5. Verify that you can access Enterprise Manager at http:VIP1:7001em. Note: When you start the Administration Server, the username and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible for the entries to be encrypted. Note: When you start the Administration Server, the username and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. 6-60 Oracle Fusion Middleware High Availability Guide 6.4.7.3 Disabling Host Name Verification for the Administration Server and the Managed Servers for APPHOST1 and APPHOST2 This step is required if you have not set up SSL communication between the Administration Server and the Node Manager. If SSL is not set up, you receive an error message unless you disable host name verification. You can re-enable host name verification when you have set up SSL communication between the Administration Server and the Node Manager. To disable host name verification:1. In Oracle WebLogic Server Administration Console, select Servers, and then
AdminServer .2. Select SSL, and then Advanced.
3. In the Change Center, click Lock Edit.
4. When prompted, save the changes and activate them.5. Set Hostname Verification to None.
6. Select WC_Spaces1, SSL, and then Advanced.
7. Set Hostname Verification to None.
8. Repeat Steps 6 and 7 for all the Managed Servers. 9. Restart the AdminServers and all the Managed Servers.6.4.7.4 Starting Node Manager on APPHOST1
Perform these steps to start Node Manager on APPHOST1: 1. Run the setNMProps.sh script, which is located in the ORACLE_COMMON_ HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: APPHOST1 cd ORACLE_COMMON_HOMEcommonbin APPHOST1 .setNMProps.sh2. Start Node Manager:
APPHOST1 cd WL_HOMEserverbin APPHOST1 .startNodeManager.sh6.4.8 Install WebLogic Server and Oracle WebCenter on APPHOST2
Repeat the procedures for installing WebLogic Server and Oracle WebCenter for APPHOST2, start with Section 6.4.3.1, Installing Oracle WebLogic Server . The directory paths for binary files and domains used when installing new nodes must be exactly the same as those used for first node. If these paths and domains are not exactly the same as those used for the first node, failover is does not occur. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. Configuring High Availability for Oracle ADF and WebCenter Applications 6-616.4.9 Propagating the Domain Configuration to APPHOST2 with packunpack Utilities
Follow these steps to propagate the domain configuration to APPHOST2 using PackUnpack utilities:1. Run the following pack command on APPHOST1 to create a template pack:
APPHOST1 cd WL_HOMEcommonbin APPHOST1 .pack.sh -managed=true -domain=ORACLE_BASEproductfmwuser_ projectsdomainswcdomain -template=wcdomaintemplate.jar -template_name=wc_domain_template2. Run the following command on APPHOST1 to copy the template file created in
the previous step to APPHOST2 using, in this example, scp: APPHOST1 scp wcdomaintemplate.jar APPHOST2:WL_HOMEcommonbin3. Run the unpack command on APPHOST2 to unpack the propagated template:
APPHOST2 cd WL_HOMEcommonbin APPHOST2 .unpack.sh -domain=ORACLE_BASEproductfmwuser_projectsdomainswcdomain -template=wcdomaintemplate.jar6.4.10 Starting Node Manager on APPHOST2
To start the Node Manager on APPHOST2, repeat the steps from Section 6.4.7.4, Starting Node Manager on APPHOST1. on APPHOST2. 6.4.11 Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers Enable Oracle HTTP Server to route to the Administration Server that contains Oracle WebCenter managed servers, by setting the WebLogicCluster parameter to the list of nodes in the cluster. 1. Add the following lines to the OHS_HOMEinstancesohs_ instance1configOHSohs1mod_wl_ohs.conf file: Spaces Location webcenter WebLogicCluster apphost1.com:8888,apphost2.com:8888 SetHandler weblogic-handler Location Location webcenterhelp WebLogicCluster apphost1.com:8888,apphost2.com:8888 SetHandler weblogic-handler Location Location rss WebLogicCluster apphost1.com:8888,apphost2.com:8888 SetHandler weblogic-handler Location Location rest WebLogicCluster apphost1.com:8888,apphost2.com:8888 SetHandler weblogic-handler 6-62 Oracle Fusion Middleware High Availability Guide Location Location wcsdocs WebLogicCluster apphost1.com:8888,apphost2.com:8888 SetHandler weblogic-handler Location Pagelet Producer Location pageletadmin WebLogicCluster apphost1.com:8889,apphost2.com:8889 SetHandler weblogic-handler Location Activity Graph The WebLogicHost below should be set to the Host on which ActivityGraph is running Location activitygraph-engines WebLogicCluster apphost1.com:8891 SetHandler weblogic-handler Location Portlet Location portalTools WebLogicCluster apphost1.com:8889,apphost2.com:8889 SetHandler weblogic-handler Location Location wsrp-tools WebLogicCluster apphost1.com:8889,apphost2.com:8889 SetHandler weblogic-handler Location Discussions Location owc_discussions WebLogicCluster apphost1.com:8890,apphost2.com:8890 SetHandler weblogic-handler Location AdminServer and EM Location console SetHandler weblogic-handler WebLogicHost VIP1 WeblogicPort 7001 Location Location consolehelp SetHandler weblogic-handler WebLogicHost VIP1 WeblogicPort 7001 Location Location em SetHandler weblogic-handler WebLogicHost VIP1 WeblogicPort 7001 Location 2. Restart Oracle HTTP Server on WEBHOST1: WEBHOST1 OHS_HOMEinstancesohs_instance1binopmnctl restartproc ias-component=OHS_COMPONENT1 Configuring High Availability for Oracle ADF and WebCenter Applications 6-636.4.11.1 Configuring a Virtual Host for Oracle Pagelet Producer and Sharepoint
The WebCenter suite includes two applications that use as the web context root: ■ Sharepoint Root - deployed on WC_Spaces ■ Pagelet Producer Root - deployed on WC_Portlet6.4.11.1.1 Virtual Hosts Requirement To route the Sharepoint Root and Pagelet Producer
Root applications without virtual hosts by using Oracle HTTP Server OHS, you could add the following entry: Location SetHandler weblogic-handler WebLogicHost webcenter.example.com WebLogicPort 8889 Location This entry grabs all context roots that are not defined explicitly. Also, Sharepoint and Pagelet Producer require mapping, which isn’t possible to do in a single OHS. For this reason, you need a virtual host configuration. A virtual host configuration is a single system that runs more than one web site, such as www.company1.com and www.company2.com. Virtual hosts are IP-based a unique IP address for each web site or name-based multiple names run on each IP address. It is not obvious to end users that the web sites run on the same physical server. For additional information on virtual hosts, please see Apache HTTP Server documentation. Oracle HTTP Server Configuration The following entry adds two name-based hosts: one for Sharepoint Root and one for Pagelet Producer Root. 1. Find OHS httpd.conf in WEBTIER_INSTANCE_HOMEconfigOHSohs. 2. Find sample VirtualHost configuration and add the following entry: NameVirtualHost :7777 VirtualHost :7777 ServerName webhost.example.com VirtualHost VirtualHost :7777 ServerName webtier-pageletproducer.example.com Location SetHandler weblogic-handler WebLogicCluster apphost1:8889,apphost2:8889 Location VirtualHost VirtualHost :7777 ServerName webtier-spaces.example.com Location SetHandler weblogic-handler WebLogicCluster apphost1:8888,apphost2:8888 Location Location webcenter Deny from all Location Location webcenterhelp Deny from all Location 6-64 Oracle Fusion Middleware High Availability Guide Location rest Deny from all Location VirtualHost 3. Ensure that the new virtual hosts webtier-pageletproducer and webtier-spaces have been added to DNS.6.4.11.1.2 Additional Configuration In case of Virtual Host setup, you must configure
additional properties to use applications routed via virtual host. Sharepoint For single sign-on setups, including integration with Oracle Access Manager 10g or Oracle Access Manager 11g, see the Oracle® Fusion Middleware Administrators Guide for Oracle WebCenter. Oracle Pagelet Producer To access Oracle Pagelet Producer, use webtier-pageletproducer.example.com. For example, when you register Oracle Pagelet Producer in WebCenter Spaces or a custom application, it should use the virtual host for Oracle Pagelet Producer. Similarly, access to Oracle Pagelet Producer and any Pagelet Producer resources should be by means of Virtual Host. Please refer to Oracle Pagelet Producer documentation for additional information.6.4.11.2 Validating Access through Oracle HTTP Server
Verify the URLS to ensure that appropriate routing and failover is working from the HTTP Server to Oracle WebCenter cluster. 1. Start WC_Spaces1, WC_Spaces2, WC_Portlet1 and WC_Portlet2 from the WebLogic Server Administration Console as follows: a. Access the Administration Console at the following URL http:APHHOST1consoleb. Click Servers.
c. Open the Control tab.
d. Select WC_Spaces1, WC_Spaces2, WC_Portlet1 and WC_Portlet2.
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