Skip Headers
Oracle® Identity Manager Connector Guide for SAP User Management
Release 9.0.3
Part Number B32371-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

2 Deploying the Connector

Deploying the connector involves the following steps:

If you want to configure the connector for multiple installations of SAP User Management, then perform the following procedure:

Step 1: Verifying Deployment Requirements

The following table lists the deployment requirements for the connector.

Item Requirement
Oracle Identity Manager Oracle Identity Manager release 8.5.3 or later
Target systems The target system can be any one of the following:

  • SAP 4.6C

  • SAP 4.7

  • SAP BIW 3.1

  • SAP CRM 4.0

  • SEM BCS on BIW3.1

  • mySAP ERP 2004 ECC 5.0

  • mySAP ERP 2005 ECC 6.0
External code The following SAP custom code files: 
sapjco.jar

For Microsoft Windows:

sapjcorfc.dll
librfc32.dll

Version: 2.0.10

For Solaris and Linux:

libsapjcorfc.so
librfccm.so

Version: 2.0.10
Target system user account Create a user account, and assign it to the SAP_ALL group.

You provide the credentials of this user account while performing the procedure in the "Defining IT Resources" section.

Step 2: Copying the Connector Files and External Code

The connector files to be copied and the directories to which you must copy them are given in the following table.

Note:

The directory paths given in the first column of this table correspond to the location of the connector files in the following directory on the installation media: 
Enterprise Applications\SAP Enterprise Applications\SAP User Management

Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.

File in the Installation Media Directory Destination Directory 
BAPI\xlsapcar.sar
This file can be copied to any location on the target system. For example: 
C:\xlsapcar\

Refer to the "Extracting the Request Files" section for more information.

 
lib\SAPAdapter.jar


OIM_home\xellerate\SAP\lib
OIM_home\xellerate\JavaTasks
Files in the resources directory 
OIM_home\xellerate\connectorResources
Files in the troubleshoot directory 
OIM_home\xellerate\SAP\troubleshoot
Files in the xml directory 
OIM_home\xellerate\SAP\xml

To download and copy the external code files to the required locations:

  1. Download the SAP Java connector file from the SAP Web site as follows:

    1. Open the following page in a Web browser:

      https://websmp104.sap-ag.de/connectors

    2. Open the SAP JAVA Connector page by selecting Application Platform, Connectivity, Connectors, SAP Java Connector, and Tools & Services.

    3. On the SAP JAVA Connector page, links for files that you can download are displayed on the right pane. Click the link for the SAP JCO release that you want to download.

    4. In the dialog box that is displayed, specify the path of the directory in which you want to save the file.

  2. Extract the contents of the file that you download.

  3. Copy the sapjco.jar file into the OIM_home\Xellerate\JavaTasks directory.

  4. Copy the RFC files into the required directory, and then modify the appropriate environment variable so that it includes the path to this directory:

    • On Microsoft Windows:

      Copy the librfccm.dll and libsapjcorfc.dll files into the winnt\system32 directory. Alternatively, you can copy these files into any directory and then add the path to the directory in the PATH environment variable.

    • On Solaris and Linux:

      Copy the librfccm.so and libsapjcorfc.so files into the /usr/local/jco directory, and then add the path to this directory in the LD_LIBRARY_PATH environment variable.

  5. Restart the server for the changes in the environment variable to take effect.

Note:

While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.

Step 3: Configuring the Oracle Identity Manager Server

Configuring the Oracle Identity Manager server involves the following procedures:

Note:

In a clustered environment, you must perform this step on each node of the cluster.

Changing to the Required Input Locale

Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.

To set the required input locale:

Note:

Depending on the operating system used, you may need to perform this procedure differently.

  1. Open Control Panel.

  2. Double-click Regional Options.

  3. On the Input Locales tab of the Regional Options dialog box, add the input locale that you want to use and then switch to the input locale.

Clearing Content Related to Connector Resource Bundles from the Server Cache

Whenever you add a new resource bundle in the OIM_home\xellerate\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:

  1. In a command window, change to the OIM_home\xellerate\bin directory.

  2. Enter one of the following commands:

    Note:

    You must perform Step 1 before you perform this step. If you run the command as follows, then an exception is thrown: 
    OIM_home\xellerate\bin\batch_file_name

    • On Microsoft Windows:

      PurgeCache.bat ConnectorResourceBundle

    • On UNIX:

      PurgeCache.sh ConnectorResourceBundle

    In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:

    OIM_home\xellerate\config\xlConfig.xml

Note:

You can ignore the exception that is thrown when you perform Step 2.

Enabling Logging

When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. 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:

  • ALL

    This level enables logging for all events.

  • DEBUG

    This level enables logging of information about fine-grained events that are useful for debugging.

  • INFO

    This level enables logging of informational messages that highlight the progress of the application at coarse-grained level.

  • WARN

    This level enables logging of information about potentially harmful situations.

  • ERROR

    This level enables logging of information about error events that may still allow the application to continue running.

  • FATAL

    This level enables logging of information about very severe error events that could cause the application to stop functioning.

  • OFF

    This level disables logging for all events.

The file in which you set the log level and the log file path depend on the application server that you use:

  • For JBoss Application Server

    To enable logging:

    1. In the JBoss_home\server\default\conf\log4j.xml file, locate the following lines:

      <category name="XELLERATE">
   <priority value="log_level"/>
</category>

    2. In the second XML code line, replace log_level with the log level that you want to set. For example:

      <category name="XELLERATE">
   <priority value="INFO"/>
</category>

    After you enable logging, log information is written to the following file:

    JBoss_home\server\default\log\server.log

  • For IBM WebSphere:

    To enable logging:

    1. Add the following line in the OIM_home\xellerate\config\log.properties file:

      log4j.logger.XELLERATE=log_level

    2. In this line, replace log_level with the log level that you want to set.

      For example:

      log4j.logger.XELLERATE=INFO

    After you enable logging, log information is written to the following file:

    WebSphere_home\AppServer\logs\server_name\startServer.log

  • For BEA WebLogic

    To enable logging:

    1. Add the following line in the OIM_home\xellerate\config\log.properties file:

      log4j.logger.XELLERATE=log_level

    2. In this line, replace log_level with the log level that you want to set.

      For example:

      log4j.logger.XELLERATE=INFO

    After you enable logging, log information is written to the following file:

    WebLogic_home\user_projects\domains\domain_name\server_name\server_name.log

Step 4: Configuring the Target System

This section describes the procedures involved in configuring the target system. You may need the assistance of the SAP Basis administrator to perform some of these procedures.

Configuring the target system involves the following tasks:

Gathering Required Information

The following information is required to configure the target system:

Note:

During SAP installation, a system number and client number are assigned to the server on which the installation is carried out. These are mentioned in the following list.

  • Login details of an admin user having the permissions required to import requests

  • Client number of the server on which the request is to be imported

  • System number

  • Server IP address

  • Server name

  • User ID of the account to be used for connecting to the SAP application server

  • Password of the account to be used for connecting to the SAP application server

Creating an Entry in the BAPIF4T Table

The User Group field is one of the fields that hold user data in SAP. F4 values are values of a field that you can view and select from a list. You must create an entry in the BAPIF4T table to be able to view F4 values of the User Group field. To create this entry in the BAPIF4T table:

  1. Run the SM30 transaction on the SAP system.

  2. Enter BAPIF4T as the table name, and then click Maintain. Ignore any warnings or messages that may be displayed.

  3. Click New Entries.

  4. Enter XUCLASS as the data element and ZXL_PARTNER_BAPI_F4_AUTHORITY as the function name.

    Note:

    If an entry already exists for the XUCLASS data element, then do not change its value.

  5. Save the entry that you create, and then exit.

Importing the Request

You must import the request to create the following custom objects in the SAP system.

Object Type Object Name
Package ZBAPI
Function Group ZXLGROUP

ZXLHELPVALUES

ZXLPROFILE

ZXLROLE

ZXLUSER
Message class ZXLBAPI
Program ZF4HLP_DATA_DEFINITIONS

ZMS01CTCO

ZMS01CTCO1

ZMS01CTP2

ZXLGROUP

ZXLHELPVALUES

ZXLPROFILE

ZXLROLE

ZXLUSER
Business object types ZXLGROUP

ZXLHELP

ZXLPROFILE

ZXLROLE

ZXLUSER
Table ZXLBAPIMODE

ZXLBAPIMODM

The xlsapcar.sar file contains the definitions for these objects. When you import the request represented by the contents of the xlsapcar.sar file, these objects are automatically created in SAP. This procedure does not result in any change in the existing configuration of SAP.

Importing the request into SAP involves the following steps:

Downloading the SAPCAR Utility

The two files, Data file and Cofile, that constitute the request are compressed in the xlsapcar.sar. You can use the SAPCAR utility to extract these files.

To download the SAPCAR utility from the SAP Help Web site:

  1. Log on to the SAP Web site at

    https://service.sap.com/swdc

  2. Click OK to confirm that the certificate displayed is the certificate assigned for your SAP installation.

  3. Enter your SAP user name and password to connect to the SAP service marketplace.

  4. Click Downloads, SAP Support Packages, Entry by Application Group, and Additional Components.

  5. Select SAPCAR, SAPCAR 6.20, and the operating system. The download object is displayed.

  6. Select the Object check box, and then click Add to Download Basket.

  7. Specify the directory in which you want to download the SAPCAR utility. For example: C:\xlsapcar

Extracting the Request Files

To extract the Data file and Cofile components of the request:

  1. Copy the xlsapcar.sar file into the directory in which you download the SAPCAR utility.

    The xlsapcar.sar file is in the BAPI directory inside the installation media directory.

  2. In a command window, change to the directory in which you store the SAPCAR utility and the xlsapcar.sar file.

  3. Enter the following command to extract the Data file and Cofile components of the request:

    sapcar -xvf xlsapcar.sar

    The format of the extracted files is similar to the following:

    K900208.I46 (Cofile)

    R900208.I46 (Data file)

Performing the Request Import Operation

To perform the request import operation:

Note:

You would need the SAP Basis administrator's assistance to perform the following steps.

  1. Copy the Data file and Cofile to the required locations on the SAP server.

  2. Import the request into SAP.

  3. Check the log file to determine whether or not the import was successful.

    To display the log file:

    1. Run the STMS transaction.

      The list of transport requests is displayed.

    2. Select the transport request number corresponding to the request that you import.

      The transport request number is the same as the numeric part of the Cofile or Data file names. In Step 3 of the preceding procedure, for the sample Cofile (K900208.I46) and Data file (R900208.I46), the transport request number is 900208.

    3. Click the log file icon.

      If the return code displayed in the log file is 4, then it indicates that the import ended with warnings. This may happen if the object is overwritten or already exists in the SAP system. If the return code is 8 or a higher number, then there were errors during the import.

  4. Confirm the import of the request by running the SE80 transaction, and checking the ZBAPI package in the ABAP objects.

Step 5: Importing the Connector XML File

To import the connector XML file into Oracle Identity Manager:

  1. Open the Oracle Identity Manager Administrative and User Console.

  2. Click the Deployment Management link on the left navigation bar.

  3. Click the Import link under Deployment Management. A dialog box for locating files is displayed.

  4. Locate and open the XML file.

    • If the target system is SAP R3, then locate the SAPR3ResourceObject.xml file.

    • If the target system is BIW, then locate the SAPBIWResourceObject.xml file.

    • If the target system is SAP CRM, then locate the SAPCRMResourceObject.xml file.

    These files are in the OIM_home\Xellerate\SAP\xml directory. Details of the XML file that you select are shown on the File Preview page.

  5. Click Add File. The Substitutions page is displayed.

  6. Click Next. The Confirmation page is displayed.

  7. Click Next. The Provide IT Resource Instance Data page for the SAP R3 IT Resource IT resource is displayed.

  8. Specify values for the parameters of the SAP R3 IT Resource IT resource. Refer to the table in the "Defining IT Resources" section for information about the values to be specified.

  9. Click Next. The Provide IT Resource Instance Data page for a new instance of the SAP R3 IT Resource IT resource type is displayed.

  10. Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.

    See Also:

    If you want to define another IT resource, then refer to Oracle Identity Manager Tools Reference Guide for instructions.

  11. Click View Selections.

    The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. Remove these nodes by right-clicking each node and then selecting Remove.

  12. Click Import. The connector XML file is imported into Oracle Identity Manager.

After you import the connector XML file, proceed to the "Step 7: Compiling Adapters" section.

Defining IT Resources

You must specify values for the SAP R3 IT resource parameters listed in the following table.

Parameter Description Sample Value
SAPClient SAP client ID 800
SAPHost SAP host IP address 172.20.70.204
SAPLanguage SAP language EN
SAPUser SAP user of the target SAP system xellerate
SAPPassword Password of SAP user changethis
SAPsnc_lib Path where the crypto library is placed

This is required only if Secure Network Communication (SNC) is enabled.

 c:\\usr\\sap\\sapcrypto.dll
SAPsnc_mode If SNC is enabled on the SAP server, then set this field to 1. Otherwise, set it to 0.

Note: It is recommended that you enable SNC to secure communication with the target system.

 0
SAPsnc_myname SNC system name

This is required only if SNC is enabled.

 p:CN=TST,OU=SAP, O=ORA,c=IN
SAPsnc_partnername Domain name of the SAP server

This is required only if SNC is enabled.

 p:CN=I47,OU=SAP, O=ORA, c=IN
SAPsnc_qop Specifies the protection level (quality of protection, QOP) at which data is transferred

The default value is 3. The value can be any one of the following:

  • 1: Secure authentication only

  • 2: Data integrity protection

  • 3: Data privacy protection

  • 8: Use value from the parameter

  • 9: Use maximum value available

This is required only if SNC is enabled.

 3
SAPSystemNo SAP system number 00
SAPType Type of SAP system

For example, R3, BIW, and CRM.

This is optional.

 R3
TimeStamp For the first reconciliation run, the timestamp value is not set. For subsequent rounds of reconciliation, the time at which the previous round of reconciliation was completed is stored in this parameter. The following are sample timestamp values:

English: Jun 01, 2006 at 10:00:00 GMT+05:30

French: juin. 01, 2006 at 10:00:00 GMT+05:30

Japanese: 6 01, 2006 at 10:00:00 GMT+05:30

After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.

Step 6: Configuring Reconciliation

Configuring reconciliation involves the following steps:

Configuring Trusted Source Reconciliation

Note:

Perform this step of the procedure only if you want to configure trusted source reconciliation. Only one connector can be configured for trusted source reconciliation. If you import any of the following files while you have another trusted source configured, then both connector reconciliations would stop working:

  • SAPR3XLResourceObject.xml

  • SAPBIWXLResourceObject.xml

  • SAPCRMXLResourceObject.xml

Refer to Oracle Identity Manager Connector Framework Guide for conceptual information about reconciliation configurations.

To configure trusted source reconciliation, you must first import the XML file for trusted source reconciliation as follows:

  1. Open the Oracle Identity Manager Administrative and User Console.

  2. Click the Deployment Management link on the left navigation bar.

  3. Click the Import link under Deployment Management. A dialog box for locating files is displayed.

  4. Locate and open the SAPR3XLResourceObject.xml, SAPBIWXLResourceObject.xml, or SAPCRMXLResourceObject.xml file. These files are in the OIM_home\Xellerate\sap\xml directory. Details of the XML file that you select are shown on the File Preview page.

  5. Click Add File. The Substitutions page is displayed.

  6. Click Next. The Confirmation page is displayed.

  7. Click Import.

  8. In the message that is displayed, click Import to confirm that you want to import the XML file and then click OK.

Then, set the value of the IsTrusted reconciliation scheduled task attribute to True while performing the procedure described in the following section.

Creating the Reconciliation Scheduled Tasks

To create the scheduled tasks for lookup fields and user reconciliations:

  1. Open the Oracle Identity Manager Design Console.

  2. Expand the Xellerate Administration folder.

  3. Select Task Scheduler.

  4. Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.

  5. For the first scheduled task, enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task.

  6. Ensure that the Disabled and Stop Execution check boxes are not selected.

  7. In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.

  8. In the Interval region, set the following schedule parameters:

    • To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option.

      If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.

    • To set the task to run only once, select the Once option.

  9. Provide values for the attributes of the scheduled task. Refer to the "Specifying Values for the Scheduled Task Attributes" section for information about the values to be specified.

    See Also:

    Oracle Identity Manager Design Console Guide for information about adding and removing task attributes

  10. Click Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.

  11. Repeat Steps 5 through 10 to create the second scheduled task.

After you create both scheduled tasks, proceed to the "Step 7: Compiling Adapters" section.

Specifying Values for the Scheduled Task Attributes

This section provides information about the values to be specified for the following scheduled tasks:

Lookup Fields Reconciliation Scheduled Task

You must specify values for the following attributes of the lookup fields reconciliation scheduled task.

Note:

Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Attribute Description Sample Value
Password Default password assigned while creating the Xellerate User Dummy
Organization Default organization assigned to a new user Xellerate Users
Role Default role assigned to a new user Consultant
Xellerate Type Default type assigned to a new user End-User Administrator
ITResource Name of the IT resource for setting up a connection to the SAP User Management server SAP R3 IT Resource
ResourceObject Resource object name into which users need to be reconciled

You must ensure that the value of this attribute is the same as the decode value of the ResourceObjectName code key in the Lookup.SAP.R3.FieldNames lookup definition.

See Also: Oracle Identity Manager Design Console Guide for information about modifying lookup definitions

 SAP R3 Resource Object
Server SAP server type

The value can be R3, BIW, or CRM.

 R3

After you specify values for these task attributes, proceed to Step 10 of the procedure to create scheduled tasks.

User Reconciliation Scheduled Task

You must specify values for the following attributes of the user reconciliation scheduled task.

Note:

Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Attribute Description Sample Value
Password Default password assigned while creating the Xellerate User Dummy
Organization Default organization assigned to a new user Xellerate Users
Role Default role assigned to a new user Consultant
Xellerate Type Default type assigned to a new user End-User Administrator
ITResource Name of the IT resource for setting up a connection to the SAP User Management server SAP R3 IT Resource
ResourceObject Resource object name into which users need to be reconciled

You must ensure that the value of this attribute is the same as the decode value of the ResourceObjectName code key in the Lookup.SAP.R3.FieldNames lookup definition.

See Also: Oracle Identity Manager Design Console Guide for information about modifying lookup definitions

 SAP R3 Resource Object
IsTrusted Configuration for a trusted or nontrusted target

If it is set to True, then the target is a trusted target. If it is set to False, then the target is a nontrusted target. The default value is False.

 False
FirstTimeReconRecords Number of records to be fetched during first-time reconciliation, if the reconciliation scheduled task times out

Initially, Oracle Identity Manager tries to fetch all the records. If the process times out, then Oracle Identity Manager tries to fetch the number of records specified by this parameter. If the task times out even before this number of records are fetched, then Oracle Identity Manager tries to fetch records by recursively dividing this number by two, until all records are fetched from the target system.

 5000
Server SAP server type

The value can be R3, BIW, or CRM.

 R3

After you specify values for these task attributes, proceed to Step 10 of the procedure to create scheduled tasks.

Step 7: Compiling Adapters

The following adapters are imported into Oracle Identity Manager when you import the connector XML file:

You must compile these adapters before you can use them to provision accounts on the target system.

To compile adapters by using the Adapter Manager form:

  1. Open the Adapter Manager form.

  2. To compile all the adapters that you import into the current database, select Compile All.

    To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select Compile Selected.

    Note:

    Click Compile Previously Failed to recompile only those adapters that were not compiled successfully. Such adapters do not have an OK compilation status.

  3. Click Start. Oracle Identity Manager compiles the selected adapters.

  4. If Oracle Identity Manager is installed in a clustered environment, then copy the compiled adapters from the OIM_home\xellerate\Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.

To view detailed information about an adapter:

  1. Highlight the adapter in the Adapter Manager form.

  2. Double-click the row header of the adapter, or right-click the adapter.

  3. Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.

Note:

To compile one adapter at a time, use the Adapter Factory form. Refer to Oracle Identity Manager Tools Reference Guide for information about using the Adapter Factory and Adapter Manager forms.

Step 8: Configuring the SAP Change Password Function

You can configure the Change Password function to modify password behavior in scenarios such as when a user profile on the target system gets locked or expires. For such scenarios, you can configure the system so that the administrator is not able to reset the password for a locked or expired user profile. This helps prevent discrepancies between data in Oracle Identity Manager and the target system.

To configure the Change Password function:

See Also:

Oracle Identity Manager Design Console Guide

  1. Open the Oracle Identity Manager Design Console.

  2. Expand the Process Management folder.

  3. Open the Process Definition form.

  4. Select the SAP R3 Process process definition.

  5. Double-click the Password Updated task.

  6. On the Integration tab, specify values for the following parameters:

    • validityChange: This is a flag that can be assigned the value true or false.

      • true: If the user's validity period has expired, then it is extended to the date specified in the validityDate parameter.

      • false: If the user's validity period has expired, then it is not extended and the user's password cannot be changed.

    • lockChange: This is a flag that can be assigned the value true or false.

      • true: If the user is locked (not by the administrator), then the user is unlocked before the password is changed. If the user is locked by the administrator, then the password cannot be changed.

      • false: If the user is locked, then the password cannot be changed.

    • validityDate: This is the date up to which the user's validity must be extended. The date must be in the following format:

      Dec 28, 2005 at 11:25:00 GMT+05:30

      If this field is empty, then the user will be valid for an indefinite period.

    • userGroupCheck: This is a string literal with the following format:

      user_group_to_check, flag(1|0), user_group_to_be_updated_after_reset_password

      This parameter can be an empty string if there are no groups to check when the password is reset.

      If the password is to be changed and if the user belongs to that group, then the value of the flag is 1. If the password is not to be changed and if the user belongs to that group, then the value of the flag is 0.

      To check multiple users, add the record for each user to this string. Use the semicolon (;) as the delimiter. For example:

      user_group_to_check, flag(1|0), user_group_to_be_updated_after_reset_password;
user_group_to_check, flag(1|0), user_group_to_be_updated_after_reset_password

      For example, if there is a user group named Inactive that is to be checked when a password is changed and if the user is assigned to this group, then the user must be moved to the Active group after the password change.

      Given the preceding scenario, the setting of the userGroupCheck parameter is as follows:

      INACTIVE,1,ACTIVE;

      If there is a group named Terminated that is to be checked when a password is changed and if the user is assigned to this group, then the password change must not be permitted. Given this scenario, the setting of the userGroupCheck parameter is as follows:

      TERMINATED,0,;

      The userGroupCheck configuration parameter has only two types of user group records:

      • User group for which password change is to be done along with user group update:

        INACTIVE,1,ACTIVE;

      • User group for which password change is not to be done:

        TERMINATED,0,;

      If the user is assigned to a group that is not in the userGroupCheck parameter, then the password is changed. Password change would be permitted for all user groups that are not mentioned in the configuration parameter value.

    Note:

    The values specified are case-sensitive and must match the case in the SAP system.

Step 9: Configuring SNC to Secure Communication Between Oracle Identity Manager and the Target System

Oracle Identity Manager uses a Java application server. To connect to the SAP system application server, this Java application server uses the Java connector (sapjco.jar) and RFC (librfccm and libsapjcorfc files). If required, you can use Secure Network Communication (SNC) to secure such connections.

Note:

The Java application server used by Oracle Identity Manager can be IBM WebSphere, BEA WebLogic, or JBoss Application Server.

This section discusses the following topics:

Prerequisites for Configuring the Connector to Use SNC

The following are prerequisites for configuring the connector to use SNC:

  • SNC must be activated on the SAP application server.

  • You must be familiar with the SNC infrastructure. You must know which Personal Security Environment (PSE) the application server uses for SNC.

Installing the Security Package

To install the security package on the Java application server used by Oracle Identity Manager:

  1. Extract the contents of the SAP Cryptographic Library installation package.

    The SAP Cryptographic Library installation package is available for authorized customers on the SAP Service Marketplace Web site at

    http://service.sap.com/download

    This package contains the following files:

    • SAP Cryptographic Library (sapcrypto.dll for Microsoft Windows or libsapcrypto.ext for UNIX)

    • A corresponding license ticket (ticket)

    • The configuration tool, sapgenpse.exe

  2. Copy the library and the sapgenpse.exe file into a local directory. For example: C:\usr\sap

  3. Check the file permissions. Ensure that the user under which the Java application server runs is able to run the library functions in the directory into which you copy the library and the sapgenpse.exe file.

  4. Create the sec directory inside the directory into which you copy the library and the sapgenpse.exe file.

    Note:

    You can use any names for the directories that you create. However, creating the C:\usr\sap\sec (or /usr/sap/sec) directory is an SAP recommendation.

  5. Copy the ticket file into the sec directory. This is also the directory in which the Personal Security Environment (PSE) and credentials of the Java application server are generated.

    See Also:

    The "Configuring SNC" section

  6. Set the SECUDIR environment variable for the Java application server user to the sec directory.

    Note:

    From this point onward, the term SECUDIR directory is used to refer to the directory whose path is defined in SECUDIR environment variable.

  7. Set the SNC_LIB environment variable for the user of the Java application server to the cryptographic library directory, which is the parent directory of the sec directory.

Configuring SNC

To configure SNC:

  1. Either create a PSE or copy the SNC PSE of the SAP application server to the SECUDIR directory. To create the SNC PSE for the Java application server, use the sapgenpse.exe command-line tool as follows:

    1. To determine the location of the SECUDIR directory, run the sapgenpse command without specifying any command options. The program displays information such as the library version and the location of the SECUDIR directory.

    2. Enter a command similar to the following to create the PSE:

      sapgenpse get_pse -p PSE_Name -x PIN Distinguished_Name

      The following is a sample distinguished name:

      CN=SAPJ2EE, O=MyCompany, C=US

      The sapgenpse command creates a PSE in the SECUDIR directory.

  2. Create credentials for the Java application server.

    The Java application server must have active credentials at run time to be able to access its PSE. To check whether or not this condition is met, enter the following command in the parent directory of the SECUDIR directory:

    seclogin

    Then, enter the following command to open the PSE of the server and create the credentials.sapgenpse file:

    seclogin -p PSE_Name -x PIN -O [NT_Domain\]user_ID

    The user_ID that you specify must have administrator rights. PSE_NAME is the name of the PSE file.

    The credentials file, cred_v2, for the user specified with the -O option is created in the SECUDIR directory.

  3. Exchange the public key certificates of the two servers as follows:

    Note:

    If you are using individual PSEs for each certificate of the SAP server, then you must perform this procedure once for each SAP server certificate. This means that the number of times you must perform this procedure is equal to the number of PSEs.

    1. Export the Oracle Identity Manager certificate by entering the following command:

      sapgenpse export_own_cert -o filename.crt -p PSE_Name -x PIN

    2. Import the Oracle Identity Manager certificate into the SAP application server. You may require the SAP administrator's assistance to perform this step.

    3. Export the certificate of the SAP application server. You may require the SAP administrator's assistance to perform this step.

    4. Import the SAP application server certificate into Oracle Identity Manager by entering the following command:

      sapgenpse maintain_pk -a serverCertificatefile.crt -p PSE_Name -x PIN

  4. Configure the following parameters in the SAP R3 IT Resource IT resource object:

    • SAPsnc_lib

    • SAPsnc_mode

    • SAPsnc_myname

    • SAPsnc_partnername

    • SAPsnc_qop

    See Also:

    The "Defining IT Resources" section

Configuring the Connector for Multiple Installations of the Target System

Note:

Perform this procedure only if you want to configure the connector for multiple installations of SAP User Management. Refer to Oracle Identity Manager Design Console Guide for detailed instructions on performing each step of this procedure.

To configure the connector for multiple installations of the target system:

  1. Create and configure one resource object for each target system installation.

    The Resource Objects form is in the Resource Management folder. The SAP R3 Resource Object resource object is created when you import the connector XML file. You can use this resource object as the template for creating the remaining resource objects.

  2. Create and configure one IT resource for each resource object.

    The IT Resources form is in the Resource Management folder. The SAP R3 IT Resource IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating the remaining IT resources, of the same resource type.

  3. Design one process form for each process definition.

    The Form Designer form is in the Development Tools folder. The following process forms are created when you import the connector XML file:

    • UD_SAPR3 (SAP R3)

    • UD_SAPR3ROL (SAP R3 role form)

    • UD_SAPR3PRO (SAP R3 profile form)

    You can use these process forms as templates for creating the remaining process forms.

  4. Create and configure one process definition for each resource object.

    The Process Definition form is in the Process Management folder. The SAP R3 Process process definition is created when you import the connector XML file. You can use this process definition as the template for creating the remaining process definitions.

    While creating process definitions for each target system installation, the following steps that you must perform are specific to the creation of each process definition:

    • From the Object Name lookup field, select the resource object that you create in Step 1.

    • From the Table Name lookup field, select the process form that you create in Step 3.

    • While mapping the adapter variables for the IT Resource data type, ensure that you select the IT resource that you create in Step 2 from the Qualifier list.

  5. Configure reconciliation for each target system installation. Refer to the "Step 6: Configuring Reconciliation" section for instructions. Note that only the values of the following attributes are to be changed for each reconciliation scheduled task:

    • ITResource

    • ResourceObject

    • IsTrusted

    Set the IsTrusted attribute to True for the SAP User Management installation that you want to designate as a trusted source. You can designate either a single or multiple installations of SAP User Management as the trusted source. For the remaining SAP User Management installations, set this attribute to False.

  6. If required, modify the fields to be reconciled for the Xellerate User resource object.

When you use the Administrative and User Console to perform provisioning, you can specify the IT resource corresponding to the SAP User Management installation to which you want to provision the user.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us