| Oracle® Identity Manager Installation and Configuration Guide for Oracle WebLogic Server Release 9.1.0.1 Part Number E14047-01 |
|
|
View PDF |
| Oracle® Identity Manager Installation and Configuration Guide for Oracle WebLogic Server Release 9.1.0.1 Part Number E14047-01 |
|
|
View PDF |
Oracle Identity Manager requires a database. You must install and configure your database before you begin the Oracle Identity Manager installation. Refer to the topics that apply to your database:
To use Oracle Database as your database, you must perform the tasks described in the following sections:
Install Oracle9i Database or Oracle Database 10g release 2 by referring to the documentation delivered with Oracle Database. See Oracle Identity Manager Readme for the specific supported versions. Oracle recommends using the Basic installation.
Note:
If you select Custom installation, then you must include the JVM option, which is required for XA transaction support.Note:
Oracle recommends that you increase the number of connections allowed to the Oracle Database. For this, you must increase the value of the processes parameter as follows:Log in as the database administrator and then run the following query:
ALTER SYSTEM SET PROCESSES = 300 SCOPE = SPFILE;
Restart the database for the changes to take effect.
You can create a new Oracle database instance for Oracle Identity Manager. When creating the database, ensure that you configure the Oracle JVM feature and enable query rewrite.
You can use the Database Configuration Assistant (DBCA) tool to create the database. To configure the Oracle JVM feature, select the Oracle JVM feature on the Standard Database Features page of the DBCA.
To enable the database for query rewrite, set the initialization parameters QUERY_REWRITE_ENABLED to TRUE and QUERY_REWRITE_INTEGRITY to TRUSTED in the All Initialization Parameters field of the DBCA.
Note:
For the Oracle Identity Manager installation, Oracle recommends that you configure a minimum block size of 8K for Oracle Database.See Oracle Database documentation for detailed instructions on creating a database instance.
For globalization support for Oracle Identity Manager, Oracle recommends configuring the database for Unicode. To configure the database for Unicode:
Select AL32UTF8 in the Character Sets tab of the DBCA. This character set supports the Unicode standard.
Set the NLS_LENGTH_SEMANTICS initialization parameter to CHAR in the All Initialization Parameters field of the DBCA.
See Also:
Oracle Identity Manager Globalization Guide for information about globalization support for Oracle Identity ManagerAfter you install Oracle Database and create a database instance, you must prepare it for Oracle Identity Manager by completing the following tasks:
Verify that query rewrite is enabled.
Note:
Query rewrite is applicable only if you are using Oracle Database Enterprise Edition.Enable XA transactions support.
Note:
A Java Virtual Machine (JVM) is required to enable XA transaction support. If you did not install the Oracle JVM component during Oracle Database installation, then you must install it now. See the Oracle Database documentation for specific instructions.Create at least one tablespace for storing Oracle Identity Manager data.
Create a database user account for Oracle Identity Manager.
You can perform the preceding tasks to prepare Oracle Database for Oracle Identity Manager by running one of the following scripts:
On Microsoft Windows, run the following:
prepare_xl_db.bat
On UNIX, run the following:
prepare_xl_db.sh
These scripts are located in the \installServer\Xellerate\db\oracle\ directory.
Apply the following guidelines when you run this script:
The script must be run by a user who has DBA privileges. For example, the oracle user on UNIX typically holds these privileges.
The script must be run on the computer on which the database is installed.
The following sections describe how to prepare the Oracle database for Oracle Identity Manager.
Note:
Perform the steps associated with the operating system on the computer hosting the Oracle database.To prepare the database on UNIX:
Copy the prepare_xl_db.sh and xell_db_prepare.sql scripts from the distribution CD to a directory on the computer hosting the database in which you (as the account user performing this task) have write permission.
Run the following command to enable permission to run the script:
chmod 755 prepare_xl_db.sh
Run the prepare_xl_db.sh script by entering the following command:
./prepare_xl_db.sh
Provide information appropriate for your database and host computer when the script prompts you for the following items:
Location of your Oracle home, which is ORACLE_HOME
Name of your database, which is ORACLE_SID
Name of the Oracle Identity Manager database user to be created
Password for the Oracle Identity Manager database user
Name of the tablespace to be created for storing Oracle Identity Manager data
Directory to store the data file for the Oracle Identity Manager tablespace
Name of the data file (do not append the .dbf extension)
Name of the temporary tablespace
Check the prepare_xl_db.lst log file located in the directory in which you ran the prepare_xl_db script to see the execution status and additional information.
Note:
If you encounter errors after running the prepare_xl_db.sh script, then run the following command to ensure that the prepare_xl_db.sh is executable on UNIX, and then run the prepare_xl_db.sh script again.$ dos2unix prepare_xl_db.sh
To prepare the database on Microsoft Windows:
Copy the prepare_xl_db.bat and xell_db_prepare.sql scripts from the distribution CD to a directory on the computer hosting the database in which you (as the account user performing this task) have write permission.
Open a command window, navigate to the directory in which you copied the scripts, and then run prepare_xl_db.bat with the following arguments:
prepare_xl_db.bat ORACLE_SID ORACLE_HOME XELL_USER XELL_USER_PWD TABLESPACE_NAME DATAFILE_DIRECTORY DATAFILE_NAME XELL_USER_TEMP_TABLESPACE SYS_USER_PASSWORD
For example:
prepare_xl_db.bat XELL C:\oracle\ora92 xladm xladm xeltbs C:\oracle\oradata xeltbs_01 TEMP manager
Table 3-1 lists the options used in the preceding example of prepare_xl_db.bat.
Table 3-1 Options for the prepare_xl_db.bat Script
| Argument | Description |
|---|---|
|
|
Name of the database |
|
|
Directory in which Oracle Database is installed |
|
|
Name of the Oracle Identity Manager user to be created |
|
|
Password for the Oracle Identity Manager user |
|
|
Name of the tablespace to be created |
|
|
Directory in which the data files will be placed |
|
|
Name of the data file (do not include the .dbf extension) |
|
|
Name of the temporary tablespace that already exists in the database |
|
|
Password for the SYS user |
Check the prepare_xl_db.lst log file located in the directory in which you have run the xell_db_prepare script to see execution status and additional information.
If the script returns a message indicating successful execution, then you can continue to the next task, which is Oracle Identity Manager installation.
If the script does not succeed, then you must manually fix all fatal (nonrecoverable) errors so that the database is prepared successfully.
You can ignore all nonfatal errors. For example, when the script tries to drop a nonexistent view, it will return the following error:
ORA-00942: table or view does not exist"
Look for errors in the log file and ignore or resolve them on an individual basis. Remember that you must successfully prepare the database for Oracle Identity Manager before you can install Oracle Identity Manager.
This section explains how to deploy Oracle Real Application Clusters (Oracle RAC) databases for Oracle Identity Manager. It discusses the following sections:
Oracle RAC is a cluster database with a shared cache architecture that provides highly scalable and available database solutions. Oracle RAC consists of multiple database instances on different computers. These database instances act in tandem to provide database solutions.
Note:
The Oracle Identity Manager Installer program does not provide support for Oracle RAC. To deploy Oracle Identity Manager for Oracle RAC, you must install Oracle Identity Manager on a single database instance in Oracle RAC and then change the application server settings, specifically the connection pool parameters, to use the Oracle RAC JDBC connection string.To install Oracle Identity Manager for Oracle RAC:
Ensure that Oracle RAC is properly set up and configured with the Oracle Identity Manager schema owner.
Start the Oracle Identity Manager Installer.
On the Database Parameters page of the installer, enter the host name, port number, and database name of a single database instance in Oracle RAC.
Complete the Oracle Identity Manager installation by performing the steps in the installer.
Configure the application server for RAC. Refer to the "Configuring Oracle WebLogic Server for Oracle RAC" section.
The net services name entry for an Oracle RAC database differs from that of a conventional database. The following is an example of the net services name entry for an Oracle RAC database:
racdb=
(DESCRIPTION=
(LOAD_BALANCE=off)
(FAILOVER=on)
(ADDRESS_LIST=
(ADDRESS=(protocol=tcp)(host=node1-vip)(port=1521))
(ADDRESS=(protocol=tcp)(host=node2-vip)(port=1521)))
(CONNECT_DATA=
(SERVER=DEDICATED)
(SERVICE_NAME=racdb)))
Table 3-2 describes the parameters in a net services name entry for an Oracle RAC database.
Table 3-2 Parameters for Oracle RAC Database Net Services Name Entries
| Parameter | Description |
|---|---|
|
LOAD_BALANCE |
Specifies whether client load balancing is enabled (on) or disabled (off). The default setting is on. |
|
FAILOVER |
Specifies whether failover is enabled (on) or disabled (off). The default setting is on. |
|
ADDRESS_LIST |
Specifies the list of all the nodes in Oracle RAC, including their host names and the ports at which they listen. |
JDBC client applications that use the Thin driver to connect to an Oracle RAC database must use the Oracle RAC net services name as a part of the JDBC URL. The entire Oracle RAC net services name is concatenated and the entire string is used in the JDBC URL so that the client application can connect to Oracle RAC.
The following sample code shows how a JDBC URL is used to connect to an Oracle RAC database:
//String url = "jdbc:oracle:thin:@dbhost:1521:dbservice"
String racUrl =
"jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=off)(FAILOVER=on)(ADDRESS_LIST=(ADDRESS=(protocol=tcp)(host=node1-vip)(port=1521))(ADDRESS=(protocol=tcp)(host=node2-vip)(port=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=racdb)))";
String strUser = "username";
String strPW = "password";
// load Oracle driver
Class.forName("oracle.jdbc.driver.OracleDriver");
// create the connection
con = DriverManager.getConnection(strURL, strUser, strPW);
The subsequent sections about configuring application servers for Oracle RAC databases explain how to modify connection pools to use a similar JDBC URL so that the application server can communicate with Oracle RAC.
This section explains how to configure Oracle WebLogic Server (nonclustered or clustered) for Oracle RAC by ensuring that the data sources and connection pools are configured to use the Oracle RAC JDBC connection string.
Note:
Before configuring Oracle WebLogic Server for Oracle RAC, you must:Get the RAC net services name from the tnsnames.ora file.
Construct the RAC JDBC URL. Refer to the "JDBC and Oracle RAC" section.
To configure nonclustered or clustered Oracle WebLogic Server for Oracle RAC:
Open the OIM_HOME/xellerate/config/xlconfig.xml file.
Locate the <DirectDB> section and replace the value of the <url>...</url> tag with the Oracle RAC JDBC URL. For example, the new tag might be similar to the following:
<url>jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=off)(FAILOVER=on)(ADDRESS_ LIST=(ADDRESS=(protocol=tcp)(host=node1-vip)(port=1521))(ADDRESS=(protocol=tcp) (host=node2-vip)(port=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_ NAME=racdb)))</url>
Save and close the OIM_HOME/xellerate/config/xlconfig.xml file.
Start Oracle WebLogic Server and open the WebLogic Server Administration Console by using a Web browser.
Log in to the WebLogic Server Administration Console by using the administrator account.
Select Services, JDBC, Data Sources, and then select xlDS.
Select the ConnectionPool tab.
In the Change center region, click Lock and Edit.
Enter the Oracle RAC JDBC URL described in Step 2 in the URL field and save the settings.
Save the settings.
Select Services, JDBC, Data Sources, and then select xlXADS.
Select the ConnectionPool tab.
Enter the Oracle RAC JDBC URL described in Step 2 in the URL field and save the settings.
Save the settings.
In the Change center region, click Activate Changes.
Restart the Administrative Server and the Managed Server. For Oracle WebLogic Server clusters, restart all nodes in the cluster.
Stop and restart the Administrative Server.
Note:
For a clustered installation, stop the Managed servers and Administrative server. Then, restart the Administrative server and Managed servers.See the following sections for detailed information:
