| Oracle® Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server Release 9.1.0.1 Part Number E14064-04 |
|
|
View PDF |
| Oracle® Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server Release 9.1.0.1 Part Number E14064-04 |
|
|
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 topic that applies to your database:
The following are the high-level tasks for using an Oracle Database for Oracle Identity Manager.
Install Oracle. Refer to the "Installing Oracle Database" section.
Create an Oracle Database. Refer to the "Creating an Oracle Database" section.
Prepare the Database. Refer to the "Preparing the Oracle Database" section.
Install Oracle9i Database or Oracle Database 10g release 2 by referring to the documentation delivered with the Oracle database. See Oracle Identity Manager Readme for the specific supported versions. Oracle recommends using the Basic installation.
Note:
If you choose the Custom installation, then you must include the JVM option, which is required for XA transaction support.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.Consult your Oracle Database documentation for detailed instructions on creating a database instance.
For globalization support for Oracle Identity Manager Release, Oracle recommends that configuring the database for Unicode. To configure the database for Unicode, perform the following steps:
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 more information about globalization support in 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:
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 the Oracle database for Oracle Identity Manager by running one of the following scripts:
Both of these scripts ship with the Oracle Identity Manager Installer and are in the \installServer\Xellerate\db\oracle\ directory.
The prerequisites to run the prepare_xl_db scripts are:
The script must be run by a user holding DBA privilege. For example, the oracle user on UNIX or Linux typically holds these privileges.
The script must be run on the computer in which the database is installed.
To prepare your Oracle database for Oracle Identity Manager, complete the steps associated with the operating system on the computer hosting the Oracle database.
To prepare the scripts on UNIX or Linux:
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 execute permission for the script:
chmod 755 prepare_xl_db.sh
Run the script prepare_xl_db.sh by entering the following command:
./prepare_xl_db.sh
Provide information appropriate for the database and host computer when the script prompts you for the following items:
The location of your Oracle home, which is ORACLE_HOME
The name of the database, which is ORACLE_SID
The name of the Oracle Identity Manager database user to be created
The password for the Oracle Identity Manager database user
The name of the tablespace to be created for storing Oracle Identity Manager data
The directory to store the data file for the Oracle Identity Manager tablespace
The name of the data file (You do not append the .dbf extension.)
The 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 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 Linux, and then run the prepare_xl_db.sh script again.$ dos2unix prepare_xl_db.sh
To prepare the scripts 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 prompt, navigate to the directory in which you copied the scripts, and 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, the string you enter on the command line might look similar to the following:
prepare_xl_db.bat XELL C:\oracle\ora92 xladm xladm xeltbs C:\oracle\oradata xeltbs_01 TEMP manager
Table 4-1 lists the options used in the preceding example of prepare_xl_db.bat.
Table 4-1 Options for the prepare_xl_db.bat Script
| Argument | Description |
|---|---|
|
|
Name of the database |
|
|
Directory in which the 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 (you do not need to 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 ran 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 error "ORA-00942: table or view does not exist".Ensure that you scan all the 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 the 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.Perform the following steps 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 your application server for Oracle RAC. Refer to the "Configuring IBM WebSphere Application 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 4-2 describes the parameters in a net services name entry for an Oracle RAC database.
Table 4-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 they listen on. |
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 IBM WebSphere Application 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 WebSphere application servers 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.
Perform the following steps to configure both nonclustered and clustered WebSphere application servers 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 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.
Log on to the WebSphere Administrative Console by using a Web browser if you are configuring a nonclustered WebSphere environment. Log on to the WebSphere Administrative Console of the Network Deployment Manager (NDM) by using a Web browser if you are configuring a clustered WebSphere environment.
Select Resources, JDBC, Data Sources, and then select Non XA DataSource.
At the bottom of the page, replace/set the value of URL property to RAC JDBC URL as described in step 2.
Save the settings.
Select Resources, JDBC, Data Sources, and then select XADataSource.
At the bottom of the page, replace/set the value of URL property to RAC JDBC URL as described in step 2.
Save the settings.
Restart the WebSphere application server if you are configuring a nonclustered WebSphere environment. Restart the WebSphere NDM if you are configuring a clustered WebSphere environment.
To use Microsoft SQL Server as the database, perform the procedures described in the following sections:
To install and configure Microsoft SQL Server 2005 for Oracle Identity Manager:
Install Microsoft SQL Server 2005 with Service Pack 2.
During installation, select mixed authentication mode, and then set the password to that of the sa user.
Note:
Perform Steps 2 through 4 on the computer hosting the application server.Download SQL Server 2005 JDBC Driver version 1.2 from the Microsoft Web site.
Note:
In this chapter, the directory into which you download and extract the driver files is referred to asSQLSERVER2005_JDBC_DRIVER_HOME.Install SQL Server 2005 JDBC Driver.
Instructions to install JDBC drivers for SQL Server 2005 are available at the following location:
SQL_SERVER_HOME\sqljdbc_1.2\enu\help\html\574e326f-0520-4003-bdf1-62d92c3db457.htm
Note:
Specify a short path for the installation folder, such as C:\JDBCjars, so that you can easily add the path to your CLASSPATH in the next step. If the classpath is more than 256 characters, then the installer does not work properly.Locate the JDBC driver file (sqljdbc.jar) from the SQLSERVER2005_JDBC_DRIVER_HOME\sqljdbc_1.2\enu\ directory.
Add their location to the system CLASSPATH environment variable. If the CLASSPATH environment variable does not exist, you must create it. The string you add should look like the following:
C:\jdbc_install_folder\sqljdbc.jar;
In this sample string, jdbc_install_folder is the location where the SQL Server 2005 JDBC Driver files is installed.
Note:
Perform Steps 5 through 7 on the computer hosting the Microsoft SQL Server database.On the computer hosting the Microsoft SQL Server database, enable distributed transactions by installing SQL Server 2005 JDBC XA procedures.
Depending on the type of operating system running on the host computer, copy the sqljdbc_xa.dll file from one of the following directories into the SQLSERVER2005_HOME\MSSQL\Binn directory:
SQLSERVER2005_JDBC_DRIVER_HOME\sqljdbc_1.2\enu\xa\x86
SQLSERVER2005_JDBC_DRIVER_HOME\sqljdbc_1.2\enu\xa\x64
SQLSERVER2005_JDBC_DRIVER_HOME\sqljdbc_1.2\enu\xa\IA64
Note:
In this chapter,SQLSERVER2005_HOME refers to the directory in which you have installed Microsoft SQL Server 2005.Log in to Microsoft SQL Server as sa and then run the SQLSERVER2005_JDBC_DRIVER_HOME\sqljdbc_1.2\enu\xa\xa_install.sql script.
Enable XA transactions as follows:
On the computer on which Microsoft SQL Server is running, click Start, Administrative Tools, and Component Services.
Expand the Component Service tree to locate the computer, right-click the computer name, and then select Properties.
On the MSDTC tab, click Security Configuration.
Under Security Settings, select Enable XA Transactions.
Click OK, and then save the changes.
Restart the Distributed Transaction Coordinator (MSDTC) service.
Restart Microsoft SQL Server.
The following procedure describes how to create a new database for Oracle Identity Manager.
Note:
From this point onward in the guide, the name XELL is used to refer to the database. You can set any name for the database.To create a SQL Server database:
Start the Microsoft SQL Server Management Studio application as follows:
From the Windows Start menu, expand All Programs, expand Microsoft SQL Server 2005, and then select SQL Server Management Studio.
In the Connect to Server dialog box, verify the default settings. Ensure that the name of the computer on which SQL Server is installed is specified in the Server name box. Then, click Connect.
On the left pane of the SQL Server Management Studio application window, right-click Databases, and then select New Database.
In the New Database Properties dialog box, on the left pane, select General, and then enter XELL in the Database Name field.
In the Database Files section, for the Initial Size and Filegroup columns in the Database files matrix, enter the information from the corresponding columns in Table 4-3.
Table 4-3 Database Files
| Logical Name | File Type | File Group | Initial Size in Megabytes (MB) | Auto Growth | Path | File Name |
|---|---|---|---|---|---|---|
|
XELL_PRIMARY |
Data |
PRIMARY |
100 |
By 1 MB, unrestricted growth (by default) |
Specify the default path to save the datafiles |
Left Blank (Default) |
|
XELL_DATA |
Data |
XELL_DATA |
500 |
By 1 MB, unrestricted growth (by default) |
Specify the default path to save the datafiles |
Left Blank (Default) |
|
XELL_INDEX |
Data |
XELL_INDEX |
300 |
By 1 MB, unrestricted growth (by default) |
Specify the default path to save the datafiles |
Left Blank (Default) |
|
XELL_TEXT |
Data |
XELL_TEXT |
500 |
By 1 MB, unrestricted growth (by default) |
Specify the default path to save the datafiles |
Left Blank (Default) |
|
XELL_UPA |
Data |
XELL_UPA |
1000 |
By 1 MB, unrestricted growth (by default) |
Specify the default path to save the datafiles |
Left Blank (Default) |
Note:
Table 4-3 lists initial sizes for a production environment. For non-production installations, you can use the default initial sizes provided for the filegroups.
To ensure successful installation of Oracle Identity Manager, filegroup names must be entered exactly as they appear in Table 4-3. You can vary the File Name and Location strings to match the database name and the location of your SQL Server installation.
The PRIMARY filegroup contains the system objects required for SQL Server to operate. The XELL_DATA filegroup stores the physical data and primary keys, XELL_INDEX filegroup stores indexes, XELL_TEXT stores large text fields and XELL_UPA stores physical data and primary keys of the User Profile Audit component.
Select the log file, then change the initial size to 500 MB. Leave all the other options on the tab at their default values.
Note:
For nonproduction installations, you can use the default initial size for the log file.Click OK to start creating the database.
The following procedure describes how to create a database account for Oracle Identity Manager and assign appropriate permissions to that account.
Note:
The following procedure assumes the account name xladm. If you want to use an account name other than xladm, then specify that login instead of xladm throughout the following procedure and also when installing Oracle Identity Manager.To create a Microsoft SQL Server database account and permissions:
Start the Microsoft SQL Server Management Studio application.
On the left pane of the SQL Server Management Studio application window, select Security, right-click Logins, and then select New Login.
In the SQL Server Login Properties dialog box, from the left pane, click the General tab, and perform the following steps:
In the Login Name field, enter xladm (or a different account name that you prefer).
Select the Enforce Password Policy check box. Deselect all other check boxes.
Select SQL Server Authentication, and then enter the password associated with the account you specified in the Password field.
In the Database box within the Defaults section, select XELL from the list.
Leave the Language box set to <default>, and then click OK.
On the left pane of the SQL Server Management Studio application window, select Security, right-click xladm, and then select Properties.
Select the User Mapping option from the left pane.
In the Users mapped to this login table, select the check box associated with the XELL database. Enter xladm in the User and Default Schema columns.
In the Database role membership for table, select the check boxes associated with the following:
public
db_owner
db_accessadmin
db_securityadmin
db_ddladmin
db_datareader
db_datawriter
In the Users mapped to this login table, select the check box associated with the master database. Enter xladm in the User and Default Schema columns.
In the Database role membership for table, select the check boxes associated with the following:
public
SqlJDBCXAUser
Click OK to commit your changes.
On the Microsoft SQL Server Management Studio, in the left pane, right-click registered server, click Properties. In the Properties dialog box, select the Security option, and then verify that Authentication is set to SQL Server and Windows.
Start the Microsoft SQL Server 2005 Surface Area Configuration application. To do so:
From the Start menu, expand All Programs, expand Microsoft SQL Server 2005, expand Configuration Tools, and then click SQL Server 2005 Surface Area Configuration. A dialog box is displayed.
Click Surface Area Configuration for Services and Connection. On the left pane, select the MSSQLSERVER-> Database Engine, and then verify that the Startup Type is set to Automatic.
If Autostart SQL Server Agent is selected, do not change the existing setting, because that setting may be required by other applications. Click OK to close the SQL Server Properties page.
To remove Oracle Identity Manager entries from a Microsoft SQL Server 2005 database after removing (deinstalling) the Oracle Identity Manager product:
Delete the Oracle Identity Manager database.
Delete the Oracle Identity Manager login.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|