The following topics provide details on these stages:
Preinstallation involves creating a target system user account for connector operations.
Preinstallation information is divided across the following sections:
The connector uses a target system account to connect to and perform operations on the target system.
To create this target system account:
For detailed information on each of these preinstallation tasks, refer to the SAP documentation.
You can deploy the SAP User Management Engine connector either locally in Oracle Identity Manager or remotely in the Connector Server. A Connector Server is a Microsoft Windows application that enables remote execution of an Identity Connector.
Connector servers are available in two implementations:
As a .Net implementation that is used by Identity Connectors implemented in .Net
As a Java Connector Server implementation that is used by Java-based Identity Connectors
The SAP User Management Engine connector is implemented in Java, so you can deploy this connector to a Java Connector Server.
Use the following steps to install and configure the Java Connector Server:
Note:
Before you deploy the Java Connector Server, ensure that you install the JDK or JRE on the same computer where you are installing the Java Connector Server and that your JAVA_HOME or JRE_HOME environment variable points to this installation.
Note:
Oracle Identity Manager has no built-in support for connector servers, so you cannot test your configuration.
When you run the Connector Installer, it automatically copies the connector files to directories in Oracle Identity Manager, imports connector XML files, and compiles adapters used for provisioning.
To run the Java Connector Server, use the ConnectorServer.bat script as follows:
You can run the connector code either locally in Oracle Identity Manager or remotely in a Connector Server.
Depending on where you want to run the connector code (bundle), the connector provides the following installation options:
To run the connector code locally in Oracle Identity Manager, perform the procedure described in Installing the Connector in Oracle Identity Manager.
To run the connector code remotely in a Connector Server, perform the procedures described in Installing the Connector in Oracle Identity Manager and Deploying the Connector Bundle in a Connector Server.
In this scenario, you install the connector in Oracle Identity Manager using the Connector Installer.
To run the Connector Installer:
Copy the contents of the connector installation media directory into the following directory:
Note:
In an Oracle Identity Manager cluster, copy this JAR file to each node of the cluster.
OIM_HOME/server/ConnectorDefaultDirectory
If you are using Oracle Identity Manager release 11.1.1.x, then perform the following steps:
Log in to the Administrative and User Console.
On the Welcome to Identity Manager Advanced Administration page, in the System Management region, click Manage Connector.
If you are using Oracle Identity Manager release 11.1.2.x, then perform the following steps:
Log in to Oracle Identity System Administration.
In the left pane, under System Management, click Manage Connector.
In the Manage Connector page, click Install.
From the Connector List list, select SAP UME Connector RELEASE_NUMBER.
Note:
If you are using SAP BusinessObjects AC system, from the Connector List list, select SAPACUME Connector RELEASE_NUMBER.
This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory in Step 1.
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select SAP UME Connector RELEASE_NUMBER.
Note:
If you are using SAP BusinessObjects AC system, from the Connector List list, select SAPACUME Connector RELEASE_NUMBER.
Click Load.
To start the installation process, click Continue.
The following tasks are performed in sequence:
Configuration of connector libraries
Import of the connector XML files (by using the Deployment Manager)
Compilation of adapters
On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 1.
If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:
Ensuring that the prerequisites for using the connector are addressed
Note:
At this stage, run the Oracle Identity Manager PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. See Clearing Content Related to Connector Resource Bundles from the Server Cache for information about running the PurgeCache utility.
There are no prerequisites for some predefined connectors.
Configuring the IT resource for the connector
Record the name of the IT resource displayed on this page. The procedure to configure the IT resource is described later in this guide.
Configuring the scheduled tasks that are created when you installed the connector
Record the names of the scheduled tasks displayed on this page. The procedure to configure these scheduled tasks is described later in this guide.
When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Table A-1.
You can deploy the connector either locally in Oracle Identity Manager or remotely in the Connector Server. A Connector Server is an application that enables remote execution of an Identity Connector, such as the SAP User Management connector.
To deploy the connector bundle remotely in a Connector Server, you must first deploy the connector in Oracle Identity Manager, as described in Installing the Connector in Oracle Identity Manager.
Note:
You can download the Connector Server from the Oracle Technology Network web page.
See Configuring the IT Resource for the Connector Server for related information.
See Using an Identity Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for more information about installing, configuring, and running the Connector Server.
To install the connector into the Connector Server:
Postinstallation for the connector involves configuring Oracle Identity Manager, enabling logging to track information about all connector events, and configuring SSL. It also involves performing some optional configurations such as enabling the reset password option, configuring password changes for newly created accounts, setting up lookup definitions for exclusion lists and so on.
Postinstallation steps are divided across the following sections:
Enabling the Reset Password Option in Oracle Identity Manager 11.1.2.1.0 or Later
Clearing Content Related to Connector Resource Bundles from the Server Cache
Setting Up the Lookup.SAPUME.UM.RoleDataSource Lookup Definition
Setting Up the Lookup.SAPUME.UM.GroupDataSource Lookup Definition
Configuring Oracle Identity Manager for Request-Based Provisioning
Configuring SSL to Secure Communication Between the Target System and Oracle Identity Manager
Configuring the Access Request Management Feature of the Connector
Synchronizing the SAPUME Process Form and SAP AC UME Process Form with Target System Field Lengths
You must create a UI form and an application instance for the resource against which you want to perform reconciliation and provisioning operations. In addition, you must run the entitlement and catalog synchronization jobs.
If you are using Oracle Identity Manager release 11.1.2 or later, you must create additional metadata such as a UI form and an application instance. In addition, you must run entitlement and catalog synchronization jobs. These procedures are described in the following sections:
You must create and activate a sandbox to begin using the customization and form management features. You can then publish the sandbox to make the customizations available to other users.
See Managing Sandboxes in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for instructions on creating and activating a sandbox.
You can use Form Designer in Oracle Identity System Administration to create and manage application instance forms.
See Managing Forms in Oracle Fusion Middleware Administering Oracle Identity Manager for instructions on creating a new UI form. While creating the UI form, ensure that you select the resource object corresponding to the Concur connector that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.
Create an application instance as follows. For detailed instructions, see Managing Application Instances in Oracle Fusion Middleware Administering Oracle Identity Manager.
Before publishing a sandbox, perform the following procedure as a best practice to validate all sandbox changes made till this stage as it is difficult to revert the changes after a sandbox is published:
To harvest entitlements and sync catalog:
For any changes you do in the Form Designer, you must create a new UI form and update the changes in an application instance. To update an existing application instance with a new form:
You can reset the password for an account after logging in as the user by navigating to My Access, Accounts tab in Oracle Identity Manager release 11.1.2.1.0 or later.
The Reset Password option is enabled for only those accounts that follow the UD_FORMNAME_PASSWORD naming convention for the password field. Otherwise, this option would be disabled as shown in the following sample screenshot:
To enable the Reset Password option in Oracle Identity Manager release 11.1.2.1.0 or later:
When you log in to SAP by using a newly created account, you are prompted to change your password at first logon. For accounts created through Oracle Identity Manager, password management can be configured by using the changePwdFlag and dummyPassword parameters of the IT resource.
You can apply one of the following approaches:
Configure the connector so that users with newly created accounts are prompted to change their passwords at first logon.
To achieve this, set the changePwdFlag parameter of the IT resource to no
. With this setting, the password entered on the process form for a new user account is used to set the password for the new account on the target system. When the user logs in to the target system, the user is prompted to change the password.
Configure the connector so that the password set while creating the account on Oracle Identity Manager is set as the new password on the target system. The user is not prompted to change the password at first logon.
To achieve this, set the changePwdFlag parameter to yes
and enter a string in the dummyPassword parameter of the IT resource. With these settings, when you create a user account through Oracle Identity Manager, the user is first created with the dummy password. Immediately after that, the connector changes the password of the user to the one entered on the process form. When the user logs in to the target system, the user is not prompted to change the password.
Note:
Security policies of a few target systems allow a user to change the password only once per day. In such a scenario, the target system allows the user to only reset the password and not to change it. The password update task throws an error message, such as Could not update user NEW_PASSWORD_INVALID.
If the password feature is disabled for users on the target system, then set the changePwdFlag parameter to no
.
Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.
You may require the assistance of the system administrator to change to the required input locale.
When you deploy the connector, the resource bundles are copied from the resources directory on the installation media into the Oracle Identity Manager database. Whenever you add a new resource bundle to the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
Oracle Identity Manager uses the Oracle Diagnostic Logging (ODL) logging service for recording all types of events pertaining to the connector.
The following topics provide detailed information about logging:
Oracle Identity Manager release 11.1.x uses Oracle Java Diagnostic Logging (OJDL) for logging. OJDL is based on java.util.logger. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
SEVERE.intValue()+100
This level enables logging of information about fatal errors.
SEVERE
This level enables logging of information about errors that might allow Oracle Identity Manager to continue running.
WARNING
This level enables logging of information about potentially harmful situations.
INFO
This level enables logging of messages that highlight the progress of the application.
CONFIG
This level enables logging of information about fine-grained events that are useful for debugging.
FINE, FINER, FINEST
These levels enable logging of information about fine-grained events, where FINEST logs information about all events.
These message types are mapped to ODL message type and level combinations as shown in Table 2-1.
Table 2-1 Log Levels and ODL Message Type:Level Combinations
Java Level | ODL Message Type:Level |
---|---|
SEVERE.intValue()+100 |
INCIDENT_ERROR:1 |
SEVERE |
ERROR:1 |
WARNING |
WARNING:1 |
INFO |
NOTIFICATION:1 |
CONFIG |
NOTIFICATION:16 |
FINE |
TRACE:1 |
FINER |
TRACE:16 |
FINEST |
TRACE:32 |
The configuration file for OJDL is logging.xml, which is located at the following path:
DOMAIN_HOME/config/fmwconfig/servers/OIM_SERVER/logging.xml
Here, DOMAIN_HOME and OIM_SEVER are the domain name and server name specified during the installation of Oracle Identity Manager.
To enable logging in Oracle WebLogic Server:
Edit the logging.xml file as follows:
Add the following blocks in the file:
<log_handler name='sap-handler' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='[FILE_NAME]'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler>
<logger name="ORG.IDENTITYCONNECTORS.SAPUME" level="[LOG_LEVEL]" useParentHandlers="false">
<handler name="sap-handler"/>
<handler name="console-handler"/>
</logger>
If you are using SAP GRC, then add the following block:
<logger name="ORG.IDENTITYCONNECTORS.SAPAC" level="[Log_LEVEL]" useParentHandlers="false">
<handler name="sap-handler"/>
<handler name="console-handler"/>
</logger>
If you are using Application Onboarding, then add the following block:
<logger name='oracle.iam.application' level="[Log_LEVEL]" useParentHandlers='false'>
<handler name='sap-handler'/>
<handler name='console-handler'/>
</logger>
Replace both occurrences of [LOG_LEVEL] with the ODL message type and level combination that you require. Table 2-1 lists the supported message type and level combinations.
Similarly, replace [FILE_NAME] with the full path and name of the log file in which you want log messages to be recorded.
The following blocks show sample values for [LOG_LEVEL] and [FILE_NAME]:
<log_handler name='sap-handler' level='NOTIFICATION:1' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\oim_server1-diagnostic-1.log'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler>
<logger name="ORG.IDENTITYCONNECTORS.SAPUME" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="sap-handler"/>
<handler name="console-handler"/>
</logger>
If you are using SAP GRC, then add the following block:
<logger name="ORG.IDENTITYCONNECTORS.SAPAC" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="sap-handler"/>
<handler name="console-handler"/>
</logger>
If you are using Application Onboarding, then add the following block:
<logger name='oracle.iam.application' level="NOTIFICATION:1" useParentHandlers='false'>
<handler name='sap-handler'/>
<handler name='console-handler'/>
</logger>
</logger>
With these sample values, when you use Oracle Identity Manager, all messages generated for this connector that are of a log level equal to or higher than the NOTIFICATION:1 level are recorded in the specified file.
Save and close the file.
Set the following environment variable to redirect the server logs to a file:
For Microsoft Windows:
set WLS_REDIRECT_LOG=FILENAME
For UNIX:
export WLS_REDIRECT_LOG=FILENAME
Replace FILENAME with the location and name of the file to which you want to redirect the output.
Restart the application server.
The Lookup.SAPUME.UM.RoleDataSource lookup definition is used to hold data source names of the role object class. By default, this lookup definition contains entry for the UME_ROLE_PERSISTENCE role data source, which is common to all SAP configurations. If there are role data sources specific to your environment, then you must update the Lookup.SAPUME.UM.RoleDataSource lookup definition for these data sources.
Note:
If you are using SAP BusinessObjects AC system, then you must update the Lookup.SAPACUME.RoleDatasource.
You must log into SAP User Management Engine as the administrator to view and determine the list of role data sources in your environment.
The name of the role data source is available as part of the Unique ID field. The value of the Unique ID field is in the following format:
ROLE.DATA_SOURCE_NAME.AUTO_GENERATED_VALUE
The following is a simple value of the Unique ID field:
ROLE.PCD_ROLE_PERSISTENCE.YJ1ku1NfcgCd1ZoMDG78ocBzkA=
In this value, PCD_ROLE_PERSISTENCE is the name of the role data source.
After you determine the names of all role data sources available in your environment, add each data source name by creating an entry in the Lookup.SAPUME.UM.RoleDataSource lookup definition as described in the following procedures:
For Oracle Identity Manager release 11.1.1.x:
The Lookup.SAPUME.UM.GroupDataSource lookup definition is used to hold data source names of the group object class. By default, this lookup definition contains entry for the PRIVATE_DATASOURCE group data source, which is common to all SAP configurations. If there are group data sources specific to your environment, then you must update the Lookup.SAPUME.UM.GroupDataSource lookup definition for these data sources.
Note:
If you are using SAP BusinessObjects AC system, then you must update the Lookup.SAPACUME.GroupDatasource lookup definition
SAP User Management Engine does not allow adding a group from the built-in groups adapter data source. Therefore, this data source must not be added in this lookup definition. If SAP User Management Engine is configured with SAP ABAP-based system as data source, such as R3_ROLE_DS, then check whether User Management Engine allows adding a group that assigns ABAP roles to a user. You can check if this is allowed from the Identity Management page of SAP User Management Engine. If adding the group is allowed, then add the data source, R3_ROLE_DS, to the Lookup.SAPUME.UM.GroupDataSource lookup definition
You must log into SAP User Management Engine as the administrator to view and determine the list of group data sources in your environment.
The name of the group data source is available as part of the Unique ID field.
The value of the Unique ID field is in the following format:
GRUP.DATA_SOURCE_NAME.AUTO_GENERATED_VALUE
The following is a sample value of the Unique ID field:
GRUP.PRIVATE_DATASOURCE.un:Guests
In this value, PRIVATE_DATASOURCE is the name of the group data source.
After you determine the names of all group data sources available in your environment, add each data source name by creating an entry in the Lookup.SAPUME.UM.GroupDataSource lookup definition as described in the following procedures:
For Oracle Identity Manager release 11.1.1.x:
In the Lookup.SAPUME.UM.ProvExclusionList and Lookup.SAPUME.UM.ReconExclusionList lookup definitions, enter the user IDs of target system accounts for which you do not want to perform provisioning and reconciliation operations, respectively. See Lookup Definitions for Exclusion Lists for information about the format of the entries in these lookups.
Note:
The Lookup.SAPUME.UM.ProvExclusionList and Lookup.SAPUME.UM.ReconExclusionList lookup definitions are optional and do not exist by default.
You must add these lookups to the Lookup.SAPUME.UM.Configuration lookup definition to enable exclusions during provisioning and reconciliation operations. See Lookup.SAPUME.UM.Configuration for more information.
To add entries in the lookup for exclusions during provisioning operations:
Note:
To specify user IDs to be excluded during reconciliation operations, add entries in the Lookup.SAPUME.UM.ReconExclusionList lookup.
In request-based provisioning, an end user creates a request for a resource by using the Administrative and User Console. Administrators or other users can also create requests for a particular user. Requests for a particular resource on the resource can be viewed and approved by approvers designated in Oracle Identity Manager.
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.1.x.
The direct provisioning feature of the connector is automatically disabled when you enable request-based provisioning. Therefore, do not enable request-based provisioning if you want to use the direct provisioning.
To configure request-based provisioning, perform the following procedures:
The request datasets (predefined or generated) can be imported by using the Deployment Manager (DM). The predefined request datasets are stored in the xml/SAPUME-Datasets.xml file on the installation media.
To import a request dataset definition by using the Deployment Manager:
The request datasets are imported into MDS.
To enable the Auto Save Form feature:
Run the PurgeCache utility to clear content belonging to the Metadata category from the server cache. See Clearing Content Related to Connector Resource Bundles from the Server Cache for instructions.
The procedure to configure request-based provisioning ends with this step.
You configure SSL to secure data communication between Oracle Identity Manager and the target system.
To configure SSL between the target system and Oracle Identity Manager:
Generate the certificate on the target system.
See the target system documentation for detailed instructions.
To import the certificate on Oracle Identity Manager:
Copy the target system certificate to the Oracle Identity Manager host computer.
In a command window, change to the directory where you copy the certificate file and then enter a command similar to the following:
keytool -import -alias ALIAS -file CER_FILE -keystore MY_CACERTS -storepass PASSWORD
In this command:
ALIAS is the alias for the certificate (for example, the server name).
CER_FILE is the full path and name of the certificate (.cer) file.
Table 2-2 shows the location of the certificate store of the supported application server.
The following is a sample command:
keytool -import -alias ibm1-cert140 -file C:\syaug24\Middleware\ibm1-cert.cer -keystore C:\syaug24\Middleware\jrockit_160_24_D1.1.2-4\jre\lib\security\cacerts -storepass changeit
Table 2-2 Certificate Store Locations
Application Server | Certificate Store Location |
---|---|
Oracle WebLogic Server |
|
To confirm whether or not the certificate has been imported successfully, enter a command similar to the following:
keytool -list -alias ALIAS -keystore MY_CACERTS -storepass PASSWORD
For example:
keytool -list -alias MyAlias -keystore C:\mydir\java\jre\lib\security\cacerts -storepass changeit
An IT resource contains connection information about the target system. Oracle Identity Manager uses this information during reconciliation and provisioning.
The SAPUME IT Resource is automatically created when you run the Connector Installer. You must specify values for the parameters of the IT resource.
Note:
If you are using SAP BusinessObjects AC system, then the SAP AC UME IT resource is automatically created when you run the Connector Installer.
Note:
If you are using SAP BusinessObjects AC system, then the SAP AC UME IT resource is automatically created when you run the Connector Installer.
The ALL USERS group has INSERT, UPDATE, and DELETE permissions on the default IT resource. This is to ensure that end users can select the IT resource during request-based provisioning. If you create another IT resource, then you must assign INSERT, UPDATE, and DELETE permissions for the ALL USERS group on the IT resource.
To specify values for the parameters of the IT resource:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 11.1.1.x:
Log in to the Administrative and User Console.
For Oracle Identity Manager release 11.1.2.x:
Log in to Oracle Identity System Administration.
If you are using Oracle Identity Manager release 11.1.1.x, then:
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Manage IT Resource.
If you are using Oracle Identity Manager release 11.1.2.x, then, in the left pane under Configuration, click IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter SAPUME IT Resource
and then click Search.
Click the edit icon for the IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the IT resource. Table 2-3 describes the parameters of the SAP UME IT resource and Table 2-4 describes the parameters of the SAP AC UME IT resource.
Note:
Entries in this table are sorted in alphabetical order of parameter names.
Table 2-3 Parameters of the SAP UME IT Resource
Parameter | Description |
---|---|
Configuration Lookup |
This parameter holds the name of the lookup definition containing configuration information. Value: |
ConnectorServerName |
Name of the IT resource of the type "Connector Server." You create an IT resource for the Connector Server in Configuring the IT Resource for the Connector Server. Note: Enter a value for this parameter only if you have deployed the SAP User Management Engine connector in the Connector Server. |
changePwdFlag |
See Configuring Password Changes for Newly Created Accounts for information about the value to be specified for this parameter. Default value: |
dummyPassword |
Enter the dummy password that you want the connector to use during a Create User provisioning operation. The connector first sets the password as this value and then changes it to the password specified on the process form. See Configuring Password Changes for Newly Created Accounts for more information about this parameter. |
enableDate |
Enter the date that must be set (in the YYYY-MM-DD format) if a user must be enabled. Sample value: |
logonNameInitialSubstring |
Enter a set of characters to support full reconciliation for the English language. For other languages, enter all characters of that language. Sample value: |
logSPMLRequest |
Enter |
pwdHandlingSupport |
If SAP User Management Engine is configured with an LDAP-based data source in writable mode, then SSL configuration between SAP User Management Engine and the LDAP-based data source is mandatory for password management. In such a scenario, if SSL is not configured between SAP User Management Engine and the LDAP-based data source and password need not be maintained from SAP User Management Engine, then set the value of this parameter Default value: |
TopologyName |
Enter the name of the topology of the computer hosting the target system |
umePassword |
Enter the password of the target system user account that you create for connector operations |
umeUrl |
|
umeUserId |
Enter the user ID of the target system user account that you create for connector operations |
Table 2-4 Parameters of the SAP AC UME IT Resource
Parameter | Description |
---|---|
changePwdFlag |
See Configuring Password Changes for Newly Created Accounts for information about the value to be specified for this parameter. Default value: |
Configuration Lookup |
This parameter holds the name of the lookup definition containing configuration information. Value: |
ConnectorServerName |
Name of the IT resource of the type "Connector Server." You create an IT resource for the Connector Server in Configuring the IT Resource for the Connector Server. Note: Enter a value for this parameter only if you have deployed the SAP User Management Engine connector in the Connector Server. |
dummyPassword |
Enter the dummy password that you want the connector to use during a Create User provisioning operation. The connector first sets the password as this value and then changes it to the password specified on the process form. See Configuring Password Changes for Newly Created Accounts for more information about this parameter. |
enableDate |
Enter the date that must be set (in the YYYY-MM-DD format) if a user must be enabled. Sample value: |
grcLanguage |
This parameter defines the language of grc. Value: |
grcPassword |
This parameter is used to authenticate the user access. |
grcUsername |
This parameter holds the GrcUsername for accessing the grc system. |
logonNameInitialSubstring |
Enter a set of characters to support full reconciliation for the English language. For other languages, enter all characters of that language. Sample value: |
logSPMLRequest |
Enter |
pwdHandlingSupport |
If SAP User Management Engine is configured with an LDAP-based data source in writable mode, then SSL configuration between SAP User Management Engine and the LDAP-based data source is mandatory for password management. In such a scenario, if SSL is not configured between SAP User Management Engine and the LDAP-based data source and password need not be maintained from SAP User Management Engine, then set the value of this parameter Default value: |
umePassword |
Enter the password of the target system user account that you create for connector operations |
umeUrl |
|
umeUserId |
Enter the user ID of the target system user account that you create for connector operations |
To save the values, click Update.
An IT resource contains connection information about the target system. Oracle Identity Manager uses this information during reconciliation and provisioning.
Perform the procedure described in this section only if you have installed the connector bundle in a Connector Server, as described in Deploying the Connector Bundle in a Connector Server. You must create a separate IT resource for the Connector Server.
To create the IT resource for the Connector Server:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 11.1.1.x:
Log in to the Administrative and User Console.
For Oracle Identity Manager release 11.1.2.x:
Log in to Oracle Identity System Administration.
If you are using Oracle Identity Manager release 11.1.1.x, then:
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Create IT Resource.
If you are using Oracle Identity Manager release 11.1.2.x, then:
In the left pane under Configuration, click IT Resource.
Note:
If you are using Oracle Identity Manager release 11.1.2.3.x or later, then in the left pane, under Provisioning Configuration, click IT Resource.
In the Manage IT Resource page, click Create IT Resource.
Note: On the Step 1: Provide IT Resource Information page, perform the following steps:
IT Resource Name: Enter a name for the IT resource.
IT Resource Type: Select Connector Server from the IT Resource Type list.
Remote Manager: Do not enter a value in this field.
Click Continue. Figure 2-1 shows the IT resource values added on the Create IT Resource page.
Figure 2-1 Step 1: Provide IT Resource Information
On the Step 2: Specify IT Resource Parameter Values page, specify values for the parameters of the IT resource and then click Continue. Figure 2-2 shows the Step 2: Specify IT Resource Parameter Values page.
Figure 2-2 Step 2: Specify IT Resource Parameter Values
Table 2-5 provides information about the parameters of the IT resource.
Table 2-5 Parameters of the IT Resource for the Connector Server
Parameter | Description |
---|---|
Host |
Enter the host name or IP address of the computer hosting the connector server. Sample value: |
Key |
Enter the key for the Java connector server. |
Port |
Enter the number of the port at which the connector server is listening. Default value: |
Timeout |
Enter an integer value which specifies the number of milliseconds after which the connection between the connector server and Oracle Identity Manager times out. Sample value: |
UseSSL |
Enter Default value: Note: If you configure the connector to communicate with the Connector Server using SSL, including setting the connectorserver.usessl property to true and importing the target system certificate into the Connector Server JDK keystore, an attempt to access the target system or run the Connector Server returns an error. |
On the Step 3: Set Access Permission to IT Resource page, the SYSTEM ADMINISTRATORS
group is displayed by default in the list of groups that have Read, Write, and Delete permissions on the IT resource that you are creating.
Note:
This step is optional.
If you want to assign groups to the IT resource and set access permissions for the groups, then:
Click Assign Group.
For the groups that you want to assign to the IT resource, select Assign and the access permissions that you want to set. For example, if you want to assign the ALL USERS
group and set the Read and Write permissions to this group, then you must select the respective check boxes in the row, as well as the Assign check box, for this group.
Click Assign.
On the Step 3: Set Access Permission to IT Resource page, if you want to modify the access permissions of groups assigned to the IT resource, then:
Note:
This step is optional.
You cannot modify the access permissions of the SYSTEM ADMINISTRATORS
group. You can modify the access permissions of only other groups that you assign to the IT resource.
Click Update Permissions.
Depending on whether you want to set or remove specific access permissions for groups displayed on this page, select or deselect the corresponding check boxes.
Click Update.
On the Step 3: Set Access Permission to IT Resource page, if you want to unassign a group from the IT resource, then:
Note:
This step is optional.
You cannot unassign the SYSTEM ADMINISTRATORS
group. You can unassign only other groups that you assign to the IT resource.
Select the Unassign check box for the group that you want to unassign.
Click Unassign.
Click Continue. Figure 2-3 shows the Step 3: Set Access Permission to IT Resource page.
Figure 2-3 Step 3: Set Access Permission to IT Resource
On the Step 4: Verify IT Resource Details page, review the information that you provided on the first, second, and third pages. If you want to make changes in the data entered on any page, click Back to revisit the page and then make the required changes.
To proceed with the creation of the IT resource, click Continue. Figure 2-4 shows Step 4: Verify IT Resource Details page.
Figure 2-4 Step 4: Verify IT Resource Details
The Step 5: IT Resource Connection Result page displays the results of a connectivity test that is run using the IT resource information. If the test is successful, then click Continue. If the test fails, then you can perform one of the following steps:
Click Back to revisit the previous pages and then make corrections in the IT resource creation information.
Click Cancel to stop the procedure, and then begin from the first step onward.
Figure 2-5 shows the Step 5: IT Resource Connection Result page.
Figure 2-5 Step 5: IT Resource Connection Result
Click Finish. Figure 2-6 shows the IT Resource Created Page.
Oracle Identity Manager can be configured as the medium for sending provisioning requests to SAP BusinessObjects AC Access Request Management. A request from Oracle Identity Manager is sent to Access Request Management, which forwards the provisioning data contained within the request to the target system (SAP R/3 or SAP CUA). The outcome is the creation of or modification to the user's account on the target system.
Note:
Before you configure the Access Request Management feature, it is recommended that you read the guidelines described in Guidelines on Using a Deployment Configuration.
The following sections provide information about configuring the Access Request Management feature:
The GRC UME-ITRes IT resource holds information that is used during communication with SAP BusinessObjects AC Access Request Management. To set values for the parameters of this IT resource:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 11.1.1.x:
Log in to the Administrative and User Console.
For Oracle Identity Manager release 11.1.2.x:
Log in to Identity System Administration.
If you are using Oracle Identity Manager release 11.1.1.x, then:
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Manage IT Resource.
If you are using Oracle Identity Manager release 11.1.2.x, then, in the left pane under Configuration, click IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter GRC UME-ITRes
and then click Search.
Click the edit icon for the IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the IT resource.
Table 2-6 lists the parameters of the GRC UME-ITRes IT resource.
Table 2-6 Parameters of the GRC UME-ITRes IT Resource
Parameter | Description |
---|---|
Configuration Lookup |
Enter the name of the configuration lookup definition. Value for Lookup
|
Connector Server Name |
Name of the IT resource of the type "Connector Server." |
language |
Enter the two-letter code for the language set on the target system. Sample value: |
password |
Enter the password of the account created on Access Request Management system. |
port |
Enter the number of the port at which Access Request Management system is listening. Sample value: |
server |
Enter the IP address of the host computer on which Access Request Management system is listening. Sample value: |
username |
Enter the user name of an account created on Access Request Management system. This account is used to call Access Request Management system APIs that are used during request validation. Sample value: |
To save the values, click Update.
SoD is a process that ensures that an individual is given access to only one module of a business process and will not be able to access other modules to reduce risk of fraud and error.
This section discusses the following procedures:
Note:
The ALL USERS group has INSERT, UPDATE, and DELETE permissions on the UD_SAPUME and UD_UME_ROLE process forms. During SoD validation of an entitlement request, data first moves from a dummy object form to a dummy process form. From there, data is sent to the SoD engine for validation. If the request clears the SoD validation, then data is moved from the dummy process form to the actual process form. Because the data is moved to the actual process forms through APIs, the ALL USERS group must have INSERT, UPDATE, and DELETE permissions on the three process forms.
To configure the SAP GRC to act as the SoD engine, see Using Segregation of Duties (SoD) in Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for 11g Release 1 (11.1.2).
The GRC UME-ITRes IT resource holds information that is used by the connector during SoD operations. This IT resource is the same as the one used by the Access Request Management feature for both Oracle Identity Manager.
To set values for the parameters of this IT resource, see Specifying Values for the GRC UME-ITRes IT Resource.
The TopologyName IT resource parameter holds the name of the combination of the following elements that you want to use for SoD validation:
Oracle Identity Manager installation
SAP BusinessObjects AC installation
SAP ERP installation
By default, the GRC-ITRes IT resource is registered. However, you must manually register the GRC UME-ITRes IT resource and enter the new topology name as the value of the TopologyName IT resource parameter.
To register the GRC UME-ITRes IT resource:
See Configuring the IT Resource for the Target System for information about specifying values for parameters of the IT resource.
This section describes the procedure to disable and enable SoD on Oracle Identity Manager.
To disable SoD:
If you are using Oracle Identity Manager release 11.1.1.x, then perform the following steps:
Log in to the Administrative and User Console.
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management tab, click System Configuration.
If you are using Oracle Identity Manager release 11.1.2.x, then perform the following steps:
Log in to Identity System Administration.
In the left pane, under System Management, click System Configuration.
In the Search System Configuration box, enter XL.SoDCheckRequired
and then click Search.
A list that matches your search criteria is displayed in the search results table.
Click the XL.SoDCheckRequired property name.
System properties for SoD are displayed on the right pane.
In the Value box, enter FALSE
to disable SoD.
Click Save.
Restart Oracle Identity Manager.
To enable SoD:
If you are using Oracle Identity Manager release 11.1.1.x, then perform the following steps:
Log in to the Administrative and User Console.
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management tab, click System Configuration.
If you are using Oracle Identity Manager release 11.1.2.x, then perform the following steps:
Log in to Identity System Administration.
In the left pane, under System Management, click System Configuration.
In the Search System Configuration box, enter XL.SoDCheckRequired
and then click Search.
A list that matches your search criteria is displayed in the search results table.
Click the XL.SoDCheckRequired property name.
System properties for SoD are displayed on the right pane.
In the Value box, enter TRUE
to enable SoD.
Click Save.
Restart Oracle Identity Manager.
You need to download the WSDL files from SAP BusinessObjects AC before configuring the web services in SAP BusinessObjects AC. WSDL is required for connector to connect SAP web services.
Since the connector supports only basic authentication, select the User ID/Password check box for the following web services supported from OIM:
WSDL | Description |
---|---|
GRAC_AUDIT_LOGS_WS |
Audit log web service |
GRAC_LOOKUP_WS |
Look Up Service |
GRAC_REQUEST_STATUS_WS |
Request status web service |
GRAC _RISK_ANALYSIS_WOUT_NO_WS |
Risk analysis without request number |
GRAC_SELECT_APPL_WS |
Select Application web service |
GRAC_USER_ACCESS_WS |
User Access Request Service |
GRAC_SEARCH_ROLES_WS |
Search role web service |
When you download the WSDL file, ensure to save it with the same name as mentioned in the SOA Management page. In addition, ensure that the folder containing WSDL files have read permission.
You can localize UI form field labels by using the resource bundle corresponding to the language you want to use. The resource bundles are available in the connector installation media.
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.2.x or later and you want to localize UI form field labels.
To localize field label that you add to in UI forms:
Log in to Oracle Enterprise Manager.
In the left pane, expand Application Deployments and then select oracle.iam.console.identity.sysadmin.ear.
In the right pane, from the Application Deployment list, select MDS Configuration.
On the MDS Configuration page, click Export and save the archive to the local computer.
Extract the contents of the archive, and open one of the following files in a text editor:
For Oracle Identity Manager 11g Release 2 PS2 (11.1.2.2.0):
SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle_en.xlf
For releases prior to Oracle Identity Manager 11g Release 2 PS2 (11.1.2.2.0):
SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle.xlf
Edit the BizEditorBundle.xlf file in the following manner:
Search for the following text:
<file source-language="en" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Replace with the following text:
<file source-language="en" target-language="LANG_CODE"
original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf"
datatype="x-oracle-adf">
In this text, replace LANG_CODE with the code of the language that you want to localize the form field labels. The following is a sample value for localizing the form field labels in Japanese:
<file source-language="en" target-language="ja" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Search for the application instance code. This procedure shows a sample edit for SAP User Management Engine application instance. The original code is:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_SAPUME_DEPARTMENT__c_description']}"> <source>Department</source> </target> </trans-unit> <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.SAPUMEFORM.entity.SAPUMEFORMEO.UD_SAPUME_DEPARTMENT__c_LABEL"> <source>Department</source> </target> </trans-unit>
Open the resource file from the connector package, for example SAPUME_ja.properties, and get the value of the attribute from the file, for example, global.udf.UD_SAPUME_DEPARTMENT=\u90E8\u9580.
Replace the original code shown in Step 6.b with the following:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_SAPUME_DEPARTMENT__c_description']}"> <source>Department</source> <target>\u90E8\u9580</target> </trans-unit> <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.SAPUMEFORM.entity.SAPUMEFORMEO.UD_SAPUME_DEPARTMENT__c_LABEL"> <source>Department</source> <target>\u90E8\u9580</target> </trans-unit>
Repeat Steps 6.a through 6.d for all attributes of the process form.
Save the file as BizEditorBundle_LANG_CODE.xlf. In this file name, replace LANG_CODE with the code of the language to which you are localizing.
Sample file name: BizEditorBundle_ja.xlf.
Repackage the ZIP file and import it into MDS.
See Also:
Deploying and Undeploying Customizations in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager, for more information about exporting and importing metadata files
Log out of and log in to Oracle Identity Manager.
You can upgrade the SAP User Management Engine connector while in production, and with no downtime. Your customizations will remain intact and the upgrade will be transparent to your users. All form field names are preserved from the legacy connector.
To upgrade the SAP User Management Engine connector, perform the procedures described in the following sections:
Note:
Before you perform the upgrade procedure, it is strongly recommended that you create a backup of the Oracle Identity Manager database. Refer to the database documentation for information about creating a backup.
As a best practice, first perform the upgrade procedure in a test environment.
Before you perform an upgrade operation or any of the upgrade procedures, you must perform the following actions:
Perform a reconciliation run to fetch all latest updates to Oracle Identity Manager.
Define the source connector (an earlier release of the connector that must be upgraded) in Oracle Identity Manager. You define the source connector to update the Deployment Manager XML file with all customization changes made to the connector.
Run the Oracle Identity Manager Delete JARs utility to delete the old connector bundle to the Oracle Identity Manager database.
See Also:
Delete JAR Utility of Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for detailed information about the Delete JARs utility
Depending on the environment in which you are upgrading the connector, perform one of the following steps:
Staging Environment
Perform the upgrade procedure by using the wizard mode.
Production Environment
Perform the upgrade procedure by using the silent mode.
See Also:
Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about the wizard and silent modes
Perform the procedure described in this section to complete the steps that are required to post-upgrade.
Run the Form Version Control (FVC) utility to manage data changes on a form after an upgrade operation.
To do so, in a text editor, open the fvc.properties file located in the OIM_DC_HOME directory.
If you are using the connector release 9x, include the following entries:
ResourceObject;SAPUME Resource Object FormName;UD_SAPEP FromVersion;V_9.0.4.12 ToVersion;v_11.1.1.8.0 Parent;UD_SAPEP_IS_LOCK;false
If you are using the connector release 11.1.1.x, include the following entries:
ResourceObject;SAPUME Resource Object FormName;UD_SAPUME FromVersion;V_11.1.1.5.0 ToVersion;v_11.1.1.8.0 Parent;UD_SAPUME_IS_LOCK;false
Depending on the type of connector that you choose to upgrade, perform one of the following procedures:
Run the Form Version Control (FVC) utility to manage data changes on a form after an upgrade operation. To do so, in a text editor, open the fvc.properties file located in the OIM_DC_HOME directory.
If you are using the connector release 11.1.1.8.0, include the following entries:
ResourceObject;SAPUME Resource Object FormName;UD_SAPUME FromVersion;V_11.1.1.8.0 ToVersion;v_11.1.1.9.0
Note:
While upgrading the connector, the following information will display. You must manually delete the following adapters and Event handlers:
The "sapume ac remove child" and "sapume ac add child" Adapters.
The "adpSAPUMEACREMOVECHIL" and "adpSAPUMEACADDCHILD" event handlers.
Perform the procedure described in this section to complete the postupgrade steps for the SoD validation of SAP BusinessObjects AC Access Risk Analysis.
Perform the procedure described in this section to complete the postupgrade steps for the SAP BusinessObjects AC Access Request Management.
Re-configure the SAPUME IT Resource IT resource with GRC credentials.
You must manually update the decode values for the following entries in the "Lookup.SAPAC10UME.Configuration" lookup definition:
roleLookupAccessURL
otherLookupAccessURL
auditLogsAccessURL
appLookupAccessURL
wsdlFilePath
userAccessAccessURL
requestStatusAccessURL
Note: Upgrading the connector will generate duplicate entries in Lookups, you must manually delete these duplicate entries.
Perform the postupgrade procedure documented in the Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Manager.
Run the Form Version Control (FVC) utility to manage data changes on a form after an upgrade operation. To do so:
In a text editor, open the fvc.properties file located in the OIM_DC_HOME directory. If you are using the connector release 11.1.1.8.0, include the following entries:
ResourceObject;SAP AC UME Resource Object FormName;UD_SAPUME FromVersion;v_11.1.1.8.0 ToVersion;v_11.1.1.9.0
Run the FVC utility. This utility is copied into the following directory when you install the design console:
For Microsoft Windows:
OIM_DC_HOME/fvcutil.bat
For UNIX:
OIM_DC_HOME/fvcutil.sh
When you run this utility, you are prompted to enter the login credentials of the Oracle Identity Manager administrator, and the logger level and log file location.
See Also:
Using the Form Version Control Utility of Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about the FVC utility
Run the PostUpgradeScript_SAPUME.sql script as follows:
Connect to the Oracle Identity Manager database by using the OIM DB User credentials.
Run the PostUpgradeScript_SAPUME.sql. This script is located in the Upgrade directory on the installation media.
Note:
Change the task name of the bulk adapter after upgrade.Example: Replace UD_SAPACUME Updated with UD_SAPUME Updated.
Create a new version of the process form.
If you are using Oracle Identity Manager release 11.1.2.x, then all changes made to the Form Designer of the Design Console must be done in a new UI form as follows:
Log in to Oracle Identity System Administration.
Create and activate a sandbox. See Creating and Activating a Sandbox for more information.
Create a new UI form to view the upgraded fields. See Creating a New UI Form for more information about creating a UI form.
Associate the newly created UI form with the application instance of your target system. To do so, open the existing application instance for your resource, from the Form field, select the form (created in the preceding step), and then save the application instance.
Publish the sandbox. See Publishing a Sandbox for more information.
Run all the following scheduled jobs that are used for SAP BusinessObjects AC lookup field synchronization:
Note:
You can specify values for the attributes of these scheduled jobs. Table 3-2 describes the attributes of these scheduled jobs. Configuring Scheduled Jobs describes the procedure to configure scheduled jobs.
SAP AC UME Role Lookup Reconciliation
SAP AC UME Group Lookup Reconciliation
SAP AC UME BusinessProcess Lookup Reconciliation
SAP AC UME FunctionalArea Lookup Reconciliation
SAP AC UME ItemProvAction Lookup Reconciliation
SAP AC UME Priority Lookup Reconciliation
SAP AC UME ReqInitSystem Lookup Reconciliation
SAP AC UME RequestType Lookup Reconciliation
Perform full reconciliation.
This operation updates the Unique Id resource object field and the lock status of the users. The lock status will be updated as per the value specified in the fvc.properties file in Step 5a.
See Full Reconciliation for more information about this step.
After upgrading the connector, you can perform delete reconciliation.
See Reconciliation Scheduled Jobs for more information about delete reconciliation.
If you are using Connector Server, Deploy the Connector Bundle in a Connector Server. See Deploying the Connector Bundle in a Connector Server for more information.