4.2 Creating the Driver in Designer

You create the PeopleSoft driver by importing the driver’s basic configuration file and then modifying the configuration to suit your environment. After you’ve created and configured the driver, you need to deploy it to the Identity Vault and start it.

4.2.1 Importing the Driver Configuration File

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver set where you want to create the driver, then select New > Driver to display the Driver Configuration Wizard.

  3. In the Driver Configuration list, select PeopleSoft50, then click Run.

  4. On the Import Information Requested page, fill in the following fields:

    Driver Name: Specify a name that is unique within the driver set.

    Active Users Container: Specify the name of the Organizational Unit object in the Identity Vault where Active users from PeopleSoft are placed. You can modify this parameter through a global configuration value (GCV) after installation.

    Inactive Users Container: Specify the name of the Organizational Unit in the Identity Vault where Inactive users from PeopleSoft are placed.You can modify this parameter through a GCV after installation.

    Active Employee Group Object: Specify the name of the Group object in the Identity Vault to which Active Employee users from PeopleSoft are added. You can modify this parameter through a GCV after installation.

    Active Manager Group Object: Specify the name of the Group object to which Active Manager users from PeopleSoft are added. You can modify this parameter through a GCV after installation.

    Driver is Local/Remote: Select Local if this driver will run on the Metadirectory server without using the Remote Loader service. Select Remote if you want the driver to use the Remote Loader service, either locally on the Metadirectory server or remotely on another server.

    PeopleSoft User ID: Specify an administrative account through which the driver can authenticate to PeopleSoft.

    Connection to PeopleSoft Server: The hostname 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.

    The connection string uses the following format:

    <hostname or IP address>:<Jolt Port Number>

    Example: //PSServer:9000

    To enable failover and load balancing, you can supply multiple server connection strings separated by a comma.

    Example: //PSServer:9000,//111.222.3.4:9000

  5. (Conditional) If you chose to run the driver remotely, click Next, then fill in the fields listed below. Otherwise, skip to Step 6.

    Remote Host Name and Port: Specify the host name or IP address of the server where the driver’s Remote Loader service is running.

    Driver Password: Specify the driver object password that is defined in the Remote Loader service. The Remote Loader requires this password to authenticate to the Metadirectory server.

    Remote Password: Specify the Remote Loader’s password (as defined on the Remote Loader service). The Metadirectory engine (or Remote Loader shim) requires this password to authenticate to the Remote Loader

  6. Click Next to import the driver configuration.

    At this point, the driver is created from the basic configuration file. To ensure that the driver works the way you want it to for your environment, you must review and modify the driver’s default configuration settings.

  7. To review or modify the default configuration settings, click Configure, then continue with the next section, Configuring the Driver.

    or

    To skip the configuration settings at this time, click Close. When you are ready to configure the settings, continue with Configuring the Driver.

4.2.2 Configuring the Driver

After importing the driver configuration file, you need to configure the driver before it can run. You should complete the following tasks to configure the driver:

  • Ensure that the driver can authenticate to PeopleSoft: Make sure that you’ve established a PeopleSoft administrative account for the driver (see Section 4.1, Creating a PeopleSoft Account) and that the correct authentication information, including the User ID and password, is defined for the driver parameters (see Section A.1.3, Authentication).

  • Configure the driver parameters: There are many settings that can help you customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). Although it is important for you to understand all of the settings, your first priority should be to configure the driver parameters located on the Driver Configuration page. For information about the driver parameters, see Section A.1.5, Driver Parameters.

  • Configure the driver policies and filter: Modify the driver policies and filter to implement your business policies. For instructions, seeSection 6.3, Modifying Driver Policies.

  • Configure password synchronization: The basic driver configuration is set up to support password synchronization through Universal Password. If you don’t want this setup, see Configuring Password Flow in the Identity Manager 3.6.1 Password Management Guide.

After completing the configuration tasks, continue with the next section, Deploying the Driver.

4.2.3 Deploying the Driver

After a driver is created in Designer, it must be deployed into the Identity Vault.

  1. In Designer, open your project.

  2. In the Modeler, right-click the driver icon Driver icon or the driver line, then select Live > Deploy.

  3. If you are authenticated to the Identity Vault, skip to Step 5, otherwise, specify the following information:

    • Host: Specify the IP address or DNS name of the server hosting the Identity Vault.

    • Username: Specify the DN of the user object used to authenticate to the Identity Vault.

    • Password: Specify the user’s password.

  4. Click OK.

  5. Read through the deployment summary, then click Deploy.

  6. Read the successful message, then click OK.

  7. Click Define Security Equivalence to assign rights to the driver.

    The driver requires rights to objects within the Identity Vault. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.

    1. Click Add, then browse to and select the object with the correct rights.

    2. Click OK twice.

  8. Click Exclude Administrative Roles to exclude users that should not be synchronized.

    You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.

    1. Click Add, then browse to and select the user object you want to exclude.

    2. Click OK.

    3. Repeat Step 8.a and Step 8.b for each object you want to exclude.

    4. Click OK.

  9. Click OK.

4.2.4 Starting the Driver

When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. Identity Manager is an event-driven system, so after the driver is started, it won’t do anything until an event occurs.

To start the driver:

  1. If you are using the Remote Loader with the driver, make sure the Remote Loader driver instance is running. For instructions, see Starting the Remote Loader in the Identity Manager 3.6.1 Remote Loader Guide.

  2. In Designer, open your project.

  3. In the Modeler, right-click the driver icon Driver icon or the driver line, then select Live > Start Driver.

  4. Continue with Section 4.4, Activating the Driver.