Preface

Oracle Identity Management Concepts and Deployment Planning Guide describes concepts pertaining to identity management and provides deployment planning information for administrators and application developers.

This preface contains these topics:

• Intended Audience

• Documentation Accessibility

• Structure

• Related Documents

• Conventions

Intended Audience

This document is intended for the following audience:

• Identity management administrators

• Oracle application administrators

• Enterprise application developers

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure

The Oracle Identity Management Concepts and Deployment Planning Guide provides the conceptual framework required to understand and deploy the Oracle Identity Management infrastructure in an enterprise. Details on how to deploy and administer specific components of the Oracle Identity Management infrastructure are covered in their respective administrator's guides.

This document contains the following chapters:

Chapter 1, "Introduction to Identity Management"

This chapter introduces identity management and describes why it is needed in an enterprise.

Chapter 2, "Oracle Identity Management Concepts and Architecture"

This chapter discusses Oracle Identity Management concepts and architecture.

Chapter 3, "Oracle Identity Management Deployment Planning"

This chapter discusses Oracle Identity Management deployment.

Chapter 4, "Oracle Identity Management Administration and Usage"

This chapter discusses Oracle Identity Management administration and usage.

Chapter 5, "Integrating with Other Identity Management Solutions"

This chapter discusses integrating Oracle Identity Management with other identity management solutions.

Appendix A, "Deploying Oracle Identity Management with Multimaster Replication"

This appendix describes how to install Oracle Identity Management with Multimaster Replication.

Appendix B, "Deploying Oracle Identity Management with Fan-Out Replication"

This appendix describes how to install Oracle Identity Management with Fan-Out Replication.

Appendix C, "Oracle Internet Directory Default Settings"

This appendix discusses the defaults available upon installation of Oracle Internet Directory.

Related Documents

For more information, see the following guides:

• Oracle Application Server Administrator's Guide

• Oracle Application Server Security Guide

• Oracle Application Server High Availability Guide

• Oracle Application Server Installation Guide

• Oracle Application Server Certificate Authority Administrator's Guide

• Oracle Application Server Single Sign-On Administrator's Guide

• Oracle Internet Directory Administrator's Guide

• Oracle Identity Management Guide to Delegated Administration

• Oracle Identity Management Integration Guide

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

• Conventions in Text

• Conventions in Code Examples

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles or emphasis.	Oracle Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
UPPERCASE monospace (fixed-width) font	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.	You can specify this clause only for a NUMBER column. You can back up the database by using the BACKUP command. Query the TABLE_NAME column in the USER_TABLES data dictionary view. Use the DBMS_STATS.GENERATE_STATS procedure.
lowercase monospace (fixed-width) font	Lowercase monospace typeface indicates executable programs, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names and connect identifiers, user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	Enter sqlplus to start SQL*Plus. The password is specified in the orapwd file. Back up the datafiles and control files in the /disk1/oracle/dbs directory. The department_id, department_name, and location_id columns are in the hr.departments table. Set the QUERY_REWRITE_ENABLED initialization parameter to true. Connect as oe user. The JRepUtil class implements these methods.
lowercase italic monospace (fixed-width) font	Lowercase italic monospace font represents placeholders or variables.	You can specify the parallel_clause. Run old_release.SQL where old_release refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Anything enclosed in brackets is optional.	DECIMAL (digits [ , precision ])
{ }	Braces are used for grouping items.	{ENABLE | DISABLE}
|	A vertical bar represents a choice of two options.	{ENABLE | DISABLE} [COMPRESS | NOCOMPRESS]
...	Ellipsis points mean repetition in syntax descriptions. In addition, ellipsis points can mean an omission in code examples or text.	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees;
Other symbols	You must use symbols other than brackets ([ ]), braces ({ }), vertical bars (|), and ellipsis points (...) exactly as shown.	acctbal NUMBER(11,2); acct CONSTANT NUMBER(4) := 3;
Italics	Italicized text indicates placeholders or variables for which you must supply particular values.	CONNECT SYSTEM/system_password DB_NAME = database_name
UPPERCASE	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. Because these terms are not case sensitive, you can use them in either UPPERCASE or lowercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Lowercase typeface indicates user-defined programmatic elements, such as names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9;