51.5 Upgrading the Identity Reporting

Identity Reporting includes Event Auditing Service and two drivers. Perform the upgrade in the following order:

Upgrade the driver package for the Data Collection Services.
Upgrade the driver package for the Managed System Gateway Service.
Upgrade the Event Auditing Service.
Upgrade Identity Reporting.

51.5.1 Upgrading the Driver Packages for Identity Reporting

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 Event Auditing Service or Identity Reporting.

In Designer, open your current project.
Right-click Package Catalog > Import Package.
Select the appropriate package. For example, Manage System Gateway Base package 2.0.0.20120509205929.
Click OK.
In the Developer View, right-click the driver and then click Properties.
Navigate to the Packages tab in the Properties page.
Click the Add package (+) symbol in the top right corner.
Select the package, and then click OK.
Complete the configuration process for the driver. For more information, see the following sections:
- Section 40.1.2, Configuring the Managed System Gateway Driver
- Section 40.1.3, Configuring the Driver for Data Collection Service
Repeat Step 2 through Step 9 to upgrade the package for the Data Collection Service Driver.
Ensure that the Managed System Gateway Driver and Data Collection Service Driver are connected to the upgraded Identity Manager.

51.5.2 Upgrading the Event Auditing Service

Before upgrading EAS, review the following considerations:

Ensure that you have upgraded the Identity Reporting drivers. For more information, see Section 51.5.4, Upgrading Identity Reporting.
To upgrade EAS, install the new version on top of the older version. For more information, see Section 37.0, Installing the Event Auditing Service.
If you used a different auditing solution such as Novell Audit, update the logevent file (.conf or .cfg) on your servers to use the correct ports to point to EAS. This ensures that events are routed to EAS rather than to the Novell Auditing server.
If you installed Identity Manager on a Windows server, ensure that xdasconfig.properties file has the correct information to connect to EAS. For more information, see Section 51.5.3, Sending XDAS Events from a Windows Server to EAS.

51.5.3 Sending XDAS Events from a Windows Server to EAS

If you host the Identity Manager engine on a Windows server, upgrading EAS does not overwrite your custom settings in the xdasconfig.properties file for the engine. After the upgrade, update the file to ensure that Identity Manager can send XDAS events to EAS.

Upgrade EAS on the Linux server.
Install or upgrade the Identity Manager engine on the Windows server.
In a text editor, open the xdasconfig.properties file, located by default in the C:\NetIQ\IdentityManager\NDS folder.
In the log4j.appender entry, remove the space between the %c and the semi-colon (:) so the line appears as follows:
```
log4j.appender.S.layout.ConversionPattern=%c: %p%m%n
```
Save and close the file.
Enable logging with XDAS for Identity Manager.

51.5.4 Upgrading Identity Reporting

Before upgrading Identity Reporting, you must upgrade the User Application and the Event Auditing Service. To upgrade Identity Reporting from version 4.0.2 or later, install the new version on top of the older version. For more information, see Installing Identity Reporting.

51.5.5 Changing the References to reportRunner in the Database

After upgrading Identity Reporting and before starting the application server for the first time, ensure that you update the references to reportRunner from the database.

Stop the application server, such as Tomcat.
Navigate to the Identity Reporting installation directory and rename the reportContent folder to ORG-reportContent.

For example: /opt/netiq/idm/apps/IdentityReporting
Clean the temporary and work directories under the Tomcat folder.
Log in to the PostgreSQL database with EAS.
1. Locate the reportRunner references in the following tables:
  - idm_rpt_cfg.idmrpt_rpt_params
  - idm_rpt_cfg.idmrpt_definition
2. 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 the application server.

Check the logs to see if the reports are regenerated with the correct reportRunner.
Log into Identity Reporting and run the reports.

51.5.6 Verifying the Upgrade for Identity Reporting

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.