2 Deploying the Oracle Identity Cloud Service Connector

The procedure to deploy the connector is divided across three stages: Preinstallation, installation, and postinstallation.

The following topics provide details on these stages:

• Preinstallation

• Installation

• Postinstallation

2.1 Preinstallation

Preinstallation for the Oracle Identity Cloud Service connector involves registering and generating a client application (that is, the Oracle Identity Cloud Service connector) with the target system so that the connector can access Oracle Identity Cloud Service Graph APIs. It also involves creating a target system account for connector operations.

Preinstallation involves performing the following tasks on the target system:

1. Register and generate an application. Because the connector operates as a multitarget environment, the application needs to be registered on the Oracle Identity Cloud Service environment for authentication.
2. Specify the permissions to choose an application type to configure your own application in the cloud. To do so:
   1. Select Resource Owner as the allowed grant type for this application.
   2. Select the Client has Access to Identity Cloud Service Admin APIs checkbox.
   3. Select Identity Domain Administrator and Me. This provides administrator permissions to any third-party client using this application to perform identity operations such as User and Group management.
   4. In the Register the Resource of the Application page, select the Register Resources radio button.
3. Create a target system account with administrative privileges to enable connector operations such as reconciliation and provisioning.

2.2 Installation

You must install the Oracle Identity Cloud Service connector in Oracle Identity Manager and if required, place the connector code bundle in the Connector Server.

The following topics discuss installing the Oracle Identity Cloud Service connector:

• Understanding Installation

• Running the Connector Installation

• Configuring the IT Resource for the Target System

• Deploying the Connector in a Connector Server

2.2.1 Understanding Installation of the Oracle Identity Cloud Service Connector

You can run the connector code either locally in Oracle Identity Manager or remotely in a Connector Server

Depending on where you want to run the generated connector, the connector provides the following installation options:

• Run the connector code locally in Oracle Identity Manager. To run the connector code locally in Oracle Identity Manager, perform the procedure described in Installing the Connector in Oracle Identity Manager. In this scenario, you deploy the connector in Oracle Identity Manager.

• Run the connector code remotely in a Connector Server. To run the connector code remotely in a Connector Server, perform the procedures described in Installing the Connector in Oracle Identity Manager and Deploying the Connector in a Connector Server. In this scenario, you deploy the connector in Oracle Identity Manager, and then, deploy the connector bundle in a Connector Server. For information about installing, configuring, and running the Connector Server, and then installing the connector in a Connector Serve, see Using an Identity Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager .

2.2.2 Installing the Connector in Oracle Identity Manager

Installation on Oracle Identity Manager consists of the following procedures:

• Running the Connector Installer

• Configuring the IT Resource for the Target System

2.2.2.1 Running the Connector Installer

When you run the Connector Installer, it automatically copies the connector files to directories in Oracle Identity Manager, imports connector XML files, and compiles adapters used for provisioning.

To run the Connector Installer:

1. Copy the contents of the connector installation media into the following directory: OIM_HOME/server/ConnectorDefaultDirectory.
2. Log in to Oracle Identity System Administration.
3. From the left pane, expand the Provisioning Configuration tab and click Manage Connector.
4. In the Manage Connector page, click Install.
5. From the Connector List, select IDCS Connector RELEASE_NUMBER. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory mentioned in the OIM_HOME/server/ConnectorDefaultDirectory.

   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, select IDCS 11.1.1.5.0.
6. Click Load.
7. To start the installation process, click Continue.

   The following tasks are performed in sequence:

   1. Configuration of connector libraries
   2. Import of the connector XML files (by using the Deployment Manager)
   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 is displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:

   1. Retry the installation by clicking Retry.

   2. Cancel the installation and begin again from Step 3.

8. Click Exit to finish the installation procedure.

   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 are displayed. These steps are as follows:

   1. Make sure 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. For information about running the PurgeCache utility, see Clearing Content Related to Connector Resource Bundles from the Server Cache. Some predefined connectors have no prerequisites.

   2. Configure 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. Configure the scheduled jobs.

      Configuring the scheduled tasks that are created when you installed the connector. 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 A-1

2.2.2.2 Configuring the IT Resource for the Target System

An IT resource for your target system is created after you install the connector. You configure this IT resource to enable the connector to connect Oracle Identity Manager with your target system.

This section contains the following topics:

• IT Resource Parameters

• Specifying Values for the IT Resource Parameters

2.2.2.2.1 IT Resource Parameters

An IT resource is composed of parameters that store connection and other generic information about a target system. Oracle Identity Manager uses this information to connect to a specific installation or instance of your target system.

The list of IT resource parameters for this connector can be grouped into the following categories:

• Connection-related parameters

• Authentication parameters

Connection Parameters

Table 2-1 lists the connection-related parameters.

Table 2-1 Connection IT Resource Parameters

Parameter	Description
host	The host name or IP address of the computer hosting the target system. Sample value: www.example.com
port	The port number at which the target system is listening. Sample value: 80
baseURI	The base URI is the base relative URL of the Oracle Identity Cloud Service target system. Sample value: http://host:port/admin/v1, then baseURI is /admin/v1
Configuration Lookup	The name of the lookup definition that stores configuration information used during reconciliation and provisioning. Default value for Oracle Identity Cloud Service: Lookup.IDCS.Configuration
Connector Server Name	If you have deployed the Oracle Identity Cloud Service connector in a Java Connector Server, then enter the name of the IT resource for the Connector Server.
acceptType	The accept type for the header denotes how the request body must be parsed. The request body should only be parsed as JSON if the Content-Type header is application/json.
sslEnabled	If the target system requires SSL connectivity, set the value of this parameter to true. Otherwise, set the value to false.
grantType	The type of authentication used by your target system. The default value is: password
scope	Scope is required to authenticate request based on 'OAuth2.0 Resource Owners Password or Client Credentials' authentication type
contentType	The content type for the header denotes the format of the request being sent to the target system. The request body should only be parsed as JSON if the Content-Type header is application or JSON.

Table 2-2 lists authentication parameters.

Table 2-2 Basic Authentication IT Resource Parameters

Parameter	Description
username	The user name or User ID used if authentication type is “basic” or “password”. Sample value: johnsmith
password	The password used if authentication type is “basic” or “password”. Sample value: password
authenticationServerUrl	The URL of the authentication server if authentication type is “BASIC”. Sample value: https://api.example.com/oauth2/token
customAuthHeaders	Authorization=Basic “<Base64 Encode ClientID:ClientSecret>”

2.2.2.2.2 Specifying Values for the IT Resource Parameters

The IT resource for the target system contains connection information about the target system. Oracle Identity Manager uses this information during provisioning and reconciliation. When you run the metadata generator, the IT resource corresponding to this connector is automatically created in Oracle Identity Manager.

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

1. Log in to Oracle Identity System Administration.
2. In the left pane, under Configuration, click IT Resource.
3. In the IT Resource Name field on the Manage IT Resource page, enter Identity Cloud Services, and then click Search.
4. Click the edit icon for the IT resource.
5. From the list at the top of the page, select Details and Parameters.
6. Specify values for the parameters of the IT resource.
7. To save the values, click Update.

2.2.3 Deploying the Connector in a Connector Server

In this scenario, you deploy the connector in Oracle Identity Manager, and then, deploy the connector bundle in a Connector Server.

For information about installing, configuring, and running the Connector Server, and then installing the connector in a Connector Server, see Using an Identity Connector Server in Developing and Customizing Applications for Oracle Identity Manager.

2.3 Postinstallation

Postinstallation for the Oracle Identity Cloud Service connector involves configuring OIM, enabling logging to track information about all connector events, and configuring SSL. It also involves performing optional configurations such as localizing the user interface.

Postinstallation steps are detailed in the following sections:

• Postinstallation on Oracle Identity Manager

• Creating the IT Resource for the Connector Server

2.3.1 Postinstallation on Oracle Identity Manager

Configuring Oracle Identity Manager involves performing the following procedures:

• Configuring Oracle Identity Manager

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

• Managing Logging for Oracle Identity Cloud Service Connector

• Localizing Field Labels in UI Forms

• Configuring SSL for Oracle Identity Cloud Service

2.3.1.1 Configuring Oracle Identity Manager

You must create a UI form and an application instance for the resource against which you want to perform reconciliation and provisioning operations. In addition, you must run entitlement and catalog synchronization jobs.

These procedures are described in the following sections:

• Creating and Activating a Sandbox

• Creating a New UI Form

• Creating an Application Instance

• Publishing a Sandbox

• Harvesting Entitlements and Sync Catalog

• Updating an Existing Application Instance with a New Form

2.3.1.1.1 Creating and Activating a Sandbox

You must create and activate a sandbox to begin using the customization and form management features. You can then publish the sandbox to make the customizations available to other users.

See Creating a Sandbox and Activating and Deactivating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.

2.3.1.1.2 Creating a New UI Form

You can use Form Designer in Oracle Identity System Administration to create and manage application instance forms. See Creating Forms By Using the Form Designer in Oracle Fusion Middleware Administering Oracle Identity Manager.

While creating the UI form, ensure that you select the resource object corresponding to the Oracle Identity Cloud Service connector that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.

2.3.1.1.3 Creating an Application Instance

Create an application instance as follows:

1. In the left pane of the System Administration console, under Configuration, click Application Instances. The Application Instances page appears.
2. From the Actions menu, select Create. Alternatively, click Create on the toolbar. The Create Application Instance page appears.
3. Enter appropriate values for the fields displayed on the Attributes form and click Save.
4. Click Save. The application instance is created.
5. Publish the application instance to an organization to make the application instance available for requesting and subsequent provisioning to users. See Publishing an Application Instance to Organizations in Oracle Fusion Middleware Administering Oracle Identity Manager.

2.3.1.1.4 Publishing a Sandbox

After you publish a sandbox, it is difficult to revert changes. Therefore, before you publish a sandbox, perform the following procedure to validate all sandbox changes made until this stage:

1. In the System Administration console, deactivate the sandbox.
2. Log out of the System Administration console.
3. Log in to the Self Service console using the xelsysadm user credentials, and then activate the sandbox that you deactivated in Step 1.
4. In the catalog, ensure that the Oracle Identity Cloud Service application instance form appears with the correct fields.
5. After you Publish the sandbox. See Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.

2.3.1.1.5 Harvesting Entitlements and Sync Catalog

To harvest entitlements and sync the catalog:

1. Run the scheduled jobs for lookup field synchronization listed in Scheduled Job for Lookup Field Synchronization.
2. Run the Entitlement List scheduled job to populate Entitlement Assignment schema from the child process form table.
3. Run the Catalog Synchronization Job scheduled job.

See Also:

For a description of the Entitlement List and Catalog Synchronization Job scheduled jobs, see Predefined Scheduled Tasks in Administering Oracle Identity Manager

2.3.1.1.6 Updating an Existing Application Instance with a New Form

For any changes that you make in the Form Designer, you must create a new UI form and update the changes in an application instance. To update an existing application instance with a new form:

1. Create a sandbox and activate it. See Creating a Sandbox and Activating and Deactivating a Sandbox in Developing and Customizing Applications for Oracle Identity Manager.
2. Create a new UI form for the resource. See Creating Forms By Using the Form Designer in Administering Oracle Identity Manager.
3. Open the existing application instance.
4. In the Form field, select the new UI form that you created.
5. Save the application instance.
6. Publish the sandbox. See Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.

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

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:

1. In a command window, switch to the OIM_HOME/server/bin directory.

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

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

     You can use the PurgeCache utility to purge the cache for any content category. See Purging Cache in Oracle Fusion Middleware Administering Oracle Identity Manager.

2.3.1.3 Managing Logging for Oracle Identity Cloud Service Connector

Oracle Identity Manager uses the Oracle Diagnostic Logging (ODL) logging service for recording all types of events pertaining to the connector.

The following topics provide detailed information about logging:

• Understanding Log Levels

• Enabling Logging

2.3.1.3.1 Understanding Log Levels

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.

ODL is the principle logging service used by Oracle Identity Manager and 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.

2.3.1.3.2 Enabling Logging

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='idcs-handler' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
      <property name='logreader:' value='off'/>
           <property name='path' value='/scratch/IDCS/Logs/IDCS.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.GENERICSCIM' level='TRACE:32'  
      useParentHandlers='false'>
           <handler name='idcs-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 specific to connector operations to be recorded.

      The following blocks show sample values for [LOG_LEVEL] and [FILE_NAME] :

      <log_handler name='idcs-handler' level='TRACE:32' 
      class='oracle.core.ojdl.logging.ODLHandlerFactory'> 
      <property name='logreader:' value='off'/>
           <property name='path' 
        value='/scratch/IDCS/Logs/IDCS.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>
      </log_handlers>  
      
       <logger name='ORG.IDENTITYCONNECTORS.GENERICSCIM' level='TRACE:32'  
      useParentHandlers='false'>
           <handler name='idcs-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.3.1.4 Localizing Field Labels in UI Forms

You can localize UI form field labels by using the resource bundle corresponding to the language you want to use. Resource bundles are available in the connector installation media

To localize field label that is added to the UI forms:

1. Log in to Oracle Enterprise Manager.
2. In the left pane, expand Application Deployments and then select oracle.iam.console.identity.sysadmin.ear.
3. In the right pane, from the Application Deployment list, select MDS Configuration.
4. On the MDS Configuration page, click Export and save the archive to the local computer.
5. 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

6. Edit the BizEditorBundle.xlf file in the following manner:

   1. Search for the following text:

      <file source-language="en" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">

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

   3. Search for the application instance code. This procedure shows a sample edit for Oracle Identity Cloud Service 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_ACMEGSAP_APP_DFLT_HOME__c_description']}">
      <source>APP_DFLT_HOME</source>
      <target/>
      </trans-unit>
      <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.ACMEFORM.entity.ACMEFORMEO.UD_ACMEGSAP_APP_DFLT_HOME__c_LABEL">
      <source>APP_DFLT_HOME</source>
      <target/>
      </trans-unit>

   4. Open the properties file created in Step 1 and get the value of the attribute, for example, global.udf.D_ACMEGSAP_APP_DFLT_HOME=\u4567d.

   5. Replace the original code shown in Step c 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_ACMEGSAP_APP_DFLT_HOME__c_description']}">
      <source>APP_DFLT_HOME</source>
      <target>\u4567d</target>
      </trans-unit>
      <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.ACMEFORM.entity.ACMEFORMEO.UD_ACMEGSAP_APP_DFLT_HOME__c_LABEL">
      <source>APP_DFLT_HOME</source>
      <target>\u4567d</target>
      </trans-unit>

   6. Repeat Steps 6.a through 6.d for all attributes of the process form.

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

7. 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
8. Log out of and log in to Oracle Identity Manager.

2.3.1.5 Configuring SSL for Oracle Identity Cloud Service

Importing the Certificate

Configure SSL to secure data communication between Oracle Identity Manager and Oracle Identity Cloud Service.

Oracle Identity Cloud Service validates the client system dates to be in sync with the SSL certificate (the certificate issued by Oracle Identity Cloud Service application) date. If there is any deviation, then the target system might throw an error. The client machine date must be in sync with the certificate timestamp range. Obtain SSL certificate from the target system.

Use the keytool command to import the SSL certificate from the target system into the identity keystore in Oracle Identity Manager.

keytool -import -alias alias -trustcacerts -file file-to-import -keystore keystore-name -storepass keystore-password

In this example, the certificate file supportcert.pem is imported to the identity keystore client_store.jks with password weblogic1:

keytool -import -alias serverwl -trustcacerts -file supportcert.pem -keystore client_store.jks -storepass weblogic1

Note:

Change the parameter values passed to the keytool command according to your requirements. Ensure that there is no line break in the keytool arguments.

2.3.2 Creating the IT Resource for the Connector Server

You must create an IT resource for the Connector Server if you have deployed the Oracle Identity Cloud Service connector in the Connector Server.

To create the IT resource for the Connector Server, perform the following procedure:

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

   • For Oracle Identity Manager release 11.1.1:

     Log in to the Administrative and User Console

   • For Oracle Identity Manager release 11.1.2.x:

     Log in to Oracle Identity System Administration

2. If you are using Oracle Identity Manager release 11.1.1, then:
   1. On the Welcome page, click Advanced in the upper-right corner of the page.
   2. On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Create IT Resource.
3. If you are using Oracle Identity Manager release 11.1.2.x, then:
   1. In the left pane under Configuration, click IT Resource.
   2. In the Manage IT Resource page, click Create IT Resource.
4. 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.

5. Click Continue. Figure 2-1 shows the IT resource values added on the Create IT Resource page.

   Figure 2-1 Step 1: Provide IT Resource Information

   
   Description of "Figure 2-1 Step 1: Provide IT Resource Information"
6. 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-2 shows the Step 2: Specify IT Resource Parameter Values page.

   Figure 2-2 Step 2: Specify IT Resource Parameter Values

   
   Description of "Figure 2-2 Step 2: Specify IT Resource Parameter Values"

   Figure 2-5 provides information about the parameters of the IT resource and Table 2-4 lists values to be specified for the parameters of the IT resource.

   Table 2-4 IT Resource Parameters

   Parameter	Description
   Host	Enter the host name or IP address of the computer hosting the connector server. Sample value: myhost.com
   Key	Enter the key for the connector server.
   Port	Enter the number of the port at which the connector server is listening. Sample value: 8759
   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: 0 A value of 0 means that the connection never times out.
   UseSSL	Enter true to specify that you will configure SSL between Oracle Identity Manager and the Connector Server. Otherwise, enter false. Sample value: false Note: It is recommended that you configure SSL to secure communication with the connector server.

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

   1. Click Assign Group.
   2. 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.
   3. Click Assign.
8. 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 unassign the SYSTEM ADMINISTRATORS group. You can unassign only other groups that you assign to the IT resource.

   1. Click Update Permissions.
   2. 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.
   3. Click Update.
9. 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.

   1. Select the Unassign check box for the group that you want to unassign.
   2. Click Unassign.
10. Click Continue. Figure 2-3 shows the Step 3: Set Access Permission to IT Resource page.

    Figure 2-3 Step 3: Set Access Permission to IT Resource

    
    Description of "Figure 2-3 Step 3: Set Access Permission to IT Resource"
11. 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.
12. To proceed with the creation of the IT resource, click Continue. Figure 2-4 shows Step 4: Verify IT Resource Details page.

    Figure 2-4 Step 4: Verify IT Resource Details

    
    Description of "Figure 2-4 Step 4: Verify IT Resource Details"
13. 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-5 shows the Step 5: IT Resource Connection Result page.

    Figure 2-5 Step 5: IT Resource Connection Result

    
    Description of "Figure 2-5 Step 5: IT Resource Connection Result"
14. Click Finish. Figure 2-6 shows the IT Resource Created Page.

    Figure 2-6 Step 6: IT Resource Created

    
    Description of "Figure 2-6 Step 6: IT Resource Created"