Identity Reporting includes two drivers. Perform the upgrade in the following order:
NOTE:Ensure that your database is upgraded to a supported version.
Upgrade your database to a supported version. For information on upgrading PostgreSQL database, see Preparing the PostgreSQL Database for Upgrade.
Upgrade the driver packages. For more information, see Upgrading the Driver Packages for Identity Reporting.
Upgrade/Migrate to Sentinel Log Management for IGA.
If you are upgrading from Identity Reporting 4.6.x, upgrade Sentinel Log Management for IGA to 4.7 version. For more information, see Upgrading Sentinel Log Management for IGA.
If you are migrating from Identity Reporting 4.5.x, migrate from EAS to Sentinel Log Management for IGA. For more information, see Updating the Drivers for Identity Reporting.
Upgrade Identity Reporting. For more information, see Upgrading Identity Reporting.
Before you perform an upgrade, the following considerations apply:
During upgrade, ensure that you specify the correct location for the postgresql-9.4.1212.jar file. The default location is /opt/netiq/idm/postgres/. The database connection will fail in the following scenarios:
if you provide the incorrect path
if you provide the incorrect jar file
if the firewall is enabled
if the database does not accept connections from remote machines
If your database is configured over SSL, remove ssl=true from the server.xml file from PATH located at:
For example, change
This section explains how to update the packages for the Managed System Gateway and Data Collection Service drivers to the latest version. You must perform this task before upgrading Identity Reporting.
In Designer, open your current project.
Select the appropriate package. For example,.
In the Developer View, right-click the driver and then click.
Navigate to thetab in the page.
Click thesymbol in the top right corner.
Select the package, and then click.
Repeat the same procedure to upgrade the package for the Data Collection Service Driver.
NOTE:Ensure that the Managed System Gateway Driver and Data Collection Service Driver are connected to the upgraded Identity Manager.
Download the SentinelLogManagementForIGA184.108.40.206.tar.gz from the NetIQ downloads Website.
Navigate to a directory where you want to extract the file.
Run the following command to extract the file.
tar -zxvf SentinelLogManagementForIGA220.127.116.11.tar.gz
Navigate to the SentinelLogManagementforIGA directory.
To install SLM for IGA, run the following command:
Specify the language that you want to use for installation, then press Enter.
Enter y to accept the license agreement and complete the upgrade.
NOTE:After SLM for IGA is upgraded, manually import the latest collectors.
Navigate to the directory where you have extracted the SentinelLogManagementForIGA18.104.22.168.tar.gz file.
Navigate to the /content/ directory.
Import and configure the collectors. For more information, see Installing and Configuring the Identity Manager Collector in NetIQ Identity Manager - Configuring Auditing in Identity Manager.
When you upgrade the operating system from SLES 11 to SLES 12, the upgrade procedure for the operating system deletes some SLM for IGA RPMs.
The following commands ensure SLM for IGA works correctly after you upgrade the operating system.
NOTE:You must upgrade SLM for IGA before you upgrade the operating system.
Use the following steps to upgrade your operating system:
Navigate to the directory where the Sentinel install file was extracted.
Stop the Sentinel services:
Run the following command:
Upgrade your operating system.
Run the following command:
Restart the Sentinel service:
Download the Identity_Manager_4.7_Linux.iso from the NetIQ Downloads website.
Mount the downloaded .iso.
Run the following command:
Read through the license agreement.
Enter y to accept the license agreement.
Specify whether you want upgrade the Identity Manager components. The available options areand .
Select Identity Reporting to proceed with the upgrade.
Specify the following details:
OSP Installed: Specify if OSP is installed.
OSP Install Folder: Specify the backup installation folder for OSP.
Reporting Installation Folder for backup: Specify the Reporting Installation folder.
Create schema for Identity Reporting: Specify whether you want to create the schema for your database now or later. The available options are, , and .
Identity Reporting Database JDBC jar file: Specify the database JAR file for Identity Reporting. The default location of the existing database jar file is /opt/netiq/idm/apps/postgres/postgresql-9.4.1212.jar.
Identity Reporting Database user: Specify the name of the Reporting database user.
Identity Reporting Database account password: Specify the Reporting database password.
IMPORTANT:If you are installing OSP on a new server, you must restore your existing OSP settings on the new server. For more information, see One SSO Provider.
NOTE:Identity Manager 4.6.1 reports do not work after you perform an upgrade. You can only use Identity Manager 4.7 reports.
During upgrade, if you have selectedcreation as or , ensure you do the following:
systemctl restart netiq-tomcat
Log in to Identity Reporting.
Delete the existing datasource and report definitions from the Identity Reporting repository.
Add the new Identity Manager Data Collection Services datasource.
Launch Identity Reporting.
Verify that old and new reports are being displayed in the tool.
Look at theto see whether your scheduled reports appear.
Ensure that thepage displays your previous settings for managed and unmanaged applications.
Verify that all other settings look correct.
Verify whether the application lists your completed reports.
NOTE:After upgrading Identity Manager to latest version (single server) if Identity Governance properties/parameters are not present in configupdate.sh.properties and ism-configuration.properies, you need to manually update the files. For more information, see Configuring Identity Manager for Integration in NetIQ Identity Manager - Administrator’s Guide to the Identity Applications.