7 Upgrading the Siebel User Management Connector

If you have already deployed the 11.1.1.6.0 version of this connector, then you can upgrade the connector to version 12.2.1.3.0 by uploading the new connector JAR files to the Oracle Identity Manager database.

You can upgrade the Siebel User Management connector while in production, and with no downtime. Your customizations remain intact and the upgrade will be transparent to your users. All form field names are preserved from the legacy connector.

Note:

  • If you have deployed the 11.1.1.5.0 or earlier version of the Siebel User Management, you must first upgrade the connector to version 11.1.1.6.0.
  • 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.

The following sections discuss the procedure to upgrade the connector:

7.1 Preupgrade Steps

Preupgrade steps involve performing a reconciliation run, defining the source, running the Delete JARs utility and connector preupgrade utility.

Before you perform an upgrade operation or any of the upgrade procedures, you must perform the following actions:
  • Perform a reconciliation run to fetch all latest updates to Oracle Identity Manager.
  • Define the source connector (an earlier release of the connector that must be upgraded) in Oracle Identity Manager.

    You define the source connector to update the Deployment Manager XML file with all customization changes made to the connector.

  • If required, create the connector XML file for a clone of the source connector.
  • Disable all scheduled tasks.
  • Run the Oracle Identity Manager Delete JARs utility to delete the old connector bundle to the Oracle Identity Manager database.
  • Run the connector preupgrade utility.
See Also:
  • For detailed information about the Delete JARs utility, see Delete JAR Utility in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.
  • For more information about the preupgrade utility, see Managing Connector LIfecycle of Oracle Fusion Middleware Administering Oracle Identity Governance .

7.2 Upgrade Steps

This is a summary of the procedure to upgrade the connector for both staging and production environments.
Depending on the environment in which you are upgrading the connector, perform one of the following steps:
  • Staging Environment
    Perform the upgrade procedure by using the wizard mode.

    Note:

    Do not upgrade IT resource type definition. In order to retain the default setting, you must map the IT resource definition to "None".
  • Production Environment

    Perform the upgrade procedure by using the silent mode.

For detailed information about the wizard and silent modes, see Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Manager.

7.3 Postupgrade Steps

This chapter describes the postupgrade steps that must be taken to configure the new resources.
Postupgrade steps involve uploading new connector JAR files, configuring the upgraded IT resource of the source connector, deploying and reconfiguring the Connector Server, and deleting duplicate entries for lookup definitions.

Note:

If you have not retained the customizations, you must reapply them after you upgrade the connector.
Perform the following procedure:
  1. Run the Oracle Identity Manager Upload JARs utility to post the new connector bundle and lib JARs to the Oracle Identity Manager database.

    Note:

    You can download the JARs from Oracle Technology Network Website (OTN) website. See Downloading the Connector Installation Package for more information.
    1. Run the Upload JARs utility for uploading connector JARs:
      $ORACLE_HOME/bin/UploadJars.sh
    2. Upload bundle/org.identityconnectors.siebel-12.3.0.jar as ICFBundle.
    3. Add a third-party JAR (if needed).
      1. Navigate to the bundle directory.
      2. Create /lib folder and copy the third party jar into that folder.
      3. Update the bundle with library "jar uvf org.identityconnectors.siebel-12.3.0.jar lib/<FILE_NAME>".

        For detailed information about the Upload JARs utility, see Upload JAR Utility in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance .

  2. If the connector is deployed on a Connector Server, then:
    1. Stop the Connector Server.
    2. Replace the existing connector bundle and lib JARs located in the CONNECTOR_SERVER_HOME/bundles directories respectively with the new connector bundles (bundle/org.identityconnectors.siebel-12.3.0.jar from the connector installation media.
    3. Start the Connector Server.
  3. Reconfigure the IT resource of the connector if the IT resource details are updated.
  4. Replicate all changes as in the previous version of the connector process form in a new UI form as follows:
    1. Log in to Oracle Identity System Administration.
    2. Create and activate a sandbox.
    3. Create a new UI form to view the upgraded fields.
    4. 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 the previous step, and then save the application instance.
    5. Publish the sandbox and perform full reconciliation.
  5. Delete the duplicated lookup entries that are generated while upgrading the connector.
  6. Perform the postupgrade procedure Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Governance.
  7. Perform full reconciliation or delete reconciliation.
See Also: