5.2 Creating the Driver Object in Designer

You create the driver by installing the driver packages and then modifying the configuration to suit your environment. After you create and configure the driver object, you need to deploy it to the Identity Vault and start it.

5.2.1 Importing the Current Driver Packages

The driver packages contain the items required to create a driver, such as policies, entitlements, filters, and Schema Mapping policies. These packages are only available in Designer. You can upgrade any package that is installed if there is a newer version of the package available. It is recommended to have the latest packages in the Package Catalog before creating a new driver object. For more information on upgrading packages, see Installing or Upgrading Packages in the NetIQ Designer for Identity Manager Administration Guide.

To verify that you have the most recent version of the driver packages in the Package Catalog:

  1. Open Designer.

  2. In the toolbar, click Help > Check for Package Updates.

  3. Click OK to update the packages

    or

    Click OK if the packages are up-to-date.

  4. In the Outline view, right-click the Package Catalog.

  5. Click Import Package.

  6. Select any SAP User Management driver packages

    or

    Click Select All to import all of the packages displayed.

    By default, only the base packages are displayed. Deselect Show Base Packages Only to display all packages.

  7. Click OK to import the selected packages, then click OK in the successfully imported packages message.

  8. After the current packages are imported, continue with Installing the Driver Packages.

5.2.2 Installing the Driver Packages

After you have imported the current driver packages into the Package Catalog, you can install the driver packages to create a new driver.

  1. In Designer, open your project.

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

  3. Select SAP User Management Base, then click Next.

  4. Select the optional features to install for the SAP User Management driver. All options are selected by default.

    Default Configuration: These packages contain the default configuration information for the SAP User Management driver. This is a mandatory package.

    Fanout and Entitlement Support: These packages contain the policies and entitlements required to enable the driver for fan-out configuration. If you are using the fan-out configuration, you should be using the NetIQ Identity Manager Driver for SAP User Management Fan-Out Implementation Guide.

    Password Synchronization: These packages contain the policies required to enable password synchronization. Leave this option selected if you want to synchronize passwords to the SAP system.

    Data Collection: These packages contain the policies that enable the driver to collect data for reports. If you are using Identity Reporting, verify that this option is selected. For more information, see the NetIQ Identity Reporting: User’s Guide to Running Reports.

    Account Tracking: This group of packages contain the policies that enables account tracking information for reports. If you are using Identity Reporting, verify that this option is selected. For more information, see the NetIQ Identity Reporting: User’s Guide to Running Reports.

    Sample Configuration: This package contains a single sample policy, which adds a user license to a user on an add event and renames a user on a rename event. This option is selected by default.

  5. After selecting the optional packages, click Next.

  6. (Conditional) If there are package dependencies for the packages you selected to install, you must install these dependencies to install the selected packages. Click OK to install the Password Synchronization Notification package dependency.

  7. (Conditional) Click OK to install the Common Settings package, if you have not installed any other packages into the selected driver set.

  8. Click OK to install the Advanced Java Class package if you have not installed any other packages into the selected driver set.

  9. (Conditional) Fill in the following fields on the Common Settings page, then click Next:

    The Common Settings page is displayed only if the Common Settings package is installed as a dependency.

    User Container: Select the Identity Vault container where the users are added if they don’t already existing in the Identity Vault. This value becomes the default value for all drivers in the driver set.

    If you want a unique location for this driver, set the value for all drivers on this page. After the driver is created, change the value on the driver’s Global Configuration Values page.

    Group Container: Select the Identity Vault container the groups are added if they don’t already exist in the Identity Vault. This value becomes the default value for all drivers in the driver set.

    If you want a unique location for this driver, set the value for all drivers on this page. After the driver is created, change the value on the driver’s Global Configuration Values page.

  10. On the Driver Information page, specify a name for the driver, then click Next.

  11. Fill in the following fields to configure the driver, then click Next:

    Authentication > SAP User ID: Specify the ID of the user the driver uses for SAP Logon. This is the User field in the SAP logon screen.

    Authentication > SAP User Password: Specify the password the driver uses for SAP Logon. This is the Password field in the SAP logon screen.

    Authentication > SAP Application Server: Specify the hostname or IP address of the appropriate SAP Application Server. In the SAP logon properties, it is referred to as the Application Server.

    Connection Type: Specify the connection that this driver will use. The options are MSGServer and APPServer. By default, APPServer is selected. This allows the driver to directly connect to the SAP application server.

    MSGServer allows the driver to use the load balancing feature of SAP.

    Connection > SAP System Number: This option is displayed only if you select APPServer as the connection type.

    Specify the SAP system number of the SAP application server. This is referred to as the System Number in the SAP logon properties. The default value is 00.

    Connection > Logon Group: This option is displayed only if you select MSGServer as the connection type. Specify the logon group to which your application server instance is assigned. The assignment can be found using SMLG transaction.

    Connection > System ID: Specify the SAP system ID of the SAP Application Server. The system ID is found in the SAP GUI status bar in the lower right corner of the main window.

    Connection > SAP System Number: Specify the SAP system ID of the SAP Application Server. This is the System Number in the SAP logon properties. The default value is 00.

    Connection > SAP User Client Number: Specify the client number on the SAP Application Server. This the Client field in the SAP logon screen.

    Connection > Logical System Name: If this is a central client, specify the name of the logical system as it is configured in SAP. If this is not a central client, specify a unique name for the logical system.

    Miscellaneous Settings > Default Reset Password: Specify a default password to be set for users when the driver resets a user’s password in the SAP system. It is set during password changes if the user-supplied password is not accepted by the SAP server. This is only used if the driver resets the password.

  12. Fill in the following fields for the Remote Loader information, then click Next:

    Connect To Remote Loader: Select Yes or No to determine if the driver will use the Remote Loader. For more information, see Configuring the Remote Loader and Drivers in the NetIQ Identity Manager Driver Administration Guide.

    If you select No, skip to Step 13. If you select Yes, use the following information to complete the configuration of the Remote Loader:

    Host Name: Specify the IP address or DNS name of the server where the Remote Loader is installed and running.

    Port: Specify the port number for this driver. Each driver connects to the Remote Loader on a separate port. The default value is 8090.

    Remote Loader Password: Specify a password to control access to the Remote Loader. It must be the same password that is specified as the Remote Loader password on the Remote Loader.

    Driver Password: Specify a password for the driver to authenticate to the Identity Manager server. It must be the same password that is specified as the Driver Object Password on the Remote Loader.

  13. (Conditional) Fill in the following fields on the Managed System Information page, then click Next:

    This page is displayed only if you selected to install the Data Collection and Account Tracking groups of packages.

    Name: Specify a descriptive name for this SAP system. The name is displayed in the reports.

    Description: Specify a brief description of this SAP system. The description is displayed in the reports.

    Location: Specify the physical location of this SAP system. The location is displayed in the reports.

    Vendor: Select SAP as the vendor of this system. The vendor information is displayed in the reports.

    Version: Specify the version of this SAP system. The version is displayed in the reports.

  14. (Conditional) Fill in the following fields to define the ownership of this SAP system, then click Next:

    This page is displayed only if you selected to install the Data Collection and Account Tracking groups of packages.

    Business Owner: Select a user object in the Identity Vault that is the business owner of this SAP system. This can only be a user object, not a role, group, or container.

    Application Owner: Select a user object in the Identity Vault that is the application owner for this SAP system. This can only be a user object, not a role, group, or container.

  15. (Conditional) Fill in the following fields to define the classification of the SAP System, then click Next:

    This page is displayed only if you selected to install the Data Collection and Account Tracking groups of packages.

    Classification: Select the classification of the SAP system. This information is displayed in the reports. The options are:

    • Mission-Critical

    • Vital

    • Not-Critical

    • Other

      If you select Other, you must specify a custom classification for the SAP system.

    Environment: Select the type of environment the SAP system provides. The options are:

    • Development

    • Test

    • Staging

    • Production

    • Other

      If you select Other, you must specify a custom classification for the SAP system.

  16. Review the summary of tasks that will be completed to create the driver, then click Finish.

  17. Continue with Configuring the Driver Object.

5.2.3 Configuring the Driver Object

After importing the driver configuration file, you need to configure the driver object before it can run. Complete the following tasks to configure the driver:

  • Ensure that the driver can authenticate to the SAP UM system: Make sure that you have established an SAP User administrative account for the driver (see Creating an SAP User Account) and that the correct authentication information, including the User ID and password, is defined for the driver parameters (see 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 Driver Parameters.

  • Customize the driver policies and filter: Modify the driver policies and filter to implement your business policies. For instructions, see Section 7.0, Customizing the Driver.

  • Configure the driver for use in a Central User Administration Environment: If you want to integrate the driver into a Central User Administration (CUA) environment, see Section 8.0, Using the Driver in a Central User Administration Environment.

Continue with the next section, Deploying the Driver Object.

5.2.4 Deploying the Driver Object

After the driver object 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 4, otherwise, specify the following information, then click OK:

    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. Read the deployment summary, then click Deploy.

  5. Read the message, then click OK.

  6. 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.

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

    2. Click OK twice.

      For more information about defining a Security Equivalent User in objects for drivers in the Identity Vault, see Establishing a Security Equivalent User in the NetIQ Identity Manager Security Guide.

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

    2. Repeat Step 7.a for each object you want to exclude, then click OK.

  8. Click OK.

5.2.5 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. In Designer, open your project.

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

  3. Continue with Activating the Driver.