Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documentation
• Conventions

Part I Cloning Oracle Fusion Applications

1 Introduction to Cloning

• 1.1 Understanding Oracle Fusion Applications Cloning
  • 1.1.1 What Is Cloning?
    • 1.1.1.1 Understanding Internal Wiring and Abstract Endpoints
    • 1.1.1.2 What Does Cloning Include?
    • 1.1.1.3 What Changes are Permitted in Cloning?
    • 1.1.1.4 Terminology
  • 1.1.2 Use Cases: When Is Cloning Useful?
    • 1.1.2.1 Other Content Movement Options and How They Differ
  • 1.1.3 Roadmap: What Does the Cloning Process Entail?
• 1.2 Understanding Your Source Environment
  • 1.2.1 If Your Source Environment Has Already Been Installed
  • 1.2.2 If Your Source Environment Was Installed and Virtualized
  • 1.2.3 If You Are Installing Your Source Environment Now
• 1.3 System Requirements for Cloning
  • 1.3.1 Source Requirements
    • 1.3.1.1 Installation and Patch Requirements
    • 1.3.1.2 Source Storage Requirements
    • 1.3.1.3 Database Requirements
    • 1.3.1.4 Oracle Identity Management Component Requirements
    • 1.3.1.5 Port Requirements
  • 1.3.2 Destination Requirements
    • 1.3.2.1 Destination Server Requirements
    • 1.3.2.2 Have JDK Installed on Destination So Clone Package Can be Extracted
    • 1.3.2.3 Target Storage Requirements

2 Cloning Procedure

• 2.1 Overview
• 2.2 Discovery
  • 2.2.1 Using the Discovery Workbook
    • 2.2.1.1 Where to Find provisioning.rsp and provisioning.plan
  • 2.2.2 Prepare for the Discovery Phase
  • 2.2.3 General Info
  • 2.2.4 Topology
    • 2.2.4.1 Topology: Find Source MidTier Abstract Host Name(s)
    • 2.2.4.2 Topology: Find Database Abstract Host Name
    • 2.2.4.3 Topology: Find Source (Real) Host Names, IP Addresses, and Users
    • 2.2.4.4 Topology: Find Oracle Identity Management Information
    • 2.2.4.5 Topology: Give Node Numbers
    • 2.2.4.6 Component Assignment: Associate Nodes with Components
    • 2.2.4.7 Complete Topology Table for Target
    • 2.2.4.8 Blacklisted Hosts
  • 2.2.5 Storage
    • 2.2.5.1 Image Files
    • 2.2.5.2 Shared Storage
    • 2.2.5.3 DMZ Storage
    • 2.2.5.4 Node Storage
    • 2.2.5.5 Directories
    • 2.2.5.6 Inventories
  • 2.2.6 WebLogic Server (WLS) Domains
    • 2.2.6.1 Fusion Applications Domains
    • 2.2.6.2 Identity Management (IDM) Domains
    • 2.2.6.3 Identity Management (IDM) Managed Servers
  • 2.2.7 Virtual Hosts
    • 2.2.7.1 FA HTTP Endpoints
    • 2.2.7.2 IDM HTTP Endpoints
    • 2.2.7.3 LDAP Abstract Names
    • 2.2.7.4 Virtual IPs (VIPs)
    • 2.2.7.5 Additional /etc/hosts File Entries
  • 2.2.8 Databases
    • 2.2.8.1 FA DB Table
    • 2.2.8.2 IDM and (Optional) OID DB Tables
    • 2.2.8.3 Whitelisted DB Links
  • 2.2.9 Identity Management
    • 2.2.9.1 LDAP Containers
    • 2.2.9.2 IDM Users
    • 2.2.9.3 FA Users
    • 2.2.9.4 OAM
    • 2.2.9.5 Credential Store: CSFName
  • 2.2.10 Email and Business Intelligence (BI)
    • 2.2.10.1 Email
    • 2.2.10.2 Business Intelligence
  • 2.2.11 Ports
    • 2.2.11.1 Identity Management Component Ports
    • 2.2.11.2 Fusion Applications Component Ports
  • 2.2.12 Passwords
  • 2.2.13 Generated RSP Entries
• 2.3 Create a Master Image of Source
  • 2.3.1 Prepare Source Environment Name Resolution
    • 2.3.1.1 Verify Whether DNS Entries for HTTP Internal Endpoints Exist on Source
    • 2.3.1.2 Move Internal HTTP Endpoint Entries to /etc/hosts If Necessary
    • 2.3.1.3 Remove Abstract Host Names from DNS if Necessary
    • 2.3.1.4 Remove Virtual IPs from DNS if Necessary
  • 2.3.2 Create Master Image (.tar) Files
• 2.4 Prepare the Target Environment
  • 2.4.1 Configure DNS Entries for External Endpoints
  • 2.4.2 Configure Load Balancer/Reverse Proxy Settings
    • 2.4.2.1 External HTTP Endpoints
    • 2.4.2.2 Internal HTTP Endpoints
    • 2.4.2.3 LDAP Endpoints
  • 2.4.3 Set Up Target Nodes and Storage
    • 2.4.3.1 Verify Target Server Setup
    • 2.4.3.2 Verify System Requirements are Met for Installation
    • 2.4.3.3 Set Up /etc/hosts File for Internal Endpoints
    • 2.4.3.4 Verify Target Storage Setup
    • 2.4.3.5 Verify WebGate Libraries
  • 2.4.4 Test Connectivity
    • 2.4.4.1 Test Hostnames
    • 2.4.4.2 Test Load Balancer/ Reverse Proxy Mapping
• 2.5 Make Master Images Accessible to Target
• 2.6 Duplicate the Databases from Source to Target
  • 2.6.1 Full Discovery of Source Database Environment
  • 2.6.2 Duplicate the Source Database Using Your Preferred Tools
  • 2.6.3 Post-Duplication Activities
  • 2.6.4 Prepare Database Files that the Clone Tool Will Use for Validation
    • 2.6.4.1 Run the discoverEnv.sh Script on Each Database
    • 2.6.4.2 Place Generated Files In Correct Directory
  • 2.6.5 Database Validation and Final Steps
• 2.7 Run faclone.sh to Extract and Rewire Components on Target
  • 2.7.1 How the Clone Phase Works
  • 2.7.2 Executing the Clone Phase Scripts
• 2.8 Perform Validation Steps
• 2.9 Post-Clone Cleanup
  • 2.9.1 Change the RPD Password
  • 2.9.2 Change OID and OVD Passwords
  • 2.9.3 Rewire Informatica Identity Resolution (IIR) in the Functional Setup Manager
  • 2.9.4 Re-Spinning Essbase Cubes for CRM and FSCM
    • 2.9.4.1 Re-spinning for Customer Relations Management (CRM)
    • 2.9.4.2 Re-spinning for Financials (FSCM)
  • 2.9.5 Enable the OIM Job Scheduler

Part II Production-to-Test Data Movement

3 Perform Production-to-Test Data Movement

• 3.1 Introduction
  • 3.1.1 What is Production-to-Test Data Movement?
    • 3.1.1.1 What is Moved in Production to Test?
    • 3.1.1.2 Terminology
  • 3.1.2 Roadmap: What Does Production to Test Data Movement Entail?
• 3.2 Prerequisites
  • 3.2.1 System Requirements
    • 3.2.1.1 Required Patches for Production-to-Test on Target Environment
  • 3.2.2 Obtaining the Production-to-Test Tools
• 3.3 Fill Out the Discovery Workbook
  • 3.3.1 Using the Discovery Workbook
    • 3.3.1.1 Where to Find provisioning.rsp and provisioning.plan
  • 3.3.2 Prepare for the Discovery Phase
  • 3.3.3 P2T Identity Management
    • 3.3.3.1 IDM Database Information (Source and Target)
    • 3.3.3.2 IDM Midtier Information (Production/Source)
    • 3.3.3.3 IDM Midtier Information (Test/Target)
  • 3.3.4 P2T Fusion Applications
    • 3.3.4.1 FA DB
    • 3.3.4.2 FA Common Information
    • 3.3.4.3 FA Test/Target Information
    • 3.3.4.4 FA BI Test/Target Information
    • 3.3.4.5 FA BI (Prod/Source) Information
  • 3.3.5 P2T Passwords
  • 3.3.6 Generated P2T RSP Entries
• 3.4 Reconcile Identity Management Data (IDM)
  • 3.4.1 Validate on the Target OID Server
  • 3.4.2 Disable Reconciliation Jobs on Target OIM
  • 3.4.3 Reconcile OID Directories
  • 3.4.4 Re-enable Reconciliation Jobs on Target OIM
  • 3.4.5 Move Identity and Policy Store Data
  • 3.4.6 Run Validation Script
• 3.5 Move Fusion Applications Data
  • 3.5.1 Run Scripts to Pack Source Files
    • 3.5.1.1 Core Files
    • 3.5.1.2 Business Intelligence (BI) Files
  • 3.5.2 Transfer Files to Target Servers
  • 3.5.3 Export Specific Data from Target (Test) System
  • 3.5.4 Replace Target Data with Source Data
  • 3.5.5 Move Packed Data and Clean Up In-Flight Transactions
    • 3.5.5.1 Validate

Part III Appendices

A Post-Clone Data Masking (Optional)

• A.1 Introduction
  • A.1.1 Data Masking Requirements
  • A.1.2 Data Masking Format Library
  • A.1.3 Data Masking Definitions
  • A.1.4 Preliminary Steps
• A.2 Importing Data Masking Definitions
  • A.2.1 For Oracle Enterprise Manager Grid Control 11g
  • A.2.2 For Oracle Enterprise Manager 11g Database Control
  • A.2.3 For Oracle Enterprise Manager Cloud Control 12c
• A.3 Additional Options
  • A.3.1 Modifying Data Masking Definition
  • A.3.2 Generating the Masking Script
  • A.3.3 Customizing Mask Formats
  • A.3.4 Frequently Asked Questions

B Best Practices: Install with Cloning in Mind

• B.1 Planning the Environment
  • B.1.1 Component Allocation
  • B.1.2 Host Recommendations
  • B.1.3 Storage Mount Points and Directories
• B.2 OS, Provisioning Framework, and JDK Recommendations
• B.3 Identity Management Installation Recommendations
  • B.3.1 Installing Identity Management Databases
  • B.3.2 Installing Identity Management Web- and Mid Tiers
• B.4 Fusion Applications Installation Recommendations
  • B.4.1 Installing Fusion Applications Database
  • B.4.2 Provisioning Fusion Applications

C Abstract Hostnames in Detail

• C.1 How to Discover Abstract Hostnames for Cloning
  • C.1.1 Discovering Fusion Applications Nodes
    • C.1.1.1 Special Case: Web Tier and Fusion Applications on Same Node but Different Hostname Were Provided
    • C.1.1.2 Special case: Hostnames Provided during Provisioning Differ from Actual Hostnames
  • C.1.2 Discovering Identity Management Nodes
    • C.1.2.1 Abstract Hostname of the OAM Node
    • C.1.2.2 Abstract hostname of the OVD Node
  • C.1.3 Discovering Database Nodes
    • C.1.3.1 OID Database
    • C.1.3.2 Identity Management (IDM) Database
    • C.1.3.3 Fusion Applications (FA) Database

D Change JPS Root Name as Needed

• D.1 Access and Edit JPS Root Name
  • D.1.1 Sample File

E Install the BI Administration Tool

• E.1 Installing the Tool
  • E.1.1 System Prerequisites
  • E.1.2 Locate and Install the Software
  • E.1.3 Set up ODBC Connection to Fusion Applications
  • E.1.4 Connect to RPD in BI Admin Tool