Before you install and use the driver, you must plan a local or remote installation and define user accounts for GroupWise driver access. The GroupWise driver provisions accounts between the Identity Vault and GroupWise. The driver can connect to a secondary GroupWise domain, but Novell recommends that the GroupWise driver connects to the primary GroupWise domain.
Figure 2-1 Local System Configuration
A local installation installs the driver on the same Windows, Linux*, or NetWare® computer where you installed Identity Manager and eDirectory™. The GroupWise domain database can either be on the same computer or a different computer.
If Identity Manager is installed on one NetWare server and the GroupWise domain database is on another NetWare server, these servers must be installed in the same eDirectory tree.
Table 2-1 Installation Configuration Options
NOTE:NFS or any other type of mounted file system is not supported if the GroupWise driver connects to it. For example, the GroupWise driver running on Linux should not connect to a domain database on another server through a mounted file system; or a domain database on a Linux server should not be accessed by a GroupWise driver running on any other server, regardless of the operating system.
A remote installation installs the driver on a different computer than the one where Identity Manager and eDirectory are installed. Identity Manager and the Identity Vault can run on different platforms than the driver can run on. For example, Option 1 in Figure 2-2 shows that if your Identity Vault and Identity Manager are installed on Solaris*, you would need to install the driver with the Remote Loader on a Linux or Windows system.
GroupWise can be installed on a separate system from where the Metadirectory engine is installed and from where the Remote Loader is installed as long as the Remote Loader runs on Windows as shown in Option 2 for Figure 2-2.
Figure 2-2 Remote System Configuration