Novell Documentation: Nsure Identity Manager Drivers

Upgrading on Windows

In this section:

Preparing to Upgrade

Make sure you have reviewed all TIDs and Product Updates for the version of the driver you are using.

The new driver shim is intended to work with your existing driver configuration, but this assumes that your driver shim and configuration have the latest fixes.

Upgrading the Driver Shim and Configuration

When you install Nsure^TM Identity Manager 2, make sure you select the option to install utilities. This installs the movecfg.exe utility necessary for upgrading, noted in ステップ 5. Instructions are in "Installation" in the Novell Nsure Identity Manager 2 Administration Guide.
You can install the upgraded driver shim at the same time you install the DirXML engine, or after. To install the driver shim, run the Identity Manager installation program and select the DirXML Driver for eDirectory. Instructions are in "Installation" in the Novell Nsure Identity Manager 2 Administration Guide.

The new driver shim replaces the previous one.

重要: Running a new driver with a previous version of the DirXML engine is not supported.
Convert your existing configuration from 1.x to 2.0 format, using the wizard.

See "Upgrading a Driver Configuration from DirXML 1.x to Identity Manager Format" in the Novell Nsure Identity Manager 2 Administration Guide.
Unload all instances of ndsrep.exe from the Domino Server Console.
Use the movecfg.exe utility to upgrade the placement of configuration parameters, as described in Using the Movecfg.exe Utility.

You can use a batch file such as the example provided in Example Batch File to Use.

The movecfg.exe utility is installed in the utilities directory if you select the option to install Utilities during DirXML installation.

For example, on Windows:
```
C:\novell\nds\DirXMLUtilities
```
重要: If you have multiple instances of NDSRep, you must run movecfg.exe once for each one, using the -ndsrep parameter.
(Windows only) Copy the following files:
- Manually copy ndsrep.exe from its installed location (\novell\NDS) to the Domino server executable folder (\Lotus\Domino).
- Manually copy dsrepcfg.ntf from its installed location (\novell\NDS) to the Domino server data folder (Lotus\Domino\Data).
  On Linux and Solaris, the package install places it in the /usr/lib/dirxml/rules/notes folder and creates a symbolic link for it in the /local/notesdata folder.
- Manually copy the Notes.jar file from the \Lotus\Domino directory to the \Novell\nds\lib directory (or the \novell\remote\loader\lib directory if running Remote Loader).
注: This is necessary for product updates as well as new releases.
If you have previously modified the Domino server's notes.ini file ServerTasks line to auto-load NDSRep (as described in Loading and Controlling NDSRep), you must add an instance name (by default, the driver name) as a parameter to NDSRep.

For example:
```
ServerTasks=Router,Replica,Update,Amgr,AdminP,maps, 
ndsrep notesdrv1,ndsrep notesdrv2
```
注: If you have multiple instances of NDSRep, you must do this for each one.

If the name of your driver includes spaces, then you must put quotes around the name.

For example, if the driver name is CN=Notes Driver, your notes.ini might look like the following:
```
ServerTasks=Router,Replica,Update,Amgr,AdminP,maps, ndsrep notesdrv1,ndsrep "Notes Driver"
```
Restart NDSRep, or restart the Domino server.
Stop and restart eDirectory and the driver for the system to use the new driver shim file.

At this point, the driver should work even though you have not made changes to the configuration other than converting it to Identity Manager 2 format.
Activate the driver. See Activating the Driver.
If you want to make changes to the driver configuration, such as using named passwords or global configuration values (GCVs) for multiple certifiers, you can do so.

See Customizing the Driver.

注: For an example of the new parameters and new features such as named passwords, review the sample driver configuration.
When your changes are complete, restart the driver.