1. Configuring the GoToMeeting Application
  2. Implementing the GoToMeeting Connector
  3. Upgrading the GoToMeeting Connector

3.7 Upgrading the GoToMeeting Connector

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

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

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

3.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. 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. Upload lib/gtm-update-accesstoken.jar as ScheduleTask.
  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. If you are using the Connector Server, update the Connector Server JARs as follows:
    1. Navigate to the bundles directory in your Connector Server directory, and replace the existing connector server bundle JAR with the new JAR.
    2. Restart the Connector Server.
  5. If any of the previous connector artifacts are retained after a successful upgrade operation, then log in to Oracle Identity Manager Design Console and delete the following duplicate entries:

    • For the Lookup.GoToMeeting.Configuration lookup definition:

      Code Key Decode

      relURIs

      "__ACCOUNT__.licenseKeys.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/licenses/$(licenseKeys)$/users/$(__UID__)$",

      "__ACCOUNT__.CREATEOP=/admin/rest/v1/accounts/$(account_key)$/users", "__ACCOUNT__.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/users/$(__UID__)$",

      "__ACCOUNT__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/users/$(Filter Suffix)$", "__ACCOUNT__.DELETEOP=/admin/rest/v1/accounts/$(account_key)$/users/$(__UID__)$", "__LICENSE__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/licenses",

      "__GROUP__.SEARCHOP=/admin/rest/v1/accounts/$(account_key)$/groups", "__ACCOUNT__.__LICENSE__.ADDATTRIBUTE=/admin/rest/v1/accounts/$(account_key)$/licenses/$(__LICENSE__.key)$/users/$(__UID__)$",

      "__ACCOUNT__.__LICENSE__.REMOVEATTRIBUTE=/admin/rest/v1/accounts/$(account_key)$/licenses/$(__LICENSE__.key)$/users/$(__UID__)$",

      "__ACCOUNT__.groupKey.UPDATEOP=/admin/rest/v1/accounts/$(account_key)$/groups/$(groupKey)$/users/$(__UID__)$"

    • For the Lookup.GTM.UM.ReconAttrMap lookup definition:

      Code Key Decode

      PrimaryLicense[LOOKUP]

      PARENT.licenseKeys

      Licenses~License Name[LOOKUP]

      CHILD.licenseKeys
  6. If any attribute mappings are missing for custom attributes, log in to Oracle Identity Manager Design Console and update the mappings.
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 Manager.

See Also: