Review the following considerations before beginning to upgrade the Identity Manager components:
You can upgrade the components only in the console mode. Silent upgrade is not supported.
You must upgrade one component at a time.
Identity Vault must be separately upgraded. This version supports eDirectory 9.2.
If Identity Vault is configured on BTRFS file system, the upgrade process will not succeed. This version supports only Ext3, Ext4, and XFS file systems.
Ensure that there are no events in the cache file before you begin upgrading Identity Manager Engine. If your driver is using MapDB, ensure that your upgraded driver works correctly with the upgraded Engine. For more information, see Working with MapDB 3.0.5.
You must review the recommended server setup before upgrading the components. Identity Manager mandates that Identity Applications and OSP are installed on the same computer. However, Identity Reporting supports a locally or a remotely installed OSP.
After upgrading Identity Manager to the 4.8 version, the new JRE files are located in the /opt/netiq/common/jre/ directory. If required, back up the old JRE files and any customizations from the /opt/netiq/idm/jre/ directory and then delete the files.
Ensure that the Identity Applications, Identity Reporting, and the databases are uniformly configured with either the FQDN or IP address. In other words, you must not configure these components with a combination of FQDN and IP addresses.
If you are using a supported version of Oracle or Microsoft SQL Server database, you must configure two database instances for Identity Applications to work correctly; Identity Applications (idmuserappdb) database and the Workflow (igaworkflowdb) database. Ensure that you configure the database instances on the same server.
If you are using NAM Reverse Proxy configuration with Identity Applications to load forms, you must utilize NAM 5.0 version.