Novell Doc: Identity Manager Driver 3.7 for PeopleSoft Implementation Guide

2.3 Importing the PeopleSoft Driver

This section talks briefly about importing the PeopleSoft driver through Designer and iManager utilities.

2.3.1 Importing the Driver Configuration File in Designer

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 the Driver Set object, then select New > Driver.
From the drop-down list in the Driver Configuration Wizard, select PeopleSoft36-IDM3_0_1-V1.xml.
Select the Perform required prompt checking check box.
Click Run.
Configure the driver by filling in the fields. Specify information for your environment.
After specifying parameters, click OK to import the driver.
After the driver is imported, customize and test the driver.
After the driver is fully tested, deploy the driver into the Identity Vault. See Deploying and Exporting in the Designer 2.1 for Identity Manager 3.5.1 .

2.3.2 Importing the Driver Configuration in iManager

The Create Driver Wizard helps you import the basic driver configuration file, which 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 Identity Manager Utilities > New Driver.
Select a driver set, then click Next.

If you place this driver in a new driver set, you must specify a driver set name, context, and associated server.
Select Import a configuration from the server (.XML file), then select PeopleSoft36-IDM3_5_0-V1.xml.

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 OK to import the driver. See Table 2-1 for a list of parameters you can set.

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, then click Finish.

Table 2-1 Driver Configuration Parameters

Parameter	Description
Driver name	The actual name you want to use for the driver.
Active Users Container	The name of the Organizational Unit object where Active users are placed. You can modify this option through the driver’s global configuration variable (GCV).
Inactive Users Container	The name of the Organizational Unit where Inactive users are placed. You can modify this option through the driver’s GCV.
Active Employees Group	The name of the Group object to which Active Employee users are added. You can modify this option through the driver’s GCV.
Active Managers Group	The name of the Group object to which Active Manager users are added. You can modify this option through the driver’s GCV.
Event Server Host Name and Port	The host name or IP address and port number of the computer where the Event Server that connects to PeopleSoft is running. The default port is 16500.
PeopleSoft Connection String	The host name or IP address and port number for connecting to the appropriate PeopleSoft Application server. This is typically referred to as the PeopleSoft application server connection string. The default port is 9000.
PeopleSoft User ID	The PeopleSoft User ID the driver uses for PeopleSoft authentication.
PeopleSoft User Password	The PeopleSoft User password this driver uses for PeopleSoft authentication.
Password Failure Notification User	Password synchronization policies are configured to send e-mail notifications to the associated user when password updates fail. You have the option of sending a copy of the notification e-mail to another user, such as a security administrator. If you want to send a copy, specify the DN of that user. Otherwise, leave this field blank.
Driver is Remote/Local	Configure the driver for use with the Remote Loader service by selecting the Remote option, or select Local to configure the driver for local use. If Local is selected, you can skip the remaining parameters.
Remote Host Name and Port	Specify the hostname or IP address and port number where the Remote Loader service has been installed and is running for this driver. The default port is 8090.
Driver Password	The driver object password is used by the Remote Loader to authenticate itself to the Metadirectory server. It must be the same password that is specified as the driver object password on the Remote Loader.
Remote Password	The Remote Loader 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.

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

Parameter	Description
Event Server Host Name	The host name or IP address of the Event Server that connects to where PeopleSoft is running.
Event Server Port Number	The IP port number on which the driver Event Server component listens for connection from the driver shim.
Data Record ID Field	The name of the field in the Data Schema CI that uniquely identifies a PeopleSoft object. The value in this field uniquely identifies a PeopleSoft object. The value in this field is used as the DirXML® object association identifier. The default field name is DIRXML_ASSOC_ID.
eDirectory Object Class Name	The eDirectory™ object Class to which the Data Record definition maps. The default value is User.
Schema Data Subscriber Activity	The name of the PeopleSoft Activity object that defines the data that can be synchronized from the Identity Vault to the PeopleSoft application. The default Subscriber Activity is DIRXML_SCHEMA01_UPDATE. The Message Definition within this Activity must match the name of the Activity.
Schema Data Query Activity	The name of the PeopleSoft Activity object that defines the data that the driver reads from the PeopleSoft application. This data is usually the subset of application data elements contained within the Schema Data Publisher Activity. The default Query Activity is DIRXML_SCHEMA01_QUERY. The Message Definition within this Activity must match the name of the Activity.
Queue Poll Interval (seconds)	The number of seconds the driver waits between attempts to process transaction records. This poll interval is only applied when no transactions are available for processing.The default poll interval is 5 seconds.
Queue Retrieval Limit	This parameter specifies how many transactions are retrieved by the driver from the PeopleSoft worklist queue each time the driver accesses the Transaction Access Activity. The default value is 5.
Transaction Access Activity	The name of the PeopleSoft Activity object that defines the set of fields required for the DirXML Transaction interface. The set of fields in the specified transaction activity must contain the same fields and keys identified in the default transaction activity in order for the driver to work. The default Transaction Activity is DIRXML_TRANS01. The Message Definition within this Activity must match the name of the Activity.
Schema Data Publisher Activity	The name of the PeopleSoft Activity object that defines the set of data to be synchronized from the PeopleSoft application to the Identity Vault. The default Publisher Activity is DIRXML_SCHEMA01. You should ensure that the Message Definition within this Activity matches the name of the Activity. NOTE:Additional transaction control key fields (field names are all capitalized) contained within the Message Definition are used for processing purposes only and are not synchronized.