Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Documentation Updates
• Conventions

1 Overview of the Installation Procedure

2 Planning the Installation

• 2.1 Host Requirements for Oracle Identity Manager Components
  • 2.1.1 Oracle Identity Manager Server (Host) Requirements
  • 2.1.2 Database Server Host Requirements
  • 2.1.3 Design Console Host Requirements
  • 2.1.4 Remote Manager Host Requirements
• 2.2 Planning for Non-English Oracle Identity Manager Environments
• 2.3 Installation Worksheet
• 2.4 Using the Diagnostic Dashboard
  • 2.4.1 Installing the Diagnostic Dashboard
  • 2.4.2 Verifying Your Preinstallation Environment

3 Installing and Configuring a Database

• 3.1 Using an Oracle Database for Oracle Identity Manager
  • 3.1.1 Installing Oracle Database
  • 3.1.2 Creating an Oracle Database
    • 3.1.2.1 Configuring the Database for Globalization Support
  • 3.1.3 Preparing the Oracle Database
    • 3.1.3.1 Preparing the Database on UNIX
    • 3.1.3.2 Preparing the Database on Microsoft Windows
    • 3.1.3.3 Evaluating Script Results
  • 3.1.4 Removing Oracle Identity Manager Entries from an Oracle Database
• 3.2 Using Oracle RAC Databases for Oracle Identity Manager
  • 3.2.1 Installing Oracle Identity Manager for Oracle RAC
  • 3.2.2 Oracle RAC Net Services
  • 3.2.3 JDBC and Oracle RAC
  • 3.2.4 Configuring JBoss Application Server for Oracle RAC
• 3.3 Using a Microsoft SQL Server Database for Oracle Identity Manager
  • 3.3.1 Installing and Configuring Microsoft SQL Server
  • 3.3.2 Configuring JBoss Application Server for Microsoft SQL Server
  • 3.3.3 Creating a Microsoft SQL Server 2005 Database
  • 3.3.4 Creating a Microsoft SQL Server Database Account
  • 3.3.5 Removing Oracle Identity Manager Entries from a Microsoft SQL Server Database

4 Installing and Configuring JBoss Application Server in Nonclustered Mode

• 4.1 Installing the Java JDK
• 4.2 Installing JBoss Application Server
  • 4.2.1 Setting Environment Variables
• 4.3 Setting Memory Parameters
  • 4.3.1 Setting Memory Allocation for Microsoft Windows
  • 4.3.2 Setting Memory Allocation for UNIX

5 Installing and Configuring JBoss Application Server in Clustered Mode

• 5.1 Overview of Installation in a Clustered Installation
• 5.2 Installing Oracle Identity Manager on the First Node
• 5.3 Copying Oracle Identity Manager to Additional JBoss Application Server Nodes
• 5.4 Setting Up the Apache Web Server for JBoss Application Server
• 5.5 Installing and Configuring a Database for Oracle Identity Manager
• 5.6 Configuring Oracle Identity Manager on the JBoss Application Server Cluster
• 5.7 Starting the JBoss Application Server Cluster

6 Installing Oracle Identity Manager on Windows

• 6.1 Installing the Database Schema
• 6.2 Installing Documentation
• 6.3 Installing Oracle Identity Manager on Microsoft Windows
• 6.4 Removing Oracle Identity Manager

7 Installing Oracle Identity Manager on UNIX

• 7.1 Installation Prerequisites and Notes
• 7.2 Installing the Database Schema
• 7.3 Installing Documentation
• 7.4 Installing Oracle Identity Manager on UNIX
• 7.5 Removing Oracle Identity Manager

8 Postinstallation Configuration for Oracle Identity Manager and JBoss Application Server

• 8.1 Starting Oracle Identity Manager
• 8.2 Stopping Oracle Identity Manager
• 8.3 Accessing the Administrative and User Console
• 8.4 Using the Diagnostic Dashboard to Verify Installation
• 8.5 Removing Backup xlconfig.xml Files After Starting or Restarting
• 8.6 Changing Keystore Passwords
• 8.7 Tuning JDBC Connection Pools
• 8.8 Reserving JBoss Application Server Ports on Microsoft Windows Installation
• 8.9 Increasing the Transaction Timeout
• 8.10 Cleaning Up the JBoss Application Server Installation
  • 8.10.1 Removing JBoss Application Server Components
  • 8.10.2 Removing Files and Directories
    • 8.10.2.1 Nonclustered Installations
    • 8.10.2.2 Clustered Installations
• 8.11 Setting the Compiler Path for Adapter Compilation
• 8.12 Encrypting Oracle Identity Manager Database Password in the xell-ds.xml File for JBoss Application Server
• 8.13 Configuring Proxies to Access Web Application URLs (Optional)
• 8.14 Setting Log Levels (Optional)
  • 8.14.1 Oracle Identity Manager Component Logging
  • 8.14.2 Setting Log Levels for JBoss Application Server
• 8.15 Enabling Single Sign-On (SSO) for Oracle Identity Manager (Optional)
• 8.16 Configuring Custom Authentication (Optional)
• 8.17 Protecting the JNDI Namespace (Optional)
• 8.18 Deploying the SPML Web Service (Optional)

9 Installing and Configuring the Oracle Identity Manager Design Console

• 9.1 Requirements for Installing the Design Console
• 9.2 Installing the Design Console
• 9.3 Postinstallation Requirements for the Design Console
• 9.4 Starting the Design Console
• 9.5 Setting the Compiler Path for Adapter Compilation
• 9.6 Configuring SSL Communication With the Design Console (Optional)
• 9.7 Removing the Design Console Installation

10 Installing and Configuring the Oracle Identity Manager Remote Manager

• 10.1 Installing the Remote Manager on Microsoft Windows
• 10.2 Installing the Remote Manager on UNIX
• 10.3 Configuring the Remote Manager
  • 10.3.1 Changing the Remote Manager Keystore Passwords
  • 10.3.2 Trusting the Remote Manager Certificate
    • 10.3.2.1 Using Your Own Certificate
  • 10.3.3 Enabling Client-side Authentication for Remote Manager
• 10.4 Starting the Remote Manager
• 10.5 Removing the Remote Manager Installation

11 Troubleshooting the Oracle Identity Manager Installation

• 11.1 Task Scheduler fails in a Clustered Installation
• 11.2 Default Login Does Not Work

A Java 2 Security for JBoss Application Server

• A.1 Policy File for Nonclustered JBoss Application Server Installation
• A.2 Policy File for Clustered JBoss Application Server Installation

B Configuring Apache Proxy Plugin

• B.1 Setting Up the Apache Web Server for JBoss Application Server on Microsoft Windows
• B.2 Setting Up the Apache Web Server for JBoss Application Server on UNIX

C Configuring Multiple JBoss Application Server Installations to Use a Single Database

Index