Please correct under
"Backup of eDirectory database for NetWare" line 6:
mkdir sys:\_netware\nici.bak to
otherwise the copy command in line 7 will fail.
K. Surya Satya Narayana
1. Getting Started
3. Backup of eDirectory database and NICI keys on NetWare 6.5 SP7 and
OES 2 SP1 Linux servers
4. Authenticate to source and target servers
5. Select migration type as Transfer ID
6. Start Migration
7. Transfer ID started
8. Reconfiguring IDM on target OES2 SP1 Linux server
This AppNote describes how the Identity Manager 3.5.1 driver set and related configuration files on NetWare 6.5 SP7 are migrated to OES2 SP1 Linux server with the help of Novell Migration Tool. The Transfer ID scenario of the migration utility migrates Netware 6.5 SP7 eDirectory with Identity Manager 3.5.1 schema and the server identity to OES2 SP1 Linux server. The following is migrated the OES 2 SP1 server
This AppNote also explains how transparently the functionality of Identity Manager 3.5.1 is migrated from NetWare to OES2 SP1 Linux server.
A brief introduction about the technologies used in this AppNote.
Data synchronization provides the foundation for automating business processes. A single data is synchronized between two or more devices automatically in Data Synchronization. As a part of its data synchronization capability, Identity Manager also helps you to synchronize sensitive information like digital certificates & passwords between systems. For example, if a user changes his or her password in Active Directory, Identity Manager can synchronize that password to Lotus Notes and Linux.
Fig 1: Package Selection
Fig 4.1: Authenticate to source server NetWare 6.5 SP7
Fig 4.2: Authenticate to target server 32-bit OES2 SP1 Linux
The Transfer ID scenario runs a series of tasks for transferring the server identity of the source server to the target server. The identity of the server is made up of its IP address, host name, eDirectory identity, NICI keys, and the user certificates from the source server. On successful completion of the Transfer ID migration, the target server functions with the identity of the source server.
Fig 5: Selection of Migration Type "Transfer ID"
Fig 6.1: Click Transfer ID
Fig 6.2: Click "Yes" to proceed
Fig 7.1: eDirectory Precheck. Click "Next" to proceed
Fig 7.2: Preparation. Click "Next" to proceed
Fig 7.3: DIB copy. Click "Next" to proceed (Contd.,)
Fig 7.4: DIB copy. Click "OK" to proceed
Fig 7.5: Shutdown source. Click "OK" to proceed
Fig 7.6: DIB Restore, Click "Next" to proceed
Fig 7.7: IP Address Change, Click "Next" to proceed
Fig 7.8: IP Address change warning message. Click "OK" to proceed
Fig 7.9: Host Name Change , Click "Next" to proceed
Fig 7.10: Reinitialize Server. Click "Next" to proceed
Fig 7.11: Server Repair. Click "Next" to proceed
Fig 7.12: Restart Server. Click Close
After reboot, target Linux server host name and IP will be seen with IP and host name of source NetWare server. Now the source NetWare server can be decommissioned.
On executing the above steps IDM 3.5.1 is migrated from NetWare 6.5 SP7 to OES2 SP1 with the sensitive data like passwords, digital certificates, eDirectory schema, Identity Manager 3.5.1 driver set configuration files and related data. To make the Identity Manager 3.5.1 up and running on 32-bit OES2 SP1, you need to install IDM 3.5.1 packages on target machine i.e OES2 SP1 Linux server. Follow the steps to install IDM 3.5.1 on the target machine:
Fig 8: Start the driver using iManager on OES2 SP1.
This AppNote helps the customer to migrate the Identity Manager 3.5.1 configuration and related data from NetWare 6.5 SP7 to 32-bit Linux OES 2SP1. The migration process also migrates Identity Manager license files from NetWare to OES2 SP1 Linux server.