1. Configuring the Database User Management Application
  2. Upgrading the Database User Management Connector

8 Upgrading the Database User Management Connector

If you have already deployed the 11.1.1.8.0 version of the Database User Management 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.

Note:

  • If you have deployed the 11.1.1.6.0 or earlier version of the Database User Management connector, you must first upgrade the connector to version 11.1.1.8.0. See “Upgrading the Connector” in Oracle Identity Manager Connector Guide for Database User Management.

  • 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, perform the upgrade procedure in a test environment initially.

The following sections discuss the procedure to upgrade the connector:

See Also:

Upgrading Connectors in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information on these steps

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

8.2 Postupgrade Steps

Postupgrade steps involve uploading new connector jars, configuring the upgraded IT resource of the source connector, deploying the Connector Server, and configuring the latest token value of the scheduled job.

Perform the following procedure:

  1. Upload new connector JARs as:

    1. Run the Upload JARs utility ($ORACLE_HOME/bin/UploadJars.sh) for uploading connector JARs.

    2. Upload bundle/org.identityconnectors.dbum-12.3.0.jar as ICFBundle.

      Note:

      If you need to add a third-party JAR:

      • Navigate to the bundle directory.

      • Create /lib folder and drop the third party jar in that folder.

      • Update the bundle with library "jar uvf org.identityconnectors.dbum-12.3.0.jar lib/FILE_NAME".

    3. Upload lib/DBUM-oim-integration.jar as JavaTask.

  2. Replicate all changes made to the Form Designer of the Design Console 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 step 2.c) and then save the application instance.

    5. Publish the sandbox.

  3. Configure the upgraded IT resource of the source connector.

  4. Deploy the Connector Server.

  5. Configure the latest token value of the scheduled job as follows:

    The following scheduled jobs contain the Latest Token attribute:

    For Oracle

    • DBUM Oracle User Target Reconciliation

    • DBUM Oracle User Trusted Reconciliation

    For MSSQL:

    • DBUM MSSQL Trusted Reconciliation

    • DBUM MSSQL User Login Target Reconciliation

    • DBUM MSSQL User Target Reconciliation

    After upgrading the connector, you can perform either full reconciliation or incremental reconciliation. This ensures that records created or modified since the last reconciliation run are fetched into Oracle Identity Manager. From the next reconciliation run onward, the reconciliation engine automatically enters a value for the Latest Token attribute.

    Note:

    If there are customizations in the query files, to include custom parameters, and for transformation/validation of data during reconciliation/ provisioning, then the same customizations have to be performed in the respective query files after upgrading the connector.

    See Also: