1. Configuring the Concur Application
  2. Upgrading the Concur Connector

7 Upgrading the Concur Connector

If you have already deployed the 11.1.1.5.0 version of the Concur 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:

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

7.1 Preupgrade Steps

Preupgrade steps for the connector involves performing a reconciliation run to fetch records from the target system, defining the source connector in Oracle Identity Manager, creating copies of the connector if you want to configure it for multiple installations of the target system, and disabling all the scheduled jobs.

Perform the following preupgrade steps:

  1. Perform a reconciliation run to fetch all latest updates to Oracle Identity Manager.
  2. Perform the preupgrade procedure documented in Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Manager.
  3. 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. See Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Manager for more information.
  4. If required, create the connector XML file for a clone of the source connector.
  5. Disable all the scheduled jobs.

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.

See Managing Connector Lifecycle in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about the wizard and silent modes.

7.3 Postupgrade Steps

Postupgrade steps involve uploading new connector JARs, configuring the upgraded IT resource of the source connector, updating the Connector Server JARs, and deleting duplicate entries for lookup definitions.

Perform the following procedure:
  1. Delete the old Connector JARs. Run the Oracle Identity Manager Delete JAR ($ORACLE_HOME/bin /DeleteJars.sh) utility to delete the existing ICF bundle org.identityconnectors.genericrest-1.0.11150.jar from the Oracle Identity Manager database. When you run the Delete JARs utility, you are prompted to enter the login credentials of the Oracle Identity Manager administrator, URL of the Oracle Identity Manager host computer, context factory value, type of JAR file being deleted, and the name of the JAR file to be removed. Specify 4 as the value of the JAR type.
  2. Upload new connector JARs as follows:
    1. Run the Upload JARs utility ($ORACLE_HOME/bin/UploadJars.sh) for uploading connector JARs.
    2. Upload bundle/org.identityconnectors.genericrest-12.3.0.jar as ICFBundle.
    3. Delete the following Code Key and Decode entries in the Lookup.Concur.Configuration lookup definition: Code Key: Bundle Version; Decode: 1.0.1115 Code Key: relURIs; Decode: "__ACCOUNT__.CREATEOP=/api/user/v1.0/users","__ACCOUNT__.UPDATEOP=/api/user/v1.0/users","__ACCOUNT__.__PASSWORD__.UPDATEOP=/api/user/v1.0/users/password","__ACCOUNT__.SEARCHOP=/api/v3.0/common/users/$(Filter Suffix)$"
  3. If any attribute mappings are missing for custom attributes, log in to Oracle Identity Governance Design Console and update the mappings.
  4. Restart Oracle Identity Governance.
  5. If the connector is deployed on a Connector Server, then:
    1. Stop the Connector Server.
    2. Replace the existing bundle JAR file org.identityconnectors.genericrest-1.0.1115.jar with the new bundle JAR file org.identityconnectors.genericrest-12.3.0.jar.
    3. Start the Connector Server. After upgrading the connector, you can perform either full reconciliation or limited reconciliation. This ensures that records created or modified since the last reconciliation run are fetched into Oracle Identity Governance.

See Also: