The database for the Identity Applications supports tasks such as storing configuration data and data for workflow activities. Before you can install the applications, the database must be installed and configured. For more information about supported databases, see the NetIQ Identity Manager Technical Information website. For more information about considerations for the User Application database, see Prerequisites for Installing the Database for the Identity Applications.
NOTE:If you are migrating to a new version of RBPM and the Identity Applications, you must use the same database that you used for the previous installation. That is, the installation from which you are migrating.
This section provides configuration options for using an Oracle database for the User Application. For information about supported versions of Oracle, see the NetIQ Identity Manager Technical Information website.
Databases from different releases of Oracle are compatible if they support the same features and those features perform the same way. If they are not compatible, certain features or operations might not work as expected. For example, creation of schema fails that does not allow you to deploy the identity applications.
To check the compatibility level of your database, perform the following steps:
Connect to the Database Engine.
After connecting to the appropriate instance of the SQL Server Database Engine, in, click the server name.
Expand, and, depending on the database, either select a user database or expand and select a system database.
Right-click the database, and then click.
Thedialog box opens.
In thepane, click .
The current compatibility level is displayed in thelist box.
To check the, enter the following in the query window and click .
SQL> SELECT name, value FROM v$parameter
WHERE name = 'compatible';
The expected output is: 126.96.36.199
Your User Application database must use a Unicode-encoded character set. When creating the database, use AL32UTF8 to specify this character set.
To confirm that an Oracle 12c database is set for UTF-8, issue the following command:
select * from nls_database_parameters;
If the database is not configured for UTF-8, the system responds with the following information:
Otherwise, the system responds with the following information that confirms the database is configured for UTF-8:
NOTE:It is recommended to use JDBC JAR version ojdbc6.jar.
For more information about configuring a character set, see “Choosing an Oracle Database Character Set”.
The User Application requires that the Oracle database user account have specific privileges. In the SQL Plus utility, enter the following commands:
CREATE USER idmuser IDENTIFIED BY password GRANT CONNECT, RESOURCE to idmuser ALTER USER idmuser quota 100M on USERS;
where idmuser represents the user account.
For your convenience, NetIQ provides an installation program for PostgreSQL, which fully supports the framework services and applications within Identity Manager. The installation program guides you through the configuration process. For more information, see Installing PostgreSQL and Tomcat.
This section provides configuration options for using an SQL Server database for the User Application. For information about supported versions of SQL Server, see the NetIQ Identity Manager Technical Information website.
SQL Server does not allow you to specify the character set for databases. The User Application stores SQL Server character data in a NCHAR column type, which supports UTF-8.
After installing a supported version of Microsoft SQL Server, create a database and database user using an application such as SQL Server Management Studio. The database user account must have the following privileges:
NOTE:It is recommended to use JDBC JAR version sqljdbc4.jar with Microsoft SQL Server 2014 and sqljdbc42.jar with Microsoft SQL Server 2016.