test

Sun Identity Manager 8.1 Installation

Preparing a Database

For a list of supported database versions, see Repository Database Servers in Sun Identity Manager 8.1 Release Notes.

You should use an approved third-party relational database to store system data. Do not host the Identity Manager repository on a virtual platform such as a VMware virtual machine because performance (transactions per second) will be adversely affected.

Use the general procedures in this section when setting up the database. Your database administrator may choose to customize the provided scripts to suit your site-specific configuration and standards. Later, during the installation of Identity Manager on your application server, you may need to install a JAR file that contains either a JDCBTM driver or a JNDI InitialContextFactory for your database.

Note –

You must configure your database with a character set that will support the characters that you want to store. If you need to store multi-byte characters, you should use a character set (such as UTF-8) that supports Unicode.

About the Sample Database Scripts

Identity Manager provides sample database scripts that you can modify and use to create tables and indexes. You may choose to use an alternate method to create equivalent tables and indexes, but these requirements must be met:

You can modify the sample scripts to suit your environment.

Common changes include:

Note –

If you make changes to the sample scripts, then you must make equivalent changes to any sample database upgrade scripts that you receive in the future.

Preparing MySQL

Note –

See the Sun Identity Manager 8.1 Release Notes for supported database server versions.

ProcedureTo Prepare MySQL for Use with Identity Manager

  1. Install the MySQLTM software. Start the MySQL process (if it does not start automatically).

  2. Create the database. To do this:

    1. Copy the create_waveset_tables.mysql script to a temporary location. This script is located in the db_scripts directory in the Identity Manager installation package, and also in the idm\sample directory if Identity Manager is already installed.

    2. Modify the create_waveset_tables.mysql script to change the database user password.

    3. Create the new tables by using one of the following commands:

      On Windows

      c:\mysql\bin\mysql -u root < create_waveset_tables.mysql

      On UNIX

      $MYSQL/bin/mysql -u root < create_waveset_tables.mysql

  3. Download a version of MySQL Connector/J to use with MySQL.

    See Notes on Configuring Databases and Downloading Supporting JAR Files for more information.

    Later, during the Identity Manager installation process, you will install the MySQL Connector/J driver to the $WSHOME/WEB-INF/lib directory on your application server.

Preparing Oracle

Note –

See the Sun Identity Manager 8.1 Release Notes for supported database server versions.

ProcedureTo Prepare Oracle for Use with Identity Manager

  1. Install Oracle or confirm the connection to an Oracle database.

  2. Connect to the Oracle instance as a user with privileges to create users and tables.

  3. Create the database. To do this:

    1. Copy the create_waveset_tables.oracle script to a temporary location. This script is located in the db_scripts directory in the Identity Manager installation package, and also in the idm\sample directory if Identity Manager is already installed.

    2. Modify the create_waveset_tables.oracle script:

      1. Change the user password.

      2. Change the path for DATAFILE to point to the location for your waveset.dbf data file.

      Your database administrator may want to modify the script to meet site-specific requirements for backup, replications, disk allocation, distribution, or other considerations.

    3. Create the new tables by using the following command:

      On Windows

      sqlplus dbausername/dbapassword @create_waveset_tables.oracle

      On UNIX

      sqlplus dbausername/dbapassword @create_waveset_tables.oracle

  4. Download the JDBC driver to use with your version of Oracle.

    See Notes on Configuring Databases and Downloading Supporting JAR Files for more information.

    Later, during the Identity Manager installation process, you will install the JDBC driver to the $WSHOME/WEB-INF/lib directory on your application server.

Configuring lh setup for Oracle RAC

If you are using Oracle RAC as your Identity Manager repository and you are connecting with the thin driver, use the following URL parameter format in lh setup:

jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=host01)(PORT=1521))(
ADDRESS=(PROTOCOL=TCP)(HOST=host02)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=host03)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=PROD)))

Preparing DB2

Before setting up DB2, you should decide how DB2 will provide JDBC access.

JDBC Access Considerations

DB2 offers two types of JDBC access, each of which requires a different URL format. The setup process allows you to select a preferred driver and automatically displays the corresponding URL template.

The application driver (COM.ibm.db2.jdbc.app.DB2Driver) requires local client software and a local database instance. Since DB2 runs on a separate (often dedicated) host in most production environments, the local database instance usually contains an alias to the remote database instance. In this configuration, the local database instance uses a DB2-specific protocol to communicate with the remote database instance.

The Type 2 network driver (COM.ibm.db2.jdbc.net.DB2Driver) does not require local client software or a local database. It does require that the DB2 Java daemon (db2jd) be running on the target server. (In most production environments, the target server is a separate host, but the network driver works as well with a local database instance.) This daemon is not started by default, but the database administrator can start it manually or configure it to start automatically when the database instance starts.

The Type 4 network driver (COM.ibm.db2.jcc.DB2Driver) connects directly to the DB2 database.

Note –

When using the type 4 driver (in a direct connection) with at least DB2 8.1.2, download the following driver:

com.ibm.db2.jcc.DB2Driver

Later, during the Identity Manager installation process, you will need to copy the following files to the $WSHOME/WEB-INF/lib directory on your application server:

db2jcc

db2jcc_license_cisuz.jar or db2jcc_license_cu.jar

See Notes on Configuring Databases and Downloading Supporting JAR Files for more information.

Preparing DB2 for Use with Identity Manager

Follow these steps to set up DB2.

Note –

See the Sun Identity Manager 8.1 Release Notes for supported database server versions.

ProcedureTo Prepare DB2 for Use with Identity Manager

  1. Install DB2 or confirm the connection to a DB2 database.

  2. Connect to the DB2 instance as a user with privileges to create users and tables.

  3. Create the database. To do this:

    1. Copy the create_waveset_tables.db2 script to a temporary location. This script is located in the db_scripts directory in the Identity Manager installation package, and also in the idm\sample directory if Identity Manager is already installed.

    2. Modify the create_waveset_tables.db2 script:

      • Change the user password.

      • Change the path for the CREATE_TABLESPACE command to a location appropriate for your environment.

      Your database administrator may want to modify the script to meet site-specific requirements for backup, replications, disk allocation, distribution, or other considerations.

      Create the new tables by using the following command:

      On Windows

      db2 -tvf create_waveset_tables.db2

      On UNIX

      db2 -tvf create_waveset_tables.db2

Preparing SQL Server

Note –

See the Sun Identity Manager 8.1 Release Notes for supported database server versions.

ProcedureTo Prepare SQL Server for Use with Identity Manager

  1. Install Microsoft SQL Server or confirm the connection to a SQL Server installation.

  2. Create the database. To do this:

    1. Copy the create_waveset_tables.sqlserver script to a temporary location. This script is located in the db_scripts directory in the Identity Manager installation package, and also in the idm\sample directory if Identity Manager is already installed.

    2. Modify the create_waveset_tables.sqlserver script to change the login password.

      Note –

      Your database administrator may want to modify the script to meet site-specific requirements for backup, replications, disk allocation, distribution, or other considerations.

    3. Create the new tables by executing the create_waveset_tables.sqlserver script, located on the installation CD; for example:

      osql -E -i PathToFile\create_waveset_tables.sqlserver

      Note –

      You must have privileges to create databases and logins.

  3. Download the Microsoft SQL Server 2005 Driver for JDBC.

    Note –

    Identity Manager version 8.1 supports SQL Server 2008 using the SQL Server 2005 JDBC drivers.

    1. Go to the Microsoft downloads website. http://www.microsoft.com/downloads

    2. In the Search for a Download area, enter “SQL Server JDBC” in the keywords field, and then click Go.

    3. Download the correct version of the driver for your installation.

      Later, during the Identity Manager installation process, you will install the SQL Server driver to the $WSHOME/WEB-INF/lib directory on your application server.

      See Notes on Configuring Databases and Downloading Supporting JAR Files for more information.