
In order to register for a class, you need to first create an EMC account
If you need further assistance, contact us
Summary
This on-demand learning guides the participant through the steps to accomplish a standard migration from RSA Authentication Manager version 6.1 to version 8.x.
Overview
Product functionality that is pertinent to the migration of v6.1 is discussed as well as the process and considerations for migrating to a v8.x environment.
Note that this course discusses migration of “out-of-box” deployments and does not address migration of customized APIs running under v6.1.
Audience
Technologists who are responsible for an RSA SecurID system and intend on migrating from RSA Authentication Manager v6.1 to v8.
Prerequisite Knowledge/Skills
Familiarity with RSA SecurID technology and RSA Authentication Manager v6.1.
RSA Authentication Manager 6.1 to 8.0 Data Migration | Migrating RSA Authentication Manager v6.1 to a v8.1 Hardware Appliance |
---|
 This course describes the features and functions that are new to RSA Authentication Manager v8.x as well as how database objects and structures map from v6.1 to v8.x. It details several deployment and migration scenarios and the steps required to migrate v6.1 data to a v8.x installation. Duration 1 hour (on-demand learning) Course Objectives Upon successful completion of this course, participants should be able to: - Provide an overview of the fundamental differences between RSA Authentication Manager v6.1 and v8.x – features and functions
- Describe the specific database objects that are migrated between product versions and how they are handled by the migration
- Describe the pre-migration steps to prepare a v6.1 database for migration
- Describe the post-migration structures that can be created in v8.x to contain and manage migrated objects
Course Outline - Comparison of v6.1/v8.x Architecture and Administrative Structures
- Describes the general architecture and compares differences/parallels between product versions
- Describes the major areas of importance in the v8.x data structures and how they map to a v6.1 environment
- Describes terminology used in v8.x
- Overview of the Migration Process
- High-level description of the methodology for approaching a migration
- Describes in detail how database objects are mapped from version to version
- Pre-Migration Preparation
- Describes the considerations and best practices involved in preparing a v6.1 environment for migration — database cleaning, creating/dismantling structures, etc. and preparing a v8.x environment to receive migrated information — what decisions and elements should be made before migration
- Post-Migration Considerations
- Description of tasks that can be performed after the completion of the migration process
- Migration of an RSA SecurID Appliance
- Describes the general process for migrating data from a v6.1 RSA SecurID Appliance to a v8 environment
|  This course augments the data migration course (described above) and focuses on the process and considerations for migrating to a version 8.1 hardware appliance from v6.1. Duration 75 minutes (on-demand learning) Course Objectives Upon successful completion of this course, participants should be able to: - Understand a deployment architecture that includes one or more v8.1 hardware appliances as primary and/or Replica instances
- Describe the migration process of migrating from a v6.1 software or hardware appliance platform to a v8.1 hardware appliance
Course Outline - Overview of v8.1 Architecture
- Describes the architecture and deployments options that include a v8.1 hardware appliance
- Overview of the Migration Process
- Describes migration tasks involved with migrating to a hardware appliance that are over and above the tasks involved with data migration alone
- Using the v6.1 Migration Assessment Tool
- Migration Steps
- Describes the initial connections and setup of a v8.1 hardware appliance
- Describes the steps involved with migration from exporting v6.1 data to importing it into a v8.1 hardware appliance
|

In order to register for a class, you need to first create an EMC account
If you need further assistance, contact us