| 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 information about the premigration tasks required for using Oracle Collaboration Suite Email Migration Tool. In addition, the chapter describes the installation process of the migration tool.
This chapter contains the following sections:
Before starting the e-mail migration, you need to ensure that Oracle Collaboration Suite and Oracle Internet Directory have been installed on the target system. In addition, the source e-mail system should be running for the entire duration of the migration process. You should try to migrate groups of users in a logical manner according to the structure of the enterprise to minimize any disruptions in communication between members of the same organizational unit. Gather preliminary information about the migration, including target domain structure, user namespace, and source domain structure and directory source.
|
Note: Only the users with Simple Mail Transfer protocol (SMTP) addresses are migrated. |
This section discusses the installation requirements that you need to meet to run Oracle Collaboration Suite Email Migration Tool. This section contains the following:
The system requirements for the computer on which Oracle Collaboration Suite Email Migration Tool will run are:
Memory: The amount of memory required to perform the migration depends upon specific variables, such as the volume of data to be migrated, profile of the message store, concurrency of the process, and size of messages. The general guideline for minimum memory is 1 GB of RAM.
Network Bandwidth: The network bandwidth requirements are the same as those for Internet Message Access Protocol version 4 (IMAP4) clients, although, for concurrent migrations, more bandwidth is required. Oracle recommends a bandwidth of 100 Mbps for Oracle Collaboration Suite Email Migration Tool.
|
Notes:
|
Intermediate Storage of Data During Migration: During an MBOX-based data migration, sufficient disk space must be available for intermediate storage of e-mail messages that need to be migrated. The formula for the calculation is as follows:
Disk space required = n * q * 1.5
where n is the number of users to be migrated and q is the quota for each user.
For example, the disk space requirement is 300 MB for migrating 10 users in an MBOX-based migration. This requirement is calculated after assuming a quota of 20 MB for each user, including all the intermediate storage files.
|
Notes: Oracle Collaboration Suite Email Migration Tool does not delete generated MBOX files. MBOX migration without the use of plug-ins is not supported. |
Configuration planning involves the following tasks:
Table 2-1 lists the various source e-mail systems supported by Oracle Collaboration Suite Email Migration Tool and the migration tasks supported by each plug-in for the corresponding source e-mail systems.
Table 2-1 Source E-mail Systems and Migration Tasks Supported
| Objects | MS Exchange 5.0 | MS Exchange 5.5 | MS Exchange 2000 | MS Exchange 2003 | Lotus Domino | Novell GroupWise | Samsung Contact | OES 5.2 |
|---|---|---|---|---|---|---|---|---|
|
LDAP-Based User Provisioning |
No |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
|
LDIF-Based User Provisioning |
Yes |
Yes |
No |
No |
No |
No |
Yes |
Yes |
|
Public Aliases |
No |
No |
No |
No |
No |
Yes |
Yes |
Yes |
|
Distribution Lists |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Address Books |
No |
No |
No |
No |
No |
No |
No |
Yes |
|
IMAP-Based Data Migration |
No |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
|
MBOX-Based Data Migration |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
|
Server-Side Rules |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
Yes |
|
Shared Folders |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
No |
Yes |
|
Routing |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
|
Note: For e-mail systems other than the ones listed in Table 2-1, all migration tasks are supported. However, none of the extraction options in the migration setup wizard are enabled. You must provide files for each of the e-mail system objects that you want to migrate, according to the formats mentioned in Appendix A, "Plug-In Generated File Formats". |
During data migration, if routing is enabled in the migration setup, Oracle Collaboration Suite Email Migration Tool creates forwarding addresses on the source e-mail system for each user. Therefore, the e-mail messages received at the source e-mail system are forwarded to Oracle Collaboration Suite.
|
Note: The forwarding addresses created by the migration tool on the source system are not deleted after migration. |
In the case of inbound and outbound SMTP servers, do the following:
Set the orclMailSMTPRecipientRewritingRules attribute in Oracle Internet Directory using the oidadmin tool as follows:
1 $*@Target_SMTP_Host, $1@Target_Domain; description
where, Target_SMTP_Host and Target_Domain are the target SMTP host and the target domain that you need to enter in the Mail Services screen of the migration setup wizard, will be as follows:
1 $*@smtp-host.acme.com, $1@acme.com
You can also set the orclMailSMTPRecipientRewritingRules attribute in Oracle Internet Directory using Oracle Enterprise Manager. To do so, you must change the string in Recipient Address Rewriting Rule field in SMTP_IN Configuration page as follows:
$*@Target_SMTP_Host, $1@Target_Domain; description
where, Target_SMTP_Host and Target_Domain are the target SMTP host and the target domain that you need to enter in the Mail Services screen of the migration setup wizard, will be as follows:
$*@smtp-host.acme.com, $1@acme.com
Set the orclMailProcessFlag attribute in Oracle Internet Directory as -l using Oracle Enterprise Manager.
Disable the anti-spam check feature for the entire duration of the migration process.
Restart the inbound and outbound SMTP servers.
In the case of collapsing domains, set the following recipient rewriting rule:
$*@source domain, $1@target domain
where source domain and target domain are the source domain and target domain which you need to enter in the Mail Services screen, will be as follows:
$*@$+.acme.com, $1@acme.com
Oracle Collaboration Suite can be configured to support different character sets.
Refer to the Oracle Mail Administrator's Guide for information about configuring the Oracle Collaboration Suite database to support different character sets.
After you ensure that you have met the system requirements for installing Oracle Collaboration Suite Email Migration Tool, you can start the installation. To install the tool:
Set ORACLE_HOME if it is not set already:
To set ORACLE_HOME on UNIX operating systems, do the following:
For C-Shell, enter the following at the command prompt:
setenv ORACLE_HOME directory_name
For Korn-Shell, enter the following at the command prompt:
set ORACLE_HOME=/directory_name
export ORACLE_HOME
To set ORACLE_HOME on Microsoft Windows operating systems, enter the following at an MS-DOS prompt:
set ORACLE_HOME=C:\directory_name
In Microsoft Windows, you can also set ORACLE_HOME by right-clicking the My Computer icon on the desktop, and then clicking Properties from the pop-up menu, and then clicking the Advanced tab on the System Properties page.
Create the following directory structure, if it is not created already:
In Microsoft Windows: %ORACLE_HOME%\oes\migration
In UNIX: $ORACLE_HOME/oes/migration
Unzip the esmigration.zip file in the oes/migration directory.
In UNIX operating systems, navigate to the Oracle home directory and enter the following command at the command prompt:
unzip dir_containing_esmigration.zip/esmigration.zip -d $ORACLE_HOME/oes/migration
For both the Windows and UNIX-based operating systems, the following files and directories are created where you unzip the esmigration.zip file:
help, log, files, bin, images, sql, lib, mesg, and dtd
Set the JREHOME environment variable to point to the Java Runtime Environment (JRE) directory (version 1.4.2 or higher). You can set up the variable either in the environment or in the migrate.cmd file for Windows or migrate.sh file for UNIX.
After you install Oracle Collaboration Suite Email Migration Tool, you must choose and set up the appropriate plug-in for your source e-mail system.
This section contains information about the migration requirements that are specific to the source e-mail system. This section contains the following:
This section discusses the premigration requirements for migrating from Microsoft Exchange 5.0, 5.5, 2000, or 2003.
|
Note: The Microsoft Exchange plug-in is available only on Microsoft Windows NT, Windows 2000 Professional and Server operating systems. |
If you are running Oracle Collaboration Suite Email Migration Tool on a computer other than the one on which Microsoft Exchange is installed, make sure that Microsoft Outlook and Microsoft Exchange Administrator are installed on the computer where Oracle Collaboration Suite Email Migration Tool is running.
Table 2-2 lists the software requirements for migrating from different versions of Microsoft Exchange.
Table 2-2 Software Requirements for Migrating from Microsoft Exchange
| Microsoft Exchange Version | Microsoft Outlook Client Version | Is Microsoft Exchange Administrator Required? |
|---|---|---|
|
5.0 |
2000 |
Yes |
|
5.5 |
2000 |
Yes |
|
2000 |
2000 |
Yes |
|
2003 |
2000 |
Yes |
Creating an Administrator Profile
For Microsoft Exchange, you need to create an administrator profile on the computer where Oracle Collaboration Suite Email Migration Tool is installed. Perform the following steps to create an administrator profile:
Ensure that Microsoft Outlook is installed on the system and is operating correctly.
Create a profile using Microsoft Outlook as follows:
Click Start, then Settings, and then Control Panel.
Double-click the Mail icon.
Click Show Profiles and then click Add.
Select Microsoft Exchange Server, and enter a name in Profile Name. Ensure that the profile name is the same as the Exchange alias. For example, the Windows user Administrator should have the profile named "Administrator".
Click Next.
Enter the name of the server in the Microsoft Exchange Server.
Enter the name of an administrator mailbox in Mailbox.
When migrating from the Lotus Domino server release 5 to Oracle Collaboration Suite, 10g Release 1 (10.1.2) , use the Lotus Notes plug-in with Oracle Collaboration Suite Email Migration Tool. The plug-in works with Lotus Domino version 5.0.8, or higher.
|
Note: The Lotus Notes plug-in is available only on Microsoft Windows NT, 2000 Professional and Server operating systems. |
The following requirements should be met to ensure successful migration:
Lotus Notes must be installed on the computer where the plug-in is run and the Lotus Notes directory should be located in the system/user path.
If you want to perform an MBOX migration, the plug-in assumes that there is one user who has administrator privileges to read the contents of every user's e-mail file. To grant read access to the Lotus Notes administrator, do the following:
Select the Lotus Notes e-mail database for which you need to provide read rights from the Lotus Notes interface.
Click File, Database, and then Access Control.
|
Note: You do not need to perform this step if the access control list is already open. |
Select the name of the person to whom you want to grant rights from People, Servers, and Groups.
Select an access level from the Access Level list box.
Select the appropriate options to give permission to the Lotus Notes administrator to perform the following:
Create documents
Delete documents
Create personal agents
Create personal folders/views
Create shared folders/views
Create LotusScript Agent
Read public documents
Write public documents
If Oracle Collaboration Suite Email Migration Tool is used to create base accounts on Oracle Collaboration Suite, the Lotus Domino Lightweight Directory Access Protocol (LDAP) server must be running.
To configure Lotus Notes plug-in, ensure the following:
The nesmtld.dll file has been moved from the $ORACLE_HOME/oes/migration/bin directory to the directory where Lotus Notes is installed.
|
Note: nesmtld.dll should be present only in the Lotus Notes directory and not in any other directory on the computer where the plug-in is run. |
The key file (user.id) of the administrator, who has permission to access and read all e-mail files, must be available on the computer where Lotus Notes is installed.
The KeyFileName entry in the notes.ini file must contain the file name of the administrator's key file. The notes.ini file is located in the directory where Lotus Notes is installed.
The notes.ini file contains the following entry. To add this entry to the file, edit the notes.ini file, located in the Lotus Notes installation directory, and add the following line at the end of the file followed by a new line feed:
EXTMGR_ADDINS=ESMTLD
The following requirements must be met to ensure successful migration from the Samsung Contact server:
Ensure that the Remote Client Interface service is running on the Samsung Contact server.
Ensure that the Samsung Contact MAPI Service Provider 08.00.02 is installed, if Oracle Collaboration Suite Email Migration Tool is running on Windows operating systems.
Ensure that all users on the Samsung Contact server have the administrator user as a real designate. To do this, perform the following steps:
In the Samsung Contact Java Windows client, click Tools, then Preferences, and then Designates.
Click New.
Select Designate.
Enter the name of the administrator in the Personal name form in the Samsung Contact system directory. For example:
John A. Smith/california,idc,dev,imteam
In the Access Area and Capabilities window, grant the minimum access permissions, as follows:
Inbox: R
Drafts: R
Sent: R
Filing Cabinet: R
Address Book: R
Bulletin Board: R
Personal Directory: R
Configuration: R/M
Select the Personal, Private, and Confidential check boxes.
Specify the start and expiry dates.
|
Note: You can leave the start and expiry dates blank to provide unlimited time for designate access. |
Click OK in client versions later than 7.5.0.
|
Note: You need to click Apply, and then click OK for client versions 7.5.0 and earlier. |
If Oracle Collaboration Suite Email Migration Tool is running on the Solaris operating system, make sure the computer on which the tool is running has a minimum swap space of 2 GB.
The following requirements must be met to ensure successful migration from a Novell GroupWise server:
If Oracle Collaboration Suite Email Migration Tool is used to provision users on Oracle Collaboration Suite, the Novell GroupWise LDAP server must be running, and it should allow anonymous binds.
Novell Directory Service (NDS) or eDirectory 8.6 with Novell GroupWise 6.0 or higher must be available on the computer where the plug-in is running.
|
Note: NDS is a Novell directory service, which is also known as eDirectory. Here, NDS and eDirectory are used interchangeably. |
Message Transfer Agent (MTA) and Post Office Agent (POA) of the Novell GroupWise server installation process must be running on the computer where the plug-in is run.
The Novell GroupWise client 6.0.2 patch must be applied on the computer from which Oracle Collaboration Suite Email Migration Tool is invoked.
The Novell Default Settings profile must contain the Novell GroupWise Address Book service.
Locate the Novell Default Settings profile in Windows by clicking Start, Settings, Control Panel, Mail, and then Show Profiles. The profile is added automatically when the GroupWise client is installed on the Windows system. If the profile does not contain the service, add it to the profile.
Users must set up proxy access for the administrator.
The GroupWise administrator must be able to access (proxy) all users on the GroupWise system.
To grant proxy access to the GroupWise administrator:
Log in as a GroupWise user.
Click Tools, Options, Security, and then Proxy Access.
Click Address Book adjacent to the Name field.
Choose the GroupWise administrator's name from the Novell GroupWise Address Book. Novell GroupWise Address Book is the GroupWise system address book that holds all users in the GroupWise domain.
Select Mail/Phone for read access.
Click OK to grant proxy access to the GroupWise administrator.
To ensure that proxy access is available to the GroupWise administrator:
Log in as the GroupWise administrator.
Click File, and then Proxy. A window that contains the Name field and Proxy list is displayed.
Click Address Book and choose a user who has granted proxy access to the GroupWise administrator.
Click OK.
