7 Upgrading the SAP User Management Engine Connector

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

If you have already deployed 11.1.1.9.0 version of this connector, then you can upgrade the connector to version 12.2.1.3.0.

To upgrade the SAP User Management Engine connector, perform the procedures described in the following sections:

Note:

  • Before you perform the upgrade procedure, it is strongly recommended that you create a backup of the Oracle Identity Governance 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.

  • Direct upgrade to release 11.1.1.9.0 or later from release 9.x of the connector is not supported. You must first upgrade to release 11.1.1.8.0 from release 9.x and then upgrade to release 11.1.1.9.0 or later.

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:

  1. Perform a reconciliation run to fetch all latest updates to Oracle Identity Governance.

  2. Define the source connector (an earlier release of the connector that must be upgraded) in Oracle Identity Governance. You define the source connector to update the Deployment Manager XML file with all customization changes made to the connector.

  3. Run the Oracle Identity Governance Delete JARs utility to delete the old connector bundle from the Oracle Identity Manager database.

  4. Run the connector preupgrade utility.

    See Also:

    • Delete JARs Utility of Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance for detailed information about the Delete JARs utility

    • Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Governance for detailed information about the preupgrade utility

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

See Also:

Managing Connector Lifecycle of Oracle Fusion Middleware Administering Oracle Identity Governance for detailed information about the wizard and silent modes

7.3 Postupgrade Steps

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 the duplicate lookup entries manually.

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 bundle JARs from Oracle Technology Network Website (OTN) website. See Downloading the Connector Installation Package for more information.
    For Basic User Management and SoD validation of SAP GRC Access Risk Analysis:
    • Upload bundle/org.identityconnectors.sapume-12.3.0.jar as an ICFBundle

    • Upload lib/sapume-oim-integration.jar as a JavaTask

    For SAP GRC Access Request Management,
    • Upload bundle/org.identityconnectors.sapacume-12.3.0.jar as an ICFBundle

    • Upload lib/sapac-oim-integration.jar as a ScheduleTask

    See Also:

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

  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 and CONNECTOR_SERVER_HOME/lib directories respectively with the new connector bundles (bundle/org.identityconnectors.sapacume-12.3.0.jar and bundle/org.identityconnectors.sapume-12.3.0.jar) and lib JARs ( lib/sapac-oim-integration.jarlib/sapume-oim-integration.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 Step 4 c) 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.

    The following are the list of lookup definitions. See Postupgrade Issue for the detailed list of entries of the these lookups:
    • For Basic User Management Engine and SoD validation of SAP GRC Access Risk Analysis:
      • Lookup.SAPUME.Configuration

      • Lookup.SAPUME.UM.ProvAttrMap

      • Lookup.SAPUME.UM.ReconAttrMap

    • For SAP GRC Access Request Management:
      • Lookup.SAPAC10UME.Configuration

      • Lookup.SAPAC10UME.UM.ProvAttrMap

      • Lookup.SAPAC10UME.UM.ReconAttrMap

    Perform the postupgrade procedure documented in Managing Connector Lifecycle of Oracle Fusion Middlware Administering Oracle Identity Governance.

  6. Run the Form Upgrade Job to manage data changes on a form after an upgrade operation.

  7. Perform full reconciliation or delete reconciliation.

    See Also: