2 Deploying the Connector

The following sections describe procedures involved in deploying the connector:

• Securing the JDBC Connection to the Target System Database

• Copying the External Code Files

• Installing the Connector on Oracle Identity Manager Release 9.1.0.x or Release 11.1.1

• Installing the Connector on Oracle Identity Manager Release 9.0.1 Through Release 9.0.3.x

• Configuring the Oracle Identity Manager Server

• Configuring the Target System

2.1 Securing the JDBC Connection to the Target System Database

Note:

It is recommended that you perform the procedure described in this section to secure the JDBC connection between the target system and Oracle Identity Manager.

You can establish secure JDBC connectivity with the target system database by adding the following parameters in the ORACLE_HOME/network/admin/sqlnet.ora file:

SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER= (MD5)
SQLNET.AUTHENTICATION_SERVICES= (NTS)
SQLNET.ENCRYPTION_TYPES_SERVER= (DES40C)
SQLNET.CRYPTO_SEED = xelsysadmin_seed

2.2 Copying the External Code Files

Copy the xerces class file to one of the following directories:

• For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:

  OIM_HOME/xellerate/ThirdParty

• For Oracle Identity Manager release 11.1.1:

  OIM_HOME/server/ThirdParty

Include the xerces class file in the CLASSPATH environment variable.

Copy the JDBC class library (ojdbc14.jar) from the ORACLE_HOME/ora92/jdbc/lib/ directory on the Oracle Database host machine to one of the following directories:

• For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:

  OIM_HOME/xellerate/ThirdParty

• For Oracle Identity Manager release 11.1.1:

  OIM_HOME/server/ThirdParty

In this source directory path, ORACLE_HOME is the directory in which Oracle Database is installed. For example, C:\Oracle. The actual source directory path would depend on the release of Oracle Database that you are using.

Include the following file path in the CLASSPATH environment variable:

OIM_HOME/xellerate/ThirdParty/ojdbc14.jar

2.3 Installing the Connector on Oracle Identity Manager Release 9.1.0.x or Release 11.1.1

Note:

In this guide, the term Connector Installer has been used to refer to the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.

Installing the connector on Oracle Identity Manager release 9.1.0.x or release 11.1.1 or later involves the following procedures:

• Running the Connector Installer

• Copying Files to the Oracle Identity Manager Host Computer

• Configuring the IT Resource

2.3.1 Running the Connector Installer

To run the Connector Installer:

1. 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.

   • For Oracle Identity Manager release 9.1.0.x: OIM_HOME/xellerate/ConnectorDefaultDirectory

   • For Oracle Identity Manager release 11.1.1: OIM_HOME/server/ConnectorDefaultDirectory

2. Log in to the Administrative and User Console by using the user account described in the "Creating the User Account for Installing Connectors" section of the following guide:

   • For Oracle Identity Manager release 9.1.0.x:

     Oracle Identity Manager Administrative and User Console Guide

   • For Oracle Identity Manager release 11.1.1:

     Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager

3. Depending on the Oracle Identity Manager release you are using, perform one of the following steps:

   • For Oracle Identity Manager release 9.1.0.x:

     Click Deployment Management, and then click Install Connector.

   • For Oracle Identity Manager release 11.1.1:

     On the Welcome to Identity Manager Advanced Administration page, in the System Management region, click Install Connector.

4. From the Connector List list, select Oracle Retail Warehouse Management System 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:

   1. In the Alternative Directory field, enter the full path and name of that directory.

   2. To repopulate the list of connectors in the Connector List list, click Refresh.

   3. From the Connector List list, select Oracle Retail Warehouse Management System RELEASE_NUMBER.

5. Click Load.

6. To start the installation process, click Continue.

   The following tasks are performed in sequence:

   1. Configuration of connector libraries

   2. Import of the connector Target Resource user configuration XML file (by using the Deployment Manager). If you want to import the target system as a trusted source for reconciliation, then see the "Configuring Trusted Source Reconciliation" section .

   3. 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 0.

7. 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:

   1. 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 the "Clearing Content Related to Connector Resource Bundles from the Server Cache" section for information about running the PurgeCache utility.

      There are no prerequisites for some predefined connectors.

   2. 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.

   3. Configuring the scheduled tasks that are created when you installed the connector

      Note:

      In Oracle Identity Manager release 11.1.1, a scheduled job is an instance of a scheduled task. In this guide, the term scheduled task used in the context of Oracle Identity Manager release 9.1.0.x is the same as the term scheduled job in the context of Oracle Identity Manager release 11.1.1.

      See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about scheduled tasks and scheduled jobs.

      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 1-1.

Installing the Connector in an Oracle Identity Manager Cluster

While installing Oracle Identity Manager in a cluster, you must copy all the JAR files and the contents of the connectorResources directory into the corresponding directories on each node of the cluster. See Section 1.6, "Files and Directories That Comprise the Connector" for information about the files that you must copy and their destination locations on the Oracle Identity Manager host computer.

2.3.2 Copying Files to the Oracle Identity Manager Host Computer

After you run the Connector Installer, you must manually copy the files listed in Table 1-1.

Note:

If a particular destination directory does not exist on the Oracle Identity Manager host computer, then create it.

Table 2-1 Files to Be Copied to the Oracle Identity Manager Host Computer

Files on the Installation Media	Destination Directory on the Oracle Identity Manager Release 9.1.0.x Host Computer	Destination Directory on the Oracle Identity Manager Release 11.1.1 Host Computer
Files in the config directory	OIM_HOME/xellerate/XLIntegrations/RWMS/config	OIM_HOME/server/XLIntegrations/RWMS/config
Files in the test/config directory	OIM_HOME/xellerate/XLIntegrations/RWMS/config	OIM_HOME/server/XLIntegrations/RWMS/config
Files in the test/scripts directory	OIM_HOME/xellerate/XLIntegrations/RWMS/scripts	OIM_HOME/server/XLIntegrations/RWMS/scripts

2.3.3 Configuring the IT Resource

You must specify values for the parameters of the RWMS IT resource as follows:

1. Log in to the Administrative and User Console.

2. If you are using Oracle Identity Manager release 9.1.0.x, expand Resource Management, and then click Manage IT Resource.

3. If you are using Oracle Identity Manager release 11.1.1, 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.

4. In the IT Resource Name field on the Manage IT Resource page, enter RWMS and then click Search.

5. Click the edit icon for the IT resource.

6. From the list at the top of the page, select Details and Parameters.

7. Specify values for the parameters of the IT resource. Table 2-2 describes each parameter.

   Table 2-2 IT Resource Parameters

   Parameter	Description
   Host	Host name or IP address of the Oracle Retail Warehouse Management System server
   Port	TCP/IP port at which the Oracle Retail Warehouse Management System server is listening The default value is 0.
   Admin	User ID to connect to the Oracle Retail Warehouse Management System database
   Admin Credential	Password of the administrator
   SID	SID for the Oracle Retail Warehouse Management System database
   IsSecure	Specifies whether or not the SSL feature is enabled The value can be YES or NO. The default value is YES.
   Schema Name	Name of the schema owner of the Oracle Retail Warehouse Management System

   
   

8. To save the values, click Update.

2.4 Installing the Connector on Oracle Identity Manager Release 9.0.1 Through Release 9.0.3.x

Note:

Perform the procedure described in this section only if you are installing the connector on any Oracle Identity Manager release from 9.0.1 through 9.0.3.x.

Installing the connector on an Oracle Identity Manager release from 9.0.1 through 9.0.3.x involves the following procedures:

• Copying the Connector Files and External Code Files

• Importing the Connector XML File

2.4.1 Copying the Connector Files and External Code Files

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

See Also:

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

File in the Installation Media Directory	Destination Directory
Files in the config directory	OIM_HOME/xellerate/XLIntegrations/RWMS/config
lib/rwmsadapter.jar	OIM_HOME/xellerate/JavaTasks OIM_HOME/xellerate/ScheduleTask
File in the resources directory	OIM_HOME/xellerate/connectorResources
scripts/RWMS.xml	OIM_HOME/xellerate/XLIntegrations/RWMS/Config
scripts/DB Schema XML/xdb_app_map.xsd	OIM_HOME/xellerate/XLIntegrations/RWMS
Files in the scripts/RWMSTrigger directory	OIM_HOME/xellerate/RWMSTrigger
Files in the test/config directory	OIM_HOME/xellerate/XLIntegrations/RWMS/config
Files in the test/scripts directory	OIM_HOME/xellerate/XLIntegrations/RWMS/scripts
xml/xlRWMSNonTrusted.xml xml/xlRWMSTrusted.xml	OIM_HOME/xlclient

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 contents of the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.

2.4.2 Importing the Connector XML File

As mentioned in the "Files and Directories That Comprise the Connector" section, the connector XML file contains definitions of the components of the connector. By importing the connector XML file, you create these components in Oracle Identity Manager.

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 opening files is displayed.

4. Locate and open the xlRWMSNonTrusted.xml file, which is in the OIM_HOME\xlclient directory. Details of this XML file 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 RWMS IT resource is displayed.

8. Specify values for the parameters of the IT resource. See the table in the "Configuring the IT Resource" 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 RWMS 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 Administrative and User Console 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. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities 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 next chapter.

2.5 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

• Clearing Content Related to Connector Resource Bundles from the Server Cache

• Enabling Logging

• Configuring Oracle Identity Manager for Request-Based Provisioning

2.5.1 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.

You may require the assistance of the system administrator to change to the required input locale.

2.5.2 Clearing Content Related to Connector Resource Bundles from the Server Cache

Note:

In an Oracle Identity Manager cluster, you must perform this step on each node of the cluster. Then, restart each node.

When you deploy the connector, the resource bundles are copied from the resources directory on the installation media into the OIM_HOME/xellerate/connectorResources directory for Oracle Identity Manager release 9.0.3.x and release 9.1.0.x, and Oracle Identity Manager database for Oracle Identity Manager release 11.1.1. 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:

1. In a command window, perform one of the following steps:

   • If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then switch to the OIM_HOME/xellerate/bin directory.

   • If you are using Oracle Identity Manager release 11.1.1, then switch to the OIM_HOME/server/bin directory.

   Note:

   You must perform Step 1 before you perform Step 2. An exception is thrown if you run the command described in Step 2 as follows:

   For Oracle Identity Manager release 9.0.3.x or release 9.1.0.x:

   OIM_HOME/xellerate/bin/SCRIPT_FILE_NAME
   

   For Oracle Identity Manager release 11.1.1:

   OIM_HOME/server/bin/SCRIPT_FILE_NAME
   

2. Enter one of the following commands:

   Note:

   You can use the PurgeCache utility to purge the cache for any content category. Run PurgeCache.bat CATEGORY_NAME on Microsoft Windows or PurgeCache.sh CATEGORY_NAME on UNIX. The CATEGORY_NAME argument represents the name of the content category that must be purged.

   For example, the following commands purge Metadata entries from the server cache:

   PurgeCache.bat MetaData

   PurgeCache.sh MetaData

   • For Oracle Identity Manager release 9.0.3.x or release 9.1.0.x:

     On Microsoft Windows: PurgeCache.bat ConnectorResourceBundle

     On UNIX: PurgeCache.sh ConnectorResourceBundle

     Note:

     You can ignore the exception that is thrown when you perform Step 2. This exception is different from the one mentioned in Step 1.

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

     OIM_HOME/xellerate/config/xlconfig.xml

   • For Oracle Identity Manager release 11.1.1:

     On Microsoft Windows: PurgeCache.bat All

     On UNIX: PurgeCache.sh All

     When prompted, enter the user name and password of an account belonging to the SYSTEM ADMINISTRATORS group. In addition, you are prompted to enter the service URL in the following format:

     t3://OIM_HOST_NAME:OIM_PORT_NUMBER
     

     In this format:

     • Replace OIM_HOST_NAME with the host name or IP address of the Oracle Identity Manager host computer.

     • Replace OIM_PORT_NUMBER with the port on which Oracle Identity Manager is listening.

   See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about the PurgeCache utility.

2.5.3 Enabling Logging

Depending on the Oracle Identity Manager release you are using, perform instructions in one of the following sections:

• Enabling Logging on Oracle Identity Manager Release 9.0.1 through 9.0.3.x or Release 9.1.0.x

• Enabling Logging on Oracle Identity Manager Release 11.1.1

2.5.3.1 Enabling Logging on Oracle Identity Manager Release 9.0.1 through 9.0.3.x or Release 9.1.0.x

Note:

In an Oracle Identity Manager cluster, perform this procedure on each node of the cluster. Then, restart each node.

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 messages that highlight the progress of the application at a 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 might 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:

• IBM WebSphere Application Server

  To enable logging:

  1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

     log4j.logger.RWMSAdapterLogger=log_level
     

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

     For example:

     log4j.logger.RWMSAdapterLogger=INFO
     

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

  WEBSPHERE_HOME/AppServer/logs/server_name/startServer.log
  

• JBoss Application Server

  To enable logging:

  1. In the JBOSS_HOME/server/default/conf/log4j.xml file, locate the following lines:

     <category name="RWMSAdapterLogger">
        <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="RWMSAdapterLogger">
        <priority value="INFO"/>
     </category>
     

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

  JBOSS_HOME/server/default/log/server.log
  

• Oracle Application Server

  To enable logging:

  1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

     log4j.logger.RWMSAdapterLogger=log_level
     

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

     For example:

     log4j.logger.RWMSAdapterLogger=INFO
     

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

  OAS_HOME/opmn/logs/default_group~home~default_group~1.log
  

• Oracle WebLogic Server

  To enable logging:

  1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

     log4j.logger.RWMSAdapterLogger=log_level
     

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

     For example:

     log4j.logger.RWMSAdapterLogger=INFO
     

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

  WEBLOGIC_HOME/user_projects/domains/domain_name/server_name/server_name.log
  

2.5.3.2 Enabling Logging on Oracle Identity Manager Release 11.1.1

Note:

In an Oracle Identity Manager cluster, perform this procedure on each node of the cluster. Then, restart each node.

Oracle Identity Manager release 11.1.1 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 log levels are mapped to ODL message type and level combinations as shown in Table 2-3.

Table 2-3 Log Levels and ODL Message Type:Level Combinations

Log 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_SERVER are the domain name and server name specified during the installation of Oracle Identity Manager.

To enable logging in Oracle WebLogic Server:

1. Edit the logging.xml file as follows:

   1. Add the following blocks in the file:

      <log_handler name='rwms-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="RWMSAdapterLogger" level="[LOG_LEVEL]" useParentHandlers="false">
           <handler name="rwms-handler"/>
           <handler name="console-handler"/>
         </logger>
      

   2. Replace both occurrences of [LOG_LEVEL] with the ODL message type and level combination that you require. Table 2-3 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='rwms-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="RWMSAdapterLogger" level="NOTIFICATION:1" useParentHandlers="false">
           <handler name="rwms-handler"/>
           <handler name="console-handler"/>
         </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.

2. Save and close the file.

3. 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.

4. Restart the application server.

2.5.4 Configuring Oracle Identity Manager for Request-Based Provisioning

Note:

Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.1 and you want to configure request-based provisioning.

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.

The following are features of request-based provisioning:

• A user can be provisioned only one resource (account) on the target system.

  Note:

  Direct provisioning allows the provisioning of multiple target system accounts on the target system.

• Direct provisioning cannot be used if you enable request-based provisioning.

To configure request-based provisioning, perform the following procedures:

• Copying Predefined Request Datasets

• Importing Request Datasets into MDS

• Enabling the Auto Save Form Feature

• Running the PurgeCache Utility

2.5.4.1 Copying Predefined Request Datasets

A request dataset is an XML file that specifies the information to be submitted by the requester during a provisioning operation. Predefined request datasets are shipped with this connector. These request datasets specify information about the default set of attributes for which the requester must submit information during a request-based provisioning operation. The following are the predefined request datasets available in the dataset directory on the installation media:

• ProvisionResource_RWMSRO.xml

• ModifyProvisionedResource_RWMSRO.xml

Copy these files from the installation media to any directory on the Oracle Identity Manager host computer. It is recommended that you create a directory structure as follows:

/custom/connector/RESOURCE_NAME

For example:

E:\MyDatasets\custom\connector\ORWMS

Note:

Until you complete the procedure to configure request-based provisioning, ensure that there are no other files or directories inside the parent directory in which you create the directory structure. In the preceding example, ensure that there are no other files or directories inside the E:\MyDatasets directory.

The directory structure to which you copy the dataset files is the MDS location into which these files are imported after you run the Oracle Identity Manager MDS Import utility. The procedure to import dataset files is described in the next section.

Depending on your requirement, you can modify the file names of the request datasets. In addition, you can modify the information in the request datasets. See Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for information on modifying request datasets.

2.5.4.2 Importing Request Datasets into MDS

All request datasets must be imported into the metadata store (MDS), which can be done by using the Oracle Identity Manager MDS Import utility.

To import a request dataset definition into MDS:

1. Ensure that you have set the environment for running the MDS Import utility. See Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for detailed information about setting up the environment for MDS utilities.

   Note:

   While setting up the properties in the weblogic.properties file, ensure that the value of the metadata_from_loc property is the parent directory of the /custom/connector/RESOURCE_NAME directory. For example, while performing the procedure in Section 2.5.4.1, "Copying Predefined Request Datasets," if you copy the files to the E:\MyDatasets\custom\connector\ORWMS directory, then set the value of the metada_from_loc property to E:\MyDatasets.

2. In a command window, change to the OIM_HOME\server\bin directory.

3. Run one of the following commands:

   • On Microsoft Windows

     weblogicImportMetadata.bat
     

   • On UNIX

     weblogicImportMetadata.sh
     

4. When prompted, enter the following values:

   • Please enter your username [weblogic]

     Enter the username used to log in to the WebLogic server

     Sample value: WL_User

   • Please enter your password [weblogic]

     Enter the password used to log in to the WebLogic server.

   • Please enter your server URL [t3://localhost:7001]

     Enter the URL of the application server in the following format:

     t3://HOST_NAME_IP_ADDRESS:PORT

     In this format, replace:

     • HOST_NAME_IP_ADDRESS with the host name or IP address of the computer on which Oracle Identity Manager is installed.

     • PORT with the port on which Oracle Identity Manager is listening.

   The request dataset is imported into MDS.

2.5.4.3 Enabling the Auto Save Form Feature

To enable the Auto Save Form feature:

1. Log in to the Design Console.

2. Expand Process Management, and then double-click Process Definition.

3. Search for and open the RWMSProcess process definition.

4. Select the Auto Save Form check box.

5. Click the Save icon.

2.5.4.4 Running the PurgeCache Utility

Run the PurgeCache utility to clear content belonging to the Metadata category from the server cache. See Section 2.5.2, "Clearing Content Related to Connector Resource Bundles from the Server Cache" for instructions.

The procedure to configure request-based provisioning ends with this step.

2.6 Configuring the Target System

Configuring the target system involves the following steps:

1. Copy the scripts/RWMSTrigger/TriggerRWMS.sql file from the installation media directory to a temporary directory on the target system.

   Note:

   This file is mentioned in the "Files and Directories That Comprise the Connector" section.

2. Open the TriggerRWMS.sql file in a text editor, and change the following line in the file:

   ALTER SESSION SET CURRENT_SCHEMA=<SchemaOwnerName>
   

   In this line, replace <SchemaOwnerName> with the name of the schema owner of the Oracle Retail Warehouse Management System database tables.

3. Log in to the Oracle Retail Warehouse Management System database by using Oracle SQL*Plus.

4. At the SQL prompt, copy the SQL code from the TriggerRWMS.sql file.

5. Run the SQL code to create the table and trigger that is used to implement reconciliation of deleted user accounts.