When installing Identity Reporting, consider the following prerequisites and considerations:
This guide provides information about installing Identity Reporting for use with Identity Governance only. If you have already installed Identity Reporting with Identity Manager, you might not need to install it again for Identity Governance. Ensure that you have the appropriate version of Identity Reporting. For more information about installing with Identity Manager, see:
Windows:
Identity Reporting Components
in the NetIQ Identity Manager Setup Guide for Windows.
You can install Identity Reporting on the same server as Identity Governance, and the two products use the same Apache Tomcat instance, or you can install it on a separate server running a separate instance of Apache Tomcat.
Assign the Report Administrator authorization to any users that you want to be able to access the reporting functionality.
Install Zulu OpenJDK and Apache Tomcat on the server that runs Identity Reporting. For more information, see Section 3.0, Installing Required Components.
Ensure that you have a supported database to which the installation process can connect. You can use the same database you deployed for Identity Governance. For more information, see Section 5.0, Creating Databases for Identity Governance and Components.
Ensure that the JDBC driver for the supported database is on the server where you install Identity Reporting. For more information, see Section 2.4.2, Database Requirements.
Ensure that the database runs in the same subnetwork as Identity Reporting.
If you use an Oracle database, you must create the database (SID) in AL32UTF-8 (Unicode UTF-8 Universal character set) before installing Identity Reporting.
Ensure that all servers in your Identity Governance environment are set to the same time, particularly the servers for the database and events auditing components. If you do not synchronize the time on your servers, some reports might be empty when executed. For example, this issue can affect data related to new users when the servers hosting Identity Governance and the reporting databases have different time stamps.
(Conditional) If you want to enable email notifications for reports, you must have an SMTP server installed and configured. If you want to guarantee email delivery, you must install ActiveMQ on the server where you install Identity Governance.
(Conditional) If you want to enable secured auditing for Identity Reporting, it is recommended that you configure the audit server to use TLS before beginning the Identity Reporting installation so that the Identity Reporting installer can connect to the audit server and retrieve the audit server certificate to add to the local keystore. For more information, see Section 3.8, Securing Connections with TLS/SSL.