There are two ways you can create and populate the databases for Identity Governance, Identity Reporting, and the Workflow Engine. You can have the Identity Governance installer create and populate the databases for you or you can have a database administrator manually create the databases and use the SQL scripts to populate the databases. It depends on your IT policies of who can modify and create databases 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 the Identity Governance installer to create and populate the required databases for Identity Governance and its components while you install Identity Governance and its components on the same server. The installer creates the databases with the correct names, populates the schema and adds the correct tables and views for each database, and it adds any additional required artifacts.
The reason you would not use this option is if your business policies do not allow installers for programs or other people than the database administrator to install and configure databases. If this is the case for you, you must manually create and populate the databases. For more information, see Section 5.6, Manually Creating and Populating the Databases.
If you are installing Identity Reporting or Workflow Engine on a separate server, there are additional steps you must perform to have the Identity Governance installer create and populate the database for Identity Reporting or Workflow Engine. For more information, see Section 5.5, Using the Identity Governance Installer to Create and Populate the Component Databases.
There are some required steps you must perform before you start the Identity Governance installation. These required steps allow the installer to properly create, configure, and populate the Identity Governance databases for you.
To have the Identity Governance installer create and populate the database:
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 server where you will install Identity Governance. For more information, see Section 5.7, Adding the JDBC File to the Application Server.
Ensure that you meet the prerequisites for the Identity Governance installation and then you can start the installation. For more information, see Section 6.3, Prerequisites for Identity Governance.
Use the information that you gather in the Table 6-1, Identity Governance Installation Worksheet to install Identity Governance.
During the installation of Identity Governance, select Configure database now to have the installer create and populate the databases.
When the installation process completes, review the Identity_Governance_InstallLog.log file. The default location of the Identity_Governance_InstallLog.log file is here:
Linux: /opt/netiq/idm/apps/idgov/logs
Windows: c:\netiq\idm\apps\idgov\logs