In iManager:
Click to display the Identity Manager Administration page.
Open the driver set that contains the driver whose properties you want to edit:
In the
list, click .If the driver set is not listed on the
tab, use the field to search for and display the driver set.Click the driver set to open the Driver Set Overview page.
Locate the driver icon, then click the upper right corner of the driver icon to display the
menu.Click
to display the driver’s properties page.By default, the Driver Configuration page is displayed.
In Designer:
Open a project in the Modeler.
Right-click the driver icon or line, then select click
The Driver Configuration options are divided into the following sections:
The driver module changes the driver from running locally to running remotely or the reverse.
Table A-1 Driver Modules
Option |
Description |
---|---|
|
Used to specify the name of the Java class that is instantiated for the shim component of the driver. This class can be located in the classes directory as a class file, or in the lib directory as a .jar file. If this option is selected, the driver is running locally. The name of the driver’s Java class is: com.novell.gw.dirxml.driver.gw.GWdriverShim |
|
This option is not used with the GroupWise driver. |
|
Used when the driver is connecting remotely to the connected system. Designer includes two suboptions:
|
Table A-2 Driver Object Password
Option |
Description |
---|---|
|
Use this option to set a password for the driver object. If you are using the Remote Loader, you must enter a password on this page or the remote driver does not run. This password is used by the Remote Loader to authenticate itself to the remote driver shim. |
The authentication section stores the information required to authenticate to the connected system.
Table A-3 Authentication Parameters
Option |
Description |
---|---|
or
|
Specify a user application ID. This ID is used to pass Identity Vault subscription information to the application. Example: Administrator |
or
|
This option is not used with the GroupWise driver. |
or
Port
|
Used only if the driver is using the Remote Loader. The parameter to enter is hostname=xxx.xxx.xxx.xxx port=xxxx kmo=certificatename, when the host name is the IP address of the the Remote Loader server and the port is the port the Remote Loader is listening on. The default port for the Remote Loader is 8090. The kmo entry is optional. It is only used when there is an SSL connection between the Remote Loader and the Metadirectory engine. Example: hostname=10.0.0.1 port=8090 kmo=IDMCertificate |
) or
|
Specify the maximum event cache file size (in KB). If it is set to zero, the file size is unlimited. Click to set the file size to unlimited in Designer. |
or
|
Specify the password of the user listed in the Username field. The same username and password must also be configured on both the servers containing the GroupWise driver and the GroupWise primary domain. |
or
|
Used only if the driver is using the Remote Loader. The password is used to control access to the Remote Loader instance. It must be the same password specified during the configuration of the Remote Loader on the connected system. |
The Startup Option section allows you to set the driver state when the Identity Manager server is started.
Table A-4 Startup Options
Option |
Description |
---|---|
|
The driver starts every time the Identity Manager server is started. |
|
The driver does not start when the Identity Manager server is started. The driver must be started through Designer or iManager. |
|
The driver has a cache file that stores all of the events. When the driver is set to Disabled, this file is deleted and no new events are stored in the file until the driver state is changed to Manual or Auto Start. |
|
This option only applies if the driver is deployed and was previously disabled. If this is not selected, the driver re-synchronizes the next time it is started. |
The Driver Parameters section lets you configure the driver-specific parameters. When you change driver parameters, you tune driver behavior to align with your network environment.
The parameters are presented by category:
Table A-5 Driver Settings
Option |
Description |
---|---|
|
Specify the name or IP address of the server where the GroupWise domain database (wpdomain.db) resides. Using the primary domain database is recommended. Leave this field blank when the GroupWise domain database is on the same physical server as this driver. You can use the hostname, DNS name, or IP address of the server. |
|
Enter the path to the directory containing the GroupWise domain database (wpdomain.db). Using the primary domain database is recommended. The domain path format is different, depending upon where the driver is located relative to the domain database:
These are only examples of path formats. Your actual path will probably be different. |
|
Enforces the Minimum Snap-in Release Version and the Minimum Snap-in Release Date set in the tab of System Preferences in ConsoleOne. If the domain to which the driver connects has overridden these settings, the domain settings are used. This means that the GroupWise driver must be running with GroupWise support files equal to or later than these settings. Select to enable this lockout setting, or select to disable this lockout setting. |
|
Select if you want the driver to create GroupWise nicknames when GroupWise accounts are renamed or moved to another post office. |
|
Select if you want the driver to reassign ownership of resources when the GroupWise accounts are disabled or expired. |
|
Specify the default user who becomes the new owner of resources that are reassigned. |
|
Specify the version of the GroupWise Domain database version the driver connects to. The options are: |
|
Cleans up Identity Vault Group memberships when removing a user from all GroupWise Distribution Lists. Select or . |
Table A-6 Publisher Settings
Option |
Description |
---|---|
|
Specifies the Publisher channel heartbeat interval in minutes. Specify 0 to disable the heartbeat. |
Table A-7 Supported Combinations of GroupWise Driver and GroupWise Domain
Setup |
Fields Needed |
Description |
---|---|---|
GroupWise driver shim is on Linux, the GroupWise primary domain is on the same Linux server as the driver. |
|
The path to the directory containing the GroupWise primary domain database (wpdomain.db). Example: /novell/groupwise/domain |
GroupWise driver shim is on a Windows server, the GroupWise primary domain is on the same Windows server as the driver. |
|
The path to the directory containing the GroupWise primary domain database (wpdomain.db). Example: c:\Novell\GroupWise\Domain |
GroupWise driver shim is on a Windows server, the GroupWise primary domain is on a different Windows server from the driver. |
|
The name or address of the server containing the GroupWise primary domain database (wpdomain.db). Example: hostname - the name of the remote Windows server. or hostname.com - the DNS name of the remote Windows server. or ###.###.###.### - the IP address of the remote Windows server. |
|
|
The path to the directory containing the GroupWise primary domain database (wpdomain.db). Example: c$\Novell\GroupWise\Domain |
|
|
The user name this driver uses to authenticate to the remote Windows server that contains the GroupWise domain database. It must be the name of a user account on the remote Windows server. The same username and password must also be configured on both Windows servers. |
|
|
The password of the user specified above. |
IMPORTANT:The GroupWise driver cannot find the GroupWise primary domain database if values are entered for the Table A-7 for more information).
and the fields when they are not needed (see