The following sections provide steps for using Designer to create and configure a new SAP User Management driver. For information about using iManager to accomplish these tasks, see Section 7.2, Using iManager to Create and Configure the Driver.
Importing the SAP User Management driver configuration file creates the driver in the Identity Vault and adds the policies needed to make the driver work properly.
In Designer, open your project.
In the Modeler, right-click the driver set where you want to create the driver, then select
to display the Driver Configuration Wizard.In the
list, select , then click .On the Import Information Requested page, fill in the following fields:
Driver name: Specify a unique name for the driver in this driver set.
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.
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.
SAP User Client Number: Specify the client number on the SAP Application Server. This the
field in the SAP logon screen.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.
Publisher IDoc Directory: Specify the file system location where the SAP User IDoc files are placed by the SAP ALE system (for a file port) or by the driver (for a TRFC port).
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.
Use User Account Entitlement: Select Section 8.0, Implementing the Preconfigured Entitlements.
if you have entitlements enabled in your environment. Select if entitlements are not enabled. The SAP User Management driver contains preconfigured entitlements. For more information, seeEnable Account Tracking: Select Identity Manager 3.6.1 Driver for Sentinel 6.1 and the Identity Vault Collector Implementation Guide.
to enable Account Tracking, which is a feature of the Novell® Compliance Management Platform. For more information, seeEnable Role Mapping: Select Identity Manager Role Mapping Administrator 1.0 Installation and Configuration Guide.
to enable the driver to work with the Role Mapping Administrator. For more information, seeUser Container: Specify the container where the users are stored. Use the slash format. The driver wizard automatically converts the DN in the dot format to the slash format.
If you are using a flat placement rule, this is the container where the users are place. If you are using a mirrored placement rule, this is the root container.
Driver is Local/Remote: Select whether the driver is running locally or is using the Remote Loader. For more information, see the Identity Manager 3.6.1 Remote Loader Guide.
SAP User ID: Specify the ID of the user the driver uses for SAP Logon. This is the
field in the SAP logon screen.SAP User Password: Specify the password the driver users for SAP Logon. This is the
field in the SAP logon screen.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.
Click
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 (if necessary) the driver’s default configuration settings.
To modify the default configuration settings, click Using Designer to Adjust the Driver Settings.
, then continue with the next section,or
To skip the configuration settings at this time, click Using Designer to Adjust the Driver Settings.
. When you are ready to configure the settings, continue with the next section,The information specified on the Import Information Requested page is the minimum information required to import the driver. However, the base configuration might not meet your needs, or you might need to change the configuration you created when you imported the driver.
You might need to change whether the driver is running locally or remotely.
You might need to change whether the driver is using entitlements.
If you need to do additional configuration for the driver, you must access the properties page of the driver. If you do not have the Driver Properties page displayed:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.This opens the properties page for the driver. Use the information in Section A.0, Driver Properties to adjust the configuration.
Continue with Section 7.1.3, Using Designer to Deploy the Driver, to deploy the driver into the Identity Vault.
After a driver is created in Designer, it must be deployed into the Identity Vault, because Designer is an offline tool.
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.If you are authenticated to the Identity Vault, skip to Step 5; otherwise, specify the following information to authenticate:
Host: Specify the IP address of 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.
Click
.Read through the deployment summary, then click
.Read the successful message, then click
.Click
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.
Click
, then browse to and select the object with the correct rights.Click
twice.Click
to exclude users that should not be synchronized.You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.
Click
.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 after the driver is deployed:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.For information about management tasks with the driver, see Section 9.0, Managing the Driver.