The following table explains the parameters you must provide during initial driver configuration.
There are options in the driver configuration that add policies to the driver to allow additional functionality. If you are not sure you need these options now, but you might want them in the future, it is better to select them now. After the driver is created, these options are enabled or disabled through global configuration values on the driver. Trying to properly add policy sets from the default driver configuration to an existing driver after is it configured is a complex process.
IMPORTANT:Selecting options during the configuration of the driver parameters does not enable the functionality. After the driver is imported, the global configuration values must be modified to enable the functionality of the selection. See Section 4.5, Modifying Global Configuration Values for more information.
Some parameters are displayed only if the answer to a previous prompt requires more information to properly configure the policy.
Table 4-1 Driver Configuration Parameters
Field |
Description |
---|---|
|
The default value is GroupWise. Specify the name you want for the driver. |
|
There are two options, or .The GroupWise driver uses entitlements to manage user accounts and distribution list membership in GroupWise. Entitlements work in conjunction with external services such as the Identity Manager User Application or Role-Based Entitlements. These external services control provisioning to GroupWise. See IMPORTANT:After the driver is imported, review Section 4.4, Viewing Driver Parameters and Section 4.5, Modifying Global Configuration Values for additional configuration options. |
|
The DN for the default GroupWise Post Office for creating Accounts. The post office can be entered in slash or dot notation. Examples: Novell\GroupWise\PO (slash) PO.GroupWise.Novell (dot) |
|
Select the version of GroupWise you have installed. Options: |
|
Select the server OS where the GroupWise driver is installed and the server OS where the GroupWise domain resides. Depending upon the option that is selected, there are additional fields that are presented. See Table 4-2 for information about each option. Options: |
|
Specify the eDirectory container in which object changes are detected and synchronize. Synchronization occurs for objects below the specified location. Specify the eDirectory tree if you want the entire tree to be monitored. |
|
The GroupWise driver can be configured to synchronize eDirectory Groups to the GroupWise Distribution List objects. Selecting adds a base set of policies to the driver that allows the eDirectory Groups to synchronize to the GroupWise Distribution List objects.IMPORTANT:This feature is not enabled by selecting this option. You must edit the GCVs on the driver after it is imported to enable this feature. See Section 4.5, Modifying Global Configuration Values. |
|
The GroupWise driver can be configured to synchronize GroupWise Distribution List objects from eDirectory to GroupWise. Selecting adds a base set of policies to the driver that allows the GroupWise Distribution List objects to synchronize.IMPORTANT:This feature is not enabled by selecting this option. You must edit the GCVs on the driver after it is imported to enable this feature. See Section 4.5, Modifying Global Configuration Values. |
|
The GroupWise driver can be configured to synchronize GroupWise External Entity objects from eDirectory to an External GroupWise Post Office. Selecting adds a base set of policies to the driver that allows GroupWise External Entity objects to be synchronize from eDirectory to an External GroupWise Post Office.IMPORTANT:This feature is not enabled by selecting this option. You must edit the GCVs on the driver after it is imported to enable this feature. See Section 4.5, Modifying Global Configuration Values. |
|
The GroupWise driver can be configured to synchronize eDirectory Organizational Units to GroupWise External Post Offices. Selecting adds a base set of policies to the driver that allows eDirectory Organizational Units to synchronize to GroupWise External Post Offices.IMPORTANT:This feature is not enabled by selecting this option. You must edit the GCVs on the driver after it is imported to enable this feature. See Section 4.5, Modifying Global Configuration Values. |
|
Configure the driver for use with the Remote Loader service by selecting , or select to configure the driver for local use. |
|
Entitlement option only. When a user is created in eDirectory with a GroupWise account entitlement, select the action you want to occur on the associated GroupWise account: |
|
Entitlements option only. When a user’s GroupWise account entitlement is removed in eDirectory, specify the action you want the driver to take on an associated GroupWise account: |
|
GroupWise External Entity synchronization policies only. To properly configure the Subscriber Placement policy, specify a default Non-GroupWise Domain defined within the GroupWise system which contains the External Post Office where the GroupWise External Entities can be created and synchronized. |
|
GroupWise External Entity synchronization policies only. To properly configure the Subscriber Placement policy, specify a default External Post Office defined within GroupWise which is subordinate to the Non-GroupWise Domain name where the GroupWise External Entities can be created and synchronized. |
|
eDirectory Organizational Unit to GroupWise External Post Office synchronization policies only. To properly configure the Subscriber placement policy, specify a Non-GroupWise Domain defined within the GroupWise System where the External Post Offices and users can be created and synchronized. |
|
Remote option only. Specify the host name or IP address and port number where the Remote Loader service is installed. The default port is 8090. |
|
Remote option only. The driver password is used by the Remote Loader service to authenticate it to the Identity Manager server. It must be the same password that is specified as the Driver Object Password on the Identity Manager Remote Loader. |
|
Remote option only. The remote password is used to control access to the Remote Loader instance. It must be the same password that is specified as the Remote Loader password on the Remote Loader service. |
Table 4-2 Optional Fields for Driver and Domain Entry