This section outlines tasks you need to complete after a local or remote installation.
If you installed the driver on the same NetWare server where the GroupWise agents exist and run, you need to modify the autoexec.ncf file. Open the file and locate the following line:
SEARCH ADD SYS:\GRPWISE\AGENTS
The \GRPWISE\AGENTS directory specifies where the GroupWise agents are installed. Immediately below this line, you should see the following:
PROTECT SYS:\GRPWISE\AGENTS\GRPWISE.NCF
This SYS line might already exist. If it does, do not add it again, but ensure that "PROTECT" proceeds the command.
You should replace \GRPWISE\AGENTS with the path to where the GroupWise agents are installed on your server.
Before you start the driver and use it to synchronize data between eDirectory and GroupWise, you must modify the driver's policies and filters for your specific business rules. See Using Policies and Filters for complete information.
In iManager, click DirXML Management > Overview.
Do one of the following options:
Click the DirXML Driver for GroupWise driver status button, then click Start Driver.
NOTE: It is important not to disable the driver. When a driver is disabled, eDirectory events are not cached for the driver.
After the driver is installed, the driver configuration is imported, and the rules and style sheets have been customized, you should test the driver to see that it is working properly. (For more information on customizing rules and style sheets, see Using Policies and Filters.)
Use the following steps to verify that the driver is working properly. When properly installed and configured, the driver synchronizes the changes to GroupWise. Use ConsoleOne with the GroupWise snap-ins to verify that the changes have been synchronized with GroupWise.
To verify the driver is working properly:
In Novell iManager, click DirXML Management > DirXML Overview.
Do one of the following options:
Click the DirXML Driver for GroupWise driver status button > click Start Driver.
Add a new user to eDirectory.
You need to specify only the Name and Surname attributes for this user.
Open ConsoleOne with the GroupWise snap-ins.
Verify that a new GroupWise account was created in the correct post office.
Using Novell iManager, delete the user from eDirectory.
Using ConsoleOne with the GroupWise snap-ins, verify that the GroupWise account is deleted from the post office.
WARNING: If you create eDirectory users with ConsoleOne, be sure to use a ConsoleOne without the GroupWise snap-ins installed. The ConsoleOne snap-ins for GroupWise follows the driver and removes some vital data from eDirectory. This has been fixed in the snap-ins released with GroupWise 6.5.
Under most circumstances, eDirectory and GroupWise already contain information prior to the installation of Identity Manager. The Migrate function in Identity Manager lets you select the users in eDirectory, then perform a migration to GroupWise. You can use the migration function to establish the initial association between eDirectory and the GroupWise driver. The driver does not work properly unless you do this. You should also complete a migrate operation if the driver or driver set name changes.
This migration option in Novell iManager lets you select individual users to migrate from eDirectory into GroupWise. The DirXML engine applies all Matching, Placement, and Creation policies and the filter to the objects that you choose to migrate.
To migrate eDirectory users to GroupWise:
In Novell iManager, click DirXML Management > Overview.
Browse to the driver object to which you will be migrating data.
Click Migrate from eDirectory.
Click Add > select the container or user objects you want to migrate.
Click OK.
When using this functionality, take into consideration any global configuration setting that controls whether or not GroupWise accounts are created for selected users who don't already have an account.