The procedure to deploy the connector is divided across three stages namely preinstallation, installation, postinstallation. upgrading the Oracle Internet Directory Connector, and cloning the Oracle Internet Directory Connector.
The following topics discuss these stages:
Preinstallation of the Oracle Internet Directory connector involves creating a target system user account for creating, modifying, and deleting entries related to the managed objects, including accounts, groups, roles (if supported), and organizational units (OU), update passwords for users; installing and configuring the connector server; running the connector server; configuring SSL for the connector; and enabling logging for the connector.
Preinstallation information is divided across the following sections:
The connector uses a target system account to connect to the target system during reconciliation and provisioning operations. Preinstallation involves creating a target system user account for performing the following functions:
Create, modify, and delete entries related to the managed objects, including accounts, groups, roles (if supported), and organizational units (ou).
Update passwords for users.
Use paging controls that have been configured in the IT resource.
Depending on the target system, create the specific target system account for connector operations as follows:
Create an admin user account on the ODSEE target system.
Create an admin user account on the OUD target system.
Create an admin user, admin group, and ACIs on the OID target system.
To perform this task, you must be an administrator on the OID target system who is familiar with command-line utilities such as ldapsearch
and ldapmodify
. If you prefer, you can also use Oracle Directory Services Manager to perform these functions.
Create an admin user account on the eDirectory target system.
The detailed instructions for performing these preinstallation tasks are available in the product documentation of the target system.
This section contains the following topics:
You can deploy this connector either locally in Oracle Identity Manager or remotely in the Connector Server. A Connector Server enables remote execution of an Identity Connector.
Connector Servers are available in two implementations:
As a .Net implementation that is used by Identity Connectors implemented in .Net
As a Java implementation that is used by Java-based Identity Connectors
Use the following steps to install and configure the Java Connector Server:
Note:
Before you deploy the Java Connector Server, ensure that you install JDK or JRE on the same computer where you are installing the Java Connector Server and that your JAVA_HOME or JRE_HOME environment variable points to this installation.
Note:
Oracle Identity Manager has no built-in support for testing the Connector Server configuration.
This section describes how to run the Connector Server, depending on your operating system:
See Also:
Using the Java Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for more information about a Java Connector Server.
To run the Connector Server on UNIX and Linux systems, use the connectorserver.sh script, as follows:
This section describes how to configure SSL for the connector, including:
Caution:
Configuring SSL is an optional procedure; however, it is recommended that you configure SSL. If you do not configure SSL, passwords can be transmitted over the network in clear text. For example, this problem can occur when you are creating a user or modifying a user's password.
This section describes the following topics:
This section contains the following topics:
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. Oracle Identity Manager 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, 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 prevent Oracle Identity Manager from running.
WARNING
This level enables logging of information about potentially harmful situations.
INFO
This level enables logging of messages that highlight the progress of the application.
CONFIG
This level enables logging of information about fine-grained events that are useful for debugging.
FINE, FINER, FINEST
These levels enable logging of information about fine-grained events, where FINEST logs information about all events.
These message types are mapped to ODL message type and level combinations as shown in Table 2-1.
Table 2-1 Log Levels and ODL Message Type: Level Combinations
Java Level | ODL Message Type:Level |
---|---|
SEVERE.intValue()+100 |
INCIDENT_ERROR:1 |
SEVERE |
ERROR:1 |
WARNING |
WARNING:1 |
INFO |
NOTIFICATION:1 |
CONFIG |
NOTIFICATION:16 |
FINE |
TRACE:1 |
FINER |
TRACE:16 |
FINEST |
TRACE:32 |
The configuration file for OJDL is logging.xml, which is located at the following path:
DOMAIN_HOME/config/fmwconfig/servers/OIM_SERVER/logging.xml
Here, DOMAIN_HOME and OIM_SEVER are the domain name and server name specified during the installation of Oracle Identity Manager.
To enable logging on Oracle WebLogic Server:
Edit the logging.xml file as follows:
Add the following blocks in the file:
<log_handler name='OIMCP.LDAP' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='[FILE_NAME]'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler>
<logger name="ORG.IDENTITYCONNECTORS.LDAP" level="[LOG_LEVEL]" useParentHandlers="false">
<handler name="OIMCP.LDAP"/>
<handler name="console-handler"/>
</logger>
Replace both occurrences of [LOG_LEVEL] with the ODL message type and level combination that you require. Table 2-1 lists the supported message type and level combinations.
Similarly, replace [FILE_NAME] with the full path and name of the log file in which you want log messages to be recorded.
The following blocks show sample values for [LOG_LEVEL] and [FILE_NAME]:
<log_handler name='OIMCP.LDAP' level='NOTIFICATION:1' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\oim_server1-diagnostic-1.log'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler>
<logger name="ORG.IDENTITYCONNECTORS.LDAP" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="OIMCP.LDAP"/>
<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.
Save and close the file.
Set the following environment variable to redirect the server logs to a file:
For Microsoft Windows:
set WLS_REDIRECT_LOG=FILENAME
For UNIX:
export WLS_REDIRECT_LOG=FILENAME
Replace FILENAME with the location and name of the file to which you want to redirect the output.
Restart the application server.
This section contains the following topics:
When you enable logging, the connector server stores in a log file information about events that occur during the course of provisioning and reconciliation operations for different statuses. By default, the connector server logs are set at INFO level and you can change this level to any one of the following:
Error
This level enables logging of information about errors that might allow connector server 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 operation.
FINE, FINER, FINEST
These levels enable logging of information about fine-grained events, where FINEST logs information about all events.
You must install the Oracle Internet Directory connector in Oracle Identity Manager and if required, place the connector code bundle in the Connector Server.
Depending on where you want to run the connector code (bundle), the connector provides the following installation options:
To run the connector code locally in Oracle Identity Manager, perform the procedure described in Installing the Connector in Oracle Identity Manager.
To run the connector code remotely in a Connector Server, perform the procedures described in Installing the Connector in Oracle Identity Manager and Installing the Connector in the Connector Server.
Installation on Oracle Identity Manager consists of the following procedures:
To run the Connector Installer:
Copy the contents of the connector installation media directory into the following directory:
OIM_HOME/server/ConnectorDefaultDirectory
If you are using Oracle Identity Manager release 11.1.1.x, then:
Log in to the Administrative and User Console by using the user account described in Creating the User Account for Installing Connectors in Oracle Fusion Middleware Administering Oracle Identity Manager.
On the Welcome to Identity Manager Advanced Administration page, in the System Management region, click Manage Connector.
If you are using Oracle Identity Manager release 11.1.2.x or later, then:
Log in to Oracle Identity System Administration.
In the left pane, under System Management, click Manage Connector.
In the Connector Management page, click Install.
From the Connector List list, select OID/LDAP/EDIR Connector RELEASE_NUMBER.
This list displays the names and release numbers of connectors whose installation files you copied into the default connector installation directory in Step 1. Select the connector for your specific target system.
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select ODSEE/OUD/LDAPV3 Connector RELEASE_NUMBER.
Click Load.
To start the installation process, click Continue.
The following tasks are performed, in sequence:
Configuration of Connector Libraries
Import of the Connector XML Files (Using Deployment Manager)
Compilation of Adapter Definitions
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 is displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 1.
If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of steps that you must perform after the installation is displayed. These steps are as follows:
Ensuring that the prerequisites for using the connector are addressed
Note:
At this stage, run the Oracle Identity Manager PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. See Clearing Content Related to Connector Resource Bundles from the Server Cache for information about running the PurgeCache utility.
There are no prerequisites for some predefined connectors.
Configuring the IT resource for the connector
The procedure to configure the IT resource is described later in this guide.
Configuring the scheduled jobs
The procedure to configure these scheduled jobs is described later in this guide.
When you run the Connector Installer, it copies the connector files to destination directories on the Oracle Identity Manager host computer. These files are listed in Files and Directories on the OID Connector Installation Media.
Note:
If you have configured your target system as a trusted source, then create an IT resource of type OID. For example, OID Trusted. The parameters of this IT resource are the same as the parameters of the IT resources described in Table 2-2 of this section. See Creating IT Resources in Oracle Fusion Middleware Administering Oracle Identity Manager for more information about creating an IT resource.
The IT resource for the target system is created during connector installation. This IT resource contains connection information about the target system. Oracle Identity Manager uses this information during reconciliation and provisioning.
You must specify values for the parameters of the target system IT resource as follows:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 11.1.1.x:
Log in to the Administrative and User Console
For Oracle Identity Manager release 11.1.2.x or later:
Log in to Oracle Identity System Administration
If you are using Oracle Identity Manager release 11.1.1.x, then:
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Manage IT Resource.
If you are using Oracle Identity Manager release 11.1.2.x or later, then:
Create and activate a sandbox. For detailed instructions on creating and activating a sandbox, see Managing Sandboxes of Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
In the left pane, under Configuration, click IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter DSEE Server, OID Server,
or eDirectory Server
and click Search.
Alternatively, from the IT Resource Type list, you can select LDAP, OID Server, or eDirectory Server and then click Search. Figure 2-1 shows the Manage IT Resource page.
Click the edit icon corresponding to the DSEE Server or OID Server IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the IT resource. Figure 2-2 shows the Edit IT Resource Details and Parameters page.
Figure 2-2 Edit IT Resource Details and Parameters Page for the Target System IT Resource
Table 2-2 describes each parameter of the IT resource.
Table 2-2 Parameters of the IT Resource for the Target System
Parameter | Description |
---|---|
host |
Enter the host name or IP address of the target system. Sample values:
|
port |
Enter the port number to connect to the target system. Sample value: |
ssl |
Specifies whether communication with the target system must be secured using SSL. Default value: Note: You can set the value to true, when SSL is enabled between Oracle Identity Manager and the Connector Server or between Oracle Identity Manager and the target system.To configure SSL between Oracle Identity Manager and the Connector Server, see the "connectorserver.usessl" property in Step 4 of Installing and Configuring the Connector Server. See also Configuring SSL for the Connector. |
principal |
Enter the bind DN for performing operations on the target system. For example: For ODSEE or OUD: For OID: For eDirectory: Note. For eDirectory, the bind DN should be the complete DN name. |
credentials |
Enter the bind password associated with the bind DN. |
failover |
Enter the complete URL of LDAP backup server or servers that the connector must switch to if the primary LDAP server fails or becomes unavailable. The URL is a fully qualified host name or an IP address in the following format: ldap://host:port The following example shows an IP address for one backup LDAP server: If you specify more than one URL, each URL must be enclosed in double quotes (") and separated by a comma (,). For example:
|
baseContexts |
Enter the base contexts for operations on the target system. Sample value: Note: In a multilevel base context, each base context must be specified within double quotes (") and separated by a comma (,). For example, |
Configuration Lookup |
Enter the name of the lookup definition that stores configuration information used during reconciliation and provisioning. If you have configured your target system as a target resource, then enter one of the following values:
If you have configured your target system as a trusted source, then enter one of the following values:
|
Connector Server Name |
Name of the IT resource of the type "Connector Server." You create an IT resource for the Connector Server in Creating the IT Resource for the Connector Server. Note: Enter a value for this parameter only if you have deployed this connector in the Connector Server. |
To save the values, click Update.
To deploy the connector bundle remotely in a Connector Server, you must first deploy the connector in Oracle Identity Manager, as described in Installing the Connector in Oracle Identity Manager.
Note:
You can download the Connector Server from the Oracle Technology Network web page. If you need to set up the Connector Server, see Installing and Configuring the Connector Server.
To install the connector in the Connector Server:
Postinstallation steps are divided across the following sections:
Configuring Oracle Identity Manager involves performing the following procedures:
Note:
You need not perform the procedures described in this section if you have configured your target system as a trusted source.
If you are using Oracle Identity Manager release 11.1.2 or later, you must create additional metadata such as a UI form and an application instance. In addition, you must run entitlement and catalog synchronization jobs. These procedures are described in the following sections:
Create and activate a sandbox as follows. For detailed instructions, see Managing Sandboxes of Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
Create a new UI form as follows. For detailed instructions, see Managing Forms in Oracle Fusion Middleware Administering Oracle Identity Manager.
Create an application instance as follows. For detailed instructions, see Managing Application Instances in Oracle Fusion Middleware Administering Oracle Identity Manager.
To publish the sandbox that you created in Creating and Activating a Sandbox:
To harvest entitlements and sync catalog:
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.2.x or later and you want to localize UI form field labels.
To localize field label that is added to the UI forms:
Log in to Oracle Enterprise Manager.
In the left pane, expand Application Deployments and then select oracle.iam.console.identity.sysadmin.ear.
In the right pane, from the Application Deployment list, select MDS Configuration.
On the MDS Configuration page, click Export and save the archive to the local computer.
Extract the contents of the archive, and open one of the following files in a text editor:
For Oracle Identity Manager 11g Release 2 PS2 (11.1.2.2.0):
SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle_en.xlf
For releases prior to Oracle Identity Manager 11g Release 2 PS2 (11.1.2.2.0):
SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle.xlf
Edit the BizEditorBundle.xlf file in the following manner:
Search for the following text:
<file source-language="en" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Replace with the following text:
<file source-language="en" target-language="LANG_CODE"
original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf"
datatype="x-oracle-adf">
In this text, replace LANG_CODE with the code of the language that you want to localize the form field labels. The following is a sample value for localizing the form field labels in Japanese:
<file source-language="en" target-language="ja" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Search for the application instance code. This procedure shows a sample edit for Oracle Internet Directory application instance. The original code is:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_OID_USR_FNAME__c_description']}"> <source>Username</source> </target> </trans-unit> <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.adform.entity.oidformEO.UD_OID_USR_FNAME__c_LABEL"> <source>Username</source> </target> </trans-unit>
Open the resource file from the connector package, for example OID_ja.properties, and get the value of the attribute from the file, for example, global.udf.UD_OID_USR_FNAME=\u540D.
Replace the original code shown in Step 6.b with the following:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_OID_USR_FNAME__c_description']}"> <source>Username</source> <target>\u30E6\u30FC\u30B6\u30FC\u540D</target> </trans-unit> <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.OracleDBForm.entity.OracleDBForm.UD_OID_USR_FNAME__c_LABEL"> <source>Username</source> <target>\u30E6\u30FC\u30B6\u30FC\u540D</target> </trans-unit>
Repeat Steps 6.a through 6.d for all attributes of the process form.
Save the file as BizEditorBundle_LANG_CODE.xlf. In this file name, replace LANG_CODE with the code of the language to which you are localizing.
Sample file name: BizEditorBundle_ja.xlf.
Repackage the ZIP file and import it into MDS.
See Also:
Deploying and Undeploying Customizations in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager, for more information about exporting and importing metadata files
Log out of and log in to Oracle Identity Manager.
When you deploy the connector, the resource bundles are copied from the resources directory on the installation media into the Oracle Identity Manager database. Whenever you add a new resource bundle to the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
This section contains the following properties:
By default, this connector uses the ICF connection pooling. Table 2-3 lists the connection pooling properties, their description, and default values set in ICF.
Table 2-3 Connection Pooling Properties
Property | Description |
---|---|
Pool Max Idle |
Maximum number of idle objects in a pool. Default value: |
Pool Max Size |
Maximum number of connections that the pool can create. Default value: |
Pool Max Wait |
Maximum time, in milliseconds, the pool must wait for a free object to make itself available to be consumed for an operation. Default value: |
Pool Min Evict Idle Time |
Minimum time, in milliseconds, the connector must wait before evicting an idle object. Default value: |
Pool Min Idle |
Minimum number of idle objects in a pool. Default value: |
Note:
This section describes an optional procedure. Perform this procedure only if you want to modify the default connection pooling properties.
If you want to modify the connection pooling properties to use values that suit requirements in your environment, then:
When an LDAP request is made by a client to a server and the server does not respond, the client waits forever for the server to respond until the TCP connection times out. On the client-side, you encounter read timed out exceptions while performing lookup field synchronization such as OID Connector Group Lookup Reconciliation. To avoid encountering such an issue, you must configure read and connect timeouts for your JNDI/LDAP service provider. To do so:
See About Request-Based Provisioning for information about request-based provisioning.
To configure request-based provisioning, perform the following procedures:
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.1.x.
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 LDAP server accounts on the target system.
Direct provisioning cannot be used if you enable request-based provisioning.
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 files contain predefined request datasets available in the xml directory on the installation media:
For ODSEE or OUD target systems: ODSEE-OUD-LDAPV3-Datasets.xml
For an OID target system: OID-Datasets.xml
For an eDirectory target system: eDirectory-Datasets.xml
Copy this file 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\LDAP
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.
The request datasets (predefined or generated) can be imported by using the Deployment Manager (DM). The predefined request dataset is stored in the xml directory on the installation media.
To import a request dataset definition by using the Deployment Manager:
The request datasets are imported into MDS.
To enable the Auto Save Form feature:
Run the PurgeCache utility to clear content belonging to the Metadata category from the server cache. See Clearing Content Related to Connector Resource Bundles from the Server Cache for instructions.
The procedure to configure request-based provisioning ends with this step.
To create the IT resource for the Connector Server:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 11.1.1.x:
Log in to the Administrative and User Console
For Oracle Identity Manager release 11.1.2.x or later:
Log in to Oracle Identity System Administration
If you are using Oracle Identity Manager release 11.1.1.x, then:
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Create IT Resource.
If you are using Oracle Identity Manager release 11.1.2.x or later, then:
Create and activate a sandbox. For detailed instructions on creating and activating a sandbox, see Managing Sandboxes of Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
In the left pane, under Configuration, click IT Resource.
The Manage IT Resource page is displayed.
Click Create IT Resource.
On the Step 1: Provide IT Resource Information page, perform the following steps:
IT Resource Name: Enter a name for the IT resource.
IT Resource Type: Select Connector Server from the IT Resource Type list.
Remote Manager: Do not enter a value in this field.
Click Continue. Figure 2-3 shows the IT resource values added on the Create IT Resource page.
Figure 2-3 Step 1: Provide IT Resource Information
On the Step 2: Specify IT Resource Parameter Values page, specify values for the parameters of the IT resource and then click Continue. Figure 2-4 shows the Step 2: Specify IT Resource Parameter Values page.
Figure 2-4 Step 2: Specify IT Resource Parameter Values
Figure 2-5 provides information about the parameters of the IT resource.
Note:
See Step 8 of Installing and Configuring the Connector Server for the values to be specified for the parameters of the IT resource.
Table 2-4 Parameters of the IT Resource for the Connector Server
Parameter | Description |
---|---|
Host |
Enter the host name or IP address of the computer hosting the connector server. Sample value: |
Key |
Enter the key for the connector server. |
Port |
Enter the number of the port at which the connector server is listening. Default value: |
Timeout |
Enter an integer value which specifies the number of milliseconds after which the connection between the connector server and Oracle Identity Manager times out. Sample value: A value of 0 means that the connection never times out. |
UseSSL |
Enter Default value: Note: It is recommended that you configure SSL to secure communication with the Connector Server. See also Configuring SSL for the Connector. |
On the Step 3: Set Access Permission to IT Resource page, the SYSTEM ADMINISTRATORS
group is displayed by default in the list of groups that have Read, Write, and Delete permissions on the IT resource that you are creating.
Note:
This step is optional.
If you want to assign groups to the IT resource and set access permissions for the groups, then:
Click Assign Group.
For the groups that you want to assign to the IT resource, select Assign and the access permissions that you want to set. For example, if you want to assign the ALL USERS
group and set the Read and Write permissions to this group, then you must select the respective check boxes in the row, as well as the Assign check box, for this group.
Click Assign.
On the Step 3: Set Access Permission to IT Resource page, if you want to modify the access permissions of groups assigned to the IT resource, then:
Note:
This step is optional.
You cannot modify the access permissions of the SYSTEM ADMINISTRATORS
group. You can modify the access permissions of only other groups that you assign to the IT resource.
Click Update Permissions.
Depending on whether you want to set or remove specific access permissions for groups displayed on this page, select or deselect the corresponding check boxes.
Click Update.
On the Step 3: Set Access Permission to IT Resource page, if you want to unassign a group from the IT resource, then:
Note:
This step is optional.
You cannot unassign the SYSTEM ADMINISTRATORS
group. You can unassign only other groups that you assign to the IT resource.
Select the Unassign check box for the group that you want to unassign.
Click Unassign.
Click Continue. Figure 2-5 shows the Step 3: Set Access Permission to IT Resource page.
Figure 2-5 Step 3: Set Access Permission to IT Resource
On the Step 4: Verify IT Resource Details page, review the information that you provided on the first, second, and third pages. If you want to make changes in the data entered on any page, click Back to revisit the page and then make the required changes.
To proceed with the creation of the IT resource, click Continue. Figure 2-6 shows Step 4: Verify IT Resource Details page.
Figure 2-6 Step 4: Verify IT Resource Details
The Step 5: IT Resource Connection Result page displays the results of a connectivity test that is run using the IT resource information. If the test is successful, then click Continue. If the test fails, then you can perform one of the following steps:
Click Back to revisit the previous pages and then make corrections in the IT resource creation information.
Click Cancel to stop the procedure, and then begin from the first step onward.
Figure 2-7 shows the Step 5: IT Resource Connection Result page.
Figure 2-7 Step 5: IT Resource Connection Result
Click Finish. Figure 2-8 shows the IT Resource Created Page.
If you want to uninstall the connector for any reason, see Uninstalling Connectors in Oracle Fusion Middleware Administering Oracle Identity Manager.
Upgrading to the OID connector release 11.1.1.5.0 is supported for Oracle Internet Directory connector version number 9.0.4.14, and Sun Java System Directory connector version 9.0.4.15. The following sections describe the upgrade process:
Note:
Preupgrade considerations are:
Before you perform the upgrade procedure, it is strongly recommended that you create a backup of the Oracle Identity Manager database. Refer to the database documentation for information about creating a backup.
As a best practice, first perform the upgrade procedure in a test environment.
Perform the following preupgrade steps:
Depending on the environment in which you are upgrading the connector, perform one of the following steps:
Development Environment
Perform the upgrade procedure by using the wizard mode.
Staging or Production Environment
Perform the upgrade procedure by using the silent mode. In the silent mode, use the silent.xml file that is exported from the development environment.
See Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about the wizard and silent modes.
Perform the postupgrade procedure documented in Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Manager.
To prevent errors during a child and parent table update, perform the following steps after you upgrade the connector:
Note:
Perform Steps 1 through 7 of the following procedure if you are using the ODSEE target system.
If you are using the OID, Novell eDirectory, or OUD target systems, then skip Steps 1 through 7, and perform Step 8.
Log in to Oracle Identity Manager Design Console.
Open Process Management and then Process Definition.
Find the LDAP User process.
Open the Remove User From Group task.
Go to the Integration tab.
Update the childTableName variable value from UD_LDAP_GRP to UD_IPNT_GRP.
Update the childTableName variable in a similar manner for these tasks and values:
Add Role to User: UD_LDAP_ROL to UD_IPNT_ROL
Remove Role From User: UD_LDAP_ROL to UD_IPNT_ROL
Add User to Group: UD_LDAP_GRP to UD_IPNT_GRP
Update User Role: UD_LDAP_ROL to UD_IPNT_ROL
Update User Group: UD_LDAP_GRP to UD_IPNT_GRP
If you are using Oracle Identity Manager release 11.1.2.x or later, then all changes made to the Form Designer of the Design Console must be done in a new UI form as follows:
Log in to Oracle Identity System Administration.
Create and active a sandbox. See Creating and Activating a Sandbox for more information.
Create a new UI form to view the upgraded fields. See Creating a New UI Form for more information about creating a UI form.
Associate the newly created UI form with the application instance of your target system. To do so, open the existing application instance for your resource, from the Form field, select the form (created in Step 5.c), and then save the application instance.
Publish the sandbox. See Publishing a Sandbox for more information.
To manage data changes on eDirectory forms after an upgrade operation, run the Form Version Control (FVC) utility. The FVC utility requires a properties file to define the data conversion actions that you want the utility to perform.
Note:
The following procedure applies to an eDirectory target system, but you can also run the FVC utility for other target systems.
Before you run the FVC utility, set the following entries in the properties file:
For User forms:
ResourceObject;eDirectory User FormName;UD_EDIR_USR FromVersion;From-Version ToVersion;To-Version ParentParent;UD_EDIR_USR_GUID;UD_EDIR_USR_REFID
For Group forms:
ResourceObject;eDirectory Group FormName;UD_EDIR_GR FromVersion;From-Version ToVersion;To-Version ParentParent;UD_EDIR_GR_GUID;UD_EDIR_GR_REFID
For Role forms:
ResourceObject;eDirectory Role FormName;UD_EDIR_RL FromVersion;From-Version ToVersion;To-Version ParentParent;UD_EDIR_RL_GUID;UD_EDIR_RL_REFID
For Organisation Unit (OU) forms:
ResourceObject;eDir Organisation Unit FormName;UD_EDIR_OU FromVersion;From-Version ToVersion;To-Version ParentParent;UD_EDIR_OU_GUID;UD_EDIR_OU_REFID
This section contains the following topics:
You can clone the OID connector by setting new names for some of the objects that comprise the connector. The outcome of the process is a new connector XML file. Most of the connector objects, such as Resource Object, Process Definition, Process Form, IT Resource Type Definition, IT Resource Instances, Lookup Definitions, Adapters, Reconciliation Rules and so on in the new connector XML file have new names.
Note:
Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about cloning connectors.
After a copy of the connector is created by setting new names for connector objects, some objects might contain the details of the old connector objects. Therefore, you must modify the following Oracle Identity Manager objects to replace the base connector artifacts or attribute references with the corresponding cloned artifacts or attributes:
IT Resource
The cloned connector has its own set of IT resources. You must configure both the cloned connector IT resources and Connector Server IT resources, and provide the reference of the cloned Connector Server IT Resource in the cloned connector IT resource. Ensure you use the configuration lookup definition of the cloned connector.
Scheduled Task
The values of the Resource Object Name and IT Resource scheduled task attributes in the cloned connector refer to the values of the base connector. Therefore, these values (values of the Resource Object Name and IT resource scheduled task attributes that refer to the base connector) must be replaced with the new cloned connector artifacts.
Lookup Definition
No change is required to be made in any of the cloned lookup definitions. All cloned lookup definitions contain proper lookup entries.
Process Tasks
After cloning, you notice that all event handlers attached to the process tasks are the cloned ones. Therefore, no changes are required for process tasks in parent forms. This is because the adapter mappings for all process tasks related to parent forms are updated with cloned artifacts.
Localization Properties
You must update the resource bundle of a user locale with new names of the process form attributes for proper translations after cloning the connector. You can modify the properties file of your locale in the resources directory of the connector bundle.
POSIX Accounts, Groups, and Roles
If you have cloned the connector and added a group or role to an account, perform the steps in Postcloning Configuration for User Accounts.
This configuration change is related to a child form. When you add a group or role to an account, perform the following steps:
Table 2-5 Mappings for OID Event Handler/Adapter
Variable Name | Data Type | Map To | Qualifer | Literal Value |
---|---|---|---|---|
processInstanceKey |
Long |
Process Data |
Process Instance |
NA |
Adapter return value |
Object |
Response Code |
NA |
NA |
objectType |
String |
Literal |
String |
User |
itResourceName |
String |
Literal |
String |
UD_OID_USR_SERVER |
childTableName |
String |
Literal |
String |
UD_OID_GRP1 |