7 Upgrading the Office 365 Connector
If you have already deployed the 11.1.1.5.0 version of the Office 365 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 Upgrade Steps
This is a summary of the procedure to upgrade the connector for both staging and production environments.
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.
-
Staging Environment
Perform the upgrade procedure by using the wizard mode. See Wizard Mode Upgrade in Staging Environment in Oracle Fusion Middleware Administering Oracle Identity Governance.
-
Production Environment
Perform the upgrade procedure by using the silent mode.
Note:
While running Step 4 in the upgrade wizard, in theOffice365 Users Process Definitions
screen, under the Define Process Definition Mappings
tab ensure that you do not retain the Process Tasks
for Enable User
and Disable User
options.
7.2 Postupgrade Steps
Postupgrade steps involve uploading new connector JAR to Oracle Identity Manager database.
Perform the following procedure:
-
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.
-
Upload the new connector JARs:
-
Run the Oracle Identity Manager Upload JARs ($ORACLE_HOME/bin/UploadJars.sh) utility to upload the connector JARs.
-
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.
-
Delete the following Code Key and Decode entries in the
Lookup.Office365.Configuration
lookup definition:-
Code Key: Bundle Version; Decode: 1.0.1115
-
Code Key: relURIs
Decode:
"__ACCOUNT__.CREATEOP=/$(tenant_id)$/users?$(api_version)$","__ACCOUNT__.UPDATEOP=/$(tenant_id)$/users/$(__UID__)$?$(api_version)$","__ACCOUNT__.SEARCHOP=/$(tenant_id)$/users?$(api_version)$/$(Filter Suffix)$","__ACCOUNT__=/$(tenant_id)$/users/$(__UID__)$?$(api_version)$","__ACCOUNT__.manager.SEARCHOP=/$(tenant_id)$/users/$(__UID__)$/manager?$(api_version)$","__ACCOUNT__.manager=/$(tenant_id)$/users/$(__UID__)$/$links/manager?$(api_version)$","__ACCOUNT__.__GROUP__.SEARCHOP=/$(tenant_id)$/users/$(__UID__)$/memberOf?$(api_version)$","__ACCOUNT__.__GROUP__.DELETEOP=/$(tenant_id)$/groups/$(__GROUP__.objectId)$/$links/members/$(__UID__)$?$(api_version)$","__ACCOUNT__.__GROUP__=/$(tenant_id)$/groups/$(__GROUP__.objectId)$/$links/members?$(api_version)$","__GROUP__.CREATEOP=/$(tenant_id)$/groups?$(api_version)$","__GROUP__.UPDATEOP=/$(tenant_id)$/groups/$(__UID__)$?$(api_version)$","__GROUP__.SEARCHOP=/$(tenant_id)$/groups?$(api_version)$/$(Filter Suffix)$","__GROUP__=/$(tenant_id)$/groups/$(__UID__)$?$(api_version)$","__GROUP__.member=/$(tenant_id)$/groups/$(__UID__)$/$links/members?$(api_version)$","__ROLE__.SEARCHOP=/$(tenant_id)$/directoryRoles?$(api_version)$/$(Filter Suffix)$","__ACCOUNT__.__ROLE__=/$(tenant_id)$/directoryRoles/$(__ROLE__.objectId)$/$links/members?$(api_version)$","__ACCOUNT__.__ROLE__.DELETEOP=/$(tenant_id)$/directoryRoles/$(__ROLE__.objectId)$/$links/members/$(__UID__)$?$(api_version)$","__ROLE__.member=/$(tenant_id)$/directoryRoles/$(__UID__)$/$links/members?$(api_version)$","__ACCOUNT__.__ROLE__.SEARCHOP=/$(tenant_id)$/users/$(__UID__)$/memberOf?$(api_version)$","__LICENSE__.SEARCHOP=/$(tenant_id)$/subscribedSkus?$(api_version)$/$(Filter Suffix)$","__ACCOUNT__.__LICENSE__.ADDATTRIBUTE=/$(tenant_id)$/users/$(__UID__)$/assignLicense?$(api_version)$","__ACCOUNT__.__LICENSE__.REMOVEATTRIBUTE=/$(tenant_id)$/users/$(__UID__)$/assignLicense?$(api_version)$"
-
-
Delete the following Code Key and Decode entry in the
Lookup.Office365.Configuration.Trusted
lookup definition:-
Code Key: Bundle Version; Decode: 1.0.1115
-
Code Key: relURIs; Decode: "__ACCOUNT__.SEARCHOP=/$(tenant_id)$/users?$(api_version)$/$(Filter Suffix)$","__ACCOUNT__=/$(tenant_id)$/users/$(__UID__)$?$(api_version)$","__ACCOUNT__.manager.SEARCHOP=/$(tenant_id)$/users/$(__UID__)$/manager?$(api_version)$","__ACCOUNT__.manager=/$(tenant_id)$/users/$(__UID__)$/$links/manager?$(api_version)$"
-
-
Delete the following Code Key and Decode entries in the
Lookup.Office365.UM.ReconAttrMap
lookup definition:Code Key: Usage Location; Decode: UsageLocation
-
Delete the following Code Key and Decode entries in the
Lookup.Office365.UM.ReconAttrMap.Trusted
lookup definition:Code Key: Usage Location; Decode: UsageLocation
-
-
Restart Oracle Identity Manager.
- If the connector is deployed on a Connector Server, then:
-
Stop the connector server.
-
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.
-
Start the connector server.
Note:
-
To configure incremental reconciliation, see Configuring Incremental Reconciliation.
- If you have configured the connector for multiple versions of target system, then refer to Configuring the Connector for Multiple Installations of the Target System for more information.
-
-