Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

What's New in This Guide

• Significant Changes in this Document for 11g Release 11.1.6

1 Enterprise Deployment Overview

• 1.1 What is an Enterprise Deployment?
• 1.2 About Oracle Fusion Applications
• 1.3 Benefits of Oracle Recommendations
  • 1.3.1 Built-in Security
  • 1.3.2 High Availability
• 1.4 Terminology

2 Introduction to the Enterprise Deployment Reference Topologies

• 2.1 Overview of Reference Enterprise Deployment Topologies
  • 2.1.1 Overall Reference Enterprise Deployment Topology
  • 2.1.2 Reference Topologies Documented in the Guide
    • 2.1.2.1 Oracle Fusion Financials Domain
    • 2.1.2.2 Oracle Fusion Customer Relationship Management Domain
    • 2.1.2.3 Oracle Fusion Common Domain
    • 2.1.2.4 Oracle Fusion Human Capital Management Domain
    • 2.1.2.5 Oracle Fusion Supply Chain Management Domain
    • 2.1.2.6 Oracle Fusion Projects Domain
    • 2.1.2.7 Oracle Fusion Procurement Domain
    • 2.1.2.8 Oracle Business Intelligence Domain
  • 2.1.3 About the Web Tier Nodes
    • 2.1.3.1 Load Balancer Requirements
  • 2.1.4 About the Application Tier
  • 2.1.5 About the Data Tier
• 2.2 Hardware Requirements
• 2.3 Installation Prerequisite
• 2.4 Implementing the Topology

3 Preparing the Network for an Enterprise Deployment

• 3.1 External Virtual Server Names
• 3.2 Internal Virtual IPs
• 3.3 Load Balancer Configuration
• 3.4 Reference Enterprise Deployment Directory Structure
  • 3.4.1 Directory Structure
  • 3.4.2 Binary Directory Structure
  • 3.4.3 Domain Configuration Directory Structure
• 3.5 Shared Storage
  • 3.5.1 Shared Storage for Oracle Business Intelligence
• 3.6 IPs and Virtual IPs
• 3.7 Firewalls and Ports
• 3.8 Clock Synchronization

4 Preparing the Database for an Enterprise Deployment

• 4.1 Understanding the Database in the Enterprise Deployment Topology
• 4.2 Setting Up the Database
  • 4.2.1 Database Host Requirements
  • 4.2.2 Supported Database Versions
  • 4.2.3 Minimum Database Configuration Parameters
• 4.3 Creating and Starting the Database Services
  • 4.3.1 Updating the Kernel Parameters
  • 4.3.2 Adding a Database Patch
• 4.4 Loading the Oracle Fusion Applications Repository into the Oracle RAC Database
• 4.5 Backing Up the Database

5 Using the Provisioning Process to Install Components for an Enterprise Deployment

• 5.1 Understanding Provisioning
• 5.2 Prerequisites for Using the Provisioning Process
• 5.3 Installing Components
  • 5.3.1 Creating the Installation Environment
    • 5.3.1.1 Downloading the Provisioning Repository
    • 5.3.1.2 Installing the Provisioning Framework Bits
  • 5.3.2 Creating a New Provisioning Response File
    • 5.3.2.1 Installation Options Screen
    • 5.3.2.2 Specify Security Updates Screen
    • 5.3.2.3 Provisioning Configurations Screen
    • 5.3.2.4 Response File Description Screen
    • 5.3.2.5 Installation Location Screen
    • 5.3.2.6 System Port Allocation Screen
    • 5.3.2.7 Database Configuration Screen
    • 5.3.2.8 Schema Passwords Screen
    • 5.3.2.9 ODI Password Configuration Screen
    • 5.3.2.10 Domain Topology Configuration Screen
    • 5.3.2.11 Web Tier Configuration Screen
    • 5.3.2.12 Virtual Hosts Configuration Screen
    • 5.3.2.13 Load Balancer Configuration Screen
    • 5.3.2.14 Web Proxy Configuration Screen
    • 5.3.2.15 IDM Properties File Screen
    • 5.3.2.16 Identity Management Configuration Screen
    • 5.3.2.17 Access and Policy Management Configuration Screen
    • 5.3.2.18 IDM Database Configuration Screen
    • 5.3.2.19 Summary Screen
  • 5.3.3 Running the Provisioning Commands to Install Components
• 5.4 Configuring Components
• 5.5 Performing Post-Provisioning Tasks
  • 5.5.1 Validation
  • 5.5.2 Other Tasks
• 5.6 Starting and Stopping the Provisioned Environment

6 Scaling Out Oracle HTTP Server

• 6.1 Performing the Scaleout
• 6.2 Performing WebGate Post-Installation Steps
• 6.3 Installing WebGate Patches
• 6.4 Wiring Oracle HTTP Server with Load Balancer
• 6.5 Validating Oracle HTTP Server on WEBHOST2

7 Setting Up Node Manager for an Enterprise Deployment

• 7.1 Prerequisites for Setting Up Node Manager
• 7.2 Setting Up Node Manager for FINHOST2
• 7.3 Creating the Identity Keystore on FINHOST2

8 Scaling Out the Oracle Fusion Financials Domain

• 8.1 Overview of the Oracle Fusion Financials Domain
• 8.2 Prerequisites for Scaling Out the Oracle Fusion Financials Domain
• 8.3 Adding a New Machine in the Oracle WebLogic Server Console
• 8.4 Packing and Unpacking the Managed Server Domain Home
• 8.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 8.6 Oracle HTTP Server Configuration
• 8.7 Configuring Server Migration for the Managed Servers
• 8.8 Validating the System

9 Scaling Out the Oracle Fusion Customer Relationship Management Domain

• 9.1 Overview of the Oracle Fusion Customer Relationship Management Domain
• 9.2 Prerequisites for Scaling Out the Oracle Fusion Customer Relationship Management Domain
• 9.3 Configuring Oracle Coherence for the odi_server Managed Server
• 9.4 Adding a New Machine in the Oracle WebLogic Server Console
• 9.5 Packing and Unpacking the Managed Server Domain Home
• 9.6 Cloning Managed Servers and Assigning Them to FINHOST2
• 9.7 Oracle HTTP Server Configuration
• 9.8 Configuring Server Migration for the Managed Servers
• 9.9 Validating the System

10 Scaling Out the Oracle Fusion Common Domain

• 10.1 Overview of the Oracle Fusion Common Domain
• 10.2 Prerequisites for Scaling Out the Oracle Fusion Common Domain
  • 10.2.1 Starting Node Manager in SSL Mode
  • 10.2.2 Removing Oracle Coherence Startup Properties from wlcs_server1
  • 10.2.3 Configuring Shared Content Folders for UCM_server1
• 10.3 Adding a New Machine in the Oracle WebLogic Server Console
• 10.4 Packing and Unpacking the Managed Server Domain Home
• 10.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 10.6 Configuring Oracle WebCenter
  • 10.6.1 Configuring Persistence Stores for JMS Servers
  • 10.6.2 Configuring the Oracle WebCenter Portal wc_spaces and wc_spaces2 Servers
  • 10.6.3 Configuring a Default Persistence Store for Transaction Recovery
  • 10.6.4 Setting the Listen Address for IPM_server1 and IPM_server2
  • 10.6.5 Adding IPM_server1 and IPM_server2 VIP Addresses to the List of Allowed Hosts
  • 10.6.6 Creating a Connection to Oracle WebCenter Content
• 10.7 Oracle HTTP Server Configuration
• 10.8 Configuring Server Migration for the Managed Servers
• 10.9 Validating the System

11 Scaling Out the Oracle Fusion Human Capital Management Domain

• 11.1 Overview of the Oracle Fusion Human Capital Management Domain
• 11.2 Prerequisites for Scaling Out the Oracle Fusion Human Capital Management Domain
• 11.3 Adding a New Machine in the Oracle WebLogic Server Console
• 11.4 Packing and Unpacking the Managed Server Domain Home
• 11.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 11.6 Oracle HTTP Server Configuration
• 11.7 Configuring Server Migration for the Managed Servers
• 11.8 Validating the System

12 Scaling Out the Oracle Fusion Supply Chain Management Domain

• 12.1 Overview of the Oracle Fusion Supply Chain Management Domain
• 12.2 Prerequisites for Scaling Out the Oracle Fusion Supply Chain Management Domain
• 12.3 Adding a New Machine in the Oracle WebLogic Server Console
• 12.4 Packing and Unpacking the Managed Server Domain Home
• 12.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 12.6 Oracle HTTP Server Configuration
• 12.7 Configuring Server Migration for the Managed Servers
• 12.8 Validating the System

13 Scaling Out the Oracle Fusion Projects Domain

• 13.1 Overview of the Oracle Fusion Projects Domain
• 13.2 Prerequisites for Scaling Out the Oracle Fusion Projects Domain
• 13.3 Adding a New Machine in the Oracle WebLogic Server Console
• 13.4 Packing and Unpacking the Managed Server Domain Home
• 13.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 13.6 Oracle HTTP Server Configuration
• 13.7 Configuring Server Migration for the Managed Servers
• 13.8 Validating the System

14 Scaling Out the Oracle Fusion Procurement Domain

• 14.1 Overview of the Oracle Fusion Procurement Domain
• 14.2 Prerequisites for Scaling Out the Oracle Fusion Procurement Domain
• 14.3 Adding a New Machine in the Oracle WebLogic Server Console
• 14.4 Packing and Unpacking the Managed Server Domain Home
• 14.5 Cloning Managed Servers and Assigning Them to FINHOST2
• 14.6 Oracle HTTP Server Configuration
• 14.7 Configuring Server Migration for the Managed Servers
• 14.8 Validating the System

15 Scaling Out the Oracle Business Intelligence Domain

• 15.1 Overview of the Oracle Business Intelligence Domain
• 15.2 Prerequisites for Scaling Out the Oracle Business Intelligence Domain
• 15.3 Starting the Default Node Manager
• 15.4 Prerequisites for Scaling Out Oracle Business Intelligence on FINHOST2
  • 15.4.1 Configuring JMS for Oracle BI Publisher
  • 15.4.2 Setting the Listen Address for bi_server1 Managed Server
  • 15.4.3 Updating the FusionVirtualHost_bi.conf Configuration File
• 15.5 Scaling Out Oracle Business Intelligence Components
  • 15.5.1 Scaling Out the Oracle Business Intelligence System on FINHOST2
  • 15.5.2 Starting Node Manager in SSL Mode
  • 15.5.3 Scaling Out the System Components
  • 15.5.4 Configuring Secondary Instances of Singleton System Components
  • 15.5.5 Configuring the bi_server2 Managed Server
    • 15.5.5.1 Setting the Listen Address for the bi_server2 Managed Server
    • 15.5.5.2 Configuring Custom Identity and Custom Trust for the bi_server2 Managed Server
    • 15.5.5.3 Disabling Host Name Verification for the bi_server2 Managed Server
    • 15.5.5.4 Adding bi_server2 System Properties to the Server Start Tab
  • 15.5.6 Performing Additional Configuration for Oracle Business Intelligence High Availability
    • 15.5.6.1 Additional Configuration Tasks for Oracle BI Scheduler
    • 15.5.6.2 Additional Configuration Tasks for Oracle Real-Time Decisions
    • 15.5.6.3 Additional Configuration Tasks for Oracle BI Publisher
    • 15.5.6.4 Additional Configuration Tasks for Oracle BI for Microsoft Office
    • 15.5.6.5 Additional Configuration Tasks for Oracle Financial Reporting
  • 15.5.7 Configuring a Default Persistence Store for Transaction Recovery
  • 15.5.8 Starting and Validating Oracle Business Intelligence on FINHOST2
    • 15.5.8.1 Starting the bi_server2 Managed Server
    • 15.5.8.2 Starting the Oracle Business Intelligence System Components
    • 15.5.8.3 Validating Oracle Business Intelligence URLs
  • 15.5.9 Validating Access Through Oracle HTTP Server
  • 15.5.10 Configuring Node Manager for the Managed Servers
  • 15.5.11 Configuring Server Migration for the Managed Servers
• 15.6 Configuring Oracle Essbase Clustering
  • 15.6.1 Redefining the Essbase Cluster Name After Essbase Scale Out
  • 15.6.2 Validating Essbase Clustering
• 15.7 Validating the System

16 Additional Configuration Procedures for Scaling Out Oracle SOA Suite Server

• 16.1 Enabling Virtual IPs on FINHOST1 and FINHOST2
• 16.2 Setting the Listen Address for soa_server1
• 16.3 Setting the Listen Address for soa_server2
• 16.4 Updating the FusionVirtualHost_fin.conf Configuration File
• 16.5 Configuring JMS for the Oracle SOA Suite Server
• 16.6 Configuring Oracle Coherence for Deploying Composites
• 16.7 Configuring a Default Persistence Store for Transaction Recovery
• 16.8 Disabling Host Name Verification for the soa_servern Managed Servers
• 16.9 Restarting Node Manager on FINHOST1
• 16.10 Starting and Validating soa_server1 on FINHOST1
• 16.11 Restarting Node Manager on FINHOST2
• 16.12 Starting and Validating soa_server2 on FINHOST2

17 Configuring Administration Server High Availability

• 17.1 Enabling Administration Server High Availability
  • 17.1.1 Enabling Administrative Virtual Host on FINHOST1
  • 17.1.2 Adding a New Machine in the Oracle WebLogic Server Console
  • 17.1.3 Enabling the Administration Server to Listen on the Virtual IP Address
• 17.2 Oracle HTTP Server Configuration
• 17.3 Validating the Administration Server
• 17.4 Manually Failing Over the Administration Server to FINHOST2
  • 17.4.1 Prerequisites
  • 17.4.2 Performing the Failover
• 17.5 Failing the Administration Server Back to FINHOST1

18 Setting Up Server Migration for an Enterprise Deployment

• 18.1 Prerequisite
• 18.2 Migrating Oracle Fusion Applications Domains
  • 18.2.1 About Configuring Server Migration
  • 18.2.2 Setting Up a User and Tablespace for the Server Migration Leasing Table
  • 18.2.3 Creating a Multi-Data Source Using the Oracle WebLogic Server Administration Console
  • 18.2.4 Editing Node Manager's Properties File
  • 18.2.5 Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
  • 18.2.6 Configuring Server Migration Targets
  • 18.2.7 Testing the Server Migration

19 Configuring Oracle Business Intelligence Applications

• 19.1 Introduction to Oracle BI Applications for Oracle Fusion Financials
  • 19.1.1 Topology
• 19.2 Roadmap for Installing Oracle BI Applications
• 19.3 Creating Databases for Oracle Business Intelligence Applications Components
• 19.4 Running Oracle BI Applications RCU to Create the Oracle BI Applications Schemas for the Data Warehouse
• 19.5 Extending the Oracle Business Intelligence Domain by Deploying Oracle BI Applications Configuration Manager, Functional Setup Manager, and DAC
  • 19.5.1 How to Configure DAC, Oracle BI Applications Configuration Manager, and Functional Setup Manager
  • 19.5.2 Configuring Data Warehouse Administration Console for High Availability
• 19.6 Configuring Oracle HTTP Server for the Managed Server
• 19.7 Performing Additional Data Warehouse Administration Console Tasks
• 19.8 Validating Oracle BI Applications Components URLs

20 Managing the Topology

• 20.1 Scaling the Topology for Additional Nodes
  • 20.1.1 Scaling Out the Topology (Adding Managed Servers to a New Node) for Oracle ADF Server
    • 20.1.1.1 Prerequisites for Scaling Out the Topology for Oracle ADF Server
    • 20.1.1.2 Adding a New Machine in the Oracle WebLogic Server Console
    • 20.1.1.3 Packing and Unpacking the Managed Server Domain Home
    • 20.1.1.4 Cloning Managed Servers and Assigning Them to FINHOST3
    • 20.1.1.5 Validating the System
  • 20.1.2 Scaling Up the Topology (Adding Managed Servers to an Existing Node) for Oracle ADF Server
    • 20.1.2.1 Cloning Managed Servers and Assigning Them to FINHOST3
    • 20.1.2.2 Validating the System
  • 20.1.3 Scaling Out the Topology (Adding Managed Servers to a New Node) for Oracle SOA Suite Server
    • 20.1.3.1 Prerequisites for Scaling Out the Topology for Oracle SOA Suite Server
    • 20.1.3.2 Adding a New Machine in the Oracle WebLogic Server Console
    • 20.1.3.3 Packing and Unpacking the Managed Server Domain Home
    • 20.1.3.4 Cloning Managed Servers and Assigning Them to FINHOST3
    • 20.1.3.5 Validating the System
    • 20.1.3.6 Additional Configuration Procedures for Scaling Out Oracle SOA Suite Server
  • 20.1.4 Scaling Up the Topology (Adding Managed Servers to an Existing Node) for Oracle SOA Suite Server
    • 20.1.4.1 Cloning Managed Servers and Assigning Them to FINHOST3
    • 20.1.4.2 Validating the System
  • 20.1.5 Scaling Out the Topology (Adding Managed Servers to a New Node) for Oracle Business Intelligence
    • 20.1.5.1 Prerequisites for Scaling Out the Topology for Oracle Business Intelligence
    • 20.1.5.2 Scale-Out Procedure for Oracle Business Intelligence
  • 20.1.6 Scaling Up the Topology for Oracle Business Intelligence
    • 20.1.6.1 Scale-Up Procedure for Oracle Business Intelligence
• 20.2 Performing Backups and Recoveries
• 20.3 Monitoring the Topology
• 20.4 Migrating from a Test Environment to a Production Environment
• 20.5 Configuring Log File Rotation
  • 20.5.1 Specifying Log File Rotation Using Oracle Enterprise Manager
  • 20.5.2 Specifying Log File Rotation Using WLST
• 20.6 Patching the Topology
• 20.7 Auditing
• 20.8 Troubleshooting
  • 20.8.1 Page Not Found When Accessing soa-infra Application Through Load Balancer
  • 20.8.2 soa-infra Application Fails to Start Due to Deployment Framework Issues (Coherence)
  • 20.8.3 Incomplete Policy Migration After Failed Restart of Oracle SOA Suite Server
  • 20.8.4 Oracle SOA Suite Server Fails to Start Due to Maximum Number of Processes Available in Database
  • 20.8.5 Administration Server Fails to Start After a Manual Failover
  • 20.8.6 Error While Activating Changes in Administration Console
  • 20.8.7 Oracle SOA Suite Server Not Failed Over After Server Migration
  • 20.8.8 Oracle SOA Suite Server Not Reachable From Browser After Server Migration
  • 20.8.9 Oracle Access Manager Configuration Tool Does Not Remove URLs
  • 20.8.10 Redirecting of Users to Login Screen After Activating Changes in Administration Console
  • 20.8.11 Redirecting of Users to Administration Console's Home Page After Activating Changes to OAM
  • 20.8.12 Configured JOC Port Already in Use
  • 20.8.13 Out-of-Memory Issues on Managed Servers
  • 20.8.14 JDBC Connection Reset Appears When on OEL 5.4
  • 20.8.15 Missing JMS Instances on Oracle BI Publisher Scheduler Diagnostics Page
  • 20.8.16 Oracle BI Publisher Jobs in Inconsistent State After Managed Server Shutdown
  • 20.8.17 JMS Instance Fails in an Oracle BI Publisher Cluster
  • 20.8.18 Administration Console Redirects from Internal URL to Container URL after Activation
  • 20.8.19 Oracle Essbase Clustering Fails After Clicking Activate Changes

A Deploying Administrative Clients for Oracle Fusion Applications

• A.1 Recommended Solution
• A.2 Implementation

B Worksheets for Oracle Fusion Financials Topology

• B.1 Hosts and Virtual IP Addresses for Oracle Fusion Financials
• B.2 Directory Mapping
• B.3 Port Mapping
• B.4 LDAP Directory Details
• B.5 Database Details
• B.6 Web Tier Details
• B.7 Application Tier Details
• B.8 User and Group Mapping