A.1 Driver Configuration
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:
A.1.1 Driver Module
The driver module changes the driver from running locally to running remotely or the reverse.
Java: 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
Native: This option is not used with the GroupWise driver.
Connect to Remote Loader: Used when the driver is connecting remotely to the connected system. Designer includes two suboptions:
-
Remote Loader Client Configuration for Documentation: Includes information on the Remote Loader client configuration when Designer generates documentation for the driver.
-
Driver Object Password: Specifies a password for the Driver object. If you are using the Remote Loader, you must enter a password on this page. Otherwise, the remote driver does not run. The Remote Loader uses this password to authenticate itself to the remote driver shim.
A.1.2 Driver Object Password
Driver Object Password: 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.
A.1.3 Authentication
The authentication section stores the information required to authenticate to the connected system.
Authentication ID: Specify a user application ID. This ID is used to pass Identity Vault subscription information to the application.
Example: Administrator
Authentication context: This option is not used with the GroupWise driver.
Remote Loader Connection Parameters: 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 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.
Application Password: This option is not used with the GroupWise driver.
NOTE: The application password is not required if the Groupwise driver and the Groupwise server are running on the same system. However, if the Groupwise driver and the Groupwise server are running on separate servers, ensure that the values for authentication ID and application password are specified. In this scenario, the driver running on one server authenticates to the other server (Groupwise server) to access the files system containing the domain folder, hence the windows server account and password are expected to be specified in the driver configuration.
Remote Loader Password: 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.
Cache limit (KB): 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.
A.1.4 Startup Option
The Startup Option section allows you to set the driver state when the Identity Manager server is started.
Auto start: The driver starts every time the Identity Manager server is started.
Manual: The driver does not start when the Identity Manager server is started. The driver must be started through Designer or iManager.
Disabled: 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.
Do not automatically synchronize the driver: 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.
A.1.5 Driver Parameters
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:
Domain Server: 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.
Domain Path: Specify 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:
-
Driver and database on same server:
Windows example: c:\Novell\GroupWise\Domain
Linux example: /Novell/GroupWise/Domain
-
Driver and database on different servers:
Windows example: c$\Novell\GroupWise\Domain
NetWare example: volume\Novell\GroupWise\Domain
These are only examples of path formats. Your actual path will probably be different.
Enforce Admin Lockout Setting: 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.
Create Nicknames: Select if you want the driver to create GroupWise nicknames when GroupWise accounts are renamed or moved to another post office.
Reassign Resource Ownership: Select if you want the driver to reassign ownership of resources when the GroupWise accounts are disabled or expired.
Default Resource Owner User ID: Specify the default user who becomes the new owner of resources that are reassigned.
GroupWise Domain Database Version: Specify the version of the GroupWise Domain database version the driver connects to. The options are:
Cleanup Group Membership: Cleans up Identity Vault Group memberships when removing a user from all GroupWise Distribution Lists. Select or .
Synchronize GroupWise External Entity Objects: Select to synchronize eDirectory’s GroupWise External Entry objects with external users in GroupWise. By default, it is set to .
Publisher Heartbeat Interval: Specifies the Publisher channel heartbeat interval in minutes. Specify 0 to disable the heartbeat.
A.1.6 ECMAScript
Displays an ordered list of ECMAScript resource files. The files contain extension functions for the driver that Identity Manager loads when the driver starts. You can add additional files, remove existing files, or change the order the files are executed.
A.1.7 Global Configurations
Displays an ordered list of Global Configuration objects. The objects contain extension GCV definitions for the driver that Identity Manager loads when the driver is started. You can add or remove the Global Configuration objects, and you can change the order in which the objects are executed.