The document outlines a six-week plan for migrating the DC Access Manager to version 5.0.4, detailing tasks, durations, and ownership for each step. Key tasks include creating new VM servers, backing up configurations, and performing the migration process while ensuring rollback measures are in place. The plan involves multiple teams, including SIB Infra and IDAM, with several tasks currently marked as open for initiation.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
20 views3 pages
IDAM Access - Manager - Upgrade - 04-OCT-2024
The document outlines a six-week plan for migrating the DC Access Manager to version 5.0.4, detailing tasks, durations, and ownership for each step. Key tasks include creating new VM servers, backing up configurations, and performing the migration process while ensuring rollback measures are in place. The plan involves multiple teams, including SIB Infra and IDAM, with several tasks currently marked as open for initiation.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 3
Plan of Action for DC Access manage
Sr.No
8 9
2 6 Weeks Duration
Plan of Action for DC Access manager migration to 5.0.4
Tasks Duration Perquisites SIB to provide 3 new VM Server to be created with given 2 Day's specification ( Spec same as in DR - 3 no's ) Backup of Access manager configuration and all configuration 1 Day files
Take Backup of DC NAM Servers Snapshot 1 Day
Port openings as required ( Hostname should be changed,
2 Day's details will be shared by Process IT) NAM VERSION MIGRATION PLAN Remove the OLD VM's from the cluster and remove from DNS 1 Day Create New VM with the given ISO file ( Process IT to provide 1 Day the ISO file ) Install Access Manager Appliance 5.0 Service Pack 4 as a secondary appliance and point to the 4.5.3 primary appliance. 2 Day's Performing basic configuration of the secondary access manager such as hostfile,ntp etc. Take a backup of the primary Administration Console which is 1 Day on 4.5.3 by using the ambkup.sh script
Switch off the primary VM which is on 4.5.x. 1 Day
Log in as root at the secondary Access Manager Appliance
and run the migration script. Follow the steps in the upgrade 1 Day document to complete the process Login to primary access manager 5.0.1 administration console, remove the old primary Access Manager Appliance and all 3 Day's objects that reference the old primary Access Manager Appliance as described in the document Checking of applications access 3 Day's Reintegration of SAML based applications with revised 7 Day's Metadata ROLLBACK PLAN Take a VM backup of existing 4.5.x version before performing upgrade. In case of failure power off the new VM 5.0.1 and restore the backup of 4.5.x to new VM. r migration to 5.0.4 Ownership Status