| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.2) Part Number B25493-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.2) Part Number B25493-03 |
|
|
View PDF |
This chapter provides an overview of the Oracle Collaboration Suite migration tools and options for e-mail and calendar.
This chapter contains the following sections:
Oracle Collaboration Suite Email Migration Tool is used to migrate from legacy source systems to the Oracle Collaboration Suite 10g Mail component of Oracle Collaboration Suite. It uses plug-ins developed to migrate from third-party e-mail systems, which include the following:
Microsoft Exchange Server versions 5.0 and 5.5
Microsoft Exchange Server 2000 and 2003
Lotus Domino Server release 5
Novell GroupWise 6.0
Samsung Contact 7.1.0 (formerly known as HP OpenMail)
Other IMAP4 rev1 compliant e-mail servers
Oracle Collaboration Suite Email Migration Tool is specifically designed to migrate large e-mail systems, such as:
Corporate installations that generally have large mailboxes
Internet service providers (ISPs) that have a large number of users with small mailboxes
You can install and run Oracle Collaboration Suite Email Migration Tool from either the source, the target, or any other intermediate system. To perform a migration, a system administrator requires the following:
A plug-in developed specifically for the source e-mail server
System administrator privileges on the source e-mail server
|
Note: Plug-ins for the preceding source e-mail systems are packaged with the Oracle Collaboration Suite Email Migration Tool. |
The plug-in communicates with the source e-mail system to extract data from the source message store, which it saves in a format that is understood by the migration tool. Once the required files are generated, the migration tool reads the files and migrates them to Oracle Collaboration Suite. The plug-in and Oracle Collaboration Suite Email Migration Tool communicate through an API.
Features of Oracle Mail migration include:
Two-phase migration: The e-mail migration spans across two phases, premigration and user migration. This facilitates large-scale migration of users and data with minimal downtime.
E-mail notifications: After creating the new user accounts and completing the migration process, users are notified about the new accounts.
Oracle Collaboration Suite Email Migration Tool performs the following tasks:
Provisions users on Oracle Collaboration Suite and defines user name creation policies on the target system
Consolidates domains
Maintains mail delivery throughout the migration process to eliminate downtime
Maintains mail delivery to the user if a data migration error occurs for a particular account
E-mail migration is an intricate process, which requires migration of the following:
Account information, including user names, public aliases, and distribution lists
Data, including messages, folders, shared folders, and server-side rules
Web client address books
In addition, the migration process requires changes to the Simple Mail Transfer Protocol (SMTP) routing so that future messages are directed to the Oracle Mail server.
Oracle Mail migration involves the following tasks:
Running the migration setup wizard to configure the migration
Extracting directory information from the source systemLoading information into migration tool and migration repositoryProvisioning users on Oracle Collaboration SuiteCreating batches of usersMigrating dataVerifying the migration
This section contains the following:
Oracle Collaboration Suite Email Migration Tool extracts account information from the source directory server or user profiles and places it into the target Oracle Collaboration Suite and the target Oracle Internet Directory, as shown in .
|
Note: Some plug-ins do not support migrating all objects. Therefore, the objects that can be migrated depend on the source system. |
Migrating user data is a major part of migration and uses the maximum system resources. It is also the most time consuming part of system migration, especially for large e-mail systems. To minimize the downtime that occurs during migration, a two-phase migration can help. Batching users is another way to efficiently manage the time needed to migrate data.
|
See Also:
|
The following operations occur during data migration:
Messages and folders are migrated
For shared messages, a copy of each message is inserted into the database with a pointer to every recipient of the same message instead of a copy of the message being sent to each recipient. This can save an enormous amount of disk space that would otherwise be taken up by duplicate e-mail messages.
Server-side rules and address books are migrated
New messages are routed to Oracle Collaboration Suite
Successful migration is verified
Oracle Collaboration Suite Email Migration Tool migrates data using migration based on either MBOX or IMAP.
Oracle Collaboration Suite Email Migration Tool invokes a plug-in to extract the folders and mails using the proprietary protocol of the source system, storing the extracted information in an MBOX format on the file system. The migration tool reads these files to migrate the data to Oracle Collaboration Suite.
The Oracle Collaboration Suite Email Migration Tool plug-in creates a collection of MBOX files for each user in a staging directory. Each MBOX file represents an e-mail folder and the plug-in appends messages to this file.
|
Note: MBOX migration without the use of plug-ins is not supported. |
An overview of the MBOX-based migration process is shown in Figure 1-2.
Figure 1-2 Overview of an MBOX-based Migration
|
See Also: Chapter3, "Step 1: Specifying Mail System Objects" for information on selecting a mail system object |
If no plug-in is available for your source e-mail system, and the system supports IMAP, Oracle Collaboration Suite Email Migration Tool can migrate users through this protocol. In this scenario, the migration tool performs an IMAP login to the source server for every user, retrieves the mail data, and transfers the data to Oracle Collaboration Suite. So, the migration tool needs to know the source IMAP password from every user. Because there is no direct way to retrieve the user's password from the source system, the source user's password has to be provided in the user list file before loading the users for mail migration. Also, when migrating to a different e-mail domain, the new domain name must be specified in the user list file.
During an IMAP-based migration, the Oracle Collaboration Suite Email Migration Tool extracts the data from the source e-mail system message store and places it directly into the Oracle Collaboration Suite message store, as shown in Figure 1-3.
|
Note: In IMAP-based migration, mail data is not written to intermediate files during the migration process. |
Figure 1-3 Overview of an IMAP-based Migration
|
Note: As long as you have a plug-in, MBOX-based migration can be used in an IMAP-supported source e-mail server to avoid source password requirements. IMAP-based migration requires user passwords to be provided. |
Oracle Collaboration Suite Email Migration Tool extracts public aliases and distribution lists from the source e-mail system and migrates them to Oracle Collaboration Suite. The tool also migrates shared folders and address books from the source e-mail system to Oracle Collaboration Suite.
For a complete list of migration tasks supported by source systems, refer to "Choosing the Migration Options".
Migrating from an existing calendar system to Oracle Collaboration Suite enables enterprises to deploy a single architecture for all collaborative applications, which in turn, reduces administrative efforts. However, Oracle Calendar migration is an intricate process that requires importing calendar data across networks for coexistence. For this reason, most Oracle Collaboration Suite customers rely on Oracle Consulting or an Oracle certified partner for performing the migration.
Oracle provides tools and utilities to migrate calendar data across various platforms including Microsoft Exchange, MeetingMaker, and Netscape. To preserve the working environment, this migration includes calendar data and other objects, such as directory information, private and public distribution lists, and aliases. The main platforms that can be migrated to Oracle Calendar are:
Microsoft Exchange Server
MeetingMaker
Netscape Calendar
In addition, Oracle Calendar supports the iCalendar standard. You can migrate calendar data from any platform that support this format.
|
See Also: Chapter 8, "Migrating Calendar Data Using the iCalendar Representation" for information about theuniical utility that is used to migrate calendar data in the iCalendar format. |
