3
Migration Tasks

This chapter provides information about migration tasks.

This chapter contains these topics:

• Administrator Responsibilities Before Migration
• Task 1: Starting the Migration Tool
• Task 2: Logging In to the Migration Repository
• Task 3: Setting Up a Migration Session
• Task 4: Migrating Users to Oracle Email
• Task 5: Extracting Mail System Objects from the Source System
• Task 6: Batching
• Task 7: Migrating Shared Folders
• Task 8: Migrating Public Aliases
• Task 9: Migrating Distribution Lists
• Task 10: Migrating WebMail Address Books
• Task 11: Migrating Data
• Post-Migration Administrator Responsibilities

Administrator Responsibilities Before Migration

Note: At least one instance of Oracle Collaboration Suite, with the Email Server component, and Oracle Internet Directory must be installed on the target system prior to installing the Migration Tool.

This section contains the following topics:

• Configuring the Domain Name Server Entry
• IMAP Server Configuration
• Verifying Source and Target IMAP Server Ports
• Installing the Migration Tool
• Setting Up the Oracle eMail Server Plug-In
• Preparing for a Microsoft Exchange Migration

Configuring the Domain Name Server Entry

You must configure the DNS entry prior to beginning the migration process so that the target Oracle Email server is visible to the rest of the internet.

IMAP Server Configuration

The source IMAP servers should be suitably configured for a possibly large number of IMAP connections for concurrently migrating users. This includes database configuration for the source and target systems, if required.

The IMAP connection requirements are one connection per concurrent user on the source IMAP server and three connections per concurrent user on the target IMAP server.

To deploy message sharing in JMA based migrations, you must configure the IMAP server as follows:

1. Use the Oracle Enterprise Manager administrator pages to add the value MigrationHeader=Message-ID to the Process Flag IMAP server process parameter.
2. Restart the IMAP server prior to running the Migration Tool.

   See Also: Oracle Email Administrator's Guide for information about setting up process parameters on your IMAP server

Verifying Source and Target IMAP Server Ports

If you are performing an IMAP-based migration, verify that both the source and target IMAP servers are configured on port 143.

If you are performing an MBOX-based migration, verify that the target IMAP server only is configured on port 143.

See Also: Oracle Email Administrator's Guide for target IMAP server configuration information

Installing the Migration Tool

The Migration Tool can be run on both Windows NT and UNIX platforms.

Note: All source Microsoft Exchange servers in the currently migrating site must stay up for the entire duration of the migration. If you are migrating from a Microsoft Exchange source e-mail system and running the Migration Tool on a machine other than the one upon which Microsoft Exchange is installed, ensure that Microsoft Outlook and Microsoft Exchange Administrator are installed on the machine from which you are running the Migration Tool.

This section contains these topics:

• Setting Up JREHOME on UNIX
• Setting Up JREHOME on Windows NT

To install the Migration Tool:

1. Unzip the esmigration.zip file.

   For UNIX operating systems, enter the following:

   unzip esmigration.zip
   
   

   For Windows NT operating systems, use WinZip to unzip and extract all files from the esmigration.zip file.

   For either operating system, the following files and directories are created where you unzip the esmigration.zip file: doc, help, log, files, bin, images, sql, config, lib, and esmsplugin.tar.

2. Set up the JREHOME environment variable to point to the Java Runtime Environment (JRE) 1.3.1 directory.

Setting Up JREHOME on UNIX

To set up JREHOME on UNIX operating systems, do the following:

• For C-Shell, enter the following:

  setenv JREHOME directory_containing_JDK_131
  
  

• For Korn-Shell, enter the following:

  set JREHOME=/directory_containing_JDK_131
  export JREHOME
  

Setting Up JREHOME on Windows NT

To set up JREHOME on Windows NT operating systems, use a MS-DOS prompt to enter the following command:

set JREHOME=C:\directory_containing_JDK_131

Once the Migration Tool is installed, you must set up the appropriate plug-in for your source e-mail system.

Setting Up the Oracle eMail Server Plug-In

If your source e-mail system is Oracle eMail Server, you must provide domain configuration name (DCN) and node information to the ES52Plugin.properties file, located in the Migration Tool bin directory, as follows:

DCN Specification

Provide one line per source domain. The entry must indicate the domain's DCN and be in the form

oracle.mail.migration.plugin.es52.dcn.domain_name=hostname:port:SID:password

For example, if the source domain is oracle.com and the SID for the DCN is db1, which runs on host h1 on port 1521, and the oo account password is oo, the DCN entry is as follows:

oracle.mail.migration.plugin.es52.dcn.oracle.com=h1:1521:db1:oo

Nodes Specification

Provide one line per source node, in the form

oracle.mail.migration.plugin.es52.node.node_name=hostname:port:SID:password

For example, if the source node is ESNODE and the SID for the node is db1, which runs on host h1 on port 1521, and the oo account password is oo, the node entry is as follows:

oracle.mail.migration.plugin.es52.node.ESNODE=h1:1521:db1:oo

Preparing for a Microsoft Exchange Migration

If your source e-mail system is Microsoft Exchange 5.0 or 5.5, you must perform the following tasks:

• Creating an Administrator Profile Using Microsoft Outlook
• Ensuring that the MAPI Spooler Process is Running
• Using Statistics Task to Estimate Disk Space Requirements (Optional)

Creating an Administrator Profile Using Microsoft Outlook

If your source e-mail system is Microsoft Exchange, perform the following steps on the machine on which the source e-mail system is installed to create an administrator profile:

1. Ensure that Microsoft Outlook is installed on the machine and is operating correctly.
2. Create a profile using Microsoft Outlook.
   1. Select Start > Settings > Control Panel from the Windows NT task bar.
   2. Double-click the Mail icon.
   3. Click Show Profiles... > Add....
   4. Select Microsoft Exchange Server and enter a name in the Profile Name field. Click Next.
   5. Enter the name of the server in the Microsoft Exchange Server field.
   6. In the Mailbox field, enter the name of an administrator.
3. Enter the profile information into the es_msplugin.ini file, which is available in the Migration Tool config directory. The format of the file is as follows:

   profile_name=profile_name
   password=password
   
   

   For example, if the profile name is admin and the password is secret, the format of the file is:

   profile_name=admin
   password=secret
   

Ensuring that the MAPI Spooler Process is Running

If Microsoft Exchange is the source e-mail system, the MAPI spooler process must be running on the source system in order to extract the various files and perform routing.

To ensure that the MAPISP32.exe MAPI spooler process is running, bring up the Windows NT Task Manager. If the process is running, it appears in the list of processes.

To start the MAPI spooler process, double-click the executable in Windows Explorer.

Note: If you do not have the MAPI spooler process, you can obtain the executable from Microsoft's Platform SDK that comes with the Microsoft Developer Network (MSDN) collection. Install the Platform SDK released April, 2000, or later.

Using Statistics Task to Estimate Disk Space Requirements (Optional)

To use Statistics Task to estimate disk space requirements, run it on the machine on which Microsoft Exchange is installed.

To run Statistics Task, enter the following command using the Windows NT command line:

msplugin.exe statistics_file=file_name user=user@domain

Note: The user@domain can be any user on the Microsoft Exchange Server, not just an administrator.

Task 1: Starting the Migration Tool

To start the Migration Tool on UNIX operating systems, run the migrate.sh script, located in the Migration Tool bin directory, by entering the following commands:

cd bin
./migrate.sh

To start the Migration Tool on Windows NT operating systems, double-click the migrate.cmd file, located in the Migration Tool bin directory, or enter the following commands:

C:\> cd bin
C:\> .\migrate.cmd

The Migration Repository Login screen displays, shown in Figure 3-1.

This section contains the following topics:

• Starting Multiple Instances of the Migration Tool
• Configuring Migration Tool Parameters

Starting Multiple Instances of the Migration Tool

Multiple instances of the Migration Tool can be started if a situation warrants the use of multiple instances, as is the case in the following situations:

• You can use multiple instances of the Migration Tool on one node to migrate more users concurrently
• You can use multiple instances of the Migration Tool to connect to many nodes to migrate several nodes in a multi-node setup

To start multiple instances of the Migration Tool, edit the following parameter located in the migrate.sh file:

-Doracle.mail.migration.migrate.instance=unique_instance_name

For example, add the following two parameters to the migrate.sh file to start two different instances on UNIX:

-Doracle.mail.migration.migrate.instance=inst1
-Doracle.mail.migration.migrate.instance=inst2

Notes: To recover a failed Migration Tool instance, restart it with -Doracle.mail.migration.migrate.instance=unique_instance_name, using the name of the failed instance. Users and batches that were migrating at the time of instance failure show the status failed. If more than one instance fails, they must all be re-run for complete recovery. When more than one Migration Tool instance runs against a single repository, each instance picks up users independently.

Configuring Migration Tool Parameters

By editing parameters located in either the migrate.sh (on UNIX) or migrate.cmd (on Windows NT) file, you can do the following:

• Specify the number of connections in a pool created by each instance of the Migration Tool
• Specify a particular instance of the Migration Tool by name
• Set the Migration Tool to communicate to the source or target IMAP servers through a port number different from the default
• Choose how the Migration Tool migrates messages to the target Oracle Email system
• Disable message sharing for two-phase migration

Following are instructions for configuring Migration Tool parameters:

• Every instance of the Migration Tool creates a pool of connections to the database. You can specify the minimum and maximum numbers of connections by editing the following parameters:

  -Doracle.mail.migration.util.dbcache.min=1
  -Doracle.mail.migration.util.dbcache.max=2
  
  

  The values shown are default values.

  Notes: Oracle Corporation recommends setting the maximum value to N, where N is the number of users migrating concurrently. If extra connections are needed after the maximum limit is reached, the Migration Tool still opens connections to the database. The extra connections immediately close when they are no longer required.

• If you plan to run more than one instance of the Migration Tool, you can name each instance, uniquely, by editing the following parameter:

  -Doracle.mail.migration.migrate.instance=instance_name
  
  

  The default value of instance_name is default. The instance name can also be passed as a command line parameter to migrate.sh or migrate.cmd.

• By default, the Migration Tool makes IMAP connections through port 143. If either the source or target IMAP server is set to a port other than 143, you can change it by editing the following parameters:

  -Dmail.imap.port.source=port_number
  -Dmail.imap.port.target=port_number
  
  

• Either Java Mail API (JMA) or Oracle Java Mail API (OJMA) can be used to append messages to the Oracle Collaboration Suite e-mail system.

  When JMA is used, the IMAP server uses an append command to append the messages to the target folders. When OJMA is used, the Migration Tool bypasses the IMAP server and creates the message in the Oracle Collaboration Suite mail database.

  To use OJMA, define the following parameter:

  -Doracle.mail.migration.migrate.jmatype=oracle
  

  Note: If OJMA is used, target passwords need not be specified.

Following is an example of a JRE command to run an instance of the Migration Tool called myhost:1 with 1 GB heap and 50 database connections, using OJMA:

$JRE -Xms1024m -Xmx1024m                                      
-Doracle.mail.migration.migrate.instance=myhost:1                                       
-Doracle.mail.migration.util.dbcache.max=50                                       
-Doracle.mail.migration.migrate.jmatype=oracle                                       
oracle.mail.migration.migrate.Migrate

Once the parameters are configured, you can start a particular instance of the Migration Tool by entering the following command:

migrate.sh instance_name (on UNIX)

or

C:\migration\bin\> migrate instance_name (on Windows NT)

Task 2: Logging In to the Migration Repository

The Migration Tool creates a repository under the es_mail user schema on the Oracle Email database. If a repository already exists, the Migration Tool reuses it.

Figure 3-1 Migration Repository Login Screen

Text description of the illustration image3th.gif

Specify the following information to log in to the migration repository:

• Password: The default password for the es_mail user is es.
• Host: Enter the host name of the machine on which the source e-mail server is installed.
• Port: Enter the port number on which the Oracle Net Services listener is running. The default port number 1521. If you use a different port number, enter the number.
• Service Name: Enter the SID where Oracle Collaboration Suite is installed.

After you enter the required information, click OK.

The Oracle Email Migration Tool screen displays.

Task 3: Setting Up a Migration Session

The Migration Setup Wizard collects details for the source and target domains; information for setting specific migration options; and notification of successful migration.

Select Tools > Migration Setup from the Migration Tool menu bar to start the Migration Setup Wizard and display the Welcome screen.

The following Migration Setup Wizard steps are described in this section:

Note: All of the following steps are not required. The number of required steps is determined by choices made in Step 1.

• Step 1: Specifying Mail System Objects
• Step 2: Specifying Migration Options
• Step 3: Specifying Notifications
• Step 4: Specifying Mail Services
• Step 5: Specifying Source Directory Server Parameters
• Step 6: Specifying Target Directory Server Parameters
• Step 7: Specifying LDAP Attribute Mapping
• Step 8: Specifying New Account User Names
• Modifying Migration Parameters

Click Next to display the Mail System Objects screen, shown in Figure 3-2.

Step 1: Specifying Mail System Objects

Figure 3-2 Mail System Objects Screen

Text description of the illustration imageb5m.gif

Specify the following information in the Mail System Objects screen:

• Select the source e-mail system from the Select source mail system drop-down list.
• Select each of the objects you want to migrate. Do not select an object if:
  • It does not exist on the source e-mail server
  • You do not want to migrate the object

After you finish entering the information, click Next to display the Migration Options screen, shown in Figure 3-3.

Step 2: Specifying Migration Options

Figure 3-3 Migration Options Screen

Text description of the illustration imageldu.gif

Specify the following information in the Migration Options screen:

• Select the number of users you want to migrate concurrently: Enter the number of users to be migrated concurrently by the Migration Tool.

  The number you choose here specifies the number of reader threads reading from an IMAP source. This number is the upward limit of users that can be migrated at the same time. For example, if you select 100 as the number of users you want to migrate concurrently, 100 users are migrated concurrently at any one time during the migration process.

  When you create batches for migration, the number of users in a batch is mutually exclusive of the number of users migrating concurrently. For example, if you create a batch of 500 users and select 100 as the number of users migrating concurrently, at most, 100 users at a time are migrated out of the batch of 500.

  The number of concurrently migrating users you choose depends upon the resources at your disposal. The size of the number will greatly affect the speed and efficiency with which the Migration Tool performs its tasks, such that the larger the number the more resources will be consumed.

  See Also: Oracle Collaboration Suite Release Notes for information about the number of users to migrate concurrently "Creating Batches" for more information about batches

• In the Account Migration section, choose as your information source either LDAP Server or User Profiles File.
  • If base accounts have not been created on the target e-mail system, check the Create Base Accounts box
  • Specify User Quota (in MB) by entering a number in the adjacent field

    Note: The user quota is applied system wide.

• In the Mail Migration section, select whether you want to perform an IMAP-based or MBOX-based migration

  Note: The Oracle eMail Server 5.2 Splug-in packaged with this release of the Migration Tool does not generate MBOX files.

  • IMAP-based: If your source e-mail system supports IMAP, the Migration Tool extracts the message information from the source e-mail system and places it directly into the target e-mail system
  • MBOX-based: If your source e-mail system does not support IMAP, as is the case with Microsoft Exchange 5.0, choose this option. Select the Generate Mbox box and use the Browse button to specify the MBOX Directory Path to where the MBOX files will be created.

    Although the MBOX option is chosen, the Migration Tool does not immediately extract the file to the target disk. Instead, the Migration Tool assumes that the extracted files are already on the disk in the specified location.

    This feature is useful for extracting MBOX files from a Microsoft Exchange system, moving them to an intermediate store on another machine, and then loading the file into the target Oracle Email server.

    Notes: MBOX is a common file-based mailstore format. The Migration Tool imports the information into the target e-mail system from the intermediate store. There must be sufficient space on the target disk to store all of the users' e-mail being migrated.

    See Also: "Viewing Log Files" for information on viewing the logs associated with MBOX file generation

  • Select the Enable Routing box to enable routing of mail to the new user accounts.

    Notes: If your source e-mail system is Microsoft Exchange and you select Enable Routing, a rule is created on the Microsoft Exchange server during each user migration to forward a copy of all future messages to the target e-mail system. If you choose to run a two-phase migration, do not select Enable Routing.

    See Also: "Performing a Two-Phase Migration" for more information about two-phase migration

• In the Shared Folder Migration section, enter the folder owner's source e-mail address.

When you finish entering the information, click Next to display the Notification screen, shown in Figure 3-4.

Step 3: Specifying Notifications

Figure 3-4 Notification Screen

Text description of the illustration imageu4c.gif

Notifications are e-mail messages that inform users about migration events.

In the Notification section, select either New Account Details, Migration Report, or both.

Note: If you choose to run a two-phase migration, do not select either New Account Details or Migration Report.

See Also: "Performing a Two-Phase Migration" for more information about two-phase migration

• When New Account Details is selected, after the account for the user is created on the target e-mail server, an e-mail is sent to the user's old e-mail account notifying the user of their new user name, password, and IMAP and SMTP host names.

  Click the Customize button to add header and footer notes to the notification.

• When Migration Report is selected, the Migration Report section becomes active. You can choose to send an e-mail to either the user's target account, the administrator, or both, notifying them that the migration is complete and that the user can begin using the new account.

  If you choose to send a migration report to the administrator, enter their target user ID in the Administrator Email Address field.

  Click the Customize button to add header and footer notes to the notification.

• Select the Verify Migration box to attach a verification report to the migration report at the end of every migration.

  When this option is selected, the Migration Tool compares the SMTP message ID of every message that is present on the target account with the source account. A report is generated from this comparison and is sent as part of the Migration Report.

  See Also: "Verifying Migration" for more information about migration verification

• You can set a Failed Message Limit by entering a number in the adjacent field. If the number of failed messages exceeds the number you enter, migration reports are delivered to the administrator, only.

When you finish entering the information, click Next to display the Mail Services screen, shown in Figure 3-5.

Step 4: Specifying Mail Services

Figure 3-5 Mail Services Screen

Text description of the illustration imagesd7.gif

Specify the following in the Mail Services screen:

• In the Oracle eMail Server Mail Store section, enter the distinguished name (DN) of the target mail store in the associated field.
• In the Source and Target Domains section, enter the following:

  Note: Depending on your selections in the previous steps, the following text boxes are enabled on an as-needed basis.

  • Source Domain: Enter the source domain name
  • Target Domain: Enter the target domain name to which the source domain maps

    The data that belongs to a source domain is created on the target domain to which this source domain is mapped. For example, all objects belonging to both us.oracle.com and uk.oracle.com are created under oracle.com.

  • Source IMAP Host: Enter the source IMAP host name (if you selected the MBOX based migration option in the previous step, this field does not appear)
  • Target IMAP Host: Enter the target IMAP host name
  • Source LDAP DN: Enter the LDAP DN for users on the source domain. If you have more than one domain, enter the LDAP DNs for all the domains. The Migration Tool looks for source account entries under the DN of the LDAP. Each domain has a separate DN.

    See Also: Your LDAP server documentation for information about DN representation

  • Target LDAP DN: Enter the LDAP DN for the target Oracle Internet Directory on which all users of this domain are created, in the format dc=oracle,dc=com, for a domain called oracle.com. The Migration Tool creates base account entries under the DN of the LDAP entry. Each domain has a separate DN.
  • Target SMTP Host: Enter the SMTP host of the target domain which listens for e-mail

    Note: The Target SMTP Host field will only be active when you choose to send out migration notifications or have the Migration Tool create routing rules.

  • Click More to enter more domains

When you finish entering the information, click Next to display the Source Directory Server screen, shown in Figure 3-6.

Step 5: Specifying Source Directory Server Parameters

Figure 3-6 Source Directory Server Screen

Text description of the illustration image4m3.gif

Specify the following source LDAP server information in the Source Directory Server screen:

• Host Name: Enter the host name of the machine on which the source directory server is running
• Port: Enter the port number on which the source directory server is listening

  The default port number for LDAP is 389. Update the port number if your port number is different.

• Directory Manager DN: Enter the directory manager distinguished name
• Directory Manager Password: Enter the directory manager password

  Leave the Directory Manager DN and the Directory Manager Password fields empty if the source LDAP server supports anonymous login.

• Object class of e-mail user: Enter the object class that identifies the schema of an e-mail user on the source LDAP server

  See Also: Oracle Email Administrator's Guide for more information about schema

When you finish entering the information, click Next to display the Target Directory Server screen, shown in Figure 3-7.

Step 6: Specifying Target Directory Server Parameters

Figure 3-7 Target Directory Server Screen

Text description of the illustration imaged0c.gif

Specify the following target Oracle Internet Directory information in the Target Directory Server screen:

• Host Name: Enter the host name of the machine on which the target directory server is running
• Port: Enter the port number on which the target directory server is listening

  The default port number for LDAP is 389. Update the port number if your port number is different.

• Directory Manager DN: Enter the directory manager distinguished name
• Directory Manager Password: Enter the directory manager password

When you finish entering the information, click Next to display the Username Generation screen shown in Figure 3-9.

Note: Depending upon choices you made in previous steps, the next screen to display is the LDAP Schema Mapping screen, shown in Figure 3-8.

Step 7: Specifying LDAP Attribute Mapping

Figure 3-8 LDAP Schema Mapping Screen

Text description of the illustration imageadm.gif

On Oracle Email, an e-mail account is described by the orclperson object class. This object class has some mandatory attributes you must map to source directory attributes. These mandatory attributes include:

• cn: Common Name
• sn: Last Name

Mandatory Attributes: Click the source attribute on the right to display a list of mapping choices and select the mapping that you want to update the source attribute.

Non-Mandatory Attributes: Attributes that are not mandatory on the target Oracle Internet Directory have the option No Mapping displayed in the right column. Click the drop-down list to display a list of attribute choices to which to map if you want to map a non-mandatory attribute.

Note: You need only map these attributes once, because the Migration Tool saves the values for the subsequent batches.

When you finish entering the information, click Next to display the Username Generation screen, shown in Figure 3-9.

Step 8: Specifying New Account User Names

Figure 3-9 Username Generation Screen

Text description of the illustration imagegdl.gif

Specify the following information in the Username Generation screen:

To generate new account user names, select one of the following choices from the User Naming section:

• Retain old user names: Specifies that the target user names remain the same as the source user names
• Construct new user names: Specifies that the Migration Tool generates the target user names

  If you choose to have the Migration Tool construct new user names, you must also supply the rules for user name generation in the New User Name Construction section.

  When supplying rules for new user name construction, you can choose to retain the first, middle, or last names, or any combination of the three. Select the appropriate Yes button to retain any of the three names.

  You can also retain only part of a name by selecting the Partial button. Specify the number of characters you want to use in the Number of characters to retain field beneath each name.

  You must also choose a separator character. To select a separator character, click the Separate names with drop-down list.

  Notes: If a name is disabled, it was not mapped in the LDAP Schema Mapping screen. The values for first name, middle name, and last name are picked up from the source LDAP attributes that map to the given name, middle name, and surname orclperson attributes. You must provide this mapping in the LDAP Attribute Mapping screen. Target user names, if specified in the user-list, are used in all cases.

When you finish entering the information, click Next. The Summary screen displays. Click Finish to quit the Migration Setup Wizard and display the Oracle Email Migration Tool screen.

Resolving Account Name Conflicts

If the Migration Tool detects any duplicate target user names (also called name conflicts) when creating accounts in the target Oracle Internet Directory, it logs an error and does not create the duplicate account.

Duplicate target user name errors (name conflict errors) can only be avoided if user name generation rules are chosen so that unique target user names are generated.

To resolve name conflicts, perform the following steps:

1. Manually create the user with a unique name in Oracle Email.
2. Select Tools > Modify User Details to edit the information for that user.
3. Update the user's status to Migrate User Data.

When all accounts have been successfully created, proceed to creating batches and migrating user data.

See Also: "Creating Batches" "Task 11: Migrating Data"

Modifying Migration Parameters

Any changes you make take effect after you cancel and restart the migration.

You cannot modify migration parameters during the migration.

Note: If two or more instances of the Migration Tool are running against the same repository, all instances except one must be shut down before modifications to the migration parameters can proceed.

To modify migration parameters, do the following:

1. Select Tools > Modify Migration Parameters from the Migration Tool menu bar. The Modify Migration Parameters screen displays, as shown in Figure 3-10.

Figure 3-10 Modify Migration Parameters Screen

Text description of the illustration imagench.gif

• Modify the parameters.
• Click OK.

  Task 4: Migrating Users to Oracle Email

  To migrate account information from the source directory server to Oracle Email, do the following:

  1. Select Extract > Users from the Migration Tool menu bar to generate users.xml.

     Note: If you selected User Profiles File from the Migration Options Screen, select Extract > User Profiles.

     See Also: "Overview of the Oracle Email Migration Tool Screen" for information about the location of the users.xml file Appendix A, "Plug-in Generated File Formats" for more information about user profile file formats

  2. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during account migration are logged in the text.log file as administrator error messages.
  3. Select Tools > Load Users from the Migration Tool menu bar to load users.xml into the repository.
  4. Select Migrate > Create Users on Oracle from the Migration Tool menu bar to create user accounts in the target Oracle Internet Directory.
  5. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during account migration are logged in the text.log file as administrator error messages.

     See Also: Oracle Collaboration Suite Administrator's Guide for descriptions of error messages

  If a user's data in the user-list file causes account migration of this user to fail, you can modify the user's details and attempt to remigrate the batch after editing.

  To modify user details, do the following:

  1. Select Tools > Modify User Details from the Migration Tool menu bar. The Modify User Details screen displays, shown in Figure 3-11.

     Note: You can also select a user from the directory tree, select Tools > Modify User Details, and proceed with modifying the user's details.

  Figure 3-11 Modify User Details Screen

  

  Text description of the illustration imagevgu.gif

• Select the user's source domain from the Domain drop-down list.
• Enter the source user name in the Userid field.
• Click Search to populate the fields with the user's information.
• Edit the field entries.
• Update the migration status by choosing from the list of choices in the Status drop-down list.
• Click OK.

  Performing a Two-Phase Migration

  Because migration of user accounts and messages involves transferring large amounts of data and is, therefore, time consuming, users must be transferred from the old system to the new in the least possible amount of time.

  The migration tool provides a two-phase migration option to achieve these conflicting goals that transfers messages from the old system to the new Oracle system in two phases.

  This section contains the following topics:

  • Phase I: Pre-Migration
  • Phase II: User Migration

  Phase I: Pre-Migration

  All users' messages from the source system are written into into the target Oracle Email system. User accounts, however, are not actually populated with messages, nor are their folders created. In this phase all the message bodies will be transferred into the Oracle Email system. This is typically done in the background over several days while users continue to use their old accounts.

  To start pre-migration, do the following:

  1. Ensure that user accounts have been created on the target Oracle Email system.
  2. Ensure that message routing has been disabled.

     See Also: "Step 2: Specifying Migration Options" for more information about message routing

  3. Select Migrate > Pre-Migrate User Data from the Migration Tool menu bar.

  Phase II: User Migration

  In Phase II, the Migration Tool takes advantage of the message sharing capability of Oracle Email to quickly populate users' folders with the messages that were transferred in the first phase.

  This phase typically involves only minimal housekeeping updates to the e-mail store and folder creation, and can be done over a weekend. During Phase II, the following operations are performed:

  • Any new messages that users receive between Phase I and Phase II are transferred to the target user account
  • Any messages that users delete in the interim will not appear in the target users' accounts
  • Any new folders that users create in the interim are transferred to the target users' account
  • Any folders that users have deleted in the interim will not appear in the target users' account

  Follow the procedures in "Task 11: Migrating Data" to perform the Phase II of migration.

  Notes: For best results Phase II should be performed as quickly as possible after Phase I is complete. When you perform a two-phase migration, all batches will be migrated during both phases. It is not possible to selectively migrate specific batches during two-phase migration. Phase II of the migration can be performed at any time because it is the typical migration approach.

  Task 5: Extracting Mail System Objects from the Source System

  1. If you chose to migrate shared folders, select Extract > Shared folders from the Migration Tool menu bar to generate the shared_folders.ldif file in the files directory.
  2. If you chose to migrate public aliases, select Extract > Public aliases from the Migration Tool menu bar to generate the public_aliases.ldif file in the files directory.
  3. If you chose to migrate distribution lists, select Extract > Distribution lists from the Migration Tool menu bar to generate the distribution_lists.ldif file in the files directory.
  4. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during mail system object extraction are logged in the text.log file as administrator error messages.

  Task 6: Batching

  Once users are created, you must group them into batches for migration.

  This section contains the following topics:

  • Creating Batches
  • Viewing Users in a Batch

  Creating Batches

  Using the Migration Tool, you can create a batch either by designating the number of users for each batch or by creating a custom batch.

  Batch creation is done on a domain basis.

  To create a batch by domain, do the following:

  1. Expand the Migration View node on the directory tree on the left side of the Migration Tool screen.
  2. Select the appropriate domain.
  3. Select Batch > Create Batches. The Create Batches screen displays, as shown in Figure 3-12.

  Figure 3-12 Create Batches Screen

  

  Text description of the illustration imagebbe.gif

• Create batches using one of the following methods:
  • Select Number of users per batch and enter the number of users you want in each batch in the adjacent field. For example, if you have 100 users and specify 5 users in each batch, 20 batches are created.
  • Select Specify users for batch to create a custom batch. Enter the source user names for the custom batch. If you need to enter more user names, click More for more fields.

  After you create the batches, you can view them by expanding the domain node on the Migration Tool screen to display all the batches in the domain.

  See Also: "Task 11: Migrating Data" for information about scheduling batches for migration

  Viewing Users in a Batch

  To view users in a batch, expand the domain node and the batch node to view the users in the batch, as shown in Figure 2-5, "Migration Tool Screen with User Information Displayed".

  Task 7: Migrating Shared Folders

  Prior to migrating shared folders, ensure that the following tasks are complete:

  • All user accounts have been migrated
  • You have generated the shared folders file

    See Also: "Task 5: Extracting Mail System Objects from the Source System" to generate the shared folder file

  To migrate shared folders, do the following:

  1. Select Migrate > Migrate Shared Folders from the Migration Tool menu bar to create the shared folders on the target e-mail server. The Shared Folder Migration Status screen displays.
  2. When 100% displays, indicating the migration is complete, click OK.
  3. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during shared folder migration are logged in the text.log file as administrator error messages.

     See Also: Oracle9iAS Unified Messaging Administrator's Guide for descriptions of error messages

  To cancel migration of shared folders, click Cancel on the status dialog that displays when you start to migrate mail objects.

  Note: If you cancel migration of shared folders, rollback does not occur and you can safely restart migration. The e-mail objects that were created before you canceled migration are not re-created when migration is recommenced. Migration continues from the point where it was canceled.

  Task 8: Migrating Public Aliases

  Prior to migrating public aliases, ensure that the following tasks are complete:

  • All user accounts have been migrated
  • You have generated the public aliases file

    See Also: "Task 5: Extracting Mail System Objects from the Source System" to generate the public aliases file

  To migrate public aliases, do the following:

  1. Select Migrate > Migrate Public Aliases from the Migration Tool menu bar to create the public aliases on the target e-mail server. The Public Alias Migration Status screen displays.
  2. When 100% displays, indicating the migration is complete, click OK.
  3. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during public aliases migration are logged in the text.log file as administrator error messages.

     See Also: Oracle9iAS Unified Messaging Administrator's Guide for descriptions of error messages

  To cancel migration of public aliases, click Cancel on the status dialog that displays when you start to migrate mail objects.

  Note: If you cancel migration of public aliases, rollback does not occur and you can safely restart migration. The e-mail objects that were created before you canceled migration are not recreated when migration is recommenced. Migration continues from the point where it was canceled.

  Task 9: Migrating Distribution Lists

  Prior to migrating distribution lists, ensure that the following tasks are complete:

  • All user accounts have been migrated
  • You have generated the distribution lists file

    See Also: "Task 5: Extracting Mail System Objects from the Source System" to generate the distribution lists file

  There are two phases to distribution list migration:

  1. All distribution lists are created.
  2. The distribution lists are populated with users.

  The status bar displays immediately, and shows progress when distribution lists are being populated with users. For example, when the status bar shows that 50% of the distribution lists have been migrated, it means all of the distribution lists have been created and 50% of the distribution lists have been populated with users.

  To migrate distribution lists, do the following:

  1. Select Migrate > Migrate Distribution Lists from the Migration Tool menu bar to create the distribution lists on the target e-mail server. The Distribution List Migration Status screen displays.
  2. When 100% displays, indicating the migration is complete, click OK.
  3. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during distribution list migration are logged in the text.log file as administrator error messages.

     See Also: Oracle9iAS Unified Messaging Administrator's Guide for descriptions of error messages

  To cancel migration of distribution lists, click Cancel on the status dialog that displays when you start to migrate mail objects.

  Note: If you cancel migration of distribution lists, rollback does not occur and you can safely restart migration. The e-mail objects that were created before you canceled migration will not be recreated when migration is recommenced. Migration continues from the point where it was canceled.

  Task 10: Migrating WebMail Address Books

  Note: WebMail Address Book migration is available only for Oracle eMail Server to Oracle Email migrations. This migration can be run only for users using the 5.2.1 WebMail client.

  The Migration Tool can migrate the private address books created by users using their Oracle eMail Server 5.2.1 WebMail clients. Migration of the WebMail address book of each user involves migrating both the private aliases and private distribution lists that users have.

  Prior to migrating address books, ensure that all user accounts have been migrated.

  To migrate WebMail address books, do the following:

  1. Select Migrate > Migrate Address Book from the Migration Tool menu bar. The Address Book Migration Status screen displays.
  2. When 100% displays, indicating the migration is complete, click OK.
  3. View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during address book migration are logged in the text.log file as administrator error messages.

     See Also: Oracle9iAS Unified Messaging Administrator's Guide for descriptions of error messages

  To cancel migration of address books, click Cancel on the status dialog that displays when you start to migrate address books.

  Note: If you cancel migration of address books, rollback does not occur and you can safely restart migration. The address book objects that were created before you canceled migration are not recreated when migration is recommenced. Migration continues from the point where it was canceled.

  Task 11: Migrating Data

  Prior to migrating data you must schedule your batches for migration.

  To schedule a start time for batch migration, do the following:

  1. Select a batch from the directory tree in the Migration Tool screen (see Figure 2-4).
  2. In the Scheduled Start Time field, select either the date or the time and edit it by using the Up and Down arrows. The date is in MM/DD/YY format and the time is in HH:MM format.

     Note: You can schedule multiple batches to migrate in parallel by scheduling them to start at the same time.

  3. After you complete your updates, click Schedule for the updated schedule to take effect.

     See Also: Figure 2-4, "Migration Tool Screen with Batch Information Displayed"

     Note: Even if you do not make changes to the schedule, you must click Schedule for the batch to be scheduled. If you do not click Schedule, the users are not scheduled for migration.

  To start data migration, select Migrate > Migrate User Data from the Migration Tool menu bar.

  To cancel migration, select Migrate > Cancel Migration from the Migration Tool menu bar.

  View the text.log file located in the log/migration/uniquenumber directory. Any errors that occur during data migration are logged in the text.log file .

  Note: If a single user in a batch fails, the batch will be marked as failed. To reschedule the batch for migration, select the failed batch from the Migration Tool screen, edit the Scheduled Start Time field, and click Schedule. Once a batch is rescheduled, the users that failed are reverted to the pending state and the batch is picked up again for data migration when the scheduled migration time occurs. Only users that have failed to migrate are migrated. Users that have been successfully migrated will not be remigrated.

  Post-Migration Administrator Responsibilities

  Upon completion of migration, the administrator must perform the following tasks:

  • Changing the MX Record
  • Verifying Migration

  Changing the MX Record

  You must change the mail exchanger (MX) record in order to redirect e-mail to the new system.

  Verifying Migration

  You can verify migration of individual users' accounts and data using one of several methods of comparison. This helps the administrator to verify the validity of the overall migration, and is also helpful to support personnel when users complain of discrepencies in their accounts.

  Notes: The verifier can be used only for users who have successfully migrated. The verifier is not available for MBOX-based migration.

  To access the Verification screen shown in Figure 3-13, select Tools > Verify New Accounts from the Migration Tool menu bar.

  Figure 3-13 Verification Screen

  

  Text description of the illustration imageeju.gif

  1. Enter the user IDs of users you want to verify in the Users To Be Verified field.

     You can populate the Users To Be Verified field using the search feature. The search feature enables you to search for specific users by entering user name, domain, or batch in the adjacent field. Click Search.

     The results of your search display in the Search Results field. Select the users you want to verify and click the Right Arrow button to populate the Users To Be Verified field.

  2. Select from one of the following verification options:

     Note: Each option verifies that all folders in an individual user's account have been created on the target e-mail system, and compares different message information between the source and target e-mail systems.

     • Message Count: Compares the message counts in the folders to verify that they match
     • Message IDs: Compares the SMTP message IDs to verify that they match
     • Message Header: Compares the message headers to verify that they match
     • Entire Message: Compares the message bodies of every message to verify that they match

       Note: If you choose either the Message Header or Entire Message verification option while migration is proceeding, migration process is slowed considerably.

  3. Enter the address of the recipient of the verification reports in the Administrator Email ID field.

  Shutting Down Microsoft Exchange Servers

  You can shut down the Microsoft Exchange servers upon completion of migration only after you determine that you no longer need routing rules set up on the source e-mail system.

  In cases where you have multiple Microsoft Exchange servers, you can move users from whichever machine they reside, to one single machine as their data is migrated to Oracle Email.

  See Also: Microsoft Exchange documentation for information about moving users from one machine to another