|Oracle® Identity Manager Connector Guide for SAP CUA
Oracle Identity Manager automates access rights management, security, and provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications. This guide discusses the procedure to deploy the connector that is used to integrate Oracle Identity Manager with SAP CUA.
Note:Oracle Identity Manager connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.
This chapter contains the following sections:
Note:In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.
At some places in this guide, SAP CUA has been referred to as the target system.
Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. It is an automated process initiated by a scheduled task that you configure.
See Also:The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about reconciliation configurations
Based on the type of data reconciled from the target system, reconciliation can be divided into the following types:
The following fields of SAP CUA are reconciled:
The following lookup fields are not reconciled:
This section discusses elements that are specific to user reconciliation between SAP CUA and Oracle Identity Manager.
The following fields are reconciled:
If trusted source reconciliation is implemented, then the following fields are reconciled:
Provisioning involves creating or modifying a user's account on the target system through Oracle Identity Manager. You use the Oracle Identity Manager Administrative and User Console to perform provisioning operations.
See Also:The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about provisioning
For this target system, the following fields are provisioned:
The following fields are mandatory for the Create User provisioning function to work:
Note:To ensure that provisioning is completed successfully, you must specify either the role or profile in the field provided in the process form and then specify whether it is a role or profile. This is to activate the user on the SAP CUA master system.
User Role or Profile
Role or Profile Option
The following table lists the functions that are available with this connector.
|Create User||Provisioning||Creates a user in SAP CUA|
|Delete User||Provisioning||Deletes a user from SAP CUA|
|Lock User||Provisioning||Locks a user in SAP CUA|
|Unlock User||Provisioning||Unlocks a user in SAP CUA|
|Reset User Password||Provisioning||Resets a user password in SAP CUA|
|Edit User||Provisioning||Modifies information about a user in SAP CUA|
|Add User to Activity Group (Role)||Provisioning||Adds a user to an activity group in SAP CUA|
|Remove User from Activity Group (Role)||Provisioning||Removes a user from an activity group in SAP CUA|
|Assign Profile to User||Provisioning||Adds a profile to a user in SAP CUA|
|Remove Profile from User||Provisioning||Removes a profile from a user in SAP CUA|
|Create User||Reconciliation||Creates a user in Oracle Identity Manager|
|Delete User||Reconciliation||Deletes a user from Oracle Identity Manager|
|Lock User||Reconciliation||Locks a user in Oracle Identity Manager|
|Unlock User||Reconciliation||Unlocks a user in Oracle Identity Manager|
|Edit User||Reconciliation||Modifies information about a user in Oracle Identity Manager|
|Add User to Activity Group (Role)||Reconciliation||Assigns an activity group to a user in Oracle Identity Manager|
|Remove User from Activity Group (Role)||Reconciliation||Removes an activity group from a user in Oracle Identity Manager|
|Add Profile to User||Reconciliation||Assigns a profile to a user in Oracle Identity Manager|
|Remove Profile from User||Reconciliation||Removes a profile from a user in Oracle Identity Manager|
See Also:Appendix A for information about attribute mappings between Oracle Identity Manager and SAP CUA
This release of the connector supports the following languages:
See Also:Oracle Identity Manager Globalization Guide for information about supported special characters
The files and directories on the installation media are listed and described in Table 1-1.
|File in the Installation Media Directory||Description|
This XML file contains configuration information that is used during connector installation.
This file is extracted and the components are deployed on the SAP CUA server for the connector to work with SAP CUA.
This JAR file contains the class files that are required for provisioning. During connector deployment, this file is copied into the following directory:
This JAR file contains the class files that are required for reconciliation. During connector deployment, this file is copied into the following directory:
Files in the
Each of these resource bundle files contains language-specific information that is used by the connector. During connector deployment, this file is copied into the following directory:
Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the Administrative and User Console. These text strings include GUI element labels and messages.
This utility is used to test connector functionality.
This file is used to specify the parameters and settings required to connect to the target system by using the testing utility.
This file is used to specify the log level and the directory in which the log file is to be created when you run the testing utility.
This XML file contains definitions for the following components of the connector:
This XML file contains the configuration for the Xellerate User (OIM User). You must import this file only if you plan to use the connector in trusted source reconciliation mode.
Note:The files in the
testdirectory are used only to run tests on the connector.
You might have a deployment of an earlier release of the connector. While deploying the latest release, you might want to know the release number of the earlier release. To determine the release number of the connector that has already been deployed:
In a temporary directory, extract the contents of the following JAR file:
manifest.mf file in a text editor. The
manifest.mf file is one of the files bundled inside the
manifest.mf file, the release number of the connector is displayed as the value of the Version property.