| Oracle® Identity Manager Release Notes Release 9.0.3.1 Part Number E10315-01 |
|
| View PDF |
| Oracle® Identity Manager Release Notes Release 9.0.3.1 Part Number E10315-01 |
|
| View PDF |
Release Notes
Release 9.0.3.1
E10315-01
May 2007
This document contains release notes for Oracle Identity Manager Release 9.0.3.1 and includes the following topics:
Notes:
Oracle Identity Manager was previously known as Oracle Xellerate Identity Provisioning.
Oracle Identity Manager connectors, which were previously referred to as resource adapters, are no longer bundled with Oracle Identity Manager. Oracle Identity Manager connectors are now distributed in the Oracle Identity Manager Connector Pack, independent from Oracle Identity Manager.
See Also:
The following documentation, located on your installation media, for detailed information on Oracle Identity Manager:Oracle Identity Manager Release 9.0.3.1 provides extended platform support. Refer to the "Certified Operating Systems" section for more information about this enhancement.
Some known issues from previous releases of Oracle Identity Manager have been fixed in this release. Refer to the "Resolved Issues" section for information about these known issues.
This section identifies components certified with Oracle Identity Manager Release 9.0.3.1 and contains the following topics:
Oracle Identity Manager Release 9.0.3.1 is certified for the following operating systems:
AIX 5L 5.3 (32-bit)
AIX 5L 5.3 (64-bit)
HP-UX 11i (PA-RISC 64-bit)
Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 R2 (EMT/AMD 64-bit)
Red Hat Enterprise Linux AS Release 4 Update 3
Red Hat Enterprise Linux AS Release 4 Update 3 (Pentium 64-bit)
Solaris Operating System 10 (UltraSparc 64-bit)
SUSE Linux Enterprise Server 10 (Pentium 32-bit)
Oracle Identity Manager Release 9.0.3.1 is certified for the following application servers:
Oracle Containers for J2EE (bundled in Oracle SOA Suite 10g Release 10.1.3.1)
Note:
Oracle Containers for J2EE (OC4J) is also licensed as a standalone product. However, you cannot use standalone OC4J. You must use the OC4J bundled in Oracle SOA Suite 10g release 10.1.3.1.
When you run the Oracle SOA Suite installer, you must select the Advanced Install option and select only the J2EE Server and Web Server option on the Select Installation Type screen. No other installation type will support Release 9.0.3.1. You must select the J2EE Server and Web Server option.
BEA WebLogic 8.1 with SP6
IBM WebSphere 5.1.1.12 (with Fix Pack 13 for WebSphere MQ 5.3)
JBoss Application Server 4.0.3 with SP1
Applying Fix Pack 13 for WebSphere MQ 5.3
Back up all applications and configurations.
Stop any running application servers and JMS servers for Network Deployment users. This will automatically stop the embedded queue manager. You must ensure that there are no running MQ processes.
Download the latest WebSphere MQ v5.3 fix pack from the WebSphere MQ support Web site at
http://www-306.ibm.com/software/integration/wmq/support/
Note:
You must download and apply Fix Pack 13 (CSD13) or later. Do not use the WebSphere MQ v6 fix packs.Install the WebSphere MQ v5.3 fix pack that you download in the earlier step. Where required, save files that will be overwritten during the installation.
Note:
For AIX users:Do not commit the installation until after you have thoroughly tested it. You must follow this guideline because you cannot roll back an MQ fix pack after you commit it.
Remove any previous Embedded Messaging interim fixes from the <WAS_HOME>/classes directory, including embedded messaging cumulative JMS interim fixes such as IC45152 and IC46552. This helps avoid potentially back-leveling parts of the WMQ v5.3 fix pack installation.
Start your application servers and JMS servers for Network Deployment users.
Oracle Identity Manager Release 9.0.3.1 is certified for the following databases:
Oracle 9i Enterprise Edition Releases:
9.2.0.7
9.2.0.8
Oracle 10g Enterprise Edition Releases:
10.1.0.5
10.2.0.1
10.2.0.2
10.2.0.2 with RAC
Oracle 10g Standard Edition Release:
10.2.0.2
Microsoft SQL Server 2000 SP 3a
Oracle Identity Manager Release 9.0.3.1 is certified for the following languages:
Chinese Simplified
Chinese Traditional
English
French
German
Italian
Japanese
Korean
Portuguese (Brazilian)
Spanish
See Also:
Oracle Identity Manager Globalization Guide for complete information on Oracle Identity Manager globalization supportFor each certified application server, Oracle Identity Manager Release 9.0.3.1 is certified for the JDKs listed in Table 1.
See Also:
"Invalid JDK Combinations"Table 1 Certified JDKs
| Application Server | Certified JDK |
|---|---|
|
BEA WebLogic |
Sun JDK 1.4.2_11 included with BEA WebLogic 8.1 SP6 |
|
IBM WebSphere |
IBM JDK 1.4.2 included with IBM WebSphere 5.1.1.12 |
|
JBoss Application Server |
Sun JDK 1.4.2_12 |
|
OC4J |
JDK 1.5.x included with OC4J bundled in Oracle SOA Suite 10g Release 10.1.3.1 |
Oracle Identity Manager Release 9.0.3.1 is certified for the configurations listed in Table 2.
Note:
Unless otherwise noted, the configurations listed in Table 2 are certified for both clustered and non-clustered configurations.Table 2 Certified Configurations for Release 9.0.3.1
| Operating System | Application Server | Database | Languages |
|---|---|---|---|
|
AIX 5L 5.3 (32-bit) |
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
AIX 5L 5.3 (64-bit) |
IBM WebSphere 5.1.1.12 |
Oracle Database |
All 10 administrative languages |
|
HP-UX 11i (PA-RISC 64-bit) |
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
Microsoft Windows Server 2003 R2 |
BEA WebLogic 8.1 with SP6 |
Oracle Database |
All 10 administrative languages |
|
|
|
Microsoft SQL Server 2000 |
English |
|
|
IBM WebSphere 5.1.1.12 |
Oracle Database |
All 10 administrative languages |
|
|
|
Microsoft SQL Server 2000 |
English |
|
|
JBoss Application Server 4.0.3 with SP1 |
Oracle Database |
All 10 administrative languages |
|
|
|
Microsoft SQL Server 2000 |
English |
|
|
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
Microsoft Windows Server 2003 R2 (EMT/AMD 64-bit) |
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
Red Hat Enterprise Linux AS Release 4 Update 3 |
BEA WebLogic 8.1 with SP6 |
Oracle Database |
All 10 administrative languages |
|
|
IBM WebSphere 5.1.1.12 |
Oracle Database |
All 10 administrative languages |
|
|
JBoss Application Server 4.0.3 with SP1 |
Oracle Database |
All 10 administrative languages |
|
|
|
Microsoft SQL Server 2000 |
English |
|
|
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
Red Hat Enterprise Linux AS Release 4 Update 3 (Pentium 64-bit) |
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
Solaris Operating System 10 (UltraSparc 64-bit) |
BEA WebLogic 8.1 with SP6 |
Oracle Database |
All 10 administrative languages |
|
|
IBM WebSphere 5.1.1.12 |
Oracle Database |
All 10 administrative languages |
|
|
JBoss Application Server 4.0.3 with SP1 Note: For non-clustered configuration only |
Oracle Database |
All 10 administrative languages |
|
|
OC4J (bundled in Oracle SOA Suite 10g Release 10.1.3.1) |
Oracle Database |
All 10 administrative languages |
|
SUSE Linux Enterprise Server 10 (Pentium 32-bit) |
JBoss Application Server 4.0.3 with SP1 Note: For non-clustered configuration only |
Oracle Database |
All 10 administrative languages |
Note:
To update OC4J JDKs for DST 2007 compliance, you must use the appropriate time zone update utility from your JDK vendor. For information about using JDK vendor time zone update utilities, refer to note 414153.1 on the OracleMetaLink Web site.
You can access the OracleMetaLink Web site at
For installing OC4J on AIX, you must apply Patch 5694581. You can download this patch from the OracleMetaLink Web site.
For IBM WebSphere, update the DST rules for the existing IBM JDK by using the JTZU tool version 1.1.7a or later. For more information, refer to the following Web page:
http://www-128.ibm.com/developerworks/java/jdk/dst/index.html
The Design Console of Oracle Identity Manager Release 9.0.3.1 is certified on all versions of Microsoft Windows 2003 and Windows XP.
The Remote Manager of Oracle Identity Manager Release 9.0.3.1 is certified on the following operating systems:
AIX 5L 5.3 (32-bit)
AIX 5L 5.3 (64-bit)
HP-UX 11i (PA-RISC 64-bit)
Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 R2 (EMT/AMD 64-bit)
Red Hat Enterprise Linux AS Release 4 Update 3
Red Hat Enterprise Linux AS Release 4 Update 3 (Pentium 64-bit)
Solaris Operating System 10 (UltraSparc 64-bit)
SUSE Linux Enterprise Server 10 (Pentium 32-bit)
Oracle Identity Manager Release 9.0.3.1 is certified for single sign-on with the following components:
Oracle Access Manager 10.1.4.0.1 (formerly known as Oracle COREid) using both ASCII and non-ASCII character logins.
Note:
Single Sign-On with Oracle Access Manager 10.1.4.0.1 for non-ASCII character logins requires an Oracle Access Manager patch. Contact your Oracle support representative and refer to Bug 5552617 for information about the appropriate Oracle Access Manager patch.OracleAS Single Sign-On 10g 10.1.4.0.1 for both ASCII and non-ASCII character logins.
RSA ClearTrust 5.5 for ASCII character logins only.
See Also:
Oracle Identity Manager Best Practices Guide for additional information about configuring Single Sign-On for Oracle Identity Manager with Oracle Access Manager and OracleAS Single Sign-OnOracle Identity Manager Release 9.0.3.1 is certified for Microsoft Internet Explorer 6.0 with SP2.
This section describes how to upgrade to Oracle Identity Manager Release 9.0.3.1 from Release 9.0.3. It contains the following topics:
Note:
You must install Oracle Identity Manager Release 9.0.3 before applying the Release 9.0.3.1 upgrade patch.To upgrade the Oracle Identity Manager server from Release 9.0.2 to Release 9.0.3, refer to Oracle Identity Manager Upgrade Guide for Release 9.0.3.
To upgrade the Oracle Identity Manager server from Release 9.0.3 to Release 9.0.3.1:
Extract the contents of the patch ZIP file to a temporary directory (referred to as the <PATCH> directory in this document).
Upgrade the Oracle Identity Manager database as follows:
Oracle Database
Log in to the Oracle Database instance with your Oracle Identity Manager database user account, and then run the following script:
Note:
Before you run the script, verify that the script file exists at the specified path on this computer.<PATCH>/db/oracle/Scripts/upg_903_to_9031.sql
Microsoft SQL Server
Open a command prompt from the Microsoft SQL Server computer, and then run the following script:
Note:
Before you run the script, verify that the script file exists at the specified path on this computer.<PATCH>\db\SQLServer\Scripts\upg_903_to_9031.bat server_name[\instance_name] db_user password db_name <PATCH>\db\SQLServer\Scripts\
Note:
After running the upgrade script, examine the log files in the<PATCH> directory for any errors.If you want to upgrade a non-XACM Oracle Identity Manager Release 9.0.3 installation to an XACM Oracle Identity Manager Release 9.0.3.1 installation:
Note:
This is not a mandatory step. You can directly proceed to Step 4 if you do not want to upgrade a non-XACM Release 9.0.3 installation to an XACM Release 9.0.3.1 installation.An "XACM" is Oracle Identity Manager installed with the Audit and Compliance Module.
Oracle Database
To compile the stored procedures, log in to the Oracle Database instance with your Oracle Identity Manager database user account and then run the following scripts:
<PATCH>/db/oracle/StoredProcedures/compile_all_XL_SP.sql
<PATCH>/db/oracle/Scripts/Oracle_Enable_XACM.sql
Load the metadata into the Oracle Identity Manager database. Refer to Appendix B, "Loading Metadata into the Database" in Oracle Identity Manager Upgrade Guide. This guide provides information about upgrading from Oracle Identity Manager Release 9.0.2 to Release 9.0.3.
Microsoft SQL Server
Compile the stored procedures as follows:
i. In a text editor, open the following BAT file:
<PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
ii. For every stored procedure listed in the Sequential Lists section of this BAT file, replace the string @sysuser with the database user name. This must be done because Microsoft SQL Server requires functions invoked from a stored procedure to be qualified by the database user name (owner).
Note:
Ensure that you replace the entire@sysuser string, including the at sign (@).iii. Run the following script:
<PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat server_name[\instance_name] db_user password db_name <PATCH>\db\SQLServer\StoredProcedures\
To upgrade the Oracle Identity Manager Audit and Compliance module, run the following command:
<PATCH>\db\SQLServer\Scripts\SQLServer_Enable_XACM.bat server_name[\instance_name] db_user password db_name <PATCH>\db\SQLServer\Scripts\
Load the metadata into the Oracle Identity Manager database. Refer to Appendix B, "Loading Metadata into the Database" in Oracle Identity Manager Upgrade Guide. This guide provides information about upgrading from Oracle Identity Manager Release 9.0.2 to Release 9.0.3.
Back up the following directories:
OIM_HOME/xellerate/config OIM_HOME/xellerate/DDTemplates OIM_HOME/xellerate/ext OIM_HOME/xellerate/GTC OIM_HOME/xellerate/lib OIM_HOME/xellerate/setup OIM_HOME/xellerate/webapp
Replace the contents of the following directories with the contents of the directories of the same name in the <PATCH>/xellerate directory:
OIM_HOME/xellerate/config OIM_HOME/xellerate/DDTemplates OIM_HOME/xellerate/ext OIM_HOME/xellerate/GTC OIM_HOME/xellerate/lib OIM_HOME/xellerate/setup OIM_HOME/xellerate/webapp
For clustered installations, repeat Steps 4 and 5 for each node of the cluster.
If you are using OC4J, BEA WebLogic, or IBM WebSphere, then ensure that your application server is running.
To retain customization that you may have performed on Release 9.0.3 of the Administrative and User Console, update the <OIM_HOME>/xellerate/webapp/xlWebApp.war file with your customization changes. You can skip this step if you had not customized Release 9.0.3 of the Administrative and User Console.
Run the upgrade script appropriate for your operating system:
Note:
In the command that you use, replaceadmin_password and OIM_datasource_password with the actual passwords for your installation.UNIX/Linux
For OC4J:
OIM_HOME/xellerate/setup/patch_oc4j.sh OC4J_admin_password OIM_datasource_password
For BEA WebLogic:
OIM_HOME/xellerate/setup/patch_weblogic.sh WebLogic_admin_password OIM_datasource_password
For IBM WebSphere:
OIM_HOME/xellerate/setup/patch_websphere.sh WebSphere_admin_password OIM_datasource_password
For JBoss Application Server:
OIM_HOME/xellerate/setup/patch_jboss.sh OIM_datasource_password
Microsoft Windows
For OC4J:
OIM_HOME\xellerate\setup\patch_oc4j.cmd OC4J_admin_password OIM_datasource_password
For BEA WebLogic:
OIM_HOME\xellerate\setup\patch_weblogic.cmd WebLogic_admin_password OIM_datasource_password
For IBM WebSphere:
OIM_HOME\xellerate\setup\patch_websphere.cmd WebSphere_admin_password OIM_datasource_password
For JBoss Application Server:
OIM_HOME\xellerate\setup\patch_jboss.cmd OIM_datasource_password
Restart your application server.
To upgrade Oracle Identity Manager Design Console to Release 9.0.3.1:
Back up the following directories:
OIM_DC_HOME\xlclient\lib OIM_DC_HOME\xlclient\ext
Replace the contents of the following directories with the contents of directories of the same name in the <PATCH>\xlclient\lib directory
OIM_DC_HOME\xlclient\lib OIM_DC_HOME\xlclient\ext
Back up the following files:
OIM_DC_HOME\xlclient\CustomClient.zip OIM_DC_HOME\xlclient\XLDesktopClient.ear OIM_DC_HOME\xlclient\xlFvcUtil.ear
For JBoss Application Server, BEA WebLogic, and OC4J, back up the following file:
OIM_DC_HOME\xlclient\fvcutil.cmd
For IBM WebSphere, back up the following file:
OIM_DC_HOME\xlclient\fvcutil_websphere.cmd
Replace the contents of the following directories with the contents of the directories of the same name in the <PATCH>\xlclient directory:
OIM_DC_HOME\xlclient\CustomClient.zip OIM_DC_HOME\xlclient\XLDesktopClient.ear OIM_DC_HOME\xlclient\xlFvcUtil.ear
For JBoss Application Server, BEA WebLogic, and OC4J, copy the following file:
OIM_DC_HOME\xlclient\fvcutil.cmd
For IBM WebSphere, copy the following file:
OIM_DC_HOME\xlclient\fvcutil_websphere.cmd
If you are using IBM WebSphere as your application server, perform the following steps to update the xlDataObjectBeans.jar file:
Note:
Do not perform these steps until after you update the Oracle Identity Manager server as described in the "Upgrading the Oracle Identity Manager Server" section.Open a Web browser window and log in to the WebSphere Administrative Console by using the following URL:
http://server_name or IP_address:9090/admin
Click Applications, and then click Enterprise Applications.
Select the Xellerate application check box, and then click Export.
Save the Xellerate.ear file.
Extract the xlDataObjectBeans.jar file from the Xellerate.ear file, and copy it to the OIM_DC_HOME\xlclient\lib directory.
To upgrade the Oracle Identity Manager Remote Manager to Release 9.0.3.1:
Back up the OIM_RM_HOME\xlremote\lib directory.
Replace the contents of the OIM_RM_HOME\xlremote\lib directory with the contents of the <PATCH>\xlremote\lib directory.
This section describes known issues for Oracle Identity Manager Release 9.0.3.1. If a suitable workaround exists for a known issue, it is listed with the description of the issue to provide a temporary solution. This section contains the following topics:
This section describes known issues related to the installation of Oracle Identity Manager Release 9.0.3.1 components. This section contains the following topics:
See Also:
Oracle Identity Manager Release Notes for Release 9.0.3 for information about other installation known issuesMinimum Temporary Storage Requirements for Installation on UNIX/Linux Platforms (Bug 5971692)
Installer Program Does Not Verify WebLogic Server Name (Bug 5389372)
Installation Fails When The Database User Name Includes Special Characters (Bug 5563636)
Design Console's xlclient.cmd Executable Does Not Launch if Paths Include a Space (Bug 5853425)
The Oracle Identity Manager Release 9.0.3 installation guides for each application server contain an inaccurate setting in the "Using Oracle RAC Databases for Oracle Identity Manager" section. The LOAD_BALANCE setting in the JDBC URL used to connect to a RAC database should be set to off, not on. The following JDBC URL demonstrates how the LOAD_BALANCE setting is assigned the value off:
<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>
See Also:
The chapter on developing applications with Oracle XA in the Oracle Database Application Developer's Guide - Fundamentals on the Oracle Technology Network atBy default, JBoss application server does not encrypt data source passwords, as described in the JBoss document at
http://wiki.jboss.org/wiki/Wiki.jsp?page=EncryptingDataSourcePasswords
This section describes how to encrypt the Oracle Identity Manager database password in JBoss deployments. Specifically, you must perform the following steps to manually encrypt a password, and then modify the xell-ds.xml and login-config.xml files so that they can access the encrypted form of the password instead of the clear text version:
Open a console window.
Run one of the following commands to encrypt the Oracle Identity Manager database password. In this command, replace password with the actual password that you want to encrypt.
UNIX/Linux
java -cp "JBOSS_HOME/lib/jboss-jmx.jar:lib/jboss-common.jar:server/ default/lib/jboss-jca.jar:server/default/lib/jbosssx.jar"org.jboss.resource.security.SecureIdentityLoginModule password
Windows
java -cp "JBOSS_HOME/lib/jboss-jmx.jar;lib/jboss-common.jar;server/ default/lib/jboss-jca.jar;server/default/lib/jbosssx.jar" org.jboss.resource.security.SecureIdentityLoginModule password
The command you run in the previous step returns an encoded form of the password you specify. For example, the password Welcome1 is encoded as 3146f9cc50afd6a6df8592078de921bc. Highlight and copy the encoded password.
Open the JBOSS_HOME/server/default/deploy/xell-ds.xml file in a text editor.
Delete the <user-name> and <password> elements from the <local-tx-datasource> element.
Add the following <security-domain> element to the end of the <local-tx-datasource> element:
<security-domain>EncryptDBPassword</security-domain>
Delete the <xa-datasource-property name="User"> and <xa-datasource-property name="Password"> elements from the <xa-datasource> element.
Add the following <security-domain> element to the end of the <xa-datasource> element:
<security-domain>EncryptXADBPassword</security-domain>
Save and close the JBOSS_HOME/server/default/deploy/xell-ds.xml file.
Open the JBOSS_HOME/server/default/conf/login-config.xml file in a text editor.
Add the following elements to the <application-policy> element:
Note:
Replacedatasource_username with the datasource user name and encoded_password with the encoded password you copy in Step 3.<application-policy name = "EncryptDBPassword"> <authentication> <login-module code = "org.jboss.resource.security.SecureIdentityLoginModule" flag = "required"> <module-option name = "username">datasource_username</module-option> <module-option name = "password">encoded_password</module-option> <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option> </login-module> </authentication> </application-policy>
<application-policy name = "EncryptXADBPassword"> <authentication> <login-module code = "org.jboss.resource.security.SecureIdentityLoginModule" flag = "required"> <module-option name = "username">datasource_username</module-option> <module-option name = "password">encoded_password</module-option> <module-option name = "managedConnectionFactoryName">jboss.jca:service=XATxCM,name=jdbc/xlXADS</module-option> </login-module> </authentication> </application-policy>
Save and close the JBOSS_HOME/server/default/deploy/login-config.xml file.
Before running the installer, ensure that your environment meets the following minimum temporary storage requirements:
There must be at least 200 MB of free storage space in the /var/tmp directory.
If there is insufficient free storage space in this directory, then the installation will fail at the precompilation stage.
To install Oracle Identity Manager there must be at least 200 MB free storage space in the home directory of the user account that you use for the installation. To determine the home directory, check in the /etc/passwd file. Note that you cannot work around this requirement by changing the value of the $HOME variable.
In the event that there is insufficient free storage space in home directory, then an exception will be thrown after you select a language during the installation process.
The Oracle Identity Manager installer does not enforce confirmation of the WebLogic Administrative Console password, regardless of the value entered in the Confirm Password field.
The Oracle Identity Manager installer program does not verify the application server name when installing on WebLogic and the installation is successful regardless if you enter the incorrect WebLogic server name.
For example, you want to install Oracle Identity Manager on a WebLogic server named myWebLogic. On the installer's Weblogic Application Server Information page, you enter the IP address for myWeblogic, but incorrectly enter yourWebLogic as the name for the myWebLogic server. The installer program installs Oracle Identity Manager on myWebLogic despite the incorrect server name. To avoid this issue, double-check the name of the WebLogic server you enter when installing Oracle Identity Manager.
Clicking the Cancel button while the Oracle Identity Manager server is installing displays the error message: The current operation cannot be cancelled.
You can ignore this error message. Clicking the Cancel button does stop the Oracle Identity Manager server installation process.
The Oracle Identity Manager installer program fails when you specify a string that includes any of the following special characters for the database user name:
Asterisks (*)
Commas (,)
Hyphens (-)
Apostrophes or single quotations (')
Double quotations (")
To avoid this issue, be sure you specify a database user name that meets the following requirements:
All characters are alphanumeric
The first character is a letter
The string does not contain any special characters
The xlclient.cmd executable that launches the Design Console will fail if directory paths in the executable contain spaces. You will have a space in a directory path in xlclient.cmd if you installed the Design Console in a location that contains a space, for example, C:\Program Files\OIM\xlclient\java.
Also, you will have a space in a directory path in xlclient.cmd if while installing the Design Console you chose to use a JRE other than the one bundled with the Design Console and the path to that JRE includes a space, for example, C:\Program Files\Java\j2re1.4.2_12.
To avoid this issue, do not install the Design Console into a directory path that includes a space and do not specify a JRE using a directory path that includes a space. Another way to avoid this issue is to add double quotation marks (") to the paths in the xlclient.cmd executable that include spaces. For example:
Use the following approach if you install the Design Console into a directory path that includes a space:
"C:\Program Files\OIM\xlclient\java"\bin\java %DEBUG_OPTS% ^ -DXL.ExtendedErrorOptions=TRUE -DXL.HomeDir="C:\Program Files\OIM\xlclient" ^ -Djava.security.policy=config\xl.policy ^ -Dlog4j.configuration=config\log.properties ^ -Djava.security.manager -Djava.security.auth.login.config=config\auth.conf ^ com.thortech.xl.client.base.tcAppWindow -server server
Use the following approach if you specified a JRE to use and the path to the JRE includes a space:
"C:\Program Files\Java\j2re1.4.2_12"\bin\java %DEBUG_OPTS% ^
-DXL.ExtendedErrorOptions=TRUE -DXL.HomeDir=C:\oracle\xlclient ^
-Djava.security.policy=config\xl.policy ^
-Dlog4j.configuration=config\log.properties ^
-Djava.security.manager
-Djava.security.auth.login.config=config\auth.conf ^
com.thortech.xl.client.base.tcAppWindow -server server
This section describes known issues related to the general run-time operation of Oracle Identity Manager Release 9.0.3.1, including known issues for Oracle Identity Manager server and known issues for the Administrative and User Console not related to reporting.
This section contains the following topics:
See Also:
Oracle Identity Manager Release Notes for Release 9.0.3 for information about other general known issuesSystem Error When Provisioning a Resource in the Design Console (Bug 5948153)
Stack Overflow Exception Thrown When Importing an XML File (Bug 5350771)
Pending Approvals Cannot be Filtered by Requester Name (Bug 5365516)
URL for Administrative and User Console Calendar Icon May Appear Twice in Windows 2003 (Bug 5330984)
Cannot Delete a Group That is A Process Owner for an Attestation Process (Bug 5469706)
Errors When Modifying Settings and Assignments for Internal System Seeded Users (Bug 5357781)
Groups with Data Object Permissions on Form Not Exported with Resource (Bug 5345276)
Resource Dependency Relationships Are Reversed After Export (Bug 5345236)
Null Pointer Exception Thrown When Running the purgecache.bat Utility (Bug 5388849)
Single Sign-On Login Fails When "Force to set questions at startup" is TRUE (Bug 5565798)
An exception similar to the following one may be thrown the first time you log in to the Administrative and User Console using SSO in a UNIX/Linux environment:
[ServletException in:/tiles/tjspSetChallengeQuestionsTiles.jsp] Cannot retrieve mapping for action/setChallengeQuestions.do; jsessionid=8223a13230d52f1b767bc1844db18365ddf733c40011'
To resolve this issue, you must use the Design Console to assign a value of FALSE to the Force to set questions at startup system property.
In the Design Console, a system error may occur when you attempt to provision a resource under the following conditions:
The Auto-Prepopulate check box is selected in both the Resource Objects form and Process Definition form.
The Pre-populate Rule Generator adapter is attached to both the Object form and Process form.
This error may occur if the JAVA_HOME and PATH environment variables reference an incorrect JDK. To resolve this issue:
Modify the JAVA_HOME and PATH environment variables so that they reference the correct JDK.
Restart Oracle Identity Manager.
Compile each prepopulate adapter.
The Best Practices Guide states that to purge all Oracle Identity Manager caching categories, you pass the value ALL to the PurgeCache utility. The PurgeCache utility is case sensitive, so you must pass the value All (with lowercase letter l's) to purge all caching categories.
Oracle Identity Manager input parameters cannot contain unsupported characters including the following: ; # / % = | +, \ ". If you run a report and enter any of these characters in the Report Display page, then you are redirected to the Report Input Parameters page. To resolve this issue, reenter the necessary criteria on the Report Input Parameters page, click Submit, and then enter the correct criteria without the unsupported characters on the Report Display page.
The combination of a Remote Manager on IBM JDK and the Oracle Identity Manager server on Sun JDK is not supported. Similarly, the combination of a Remote Manager on Sun JDK and the Oracle Identity Manager server on IBM JDK is also not supported.
There is a known issue when data flow is configured between the object form and process form for the date field and the Pre-populate check box is selected for the Process Form.
For example, suppose you use Design Console to create a process definition for a resource object and select the Auto Pre-populate check box on the process form. You establish the data flow from the date field of the object form to the date field of the process form. Then, if you use Administrative and User Console to perform a task such as direct provisioning, the "Invalid Date Format" message displays after you specify the date and other values on the object form and click Continue.
To work around this problem, ensure that the Auto Pre-populate check box is deselected on the process form in the Design Console.
If a resource is in the Waiting state, then it is not displayed on the Users Associated With This Resource page.
When you import an XML file, a stack overflow exception may be thrown if the import operation changes the organizational hierarchy. You can safely ignore this exception.
After installing Release 9.0.3.1 on WebSphere 5.1.1.12 and starting the application server, a benign exception warning message appears in the WebSphere log regarding the following:
J2CA0007W: An exception occurred while invoking method setsetMcfPassword on com.ibm.ejs.jms.JMSManagedQueueSessionFactory
This is a known WebSphere exception warning message and can safely be ignored. Refer to IBM's WebSphere Application Server support Web site for more information.
When replicating session data, the JBoss application server may fail and generate the following exception in a clustered configuration:
16:43:07,296 ERROR [JBossCacheManager] processSessionRepl: failed with exception: java.util.ConcurrentModificationException 16:43:07,296 WARN [InstantSnapshotManager] Failed to replicate sessionID:GzUYJdxlSLVxS7ssRtvWwQ**.tqx00
If you attempt to use the Requester filter to refine the results in the Pending Approvals page, a message displays indicating the search did not return any results. You can only use the Requester filter to refine results by the requester ID and not by requester first name or last name.
The URL for the calendar icon in the Administrative and User Console may appear twice on Windows 2003 platforms.
In the Administrative and User Console, searching based on the Date Type User Defined Field may return all records instead of just the records matching the specified dates. Using character string input as search criteria may also return all records. To avoid these issues, be sure to use the following date format: YYYY-MM-DD.
If an Attestation process has a group as its Process Owner, that group cannot be deleted. Attempting to delete the group will display a System Error page. To avoid this issue, modify the attestation process definition and assign a different group as the process owner group. You can delete the original group after assigning a different process owner group.
All dates in the Administrative and User Console must be edited using the calendar icon associated with the Date field. Do not edit dates directly by entering text in a Date field, instead, use that field's calendar icon to edit the date value.
Do not modify any settings or assignments for internal system seeded users. If you attempt to modify any settings or assignments for internal system seeded users you may encounter errors.
When you export a resource, groups with Data Object permissions on that form are not exported with the resource.
Resource dependency relationships are reversed after exporting a resource using the Administrative and User Console's Deployment Manager. For example, Resource-Y depends on Resource-X. After exporting Resource-Y, Resource-X is not displayed as a dependency. However, after exporting Resource-X, Resource-Y is displayed as its dependency.
After a Single Sign-On session time out, clicking Restart in the Administrative and User Console's Deployment Manager or WorkFlow Visualizer windows may cause a "Client-Side error occurred" error message to appear. If this message appears, close the browser and access the Administrative and User Console using a new browser window.
When you run the purgecache.bat utility, the following exception is thrown:
java.lang.NullPointerException
at
com.opensymphony.oscache.base.AbstractCacheAdministrator
.finalizeListeners(Abs
tractCacheAdministrator.java:323)
at
com.opensymphony.oscache.general.GeneralCacheAdministrator
.destroy(GeneralCacheAdministrator.java:168)
at net.sf.hibernate.cache.OSCache.destroy(OSCache.java:59)
at
net.sf.hibernate.cache.ReadWriteCache.destroy(ReadWriteCache.java:215)
at
net.sf.hibernate.impl.SessionFactoryImpl.close(SessionFactoryImpl.java:542)
This exception can be safely ignored.
After running a report in the Administrative and User Console and clicking the Export CSV button to export the report data to Comma Separated Value format, a File Download window appears. In Internet Explorer version 6.0.2800, clicking on the Open button in the File Download window may display the same File Download window again. Click the Open button on the second File Download window to open the CSV file. This issue does not occur with Internet Explorer version 6.0.2900 and higher.
The Administrative and User console does not support password reset questions in Single Sign-On mode. When the "Force to set questions at startup" flag is set to TRUE, login fails. To avoid this issue, perform the following steps:
Log in to the Design Console as xelsysadm.
Search for the system configuration parameter "Force to set questions at startup", set it to FALSE, and save the change.
You cannot disable organizations that have child, suborganizations without first removing the suborganizations. Release 9.0.3.1 contains a known issue where disabling an organization with a suborganization is permitted and no message is displayed. The organization is disabled regardless if it has suborganizations and no message appears to alert you if the organization has suborganizations.
Each application server exhibits different behavior when a database connection is lost during execution. While JBoss can automatically reestablish database connection, WebLogic and WebSphere cannot. For WebLogic, you can define settings for testing reserved connections, in which case the connections are established automatically. For WebSphere, you must configure your database for high-availability.
When connecting to the Administrative and User Console on Oracle Application Servers, do not use the IP address of the machine hosting the Oracle Application Server in the URL, as you may encounter errors. Instead, be sure to use the fully-qualified domain name of the machine hosting the Oracle Application Server in the URL for the Administrative and User Console, for example:
http://localhost:7777/xlWebApp
Release 9.0.3.1 contains the following known issues for users that were created with the same user ID as a previously deleted user, regardless if the user ID reuse property is enabled:
those users cannot Create Request (Bug 5740274)
those users cannot be assigned as a proxy (Bug 5741955)
the Oracle Identity Manager Administrator cannot unlock those users after they have been locked-out as a result of multiple login attempts with incorrect passwords (Bug 5741957)
reports may not generate information for those users, but instead will generate information for the deleted user with same ID (Bug 5741951)
In Windows Server 2003 Service Pack 1 (SP1) environments, you may receive a System Error in the Administrative and User Console if you click the Back button after receiving the Illegal Script tag or Characters error message. This is a known issue (believed to be caused by patch MS03-048) in Windows Server 2003 SP1.
After installing Release 9.0.3.1 on Oracle Application Server and then starting Oracle Application Server, benign warning messages regarding files with the same name but that are not identical may appear in the Oracle Application Server log file. These warning messages are benign and can safely be ignored.
Export using the Administrative and User Console's Deployment Manager may experience problems when Internet Explorer is configured to use Microsoft Virtual Machine. To reset the default Virtual Machine, perform the following:
Download and install the Sun JRE 1.4.2_xx from the following Web site:
Select Tools from the Internet Explorer menu.
Select Internet Options.
Select the Advanced tab.
Scroll down to Java (Sun).
Check Use Java 2v1.4.2_xx for <applet>.
Scroll down to Microsoft VM.
Uncheck Java console enabled and Java logging enabled.
Restart the computer.
Note:
JRE 1.4.2 is not required to run the Oracle Identity Manager Administrative and User Console—it is only required to run the Deployment Manager.If you are running JBoss on Linux and the Linux kernel supports IPv6, you may encounter the following exception:
IP_MULTICAST_IF: java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method) at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:295)
This exception is caused by versions of Sun Microsystem's JDK, up to and including JDK 5. If you do not need IPv6 support, you can avoid this exception by disabling IPv6 support in the JVM by adding -Djava.net.preferIPv4Stack=true to the <XL_HOME>/bin/xlStartServer.sh java command used to start JBoss.
When more than one approval task is assigned to a user, multiple entries for the same request ID are displayed on the pending approvals page in Administrative and User Console. You can selected any of the displayed entries to perform the approval process.
This section describes known issues related to tasks performed using the Release 9.0.3.1 Design Console—it does not contain known issues related to the installation of the Design Console or its translated text. This section contains the following topics:
Invoking FVC Utility on WebSphere May Display "Realm/Cell is Null" Error (Bug 5563654)
Form Designer Feature Does Not Support Special Characters for Column Name (Bug 5373011)
Design Console's xlclient.cmd Executable Does Not Launch if Paths Include a Space (Bug 5853425)
Default Tasks Not Added to Resource Object After Changing its Process Definition Type (Bug 5637994)
When attempting to use the FVC utility in WebSphere deployments, a dialog box with the error message Realm/cell is Null may appear. You can safely close the dialog box and ignore the error message to continue.
To avoid this issue entirely, change the properties in the <WEBSPHERE_HOME>\AppClient\properties\sas.client.props to the following:
Note:
<WEBSPHERE_HOME> represents the location where WebSphere is installed.Change the preceding values to the following:
Com.ibm.CORBA.loginSource = properties
Com.ibm.CORBA.loginTimeout = 300
Com.ibm.CORBA.securityEnabled = true
Com.ibm.CORBA.loginUserid = xelsysadm
Com.ibm.CORBA.loginPassword = xelsysadm
The Form Designer feature in the Design Console will not save entries that contain any the following special characters in the Column Name:
; / % = | + , \ ' " < >
The xlclient.cmd executable that launches the Design Console will fail if directory paths in the executable contain spaces. You will have a space in a directory path in xlclient.cmd if you installed the Design Console in a location that contains a space, for example, C:\Program Files\OIM\xlclient\java.
Also, you will have a space in a directory path in xlclient.cmd if while installing the Design Console you chose to use a JRE other than the one bundled with the Design Console and the path to that JRE includes a space, for example, C:\Program Files\Java\j2re1.4.2_12.
To avoid this issue, do not install the Design Console into a directory path that includes a space and do not specify a JRE using a directory path that includes a space. Another way to avoid this issue is to add double quotation marks (") to the paths in the xlclient.cmd executable that include spaces. For example:
Use the following approach if you install the Design Console into a directory path that includes a space:
"C:\Program Files\OIM\xlclient\java"\bin\java %DEBUG_OPTS% ^ -DXL.ExtendedErrorOptions=TRUE -DXL.HomeDir="C:\Program Files\OIM\xlclient" ^ -Djava.security.policy=config\xl.policy ^ -Dlog4j.configuration=config\log.properties ^ -Djava.security.manager -Djava.security.auth.login.config=config\auth.conf ^ com.thortech.xl.client.base.tcAppWindow -server server
Use the following approach if you specified a JRE to use and the path to the JRE includes a space:
"C:\Program Files\Java\j2re1.4.2_12"\bin\java %DEBUG_OPTS% ^
-DXL.ExtendedErrorOptions=TRUE -DXL.HomeDir=C:\oracle\xlclient ^
-Djava.security.policy=config\xl.policy ^
-Dlog4j.configuration=config\log.properties ^
-Djava.security.manager
-Djava.security.auth.login.config=config\auth.conf ^
com.thortech.xl.client.base.tcAppWindow -server server
In the Design Console, after changing the Process Definition type for a Resource Object from Approval to Provisioning, or from Provisioning to Approval, the Resource Object is not updated with the default tasks associated with each type of Process Definition. To avoid this issue, do not change the Process Definition type after setting it initially.
Attempting to delete User Defined Fields in the Design Console when the Required and Visible properties are set to true causes an error message to appear. To avoid this issue, delete the properties first, and then delete the User Defined Column.
The Rule Designer feature in the Design Console cannot save multiple rules simultaneously. To avoid this issue, save each rule individually before creating additional rules.
Toolbars in the Creating New Task window may become disabled after adding Eventhandlers or Adapters from the Integration tab when using the same Create New Task window for a second time to add a task (by clicking the New Form icon). To avoid this issue, be sure to close the Creating New Task window before creating another new task.
This section describes known issues related to reporting functionality in Release 9.0.3.1. This section contains the following topics:
Various Filters Are Inactive During Historical Report Queries (Bug 5355907)
Group Membership History Report Does Not Distinguish Between Active and Deleted Groups (Bug 5249535)
Group Membership History Report May Not Display Some Sectional Header Values (Bug 5243112)
Resource Access List Report Shows Data for Deleted Users (Bug 5472481)
When using the Administrative and User Console to query Historical Reports, various filters are inactive, including filtering by user First, Middle, and Last Name; Employee Type; and Email. Using these filters will not refine the query results.
When you run a Group Membership History report, the report results do not distinguish between active and deleted groups.
When you run a Group Membership History report, the report results may not display some sectional header values for deleted groups.
The Resource Access List report may return data for deleted users.
In the Administrative and User Console, clicking the Resource Name Lookup icon on the Input Parameters page for various reports will display a Lookup window. This Lookup window incorrectly displays Organization resources in addition to User resources for the following reports:
Resource Access List
Entitlement Summary
Resource Access List History
Resource Password Expiration
Ignore the Organization resources listed in the Lookup window. Running these reports for Organization resources will return no data.
This section describes known issues in Release 9.0.3.1 related only to globalization or translation. This section contains the following topics:
Installer Programs for Non-English Languages May Contain Some English Text (Bug 5232751)
Notes in the Administrative and User Console's Task Details Page Not Localized (Bug 5856579)
Cannot Export Reports to CSV for Multibyte Languages on WebSphere (Bug 5760558)
Some Information in Workflow Visualizer May be Displayed as Square Characters (Bug 5704436)
Inconsistent Ordering of Names in Columns of Some Reports in Non-English Environments (Bug 5557974)
Deployment Manager Import and Export Features Include an Untranslatable String (Bug 5501127)
After completing the Design Console installation for Oracle Application Server in non-English languages for Release 9.0.3.1, a pop-up window in the installer program may give the impression that the ejb.jar and oc4jclient.jar files are automatically copied to the appropriate Design Console directory.
You are required to copy the following files manually, as the installer program does not copy these files automatically:
Copy the <ORACLE_HOME>\j2ee\home\lib\ejb.jar file on the Oracle Application Server system to the <XL_DC_HOME>\xlclient\ext directory on the Design Console system.
Copy the <ORACLE_HOME>\j2ee\home\oc4jclient.jar file on the Oracle Application Server system to the <XL_DC_HOME>\xlclient\ext directory on the Design Console system.
The Release 9.0.3.1 installer programs for non-English languages may contain some untranslated text that appears in English.
In Japanese environments, the Design Console's Request Submitted page does not display the Boolean Type User Defined Field check box. If the User Defined Field enables the Boolean Type, the Requested Submitted page displays the number 1 instead of the check box. If the Boolean Type is not enabled, the Requested Submitted page displays a blank space.
In the Administrative and User Console, if the Deployment Manager's Export and Import windows or the Workflow Visualizer window are open and the session times out, the text in these windows may appear in the language of the default locale of the system where the Oracle Identity Manager server is installed. After closing the session timeout window and clicking any of the Administrative and User Console menu options, the Oracle Identity Manager Logout page appears and may also be displayed in the language of the default locale of the system where the Oracle Identity Manager server is installed.
In the Administrative and User Console, some text in the Notes field on the Task Details page may appear in English in non-English environments. Task instances that have the following names may encounter this issue:
Reconciliation Update Received
Reconciliation Insert Received
Reconciliation Delete Received
In the Administrative and User Console's Task Details page, text in the Notes field appears in the language that it is entered in—the Notes text is not displayed according to the browser locale.
Release 9.0.3.1 requires that you use only English characters for the following:
Installation paths and directory names (Bug 5397854)
Host names (Bug 5360993)
Email IDs (Bug 5397105)
If used, external certificate names and certificate content (Bug 5387397)
The Administrative and User Console requires that you use only English characters for the Email Address fields on the Create/Edit User, Account Profile, and Self-Registration pages. When installing the Remote Manager, you must also use only English characters for the Service Name on the Configuration page (Bug 5460100).
Refer to the Oracle Identity Manager Globalization Guide for complete information on the character restrictions for various components and attributes.
Due to a limitation in WebSphere, you cannot export report data to CSV format for multibyte character languages such as Japanese or Chinese.
In Windows environments, some information may appear as box characters in the Administrative and User Console's Workflow Visualizer due to a known limitation with Java Applets and globalized characters. The browser's JVM displays only those characters that are in the current locale of the system where Oracle Identity Manager is installed. Globalized characters appear correctly in applets only if you set the browser to the same locale of the system where Oracle Identity Manager is installed.
In some reports in non-English environments, the ordering of first and last names does not depend on the browser locale of the logged in user. Table 3 lists the reports and their columns where ordering of first and last names may appear incorrectly:
Table 3 Reports and Columns That May Display Incorrect Ordering of Names
| Report | Column Name |
|---|---|
|
Policy List |
Created By |
|
Policy Detail |
Created By |
|
Attestation Requests By Process |
Reviewer |
|
Attestation Process List |
Owner, Reviewer |
|
User Resource Access |
Manager Name |
|
Group Membership |
Group Created By |
|
Group Membership History |
Group Created By |
|
User Membership History |
Manager Name |
|
User Resource Access History |
Manager Name |
In non-English environments, the following reports require that the given input and filter parameters use only English values:
Entitlement Summary report
Input parameter: Account Status
Filter parameter: Account Status
Group Membership History report
Input Parameter: Membership Status
Filter Parameter: Membership Status
User Membership History report
Input Parameter: Membership Status
Filter Parameter: Membership Status
For example, searching on Account Status in the Entitlement Summary report in non-English environments and using a translated version of the status Active will return nothing. You must use the English value Active.
In the Administrative and User Console, the sorting functionality on the Group Detail >> Menu Items and Group Detail >> Menu Items >> Assign Menu Items pages sorts values based on the English values in the database and not the translated values on the screen.
The Administrative and User Console's Deployment Manager import and export features use the Java AWT file dialog that shows the string All Files (*.*) in the dialog filter. The All Files (*.*) string is not translated for any locale and remains in English. This limitation is caused by the Java implementation and the string cannot be translated. Refer to the Sun Microsystems bug report for Bug ID 4152317 at the following URL for more information:
After a successful archive with the Reconciliation Archival utility, the name of its log files for some non-English environments may not include the time stamp. For example, you may see a log file that looks something like Arch_Recon____15_56.log instead of Arch_Recon_Wed_31_2007_03_31.log.
Oracle Identity Manager Release 9.0.3.1 resolves the known issues from previous releases listed in Table 4.
Table 4 Issues Resolved by Release 9.0.3.1
| Bug # | Description |
|---|---|
|
5886065 |
For approval tasks assigned to a target user's manager, if a request is made for multiple users with different managers, then only one user-defined approval task is inserted. |
|
5887011 |
Task approvers did not receive e-mail notification for submitted resource requests even though Group was selected as the target type in the approval task for the resource. |
|
5891802 |
An entity adapter did not return a value to the resource form when the entity adapter was mapped to the E-mail Address (USR_EMAIL) field. |
|
5902137 |
Attribute mapping discrepancies cause reconciliation to fail. |
|
5958235 |
The |
|
6027182 |
The "Password is invalid" message was displayed when logging into the Administrative and User Console using an expired password on OC4J installations. |
See Also:
Oracle Identity Manager Release Notes for Release 9.0.3 for information about known issues resolved by Oracle Identity Manager Release 9.0.3No API changes were introduced as part of Oracle Identity Manager Release 9.0.3.1. Refer to the API JavaDocs included with Release 9.0.3 for a full description of all implemented interface functionality.
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. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation
Screen readers 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, some screen readers 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.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Identity Manager Release Notes Release 9.0.3.1
E10315-01
Copyright © 1991, 2007, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
