As you plan your upgrade, keep in mind the following considerations:
You might need to upgrade the hardware and software required to install the latest version of Identity Governance. For more information, see Section 2.4, Hardware and Software Requirements.
Open fulfillment requests are available after the upgrade.
In Identity Governance, only review owners and administrators can view the review runs that were completed in a previous version. If you have reporting installed, run reports before you upgrade to capture these details and make them available to other users after the upgrade.
Ensure you have the DNS names to identify server hosts before beginning the upgrade procedure. Because of new standards-based authentication, using IP addresses might not work correctly in all circumstances. The side effect is that the OSP integration with Identity Governance and Identity Reporting will not work correctly in these circumstances.
Upgrading Identity Governance does not update data collectors. New data collection options added in the new release only appear if you create a new collector from the new template.
Before you upgrade, record the values for the following settings. The installation process fails to restore or adversely modifies these settings:
Location of settings |
Affected Settings |
---|---|
Workflow Setting > Notification System in the Identity Governance Configuration utility |
|
Upgrade the Identity Governance components:
Verify you have the correct operating system for this upgrade. For more information, see Section 2.4, Hardware and Software Requirements.
Upgrade the framework components to supported versions. You can download scripts from the Identity Governance documentation page under the Reference heading to help you upgrade these components.
Zulu OpenJDK
Apache Tomcat
Identity Vault (LDAP server)
Access Manager if it is your authentication service
Database
IMPORTANT:If you are upgrading and changing database platforms, you cannot migrate your existing data to the new platform. For example, if you are running Identity Governance with PostgreSQL as your database and you plan to upgrade and use Microsoft SQL Server as your database, your existing data cannot move to the new database.
(Conditional) To upgrade your Identity Governance Oracle database, you must grant the CREATE PUBLIC SYNONYM and DROP PUBLIC SYNONYM privileges to the igops schema.
Back up your trust store files, and then run the OSP installer.
Run the Identity Governance and Identity Reporting installers.
Restore trust store files.
If you installed the Identity Governance components on the same server and you want to install the components separately, prepare the proper amount of new servers to run the components.
NOTE:If you have additional conditions or questions, work with your support representative or consultants to upgrade in your environment.