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

7 Upgrading the Box Connector

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

See Also:

About 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 JAR to Oracle Identity Manager database.

Perform the following procedure:

  1. Delete the old Connector JARs. Run the Oracle Identity Manager Delete JARs ($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 the new connector JARs:

    1. Run the Oracle Identity Manager Upload JARs ($ORACLE_HOME/bin/UploadJars.sh) utility to upload the connector JARs.

    2. Upload the org.identityconnectors.genericrest-12.3.0.jar bundle as an ICF Bundle. Run the Oracle Identity Manager Upload JARs utility to post the new ICF bundle org.identityconnectors.genericrest-12.3.0.jar file to the Oracle Identity Manager database.

      When you run the Upload 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 uploaded, and the location from which the JAR file is to be uploaded. Specify 4 as the value of the JAR type.

    3. Delete the following Code Key and Decode entries in the Lookup.Box.Configuration lookup definition:

      • Code Key: Bundle Version Decode: 1.0.1115

      • Code Key: relURIs

        Decode:

        "__ACCOUNT__.CREATEOP=/users","__ACCOUNT__.UPDATEOP=/users/$(__UID__)$","__ACCOUNT__.SEARCHOP=/users/$(Filter Suffix)$","__ACCOUNT__.DELETEOP=/users/$(__UID__)$","__GROUP__.SEARCHOP=/groups/$(Filter Suffix)$","__ACCOUNT__.__GROUP__.CREATEOP=/group_memberships","__ACCOUNT__.__GROUP__.UPDATEOP=/group_memberships","__ACCOUNT__.__GROUP__.SEARCHOP=/users/$(__UID__)$/memberships","__ACCOUNT__.__GROUP__.DELETEOP=/group_memberships/$(__MEMBERSHIP__.id)$","__ACCOUNT__.__MEMBERSHIP__.__GROUP__.SEARCHOP=/users/$(__UID__)$/memberships","__ACCOUNT__.email.UPDATEOP=/users/$(__UID__)$/email_aliases","__ACCOUNT__.email.SEARCHOP=/users/$(__UID__)$/email_aliases","__ACCOUNT__.email.DELETEOP=/users/$(__UID__)$/email_aliases/$(__MEMBERSHIP__.id)$","__ACCOUNT__.__MEMBERSHIP__.email.SEARCHOP=/users/$(__UID__)$/email_aliases","__ACCOUNT__.role.SEARCHOP=/users/$(__UID__)$?fields=role","__ACCOUNT__.is_sync_enabled.SEARCHOP=/users/$(__UID__)$?fields=is_sync_enabled","__ACCOUNT__.is_exempt_from_login_verification.SEARCHOP=/users/$(__UID__)$?fields=is_exempt_from_login_verification"

    4. Delete the following Code Key and Decode entries in the Lookup.Box.UM.ReconAttrMap.Trusted lookup definition:

      Code Key: Usage Location; Decode: UsageLocation

  3. Restart Oracle Identity Manager.

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

      Note:

      If you have configured the connector for multiple versions of target system, see Configuring the Connector for Multiple Installations of the Target System.