Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Directory Server Enterprise Edition Upgrade and Migration Guide 11 g Release 1 (11.1.1.5.0) |
Part I Patching Directory Server Enterprise Edition 7 to 11g Release 1 (11.1.1.5.0)
2. Patching Directory Server Enterprise Edition 7 to Version 11g Release 1 (11.1.1.5.0)
Part II Upgrading Directory Server Enterprise Edition 6 to 11g Release 1 (11.1.1.5.0)
3. Upgrading Directory Server Enterprise Edition 6 to Version 11g Release 1 (11.1.1.5.0)
Part III Migrating Directory Server Enterprise Edition 5.2 to Version 11g Release 1 (11.1.1.5.0)
4. Overview of the Migration Process for Directory Server
5. Automated Migration Using the dsmig Command
6. Migrating Directory Server Manually
7. Migrating a Replicated Topology
8. Architectural Changes in Directory Server Since Version 5.2
9. Migrating Directory Proxy Server
10. Migrating Identity Synchronization for Windows
Before You Migrate Identity Synchronization for Windows
Preparing for Identity Synchronization for Windows Migration
Exporting Version 1.1 Configuration
Inserting Clear-Text Passwords
Sample Export Configuration File
Checking for Undelivered Messages
Forcing Password Changes on Windows NT
Preparing to migrate from version 1.1, and 1.1 SP1, to version 6.0 SP1
Uninstalling Identity Synchronization for Windows
To Uninstall Identity Synchronization for Windows Version 1.1
Installing or Upgrading the Dependent Products
Installing Identity Synchronization for Windows 6.0 SP1
To install the Identity Synchronization for Windows 6.0 SP1 components:
What to Do if the 1.1 Uninstallation Fails
Manually Uninstalling 1.1 Core and Instances from Solaris
To Manually Uninstall Core From a Solaris Machine:
Manually Uninstalling 1.1 Core and Instances from Windows 2000
To uninstall Core from a Windows 2000 machine:
Manually Uninstalling a 1.1 Instance from Windows NT
Multi-Master Replication Deployment
This section provides instructions for migrating a single-host deployment to version Identity Synchronization for Windows 6.0 SP1.
In a single-host deployment, all Identity Synchronization for Windows components are installed on a single host (Windows 2000 Server, Solaris version 8 or 9, or SPARC), as follows:
Directory Server (one instance)
Core (Message Queue, Central Logger, System Manager, and Console)
Directory Server Connector
Directory Server Plug-in
Note - If you are using Solaris as your installation host, then a Windows 2000 machine with Active Directory is required for synchronization purposes only. (No components would be installed on the Windows 2000 machine.)
The following figure illustrates the migration process and serves as a checklist to supplement the migration instructions that follow.
Figure 10-1 Migrating a Single-Host Deployment
Use the following procedure to prepare for migration to version 6.0 SP1.
On Solaris type the following command.
uncompress -c filename | tar xf -
On Windows type the following command or use any archive program for Windows, such as WinZip.
%JAVA_HOME%\bin\jar -xf filename
When the binaries are unpacked, the following subdirectories contain the required migration tools:
|
From the migration directory, execute export11cnf as described in Using the export11cnf Utility.
java -jar export11cnf.jar -D “cn=directory manager” -w - \ -s “dc=example,dc=com” -q - -f export.cfg
Enter a password between the double quotes for each cleartextPassword field in the exported configuration file. For more information, see Inserting Clear-Text Passwords.
From the migration directory, execute checktopics as described in Using the checktopics Utility. The following example shows the execution of the checktopics command.
java -jar checktopics.jar -D “cn=directory manager” -w - \ -s “dc=example,dc=com” -q -Z
Note - Do not stop the Sun ONE Message Queue service.
net stop “Sun One NT ChangeDetector Service”
On Solaris, type the following command.
cd serverRoot/isw-hostname tar cf /var/tmp/connector-state.tar persist etc
On Windows, type the following command.
cd serverRoot\isw-hostname zip -r C:\WINNT\Temp\connector-state.zip persist etc %JAVA_HOME%\bin\jar -cfM %TEMP%\connector-state.jar persist etc
Alternatively, use any archive program for Windows, such as WinZip.
Note - The Identity Synchronization for Windows 1.1 uninstall program removes the SUNWjss package if it is not registered for use by another application. In particular, this situation may occur on a Solaris machine if you installed a zip version of Directory Server 5.2, where the uninstall program removes the jss3.jar file from /usr/share/lib/mps/secv1.
If you encounter this situation as you migrate to Identity Synchronization for Windows 6.0 SP1, the installer reports that a required file is missing, and logs the file name to the installation log. When this happens, you must reinstall the required patches and restart the installation process. For a list of required patches, see (see Software Dependency Requirements in Oracle Directory Server Enterprise Edition Release Notes.
Execute the following steps on each Directory Server where the plug-in was installed:
cn=config,cn=pswsync,cn=plugins,cn=configcn=pswsync,cn=plugins,cn=config
For example:
ldapdelete -D “cn=directory manager” -w - -p <port> \ -c cn=config,\ cn=pswsync,cn=plugins,cn=configcn=pswsync,cn=plugins,cn=config
Note - You must uninstall Connectors before uninstalling Core components.
The location of the file is as follows:
On Solaris: /var/sadm/install/productregistry
On Windows: C:\WINNT\System32\productregistry
To remove the Identity Synchronization for Windows related entries from the product registry file, follow the instructions provided in Manually Uninstalling 1.1 Core and Instances from Solaris.
Note - If the uninstall fails, you might have to manually uninstall the Identity Synchronization for Windows components. Instructions are provided in What to Do if the 1.1 Uninstallation Fails
net stop “Sun ONE Identity Synchronization for Windows”
If this service continues running after uninstallation, it causes a sharing violation that prevents you from deleting the instance directory.
Use the following steps to upgrade the Java Run Environment, install Message Queue, and upgrade Directory Server.
Upgrade the Java 2 Runtime Environment (or Java 2 SDK) on each host (except on Windows NT) where Identity Synchronization for Windows components are installed. The minimum required version is 1.5.0.
Java 2 SDK: http://java.sun.com/j2se/1.5.0/install.html
Java 2 Runtime Environment: http://java.sun.com/j2se/1.5.0/jre/install.html
Install Message Queue 3.6 by using the instructions provided in Sun Java System Message Queue 3.6 Installation Guide.
Upgrade Directory Server to version 11g Release 1 (11.1.1.5.0). For more information, see Chapter 4, Overview of the Migration Process for Directory Server.
Note - To keep the Administration Server intact, use the -N option while migrating Directory Server (configuration and data) to version 11g Release 1 (11.1.1.5.0). For more information on migrating configuration data and user data, see Using dsmig to Migrate Configuration Data and Using dsmig to Migrate User Data respectively.
The Directory Server upgrade preserves your current Directory Server configuration and database.
Use the following steps to install the Identity Synchronization for Windows 6.0 SP1 components.
On Solaris type the following commands.
cd /opt/SUNWisw/bin idsync prepds arguments\
On Windows type the following commands.
cd serverRoot\isw-hostname\bin idsync prepds arguments\
For more information about idsync prepds, see Appendix A, Using the Identity Synchronization for Windows Command Line Utilities, in Oracle Identity Synchronization for Windows 6.0 Installation and Configuration Guide.
idsync importcnf arguments\
Note - If the program detects errors in your input configuration file, an error results. Identity Synchronization for Windows aborts the importcnf process and provides the necessary information to correct errors.
For more information about using idsync importcnf , see Using importcnf in Oracle Identity Synchronization for Windows 6.0 Installation and Configuration Guide
net stop “Sun Java(TM) System NT Change Detector”
HighestChangeNumber
LastProcessedSecLogRecordNumber
LastProcessedSecLogTimeStamp
QueueSize
net start “Sun Java(TM) System NT Change Detector”
On Solaris, type the following command.
cd /var/opt/SUNWisw rm -rf etc persisttar xf /var/tmp/connector-state.tar
On Windows, type the following command.
cd serverRoot\isw-hostname rd /s etc persist%JAVA_HOME%\bin\jar -xf %TEMP%\ connector-state.jar
Alternatively, use any archive program for Windows, such as WinZip.
Note - If you have customized the version 1.1 log settings, you must manually apply those customizations to your version Identity Synchronization for Windows 6.0 SP1 installation. Use the Identity Synchronization for Windows Console to configure your log settings.