4 Performing Postconfiguration Tasks for the Salesforce Connector

These are the tasks that you must perform after creating an application in Oracle Identity Governance.

• Configuring Oracle Identity Governance

• Harvesting Entitlements and Sync Catalog

• Managing Logging

• Configuring the IT Resource for the Connector Server

• Localizing Field Labels in UI Forms

• Configuring SSL for the Connector

• Obtaining GUID of Roles

4.1 Configuring Oracle Identity Governance

During application creation, if you did not choose to create a default form, then you must create a UI form for the application that you created by using the connector.

Note:

Perform the procedures described in this section only if you did not choose to create the default form during creating the application.

• Creating and Activating a Sandbox

• Creating a New UI Form

• Publishing a Sandbox

• Creating an Application Instance

• Updating an Existing Application Instance with a New Form

4.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 a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.

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

While creating the UI form, ensure that you select the resource object corresponding to the newly created application that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.

4.1.3 Publishing a Sandbox

Before publishing a sandbox, perform this procedure as a best practice to validate all sandbox changes made till this stage as it is difficult to revert the changes after a sandbox is published.

1. In Identity System Administration, deactivate the sandbox.

2. Log out of Identity System Administration.

3. Log in to Identity Self Service using the xelsysadm user credentials and then activate the sandbox that you deactivated in Step 1.

4. In the Catalog, ensure that the application instance form for your resource appears with correct fields.

5. Publish the sandbox. See Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.

4.1.4 Creating an Application Instance

Create an application instance as follows:

See Managing Application Instances in Oracle Fusion Middleware Administering Oracle Identity Governance.

1. In the left pane of the Identity System Administration, 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. Specify values for the following fields:

   • Name: The name of the application instance

   • Display Name: The display name of the application instance.

   • Description: A description of the application instance.

   • Resource Object: The resource object name. Click the search icon next to this field to search for and select Salesforce User.

   • IT Resource Instance: The IT resource instance name. Click the search icon next to this field to search for and select Salesforce.

   • Form: Select the form name (created in Creating a New UI Form).

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 Managing Organizations Associated With Application Instances in Oracle Fusion Middleware Administering Oracle Identity Governance.

4.1.5 Updating an Existing Application Instance with a New Form

For any changes that you do in the schema of your application in Identity Self Service, 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 and activate a sandbox.

2. Create a new UI form for the resource.

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

• Creating a Sandbox and Activating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance

• Creating Forms By Using the Form Designer in Oracle Fusion Middleware Administering Oracle Identity Governance

• Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance

4.2 Harvesting Entitlements and Sync Catalog

To harvest entitlements and sync catalog:

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

See Also:

Predefined Scheduled Tasks in Oracle Fusion Middleware Administering Oracle Identity Governance for a description of the Entitlement List and Catalog Synchronization Job scheduled jobs

4.3 Managing Logging

Oracle Identity Governance 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

4.3.1 Understanding Log Levels

When you enable logging, Oracle Identity Governance 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 Governance 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 Governance 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 message types are mapped to ODL message type and level combinations as shown in Table 4-1.

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

4.3.2 Enabling Logging

To enable logging in the Oracle WebLogic Server:

1. Edit the logging.xml file as follows:
   1. Add the following blocks in the file:

      <log_handler name='Salesforce-handler' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
      <property name='logreader:' value='off'/>
          <property name='path' value='[FILE_NAME]'/>
          <property name='format' value='ODL-Text'/>
          <property name='useThreadName' value='true'/> 
          <property name='locale' value='en'/> 
          <property name='maxFileSize' value='5242880'/> 
          <property name='maxLogSize' value='52428800'/>
          <property name='encoding' value='UTF-8'/>
      </log_handler>
      
      <logger name="ORG.IDENTITYCONNECTORS.GENERICREST" level="[LOG_LEVEL]" useParentHandlers="false">
          <handler name="Salesforce-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 4-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='Salesforce-handler' level='NOTIFICATION:1' class='oracle.core.ojdl.logging.ODLHandlerFactory'> 
      <property name='logreader:' value='off'/>
          <property name='path' value='F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\
           oim_server1-diagnostic-1.log'/>
          <property name='format' value='ODL-Text'/> 
          <property name='useThreadName' value='true'/> 
          <property name='locale' value='en'/> 
          <property name='maxFileSize' value='5242880'/> 
          <property name='maxLogSize' value='52428800'/> 
          <property name='encoding' value='UTF-8'/> 
        </log_handler> 
      
      <logger name="ORG.IDENTITYCONNECTORS.GENERICREST" level="NOTIFICATION:1" useParentHandlers="false"> 
          <handler name="Salesforce-handler"/> 
          <handler name="console-handler"/> 
        </logger>

      With these sample values, when you use Oracle Identity Governance, 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.

4.4 Configuring the IT Resource for the Connector Server

If you have used the Connector Server, you must configure values for the parameters of the Connector Server IT resource.

Note:

This procedure is optional and is required only when the Connector Server is being used.

To configure or modify the IT resource for the Connector Server:

1. Log in to Oracle Identity System Administration.

2. Create and activate a sandbox. For detailed instructions on creating and activating a sandbox, see Managing Sandboxes in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.

3. In the left pane, under Configuration, click IT Resource.

4. In the IT Resource Name field on the Manage IT Resource page, enter SalesForce and then click Search. Figure 4-1 shows the Manage IT Resource page.

   Figure 4-1 Manage IT Resource Page for Connector Server IT Resource

   
   Description of "Figure 4-1 Manage IT Resource Page for Connector Server IT Resource"

5. Click the edit icon corresponding to the Connector Server IT resource.

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

7. Specify values for the parameters of the Connector Server IT resource. Figure 4-2 shows the Edit IT Resource Details and Parameters page.

   Figure 4-2 Edit IT Resource Details and Parameters Page for the Connector Server IT Resource

   
   Description of "Figure 4-2 Edit IT Resource Details and Parameters Page for the Connector Server IT Resource"

   Table 4-2 provides information about the parameters of the IT resource.

   Table 4-2 Parameters of the IT Resource for the Salesforce Connector Server

   Parameter	Description
   Host	Enter the host name or IP address of the computer hosting the Connector Server. Sample value: HostName
   Key	Enter the key for the Connector Server.
   Port	Enter the number of the port at which the Connector Server is listening. Default value: 8763
   Timeout	Enter an integer value which specifies the number of milliseconds after which the connection between the Connector Server and Oracle Identity Governance times out. If the value is zero or if no value is specified, the timeout is unlimited. Sample value: 0 (recommended value)
   UseSSL	Enter true to specify that you will configure SSL between Oracle Identity Governance and the Connector Server. Otherwise, enter false. Default value: false

8. To save the values, click Update.

4.5 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 the following file in a text editor:
   SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle_en.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 Database application instance. The original code is:

      <trans-unit 
      id="${adfBundle['oracle.adf.businesseditor.model.util
      .BaseRuntimeResourceBundle']['persdef.sessiondef.orac
      le.iam.ui.runtime.form.model.user.entity.use 
      rEO.UD_SF_USERNAME__c_description']}">
      
      <source>Username</source>
      
      </target> </trans-unit> <trans-unit
      
      id="sessiondef.oracle.iam.ui.runtime.form.model.Sales
      force.entity. sEO.UD_SF_USR_USERNAME__c">
      
      <source>Username</source>
      
      </target> </trans-unit>

   4. Open the resource file from the connector package, for example Salesforce_ja.properties, and get the value of the attribute from the file, for example, global.udf.UD_SF_USR_USERNAME=\u30A2\u30AB\u30A6\u30F3 \u30C8\u540D.

   5. Replace the original code shown in Step 6.c with the following:

      <trans-unitid="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.
      runtime.form.model.user.entity.userEO.UD_SF_USR_USERNAME__c_description']}">
      
      <source>User Name</source> 
      <target>u30A2\u30AB\u30A6\u30F3\u30C8\u540D</target>
      </trans-unit> 
      <trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.Salesforce.entity sEO.UD_SF_USR_USERNAME__c_LABEL
      ">
      <source>Account Name</source> <target>\u30A2\u30AB\u30A6\u30F3\u30C8\u540D</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 Governance for information about exporting and importing metadata files.

8. Log out of and log in to Oracle Identity Governance.

4.6 Configuring SSL for the Connector

Configure SSL to secure data communication between Oracle Identity Governance and Salesforce.

Note:

If you are using this connector along with a Connector Server, then there is no need to configure SSL. You can skip this section.

Salesforce validates the client system dates to be in sync with the SSL certificate (the certificate issued by Salesforce 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.

Importing the Certificate

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

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

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

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

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.

4.7 Obtaining GUID of Roles

You must obtain the GUID of roles from the target system to populate the Code Key values of the Lookup.Salesforce.Roles lookup definition.

The REST services exposed by Salesforce.com do not provide any endpoint to fetch the Role GUIDs programatically. Therefore, to manage provision roles for users, you have to populate the Lookup.Salesforce.Roles lookup manually.

To obtain GUID of roles, from your organization’s role hierarchy, click on any role for which you want to determine the GUID. The GUID is available as part of the URL. For example, in the following URL, 00E800000016mY is the GUID of the selected role:

https://cs40.salesforce.com.00E800000016mY.setupid=Roles