Depending on your system and environment, you may need to perform some of the following actions when you install or upgrade RSA Identity Governance and Lifecycle.
- Run the appliance updater.If your environment is a purchased hardware or software appliance, RSA recommends running the latest appliance updater. The appliance OS updater bundles a certified patch set for the operating system of an RSA appliance and the database on the appliance. Downloading and running these patches closes vulnerabilities and addresses bugs. If using a hardware appliance or software appliance with a local RSA Oracle instance, RSA recommends running the appliance Oracle updater to update any critical Oracle patches. The appliance updater does not patch the RSA Identity Governance and Lifecycle application. The patches are provided in a compressed file (rsaimg_updater_<release_date>_<platform>.tar.bz2) and posted on RSA Link at https://community.rsa.com/community/products/governance-and-lifecycle. Download and apply the appliance updater patches on a regular basis as new patches are released.
For more information, see the RSA Identity Governance and Lifecycle Appliance Updater Guide.
Review certificate configuration if your deployment contains Active Directory collectors that use SSL. The JRE has been upgraded to Java 8. By default, Java 8 enforces endpoint identification on LDAPS connections to improve the robustness of the connections. After upgrading, Active Directory collectors that use SSL that were previously able to connect might be unable to connect. View the aveksaServer.log for details about connection failures. If this occurs, ensure that the certificate of the host configured in the collector settings has the correct subject alternative name attributes available that match the hostname.
- If upgrading RSA Identity Governance and Lifecycle in a WebLogic or WebSphere environment, you must update the AVDWDB data source. Instructions are provided in the RSA Identity Governance and Lifecycle Upgrade and Migration Guide.
When migrating to 7.1.1 Patch 2 or 3 using the command line, there is a potential issue in which the migration is unable to find the aveksa-version.properties file. If this occurs, you should complete the migration through the browser interface. Note that the migration may take some time. Check /home/oracle/wildfly/standalone/log/migrate.log to view the migration status.
If you are unable to complete the migration using a browser, download the appropriate file for your migration from the following list and rename it to aveksa-version.properties. As the oracle user, copy the renamed file to the /home/oracle/database/ directory, then run the migrate.sh command.