27.3 Copying Server-specific Information for the Driver Set

You must copy all server-specific information that is stored in each driver and driver set to the new server’s information. This also includes GCVs and other data on the driver set that will not be there on the new server and need to be copied. The server-specific information is contained in:

  • Global configuration values

  • Engine control values

  • Named passwords

  • Driver authentication information

  • Driver startup options

  • Driver parameters

  • Driver set data

You can do this in Designer or iManager. If you use Designer, it is an automated process. If you use iManager, it is a manual process. If you are migrating from an Identity Manager server earlier than 3.5 version to an Identity Manager server greater than or equal to 3.5, you should use iManager. For all other supported migration paths, you can use Designer.

27.3.1 Copying the Server-specific Information in Designer

This procedure affects all drivers stored in the driver set.

  1. In Designer, open your project.

  2. In the Outline tab, right-click the server, then select Migrate.

  3. Read the overview to see what items are migrated to the new server, then click Next.

  4. Select the target server from the list available servers, then click Next.

    The only servers listed are servers that are not currently associated with a driver set and are equal to or newer than the source server’s Identity Manager version.

  5. Select one of the following options:

    • Make the target server active: Copies the settings from the source server to the target server and disables the drivers on the source server. NetIQ recommends using this option.

    • Keep the source server active: Does not copy the settings and disables all drivers on the target server.

    • Makes both target and source servers active: Copies settings from the source server to the target server without disabling the drivers on the source or target servers. This option is not recommended. If both drivers are started, the same information is written to two different queues and this can cause corruption.

  6. Click Migrate.

  7. Deploy the changed drivers to the Identity Vault.

    For more information, see Deploying a Driver to an Identity Vault in the NetIQ Designer for Identity Manager Administration Guide.

  8. Start the drivers.

    For more information, see Stopping, Starting, or Restarting a Driver in Designer in the NetIQ Identity Manager Driver Administration Guide.

27.3.2 Changing the Server-specific Information in iManager

  1. In iManager, click to display the Identity Manager Administration page.

  2. Click Identity Manager Overview.

  3. Browse to and select the container that holds the driver set.

  4. Click the driver set name to access the Driver Set Overview page.

  5. Click the upper right corner of the driver, then click Stop driver.

  6. Click the upper right corner of the driver, then click Edit properties.

  7. Copy or migrate all server-specific driver parameters, global configuration values, engine control values, named passwords, driver authentication data, and driver startup options that contain the old server’s information to the new server’s information. Global configuration values and other parameters of the driver set, such as max heap size, Java settings, and so on, must have identical values to those of the old server.

  8. Click OK to save all changes.

  9. Click the upper right corner of the driver to start the driver.

  10. Repeat Step 5 through Step 9 for each driver in the driver set.

27.3.3 Changing the Server-specific Information for the User Application

You must reconfigure the User Application to recognize the new server. Run configupdate.bat.

  1. Navigate to the configuration update utility located by default in the installation subdirectory of the User Application.

  2. At a command prompt, launch the configuration update utility (configupdate.bat).

  3. Specify the values as described in Configuring the Settings for the Identity Applications.