2 Deploying the Connector

Deploying the connector involves the following steps:

Step 1: Verifying Deployment Requirements
Step 2: Configuring the Target System
Step 3: Copying the Connector Files and External Code Files
Step 4: Configuring the Oracle Identity Manager Server
Step 5: Importing the Connector XML File

2.1 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.1 or later
Target systems	Oracle Retail Warehouse Management System release 12.0

An Oracle Database user can create users in Oracle Retail Warehouse Management System. The CONNECT and RESOURCE privileges must be granted to this Oracle Database user from the system administrator:

The following table specifies the privileges that the user must have on some of the Oracle Retail Warehouse Management System tables.

Table Name	Select	Insert	Delete	Update
DMS_USER	Yes	Yes	Yes	Yes
FACILITY	Yes
SUPPORTED_LANGUAGE	Yes
DC_DEPARTMENT	Yes
USER_CLASS	Yes

In addition to the requirements mentioned in the preceding table, you must ensure that the following requirements are addressed:

JDBC connectivity is available to the target database.
The JDBC driver and xerces class files are included in the CLASSPATH environment variable on the Oracle Identity Manager server.
For secure connectivity to the target system database, the required configuration has been performed on the target server.

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 Step 2: Configuring the Target System

Configuring the target system involves the following steps:

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.
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.
Log in to the Oracle Retail Warehouse Management System database by using Oracle SQL*Plus.
At the SQL prompt, copy the SQL code from the TriggerRWMS.sql file.
Run the SQL code to create the table and trigger that is used to implement reconciliation of deleted user accounts.

2.3 Step 3: 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.

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/Oracle Retail Applications/Oracle Retail Warehouse Mgmt

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

Copy the JDBC class library (ojdbc14.jar) from the ORACLE_HOME/ora92/jdbc/lib/ directory to the OIM_HOME/xellerate/ThirdParty directory. 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

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 Step 4: 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

2.4.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.4.2 Clearing Content Related to Connector Resource Bundles from the Server Cache

While performing the instructions described in the "Step 3: Copying the Connector Files and External Code Files" section, you copy files from the resources directory on the installation media into the OIM_HOME/xellerate/connectorResources directory. Whenever you add a new resource bundle in 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:

In a command window, change to the OIM_HOME/xellerate/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:
```
OIM_HOME/xellerate/bin/batch_file_name
```
Enter one of the following commands:
- 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.

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
```

2.4.3 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 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 may 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:

BEA WebLogic Server

To enable logging:
1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:
```
log4j.logger.Adapter.RWMSAdapterLogger=log_level
```
2. In this line, replace log_level with the log level that you want to set.
  
  For example:
```
log4j.logger.Adapter.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
```
IBM WebSphere Application Server

To enable logging:
1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:
```
log4j.logger.Adapter.RWMSAdapterLogger=log_level
```
2. In this line, replace log_level with the log level that you want to set.
  
  For example:
```
log4j.logger.Adapter.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="Adapter.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="Adapter.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.Adapter.RWMSAdapterLogger=log_level
```
2. In this line, replace log_level with the log level that you want to set.
  
  For example:
```
log4j.logger.Adapter.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
```

2.5 Step 5: 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:

Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for opening files is displayed.
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.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the RWMS IT resource is displayed.
Specify values for the parameters of the IT resource. Refer to the table in the "Defining IT Resources" section for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the RWMS IT resource type is displayed.
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.
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.
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.1 Defining IT Resources

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

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

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