000031229 - Questions regarding V7.0+ RSA Identity Governance and Lifecycle release:  What are the features, guidelines and considerations?

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Nov 1, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031229
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0+
 
IssueRSA Identity Governance and Lifecycle version 7.0 has several major changes associated with the application as well as the environment. Where can information to help prepare for this upgrade be found?
TasksLogin to RSA LINK and reference the available RSA Identity Governance and Lifecycle V7.0.0 and up documents and whitepapers.
Select product  RSA Identity Governance and Lifecycle,  then select the documentation link and look under the version you are upgrading to:
RSA Identity Governance and Lifecycle Data Collection Migration:  The Collection Migration Utility:  - It is crucial that customers upgrading from previous versions execute the Collection Migration Utility before they upgrade and review the resultant report to understand what changes may be required for V7.0.0 and up to work properly.  This is also documented in Chapter 2 of the Upgrade and Migration Guide.

 

RSA Identity Governance and Lifecycle Platform Datasheet and Support Matrix for Version 7.0.x:    This document outlines the hardware and software versions which are supported for V7.0.x.  
Customer Preparations for Upcoming RSA Identity Governance and Lifecycle 7.0.x Release: - This document outlines key features and notes to help prepare for the upgrade.

 

ResolutionKey changes to note which are included as part of the major V7.0.0  RSA Identity Governance and Lifecycle release are listed below.



   -  Migration Utility available

   -  Database upgrade from Oracle 11.x Standard Edition(SE) to Oracle 12c Enterprise Edition (EE)

   -  Deprecation of support for earlier Internet Explorer (IE) versions

   -  Deprecation of support for original Aveksa Security Model

   -  Deprecation of Identity Collector (IDC) groups

   -  Rejection of duplicate entitlements

   -  Rejection of cyclic groups

   -  Significant role data collector changes
NotesThe migration report scripts can be run against a remote database from the application server. Just note that they look for existence of Aveksa_System.cfg and environment variables that may not be present if your application server is deployed in WebSphere or WebLogic.

Attachments

    Outcomes