TTY Access to Oracle Support Services Oracle provides … in the following sample XML code. < operation name=” update ” xel_data … classes12.zip (for Oracle Database) or jconn2.jar … Oracle® Identity Manager Connector Guide for Database Tables Oracle Identity Manager Connector Guide for Database Tables Oracle Identity Manager Connector Guide for Database Tables, Release 9.0.1 B31115-01 Copyright © 2006, Oracle. All rights reserved. Primary Authors: Debapriya Datta, Shiladitya Guha Contributing Authors: Don Gosselin, …

Step 1: Verifying Deployment Requirements The following table lists the deployment requirements for the connector. In addition to the requirements mentioned in the preceding table, you must ensure that the following requirements are addressed: ? JDBC connectivity is available to the target database. ? The target database application schema is analyzed and the corresponding XML file is available according to the IT resource definition. Item Requirement Oracle Identity Manager Oracle Identity Manager release 8.5.3 or later Target systems The target system can be one of the following: ? Oracle9 i Database ? Sybase 12.5.2 Target system host platforms Solaris 9 External code ? xerces.jar (the XML parser) ? classes12.zip (required if the target system is Oracle Database) ? jconn2.jar (required if the target system is Sybase) Step 2: Configuring the Target System 2-2 Oracle Identity Manager Connector Guide for Database Tables ? The JDBC driver and Xerces classes are available in the Oracle Identity Manager classpath. ? For secure connectivity to the target database, the required configuration has been performed on the database server. Step 2: Configuring the Target System For successful provisioning and reconciliation, you must analyze and configure the schema of the target application according to the configuration XML file. The configuration file is validated against the XML schema for database applications. Therefore, it is recommended that you review the schema before creating the XML file. The configuration XML file can be divided into the following sections: ? target_application ? target_database ? mapping_data ? database_adapter target_application This section is used to identify the target application. The purpose of this section is to provide information that simplifies maintenance of the configuration file. target_database This section contains information that is used to configure the database connection properties. mapping_data This section is used to keep track of the configuration files modification history. database_adapter This section is divided into operations. Each operation is further divided into one or more tasks. The number of tasks in an operation depends on the number of tables involved in the operation. Tasks are divided into columns depending on the target application table. The following table explains the organization of the database_adapter section.

Download Oracle Identity Manager Connector Guide for Database Tables.Pdf