2 Preinstallation Considerations for Globalization

Before installing the Oracle Identity Manager application components, configure your locale and set up your database for globalization.

This chapter discusses the following topics:

Configuring Settings for a Locale
Setting Up the Database

Configuring Settings for a Locale

Prior to installation, you must configure regional language settings for your locale on the application server. Ensure that you install the appropriate language version of your operating system and set any other required language settings.

The combination of a UTF-8 locale for multibyte languages and a Linux operating system is not supported by the Oracle Identity Manager Installer. To run Oracle Identity Manager on a Linux computer set to a UTF-8 locale for multibyte languages, use a non-UTF-8 locale only for installing Oracle Identity Manager, and then switch to the required UTF-8 locale after the installation.

If you run the Oracle Identity Manager Installer on a computer set to the Danish language locale, then the Danish language option is displayed as dansk in the list from which you select a language for the installation.

The combination of the Portuguese (Brazilian) locale and IBM WebSphere Application Server is not supported. For more details, see the following Web page:

http://www-1.ibm.com/support/docview.wss?rs=3068&context=SSNVBF&dc=DB550&uid=swg1IZ01077&loc=en_US&cs=UTF-8%3C=en&rss=ct3068websphere

Setting Up the Database

In this release, Oracle Identity Manager only supports globalization on Oracle Database.

For globalization support in Oracle Identity Manager, Oracle recommends configuring the database for Unicode. To configure Unicode support for Oracle Database, use the following settings:

Note:

See Oracle Database Installation Guide to understand whether or not you must select the AL32UTF8 character set and set the NLS_LENGTH_SEMANTICS initialization parameter to CHAR.

When you install Oracle Database, select the AL32UTF8 character set, as described in Oracle Database Installation Guide.
If you have not already set the NLS_LENGTH_SEMANTICS initialization parameter to CHAR, do this as described in the following procedures.

To set the initialization parameter NLS_LENGTH_SEMANTICS to CHAR when you use a server parameter file (SPFILE):

Connect to SQL*Plus as the SYSDBA.

Run the following command in SQL*Plus:

ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH

To set the initialization parameter NLS_LENGTH_SEMANTICS to CHAR when you use the init.ora parameter file (PFILE):

Connect to SQL*Plus as the SYSDBA:
Run the following command in SQL*Plus:
```
ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR
```
This command takes effect immediately and persists until the database is shut down.
Modify your init.ora parameter file to add NLS_LENGTH_SEMANTICS=CHAR.

This step ensures that NLS_LENGTH_SEMANTICS is set if you restart the database.