There are two ways you can create and populate the databases for Identity Governance. You can have the Identity Governance installation program create and populate the databases or you can have a database administrator manually create the databases and use the SQL scripts to populate the databases. It depends on your business policies of who can modify and as to whether you allow the Identity Governance installer to create and populate the databases or whether your database administrator creates and populates the databases.
This section explains the steps required to have a database administrator manually create and populate the databases. The Identity Governance installer generates a SQL script that can be run after the Identity Governance installation completes. To generate the SQL scripts, the installer asks for the name of the database, user tablespace (USERS by default), the temporary tablespace (TEMP by default), and the user schemas to represent the operations, archive, data collection, provisioning workflow, and analytics tables for Identity Governance.
The database must exist before you install Identity Governance. The database administrator can populate the databases after you complete the Identity Governance installation. This option allows your database administrator to see what changes the Identity Governance installer makes to the database server before making the changes.
To use the SQL script to populate the databases:
Ensure that Identity Governance supports the database version you are using. For more information, see Section 2.4, Hardware and Software Requirements.
Ensure that the database server and the Identity Governance server run on the same subnetwork in your IT environment.
(Conditional) If you are not using PostgreSQL, download the appropriate JDBC driver for your database and copy it to the application server. For more information, see Section 5.7, Adding the JDBC File to the Application Server.
Create the appropriate database for your IT environment. For more information, see Section 5.8, Creating the Databases before Installing Identity Governance.
Create a temporary database administrator account that the Identity Governance installer uses to populate the databases. For more information, see Section 5.9, Creating a Temporary Database Administrator.
Install Identity Governance, then select Generate SQL for later in the Database details section of the installation program.
(Conditional) If you install Identity Reporting on a separate server from Identity Governance, install Identity Reporting after you install Identity Governance, then select Generate SQL for later in the Database details section of the installation program.
After the installation completes, have the database administrator review the SQL scripts to see what changes they make to the database.
Use the SQL scripts to populate the databases. For more information, see Section 5.11, Configuring the Databases Using the SQL Scripts.
IMPORTANT:If you start Identity Governance or Identity Reporting before using the SQL scripts, Identity Governance automatically populates the databases for you. If you do not want to have the Identity Governance installer modify the databases, ensure to run the SQL scripts before starting Identity Governance or Identity Reporting.