Oracle® Identity Manager Connector Guide for Siebel Enterprise Applications Release 9.0.4 Part Number E10174-01 |
|
|
View PDF |
Deploying the connector involves the following steps:
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:
|
External code | For Siebel 7.5:
For Siebel 7.8:
For Siebel 8:
|
Target system user account | To create a target system user account with the required rights:
You provide the credentials of this user account while performing the procedure in the "Defining IT Resources" section. If the ERM Employee View responsibility is not assigned to this user account, then Oracle Identity Manager cannot interchange any data with the target system. |
The connector files and external code files to be copied and the directories to which you must copy them are given in the following table.
Note:
The directory paths of the connector files 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/Siebel Enterprise Applications
Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.
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 theconnectorResources
directory and the JAR files to the corresponding directories on each node of the cluster.Note:
In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.Configuring the Oracle Identity Manager server involves performing 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 (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.
While performing the instructions described in the "Step 2: Copying the Connector Files and External Code" 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. If you run the command described in Step 2 as follows, then an exception is thrown: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
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:
BEA WebLogic
To enable logging:
Add the following lines in the OIM_home
/xellerate/config/log.properties
file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.SIEBEL=log_level
In these lines, replace log_level
with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.SIEBEL=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
To enable logging:
Add the following lines in the OIM_home
/xellerate/config/log.properties
file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.SIEBEL=log_level
In these lines, replace log_level
with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.SIEBEL=INFO
After you enable logging, the log information is written to the following file:
WebSphere_home/AppServer/logs/server_name/startServer.log
JBoss Application Server
To enable logging:
In the JBoss_home
/server/default/conf/log4j.xml
file, locate or add the following lines:
<category name="XELLERATE">
<priority value="log_level"/>
</category>
<category name="XL_INTG.SIEBEL">
<priority value="log_level"/>
</category>
In the second XML code line of eac h set, replace log_level
with the log level that you want to set. For example:
<category name="XELLERATE"> <priority value="INFO"/> </category>
<category name="XL_INTG.SIEBEL"> <priority value="INFO"/> </category>
After you enable logging, the log information is written to the following file:
JBoss_home/server/default/log/server.log
OC4J
To enable logging:
Add the following lines in the OIM_home
/xellerate/config/log.properties
file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.SIEBEL=log_level
In these lines, replace log_level
with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.SIEBEL=INFO
After you enable logging, the log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log
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 files 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 locating files is displayed.
Locate and open the SiebelEmpResourceObject.xml
file, which is in the OIM_home
/xellerate/Siebel/xml
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 SIEBEL IT Resource
IT resource is displayed.
Specify values for the parameters of the SIEBEL IT Resource
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 SIEBEL IT Resource Definition
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 Tools Reference 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 files, proceed to the "Step 5: Configuring the Target System for Encryption" section.
You must specify values for the SIEBEL IT Resource
IT resource parameters listed in the following table.
Parameter | Description | Sample/Default Value |
---|---|---|
EnterpriseServer |
Name of the Enterprise server | siebel |
GatewayServer |
Name of the Gateway server | STS_TESTING |
GatewayServerPort |
Listening port number for the SCBroker component | 2321 |
Language |
Language | You can specify any one of the following:
For English: For Brazilian Portuguese: For French: For German: For Italian: For Japanese: For Korean: For Simplified Chinese: For Spanish: For Traditional Chinese: |
ObjectManager |
Name of the object manager | You can specify any one of the following:
For English: For Brazilian Portuguese: For French: For German: For Italian: For Japanese: For Korean: For Simplified Chinese: For Spanish: For Traditional Chinese: |
Password |
Password of the Siebel Enterprise Applications administrator | sadmin |
SiebelServer |
Name of the Siebel Enterprise Applications server | STS_TESTING |
UserName |
User name of the Siebel Enterprise Applications administrator | sadmin |
Encryption |
Type of encryption for secure communication
Note: The value of this parameter is case-sensitive. |
If encryption is required, then specify RSA . Otherwise, specify None . |
Version |
Version of Siebel Enterprise Applications supported by this connector | 7.5 or 7.8 |
TimeStamp |
For the first reconciliation run, the times-tamp 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:
For English: For French: For Japanese: |
CustomizedReconQuery |
Query condition on which reconciliation must be based
If you specify a query condition for this parameter, then the target system records are searched based on the query condition. If you want to reconcile all the target system records, then do not specify a value for this parameter. The query can be composed with the AND (&) and OR (|) logical operators. For more information about this parameter, refer to the "Partial Reconciliation" section. |
First Name=John&Last Name=Doe |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
Note:
Perform this procedure only if you want to use RSA encryption on the target system.You can configure encryption to secure communication between the Siebel Enterprise Applications server and Oracle Identity Manager. This section discusses the following topics related to configuring encryption:
Configuring Siebel Enterprise Applications for RSA Encryption
Configuring the Siebel Web Server Extension for RSA Encryption
Enabling RSA Encryption for the Siebel Call Center Application
This section describes how to configure Siebel Enterprise Applications to use RSA encryption for Siebel Internet Session API (SISNAPI) communication between the Siebel Enterprise Applications server and Oracle Identity Manager.
To enable RSA encryption for Siebel Enterprise Applications:
Start the Siebel Software Configuration Wizard.
This wizard is started automatically when you install Siebel Enterprise Applications. If required, you can start it manually by following instructions given in the "Starting the Siebel Software Configuration Wizard" section.
On the Encryption Type page of the wizard, select the RSA option to specify that you want to use the RSA Security Systems 128-bit strong encryption feature for Siebel Enterprise Applications components.
Review the settings, and exit the wizard.
Restart the server.
After you configure Siebel Enterprise Applications for RSA encryption, perform the same procedure to configure the Siebel Web Server Extension for RSA encryption.
To enable RSA encryption for the Siebel Call Center Application:
Start the Siebel Call Center Application.
Navigate to Sitemap, Server Administration, Components, and Component Parameters.
Query for Call Center Object Manager (ENU) in the Server Component-Parameter List applet.
In the applet, select the Encryption Type parameter and select RSA
. If RSA encryption is not required, then select None
instead of RSA
.
This section provides information about starting the Siebel Software Configuration Wizard.
The Siebel Software Configuration Wizard opens automatically after the installation of most server components. If required, you can use one of the following methods to manually start the wizard on a Microsoft Windows computer:
From the Microsoft Windows desktop:
Click Start.
Select Programs, Siebel Servers 7.0, and Configure Server_Type
, where Server_Type
is the server you want to configure. For example, Server_Type
can be Siebel Gateway.
From a command window:
In a command window, navigate to the bin
subdirectory component to configure components in the SIEBEL_ROOT
directory. For example, D://sea700/siebsrvr/bin.
Depending on the component that you want to configure, enter one of the following commands:
To configure the Siebel Database Server, enter the following command:
ssincfgw -l LANGUAGE -v y
To configure any component except the Siebel Database Server, enter the following command:
ssincfgw -l LANGUAGE
In these commands, LANGUAGE
is the language in which the Siebel Software Configuration Wizard must run. For example, ENU
for U.S. English or DEU
for German. When you run any one of these commands, a menu of configuration modules for each installed component is displayed.