This section talks briefly about importing the PeopleSoft driver through Designer and iManager utilities.
Designer allows you to import the basic driver configuration file for PeopleSoft. This file creates and configures the objects and policies needed to make the driver work properly. The following instructions explain how to create the driver and import the driver’s configuration.
There are many different ways of importing the driver configuration file. This procedure only documents one way.
Open a project in Designer and in the modeler, right-click on the Driver Set object and select
.From the drop-down list, select
, then click .Click
, in the Perform Prompt Validation window. It has you fill in all of the fields to correctly configure the PeopleSoft driver.Configure the driver by filling in the fields. Specify information specific to your environment.
After specifying parameters, click
to import the driver.After the driver is imported, customize and test the driver.
Once the driver is fully tested, deploy
the driver into the Identity Vault. See Deploying
a Driver to an Identity Vault
in the Designer
for Identity Manager 3: Administration Guide.
The Create Driver Wizard helps you import the basic driver configuration file. This file creates and configures the objects and policies needed to make the driver work properly.
The following instructions explain how to create the driver and import the driver’s configuration.
In Novell iManager, click
.Select a driver set, then click
.If you place this driver in a new driver set, you must specify a driver set name, context, and associated server.
Select
, then select .The driver configuration files are installed on the Web server when you install Identity Manager. During the import, you are prompted for the driver’s parameters and other information.
Specify the driver’s parameters, then click
to import the driver.Table 2-1 Driver Configuration Parameters
The additional driver parameters are set to default values during the import process, but they can be modified in iManager (by clicking the Driver Configuration tab on the driver object.)
Table 2-2 Additional Driver Parameters
When the import is finished, you can define security equivalences and exclude administrative roles from replication.
The driver object must be granted sufficient eDirectory rights to any object it reads or writes. You can do this by granting Security Equivalence to the driver object. The driver must have Read/Write access to users, post offices, resources, and distribution lists, and Create, Read, and Write rights to the post office container. Normally, the driver should be given security equal to Admin.
Review the driver objects on the Summary page, and then click
.