Identity Synchronization for Windows 6.0 Service Pack 1 Release Notes 11g Release 1 (11.1.1.5.0) Part Number E27423-01 |
|
|
View PDF |
This chapter provides instructions for installing Identity Synchronization for Windows 6.0 Service Pack 1 in a greenfield environment, an environment where no instance of Identity Synchronization for Windows already exists. This chapter contains the following sections:
The LDAP directory used to store the Identity Synchronization for Windows configuration and synchronization data must be created and configured manually before you run the Identity Synchronization for Windows installer.
When creating tthis type of Directory Server instance, observe the following recommendations:
Do not use an existing 5.2x Directory Server o=netscaperoot
for the Identity Synchronization for Windows configuration data store. Create a new Directory Server that includes an instance of Identity Synchronization for Windows and is dedicated to Identity Synchronization for Windows configuration (o=netscaperoot
) and synchronization ( ou=isw_config
) data stores.
For example, create a new ou=isw_config
suffix, and then allow the Identity Synchronization for Windows administration console to create its own o=NetscapeRoot
suffix on the same server during installation. Be sure to create a Top Entry when you create the new ou=isw_config
suffix. When creating the ou=isw_config
suffix using DSCC, on the "Step5 : Choose Data Options" page, choose "Create Top Entry for the suffix. "
There should be no exisisting o=NetscapeRoot
suffix when installing the Identity Synchronization for Windows Java console.
Configure the configuration data store so that the o=netscaperoot
suffix that Identity Synchronization for Windows uses is not replicated with configuration changes from multiple management domains.
The Identity Synchronization for Windows configuration suffix should not reside in a replicated suffix. Use something like ou=isw_config
as a root suffix.
Avoid using anything other than o
or ou
notation for the Identity Synchronization for Windows configuration suffix. Using dc
suffix notation can cause install to fail.
The o=netscaperoot
suffix must not be a parent of the ou=isw_config
suffix.
Use a non-standard root level suffix so it is not a part of user LDAP space.
For detailed steps, see "Creating Directory Sources" in "Chapter 4, Configuring Core Resources" of the Oracle Identity Synchronization for Windows 6.0 Installation and Configuration Guide.
See Section 1.3, "Obtaining the Software as Part of Directory Server Enterprise Edition."
Review the following sections of this document:
After you unzip the distribution file, the ODSEE_Identity_Synchronization_for_Windows
directory should contain the following components:
The Identity Synchronization for Windows 6.0 Service Pack 1 patch
JDK 5.0_u29
Message Queue 4.3
Install JDK 5.0_u29.
Install the packages available under the appropriate jdk
directory.
Launch the .exe
file.
Install Message Queue 4.3.
See Section 2.2, "Installing or Upgrading Sun Java System Message Queue." for detailed information.
Unpack the Identity Synchronization for Windows 6.0 Service Pack 1 binaries.
Change to the patch-id directory that corresponds to your platform and unzip the Identity Synchronization for Windows zip file.
For example:
C:\> cd 144592-01 C:\> unzip.exe isw.6.0.sp1.windows.zip
Install the Identity Synchronization for Windows 6.0 Service Pack 1 Core.
For more information, see Chapter 3, Installing Core, in Oracle Identity Synchronization for Windows 6.0 Installation and Configuration Guide.
Configure the Identity Synchronization for Windows 6.0 Service Pack 1 Core.
For more information, see Chapter 4, Configuring Core Resources, in Oracle Identity Synchronization for Windows 6.0 Installation and Configuration Guide.
Start the Identity Synchronization for Windows services.
Start synchronization.
To confirm that the Identity Synchronization for Windows 6.0 Service Pack 1 installation has been successful, run the following command:
C:\Program Files\Sun\MPS\isw-win2k3-isw\bin\idsync -V
The output should be the same as the following:
common.jar : 6 2009Q1_SP1 (ISW build id:2010.116.1139 built by svbld) connector.jar : 6.0SP1_COMBO_5_20110722 (ISW build id:2011.203.1459 built by pduc) install.jar : 6.0SP1_COMBO_5_20110722 (ISW build id:2011.203.1459 built by pduc) registry.jar : 6.0SP1_COMBO_5_20110722 (ISW build id:2011.203.1459 built by pduc) ui.jar : 6.0SP1_COMBO_5_20110722 (ISW build id:2011.203.1459 built by pduc) watchdog.jar : 6 2009Q1_SP1 (ISW build id:2010.116.1139 built by svbld) manager.jar : 6.0SP1_COMBO_5_20110722 (ISW build id:2011.203.1459 built by pduc) Statu