6 Extending the Functionality of the Connector

You can extend the functionality of the connector to address your specific business requirements.

This section discusses the following topics:

6.1 Configuring Transformation and Validation of Data

Configure transformation and validation of user account data by writing Groovy script logic while creating your application.

You can configure transformation of reconciled single-valued user data according to your requirements. For example, you can use First Name and Last Name values to create a value for the Full Name field in Oracle Identity Governance.

Similarly, you can configure validation of reconciled and provisioned single-valued data according to your requirements. For example, you can validate data fetched from the First Name attribute to ensure that it does not contain the number sign (#). In addition, you can validate data entered in the First Name field on the process form so that the number sign (#) is not sent to the target system during provisioning operations.

To configure transformation or validation of user account data, you must write Groovy scripts while creating your application. For more information about writing Groovy script-based validation and transformation logic, see Managing Application Onboarding of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

6.2 Configuring Action Scripts

You can configure Action Scripts by writing your own Groovy scripts while creating your application.

These scripts can be configured to run before or after the create, update, or delete an account provisioning operations. For example, you can configure a script to run before every user creation operation.

For information on adding or editing action scripts, see Updating the Provisioning Configuration in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

6.3 Configuring the Connector for Multiple Installations of the Target System

You must create copies of configurations of your base application to configure it for multiple installations of the target system.

The following example illustrates this requirement:

The London and New York offices of Example Multinational Inc have their own installations of the target system, including independent schema for each. The company has recently installed Oracle Identity Governance, and they want to configure it to link all the installations of the target system.

To meet the requirement posed by such a scenario, you must clone your application which copies all configurations of the base application into the cloned application. For more information about cloning applications, see Cloning Applications in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

6.4 Configuring the Connector for Multiple Versions of the Target System

For multiple versions of the target system:

  1. Configure values for the parameters of the connector server IT resource.
  2. After configuring follow below steps :
    1. Copy the bundle/org.identityconnectors.siebel-12.3.0.jar file into the CONNECTOR_SERVER_HOME/bundles directory.
    2. Depending on the target system that you are using, copy the following third-party JAR files from the SIEBEL_INSTALLATION_DIRECTORY/siebsrvr/CLASSES directory into the CONNECTOR_SERVER_HOME/lib directory:
    • - For Siebel 7.5 through 7.7:
    • SiebelJI.jar
    • SiebelJI_Common.jar
    • SiebelJI_enu.jar
    • - For Siebel 7.8 through 8.2.2 and Siebel Innovation Pack 2015, 2016, 2017, 2018, Siebel 19.xand Siebel 20.x:
      • Siebel.jar
      • SiebelJI_enu.jar
  3. Start the connector server.

See Also: