Identity Reporting includes two drivers. Also, you might need to migrate content from OpenText Event Auditing Service to Sentinel Log Management for IGA. Perform the upgrade in the following order:
Upgrade Sentinel Log Management for IGA. For more information, see Upgrading Sentinel Log Management for IGA in the OpenText™ Identity Manager CE 24.4 (v4.10) Install and Upgrade Guide for Linux.
Upgrade Identity Reporting.
If your database is configured over SSL, replace ssl=true with sslmode=require in the server.xml file from PATH located at C:\NetIQ\idm\apps\tomcat\conf.
For example, change
jdbc:postgresql://<postgres db>:5432/idmrptdb?ssl=true
to
jdbc:postgresql://<postgres db>:5432/idmrptdb?sslmode=require
Before upgrading Identity Reporting, you must upgrade the identity applications and SLM for IGA. To upgrade Identity Reporting, install the new version on top of the older version.
Perform the following steps to upgrade Identity Reporting:
Download the Identity_Manager_4.10.0_Windows.iso from the Software License and Download portal.
Mount the downloaded .iso.
Navigate to the <ISO installed location>\IdentityReporting folder and run the install.exe.
Select the language that you want to use for the installation and click OK.
In the Introduction page, click Next.
Read and accept the license agreement and then click Next.
The installed components and their versions are displayed.
Select Identity Reporting and click Next.
Specify the configuration settings for Identity Reporting. For more information, see Configuration Worksheet for Identity Reporting.
In the pre-upgrade summary page, review the settings and click Upgrade.
After Identity Reporting has been successfully upgraded, log in to the reporting user interface and check the version. For more information, see Verifying the Upgrade for Identity Reporting.
NOTE:
The com.netiq.rpt.ssl-keystore.type property in ism-configuration.properties file will retain the value (JKS/PKCS12) that was set prior to upgrade.
If you are upgrading Identity Reporting from 4.8.7 to 4.10, Java 8 based Tomcat is backed up in the following location: c:\netiq\idm\apps\tomcat\conf.
During Upgrade, if you select startup or file option for the prompt when to create schema for Identity Reporting, you must manually add the data source from the Identity Reporting user interface. To add, navigate to the Data sources option, click Add, and then choose IDMDCSDataSource from the list. Also, restart Tomcat after you have started it once to ensure that the available database runs properly.
After upgrading Identity Reporting to 4.9, navigate to the ism-configuration.properties file located at /opt/netiq/idm/apps/tomcat/conf/ directory and perform the following actions:
Change the value of the com.netiq.rpt.landing.url property as follows:
com.netiq.rpt.landing.url = ${com.netiq.idm.osp.url.host}/idmdash/#/landing
Change the value of the com.netiq.idmdcs.landing.url property as follows:
com.netiq.idmdcs.landing.url = ${com.netiq.idm.osp.url.host}/idmdash/#/landing
Specify the value for the com.netiq.rpt.redirect.url property in the following format: https:<hostname>:<port>/path
For example, com.netiq.rpt.redirect.url = https://192.168.0.1:8543/IDMRPT/oauth.html
After upgrading OpenText Identity Manager from 4.7.5 to 4.10 the keystore file type will be automatically changed to pkcs12 in config update utility, Ensure to change the keystore files type from pkcs12 to jks in the config update utility that are in jks before upgrade for the following entries:
Identity Vault certificates
Authentication server
Authentication keys
RBPM
After upgrading Identity Reporting from 4.7.5 to 4.9, perform the following steps:
(Conditional) If you have installed Identity application in a distributed setup, then edit configupdate.properties and change edition to advanced.
Make the following changes in configupdate:
Specify the correct OSP port.
Ensure all the tabs are corrected for TLS entries.
Update the following properties ism-configuration.properties:
com.netiq.rpt.authserver.url = https://apps.<example>.com:8543
com.netiq.rpt.ssl-keystore.file = C:\\\\NetIQ\\\\IDM\\\\apps\\\\tomcat\\\\conf\\\\idm.jks
com.netiq.rpt.ssl-keystore.pwd._attr_obscurity = ENCRYPT
com.netiq.rpt.ssl-keystore.pwd = GqJVxLBPwgWLK1/ULnOb4A==:JoxqTICngaIQtU3z/u7v/w==:2jk5gzsEca+kaz6x7xjE6g==
com.netiq.rpt.ssl-keystore.type = JKS/PKCS12
com.netiq.idm.osp.oauth-truststore.file = C:\\\\NetIQ\\\\IDM\\\\apps\\\\tomcat\\\\conf\\\\idm.jks
com.netiq.idm.osp.oauth-truststore.pwd._attr_obscurity = ENCRYPT
com.netiq.idm.osp.oauth-truststore.pwd = GqJVxLBPwgWLK1/ULnOb4A==:JoxqTICngaIQtU3z/u7v/w==:2jk5gzsEca+kaz6x7xjE6g==
Restart the tomcat service.
After upgrading Identity Reporting and before starting Tomcat for the first time, ensure that you update the references to reportRunner from the database.
Stop Tomcat.
Navigate to the Identity Reporting installation directory and rename the reportContent folder to ORG-reportContent.
For example: C:\NetIQ\idm\apps\IdentityReporting
Clean the temporary and work directories under the Tomcat folder.
Log in to the PostgreSQL database.
Locate the reportRunner references in the following tables:
idm_rpt_cfg.idmrpt_rpt_params
idm_rpt_cfg.idmrpt_definition
Issue the following delete statements:
DELETE FROM idm_rpt_cfg.idmrpt_rpt_params WHERE rpt_def_id='com.novell.content.reportRunner';
DELETE FROM idm_rpt_cfg.idmrpt_definition WHERE def_id='com.novell.content.reportRunner';
Start Tomcat.
Check the logs to see if the reports are regenerated with the correct reportRunner.
Log into Identity Reporting and run the reports.
Launch Identity Reporting.
Verify that old and new reports are being displayed in the tool.
Look at the Calendar to see whether your scheduled reports appear.
Ensure that the Settings page displays your previous settings for managed and unmanaged applications.
Verify that all other settings look correct.
Verify whether the application lists your completed reports.