Oracle® Identity Manager Connector Guide for SAP User Management Release 9.0.2 Part Number B32173-01 |
|
|
View PDF |
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. The connector for SAP User Management is used to integrate Oracle Identity Manager with SAP User Management.
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:
The following table lists the functions that are available with this connector.
Function | Type | Description |
---|---|---|
Create User | Provisioning | Creates a user in SAP User Management |
Update User | Provisioning | Updates a user in SAP User Management |
Delete User | Provisioning | Deletes a user from SAP User Management |
Lock User | Provisioning | Locks a user in SAP User Management |
UnLock User | Provisioning | Unlocks a user in SAP User Management |
Add User Role | Provisioning | Adds a role to a user in SAP User Management |
Add User Profile | Provisioning | Adds a profile to a user in SAP User Management |
Remove User Role | Provisioning | Removes the role of a user in SAP User Management |
Remove User Profile | Provisioning | Removes the profile of a user in SAP User Management |
List Roles of User | Provisioning | Lists the roles of a user in SAP User Management |
List Profiles of User | Provisioning | Lists the profiles of a user in SAP User Management |
List All Roles | Provisioning | Lists all the roles present in SAP User Management |
List All Profiles | Provisioning | Lists all the profiles present in SAP User Management |
Reconciliation Insert Received | Reconciliation | Creates a user in Oracle Identity Manager if a user is created in SAP User Management |
Reconciliation Update Received | Reconciliation | Updates a user in Oracle Identity Manager if a user is updated in SAP User Management |
Reconciliation Delete Received | Reconciliation | Deletes a user from Oracle Identity Manager if a user is deleted from SAP User Management |
See Also: Appendix A for information about attribute mappings between Oracle Identity Manager and SAP User Management. |
In addition to English, this release of the connector supports the following languages:
French
Japanese
This section discusses the elements that are extracted from the target system by the reconciliation module for constructing reconciliation event records. The following are features of the reconciliation module:
The default data elements of each reconciliation event record are Organization, Xellerate Type, and Role.
The default labels for the data elements in each reconciliation event record are as follows:
Event Linked (for successful reconciliation)
No Match Found (for failed reconciliation)
The following lookup fields are reconciled:
Lookup.SAP.R3.Roles
Lookup.SAP.R3.TimeZone
Lookup.SAP.R3.LangComm
Lookup.SAP.R3.UserTitle
Lookup.SAP.R3.DecimalNotation
Lookup.SAP.R3.DateFormat
Lookup.SAP.R3.UserGroups
Lookup.SAP.R3.CommType
Lookup.SAP.R3.Profiles
The following lookup fields are not reconciled:
Lookup.SAP.R3.UserType
Lookup.SAP.R3.LockUser
User reconciliation can be divided into the following:
The following fields are reconciled:
Extension
Telephone
Time Zone
Lang Logon
User Group
Department
Lang Comm
Last Name
First Name
User Title
Password
User ID
Start Menu
User Type
Alias
Lock User
Comm Type
Code
Building
Floor
Room No
Function
Decimal Notation
Date Format
Fax
IT Resource Type
User Profile
User Role
If trusted source reconciliation is implemented, then the following additional fields are reconciled:
UserId
Password
Organization
FirstName
LastName
Xellerate
Role
Xellerate Type
The files and directories that comprise this connector are compressed in the following ZIP file on the installation media:
Enterprise Applications\SAP Enterprise Applications\SAP User Management Rev 3.2.0.zip
These files and directories are listed in the following table.
Note: The files in thetroubleshoot directory are used only to run tests on the connector. |
The "Step 2: Copying the Connector Files and External Code" section provides instructions to copy these files into the required directories.
You can determine the release number of the connector at any of the following stages:
Before Deployment
To determine the release number of the connector before you deploy it:
Extract the contents of the SAPAdapter.jar
file. This file is in the lib
directory inside the installation media directory.
Open the manifest.mf
file in a text editor, which is one of the files bundled inside the SAPAdapter.jar
file.
In the manifest.mf
file, the release number of the connector is displayed as the value of the Version
property.
Note: If you maintain a copy of theSAPAdapter.jar file after deployment, then you can use this method to determine the release number of the connector at any stage. However, after you deploy the connector, it is recommended that you use the After Deployment method. |
During Deployment
To determine the release number of the connector while deploying the connector, refer to Step 4 of the procedure described in the "Step 5: Importing the Connector XML File" section.
After Deployment
To determine the release number of the connector after deploying the connector:
See Also: Oracle Identity Manager Design Console Guide |