| Oracle® Identity Manager Connector Guide for Microsoft Exchange Release 9.1.1 Part Number E11198-06 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for Microsoft Exchange Release 9.1.1 Part Number E11198-06 |
|
|
View PDF |
This chapter provides an overview of the updates made to the software and documentation of the Microsoft Exchange connector in release 9.1.1.
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 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.
There are no software updates in release 9.1.0.1.
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. |
The following sections discuss documentation-specific updates:
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.
Information specific to installing the Remote Manager for Microsoft Exchange 2007 has been added in the following sections:
The following is a documentation-specific update 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" 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.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
