This chapter provides an overview of the updates made to the software and documentation for release 9.1.1.7 of the Microsoft Exchange connector.
Note:
Release 9.1.1.7 of the connector comes after release 9.1.1.5. Release number 9.1.1.6 has not been used.The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software. This section also points out the sections of this guide that have been changed in response to each software update.
Documentation-Specific Updates
These include major changes made to this guide. For example, the relocation of a section from the second chapter to the third chapter is a documentation-specific update. These changes are not related to software updates.
The following sections discuss software updates:
The following are the software updates in release 9.1.1.7:
In the earlier releases, if you were using Microsoft Exchange 2007 or Microsoft Exchange 2010 as the target system, then a Delete Mailbox provisioning operation was implemented by using the LDAP objects of Microsoft Active Directory. From this release onward, the connector is shipped with the DeleteMailboxExchange2007.vbs and DeleteMailboxExchange2010.vbs files that are used by the Remote Manager to delete mail boxes.
See the following sections in the connector guide for more information:
Files and Directories On the Connector Installation Media
Creating the IT Resource
The following are issues resolved in release 9.1.1.7:
| Bug Number | Issue | Resolution |
|---|---|---|
| 9243009 | During an Update Primary E-mail Address provisioning operation, the connector applied case-sensitive checks on the primary e-mail address. | This issue has been resolved. The connector does not apply any case-sensitive checks on the primary e-mail address during an Update Primary E-mail Address provisioning operation. |
| 9484364 | During a mailbox provisioning operation, the connector set incorrect values to attributes in Microsoft Active Directory. | This issue has been resolved. During a mailbox provisioning operation, the connector does not set incorrect values to attributes in Microsoft Active Directory. |
| 9709126 | During a Modify User provisioning operation, if you modified the primary e-mail address of the user, then the change was not reflected on the target system. | The issue has been resolved. If you modify the primary e-mail address, then the change is propagated to the target system. |
| 11067013 | The following issue was observed when you configured your connector for multiple installations of the target system
When you run two instances of the same scheduled task at the same time (on different target system installations), then the Microsoft Exchange resource for each target system installation linked to the same OIM User. |
This issue has been resolved. |
The following are the software updates in release 9.1.1.5:
From this release onward, the connector can be installed and used on Oracle Identity Manager 11g release 1 (11.1.1). Where applicable, instructions specific to this Oracle Identity Manager release have been added in the guide.
See Section 1.1, "Certified Deployment Configurations" for the full list of certified Oracle Identity Manager releases.
From this release onward, the connector provides support for request-based provisioning on Oracle Identity Manager 11g release 1 (11.1.1).
See Section 3.6.2.2, "Request-Based Provisioning" for more information.
The following are software updates in release 9.1.1.4:
The Microsoft Exchange 2010 target system is now certified.
New scripts are added to support this target system version. To differentiate amongst the scripts a new attribute called, isexchange2010, is added to the Lookup.Exchange.Configuration lookup definition.
See "Certified Deployment Configurations" section for information about the certified components.
The following are issues resolved in release 9.1.1.4:
| Bug Number | Issue | Resolution |
|---|---|---|
| 9232682 | When the Mail Store lookup reconciliation was ran, mailbox policies were also reconciled. | This issue has been resolved. From this release onward, all the storage groups are extracted and the mail stores in each storage group are reconciled. In Microsoft Exchange 2010 the mailstore lookup reconciliation runs as expected. This is because the storage groups and mailbox policies are not seen. Change the value of isexchange2010 parameter to yes in the Lookup.Exchange.Configuration lookup definition. |
The following are issues resolved in release 9.1.1.1:
The following certification changes have been made in this release:
From this release onward, the connector can be installed and used on Oracle Identity Manager release 9.1.0.2 or later.
The Microsoft Exchange 2007 target system is now certified for both x86 and x64 computers.
See "Certified Deployment Configurations" for information about the certified components.
From this release onward, the connector supports reconciliation and provisioning of mailboxes for users across multiple Microsoft Active Directory domains.
See "Reconciliation and Provisioning of Mailboxes Across Multiple Domains" for more information.
In the Mailstore lookup definition (Lookup.ExchangeReconciliation.MailStore) on the process form, the IT resource key and IT resource name are displayed along with the name of the mailstore. During provisioning operations, this feature enables you to select mailstores from a specific Microsoft Exchange installation.
See "Lookup Field Synchronization" for information about the format of entries in this lookup definition. In addition, if your Oracle Identity Manager installation is running on Microsoft SQL Server, then perform the procedure described in "Modifying Dependent Lookup Query Properties for Lookup Fields on Microsoft SQL Server".
The following are issues resolved in release 9.1.1.1:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8229697 | Data logged for error scenarios did not provide sufficient detail. | This issue has been resolved. Log messages have been made more descriptive. In addition, the stack trace is captured for some error scenarios. |
| 8669819 | The connector had code-level dependencies on the Microsoft Active Directory User Management connector. | From this release onward, the code-level dependencies have been removed. While deploying the connector, you must perform the procedure described in the "Linking the Exchange Resource Object with the AD User Resource Object" section. |
The following are issues resolved in release 9.1.1:
Microsoft Windows Server 2008 Added to the List of Certified Target System Host Platforms
Introduction of the Lookup.Exchange.Constants Lookup Definition
From this release onward, Microsoft Windows Server 2008 has been added to the list of certified target system host platforms. This has been mentioned in the "Certified Deployment Configurations" section.
From this release onward, Oracle Identity Manager release 9.1.0.1 is the minimum supported Oracle Identity Manager release. This is mentioned in the "Certified Deployment Configurations" section.
The Parameters.Exchange lookup definition has been renamed to "Lookup.Exchange.Configuration." In addition, new entries that hold the names of process form fields used for matching user records have been added in this lookup definition. If you create a copy of the process form, then you can specify details of the new process form in the copy of the Lookup.Exchange.Configuration lookup definition. This feature enables you to create multiple copies of the connector without making code-level changes.
See the following sections for more information:
The Lookup.Exchange.Constants lookup definition stores the constants and variables defined in the Java classes that constitute the connector.
Caution:
You must not change any entry in the Lookup.Exchange.Constants lookup definition. If you change any entry, then the connector will not function correctly.The name of this lookup definition is specified as the value of the Exchange Constants Lookup Code Key in the Lookup.Exchange.Configuration lookup definition.
You use the Query attribute of the user reconciliation scheduled tasks to specify the query condition that must be applied during reconciliation. In earlier releases, you used the Use Native Query attribute to specify that the query condition was in native LDAP format. From this release onward, you can use only native LDAP queries. The Use Native Query attribute has been removed from the scheduled tasks.
The following are issues resolved in release 9.1.1:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7157839, 7676069, and 7507908 | If the target system was Microsoft Exchange 2007, then the connector did not respond correctly to the RMTimeOut setting in the Lookup.Exchange.Configuration lookup definition. | This issue has been resolved. The RMTimeOut attribute of the Lookup.Exchange.Configuration lookup definition has been removed. This feature is now handled internally by the connector. |
| 7157996 | When you enabled a mailbox, you were not required to set an incoming or outgoing message size. This is not the same as the behavior on the target system. | This issue has been resolved. The DefaultInComingMsgSize and DefaultOutGoingMsgSize parameters have been added in the Lookup.Exchange.Configuration lookup definition.
See "Configuring the Lookup.Exchange.Configuration Lookup Definition" for more information. |
| 8276367 | Earlier the mail store name was extracted from the mail store DN and displayed in the lookup field on the Administrative and User Console. | This issue has been resolved. From this release onward, the full mail store DN is displayed in the lookup field. |
| 7577059 | An exception is encountered on running a scheduled task for which an attribute's value is not specified. In earlier releases, the message displayed did not provide sufficient details to identify the cause of the exception. | This issue has been resolved. The stack trace is displayed on the Java console and is also recorded in the log file. |
| 7145460 | Suppose an OIM User was provisioned a Microsoft Active Directory resource and a Microsoft Exchange mailbox. After the next target resource reconciliation run, suppose the user was deleted on the target system and the scheduled task for reconciliation of deleted users was then run. At this point, the Microsoft Active Directory resource was revoked but the mailbox was not revoked. | This issue has been resolved. The mailbox is revoked along with the Microsoft Active Directory resource. |
This is the first release of the Oracle Identity Manager Connector for Microsoft Exchange release 9.1.x. The following are issues resolved in release 9.1.0:
Support for Specifying the Exchange Server and Mail Store for Provisioning Operations
Support for Reconciliation of Mailbox Data from Specific Mail Store and Distribution Group
Support for the Application of Native LDAP Queries During Reconciliation
Introduction of Scheduled Task for Reconciliation of Deleted Mailboxes
The connector can be used to integrate Microsoft Exchange 2000, 2003, or 2007 with Oracle Identity Manager. In addition, the connector also supports mixed mode operation in which a single connector is used to integrate more than one version of the target system with Oracle Identity Manager.
Information specific to the Microsoft Exchange 2007 has been provided at various places in this guide.
You can now install the connector by using the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.
See "Running the Connector Installer" for more information.
The MailStore Name field has been added to the process form for provisioning operations. You can use this field to specify the Exchange server and mail store in which provisioning operations must be performed.
By using the Mail Store Name and Distribution Group Name attributes of the Exchange Reconciliation Task scheduled task, you can specify the mail store or distribution group from which mailbox data must be reconciled.See "Types of Reconciliation Enabled by the Connector" for more information.
In the earlier release, you specify the query condition for limited reconciliation by using operators that are not native to the target system. You can now specify the query condition using either non-native or native operators.
See "Limited Reconciliation vs. Regular Reconciliation" for more information.
You can use the MEXC Timestamp attribute of the reconciliation scheduled task to specify whether you want to configure full reconciliation or incremental reconciliation.
See "Full Reconciliation vs. Incremental Reconciliation" for more information.
The connector can be configured to reconcile deleted mailbox data. The Exchange Delete Recon Task scheduled task has been introduced to automate this process.
See "Exchange Delete Recon Task" for more information about this scheduled task.
The following sections discuss documentation-specific updates:
The following documentation-specific update has been made in revision "17" of release 9.1.1.7:
Section 4.4.2, "Populating the Second IT Resource on the Process Form" has been added.
The following documentation-specific updates have been made in revision "16" of release 9.1.1.7:
The "Oracle Identity Manager" row in Table 1-1, "Certified Deployment Configurations" has been modified.
Section 1.2, "Usage Recommendation" has been added.
The following are documentation-specific updates in revision "15" of release 9.1.1.7:
A note has been added in the beginning of Section 4.4, "Configuring the Connector for Multiple Installations of the Target System."
The name of the "Known Issues" chapter has been changed to "Known Issues and Troubleshooting."
An issue related to Powershell 3.0 has been documented in Table 5-1, "Troubleshooting".
The following are documentation-specific updates in revision "14" of release 9.1.1.7:
The "Oracle Identity Manager" row in Table 1-1, "Certified Deployment Configurations" has been modified.
A note has been added in the "Files in the Datasets directory" rows of Table 2-1, "Files and Directories On the Connector Installation Media".
The following sections have been added:
Instructions specific to Oracle Identity Manager release 11.1.2.x have been added in the following sections:
The following are documentation-specific updates in earlier revisions of release 9.1.1.7:
The Section 2.1.2.1, "Creating a Target System User Account for Connector Operations" has been modified.
In Section 4.4, "Configuring the Connector for Multiple Installations of the Target System," information has been added to the note.
In Table 2-2, "Parameters of the IT Resource" the description of the Report Log Location parameter has been updated.
In Section 3.1.2, "Guidelines on Performing Provisioning Operations," a new guideline has been added.
There are no documentation-specific updates in release 9.1.1.5.
The following are documentation-specific updates in release 9.1.1.4:
In Section 1.1, "Certified Deployment Configurations," the target system requirement has been added.
In Table 3-1, "Attributes of the Lookup.Exchange.Configuration Lookup Definition" a new attribute has been added.
A new Section 2.1.2.2, "Configuring Microsoft Exchange 2010" has been added.
In Section 1.4.1.2, "Architecture of the Connector for Microsoft Exchange 2007," the connector architecture has been updated.
The following are documentation-specific updates in release 9.1.1.1:
It has been certified that the Remote Manager can be installed on any domain member on which Microsoft Exchange Management Tools is installed. This is also mentioned in the "Installing the Remote Manager" section.
In Section 1.1, "Certified Deployment Configurations," the JDK requirement has been added.
The following are documentation-specific updates in release 9.1.1:
In the "Mailbox Provisioning Functions Supported by the Connector" section, the following functions have been added:
Disable Mail box
Enable Mail box
In the "Mailbox Fields for Target Resource Reconciliation" section, the following fields have been added to the list of target system fields that are reconciled:
userPrincipalName
homeMDB
mDBUseDefaults
In the "Known Issues and Troubleshooting" chapter, a description for Bug 7207232 has been added.
Microsoft Windows 2000 is no longer a supported host for the target system. All occurrences of "Microsoft Windows 2000" have been removed from this guide.
Information about JDK requirement for installing Remote Manager has been added in the following sections:
In the "Certified Deployment Configurations" section, changes have been made in the "Target Systems" row.
Information specific to installing the Remote Manager for Microsoft Exchange 2007 has been added in the following sections:
Major changes have been made in the structure of the guide. The objective of these changes is to synchronize the guide with the changes made to the connector and to improve the usability of information provided by the guide.
See "Roadmap for Deploying and Using the Connector" for detailed information about the organization of content in this guide.