5.3 Preparing the Database Environment for Identity Reporting

When using PostgreSQL, the installation process for Identity Reporting can create the igrpt database. For MS SQL Server and Oracle, the installation process needs to connect to an existing, empty database. Create the database before installing Identity Reporting if you use MS SQL Server or Oracle for the reporting database platform.

5.3.1 Preparing MS SQL Server

If you are using MS SQL Server, you must provide the latest JDBC file and create a database for the installation program to use.

Obtaining the MS SQL Server JDBC File for the Application Server

To run queries against an MS SQL Server database, you must add an MS SQL Server JDBC file to the library for your application server. The installation program copies it there for you, but you must download and have the file ready during the installation.

  1. Download the mssql-jdbc-7.0.0.jar file from the Microsoft website.

  2. Copy the file so that it is accessible during the installation.

Creating an MS SQL Server Database for Reporting

As a system administrator, create a database, such as igrpt. Alternatively, you can allow the installation program to create a database for you. Specify an account for the database owner that the installation process can use. For more information, see Creating a Temporary MS SQL Server Database Administrator for the installation process.

5.3.2 Preparing Oracle

If you are using Oracle, you must provide the latest JDBC file and create a database for the installation program to use.

Obtaining the Oracle JDBC File for the Application Server

To run queries against an Oracle database, you must add an Oracle JDBC file to the library for your application server. The installation program copies it there for you, but you must download and have the file ready during the installation.

  1. Download the ojdbc8.jar file from the Oracle website.

  2. Copy the file so that it is accessible during the installation.

Creating an Oracle Database for Reporting

The schema names for Identity Reporting must be exactly as listed in the following procedure. This requirement means you can only have one instance of Identity Reporting within an Oracle database (SID). If you are going to have multiple environments of development, staging, and production, you can only have one Oracle server for all three environments with three separate SIDs for each instance.

Your database administrator can choose to create the schemas in the Identity Reporting database before you run the installation. Otherwise, the installation program can generate the schemas.

  1. Install a supported version of Oracle.

    For more information, see Section 1.9.2, Database Server System Requirements.

    IMPORTANT: You must create the database (SID) in AL32UTF-8 (Unicode UTF-8 Universal character set) before installing Identity Reporting.

  2. To prepare the database, complete the following steps:

    1. Create or identify the database that you want Identity Reporting to use, such as igrpt.

    2. In the database, create the schema for idm_rpt_cfg with the connect privilege.

      or

      You can allow the installation program to create the schema for you.

    3. Specify a password for the schema.

  3. When installing Identity Reporting, specify Configure database now or at startup if you want the installation program to generate the schema, tables, and views.

    For more information about using SQL statements after installation, see Section 6.1, Configuring the Databases after Installation.

5.3.3 Preparing PostgreSQL

If you are using PostgreSQL, the installation program removes existing PostgreSQL JDBC jars and installs the latest PostgreSQL JDBC file. If you want to create the reporting database for the installation program to use, you can do that before installing reporting.

Creating a PostgreSQL Database for Reporting

As a Postgres administrator, create a database, such as igrpt. Alternatively, you can allow the installation program to create a database for you. Specify an account for the database owner that the installation process can use. For more information, see Section 4.4.3, Creating a Temporary PostgreSQL Database Administrator for the Installation Process.