Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.1) Part Number B14486-02 |
|
|
View PDF |
This chapter provides migration planning information and contains the following sections:
The
ExMigrate utility is used to migrate calendar data from Microsoft Exchange to Oracle Calendar. Oracle recommends using
only with the help of Oracle Support Services or an Oracle certified partner because the utility runs on the command prompt and does not provide a GUI or predefined flow of instructions. Any process involving third-party technology should be handled by a consultant familiar with both the source and target systems as well as the intricacies of ExMigrate
and Oracle Calendar.ExMigrate
Before migration, perform the following tasks:
Determine the data that you need to migrate, calendar data, e-mail, or both.
Install Oracle Collaboration Suite, if applicable.
Install an IMAP4 Server, if applicable.
Install Oracle Connector for Outlook on the computer where
will run.ExMigrate
Note:
Use only the version of Oracle Connector for Outlook that is specified in theExMigrate
README file.Create a single Microsoft Outlook profile with administrator privileges to access the user accounts and user data for both Microsoft Exchange and Oracle Collaboration Suite users. You can use this profile to compare the Microsoft Exchange and postmigration Oracle Collaboration Suite user accounts.
Ensure that the versions of Oracle Connector for Outlook and
match.ExMigrate
Ensure that the migration computer is on the same Windows domain as the Microsoft Exchange Server.
In the file system of the migration computer, create a migration folder that contains:
The exmigrate.exe
and exmigrateproc.exe
files from the
package.ExMigrate
The ExMigrateUsers
.ini
, ExMigrateConfig
.ini
and ExMigratePasswd
.ini
files, which are the templates for the users and configuration options.
All the Oracle Calendar accounts should be created and set up before the migration starts.
If the Oracle Collaboration Suite server being migrated has multiple nodes, then to ensure that the attendee status of users on remote nodes is migrated properly, the following entry needs to be appended to the unison.ini
file of the server:
[CWS] noreqsleep=1 [LIMITS] remotemaxretry=10 { suggested value } remotewait=2 { suggested value } { for busy/slow servers, suggested value is 10 }
The
executables must exist in the Oracle Connector for Outlook directory for the encryption or decryption of the passwords. If the ExMigrate
executables exists in any other directory, then you have to ensure that ExMigrate
ctgt_c.dll
and other libraries on which ctgt_c.dll
is dependant, are specified in the PATH
variable.
The unimmimpsrv
utility is used to migrate data from MeetingMaker to Oracle Calendar. The utility uses the unimmimpsrv.ini
file to determine the MeetingMaker files to be imported and the Oracle Calendar nodes that receive the data. However, the utility does not work with the Oracle Calendar servers that use directory servers.
Note:
Only trained Oracle personnel should useunimmimpsrv
. Data loss or corruption resulting from the use of this utility by unauthorized persons is not the responsibility of Oracle and support for such loss is not covered under the standard support contract.Before performing the migration from MeetingMaker, consider the following facts:
A single MeetingMaker server cannot be split among two or more Oracle Calendar nodes, but any number of MeetingMaker servers can be imported into a single Oracle Calendar node.
The MeetingMaker servers that are connected to separate hubs should be imported in separate operations.
All the MeetingMaker servers attached to the same hub should be imported in a single operation.
If only a subset of the MeetingMaker servers attached to a hub are imported, the following conditions apply:
Oracle Calendar accounts are created for all users in all the MeetingMaker servers attached to the hub, within and outside the targeted subset.
Agenda entries are created for users outside the targeted subset only if these entries were proposed by a user in the targeted subset. The uniuser
utility may subsequently be used to delete those users who are outside the targeted subset, from the Oracle Calendar database.
Note:
The current version ofunimmimpsrv
works only on Oracle Calendar Server version 10.1.1.In addition to the above-mentioned points, plan your Calendar server deployment carefully. Install the standalone internal Calendar server according to your Oracle Collaboration Suite deployment plan. For example, if you plan for three Calendar nodes in Oracle Collaboration Suite, install the Calendar servers in internal configuration accordingly. It is strongly recommended to use a Domain Naming System (DNS) alias instead of the real hostname of the computer. Finally, connect the Calendar nodes together.
During migration, certain data is not transferred to the destination Oracle Calendar node. You need to plan the migration so that the non-transferable data is retained after migration.
The following table summarizes the data that is transferable from MeetingMaker to Oracle Calendar:
Table 4-1 Data Mapping for the unimmimpsrv Utility
MeetingMaker Data Type | Data | Oracle Calendar Mapping |
---|---|---|
Administrative Data |
|
|
|
Server Name |
Node alias. It must be set manually during node creation. |
Administrative Rights |
Administration rights must be set manually |
|
MeetingMaker Holidays |
Oracle Calendar Holidays (Convert yes/no) |
|
|
MeetingMaker Public Groups & associated sub-groups |
Oracle CalendarPublic Groups |
|
Time Zones |
Oracle Calendar node time zone, which is configured in the |
User Data |
|
|
|
First Name, Last Name |
X.400 given name, X.400 surname, Password is set to |
|
Sign-in Name |
UID |
|
Password |
Configured in |
|
Title, Phone, Extension, Fax |
Job title, phone number, and extension |
|
Server Name |
Stored in Organizational Unit 1 field of X.400 address |
|
Proxies |
Calendar designates. All proxies regardless of read/write access are granted only viewing rights to the grantor's Oracle Calendar agenda |
|
User-defined Groups |
Private Oracle Calendar groups owned by user |
|
User Activities |
Oracle Calendar meeting with no invitees |
|
User Meetings |
Oracle Calendar meeting with same invitees |
|
User Banners |
Oracle Calendar note on each day that banner covers |
|
User To Do's |
Oracle Calendar tasks |
Resource Data |
|
|
|
First Name, Last Name |
First and last name become new Oracle Calendar resource name The resource number is assigned by the |
MeetingMaker Activities and Meetings Data |
|
|
Title, Location, Time, Date, Duration and Repetitions |
Oracle Calendar Title, Location, Time, Date, Duration and Repetitions |
|
Information |
Invitees and Status |
|
MeetingMaker Banners |
|
|
|
Title, Location, Date, and Repetitions |
Oracle Calendar Title, Location, Date, and Repetitions |
|
Information |
Invitees and Status |
MeetingMaker To Do's Data |
|
|
|
Title & Date |
Oracle Calendar title and date |
|
Invitees |
To Do's become Oracle Calendar tasks, so that a task is created for each invitee. |
The following table lists the data that is not transferred after migrating from MeetingMaker to Oracle Calendar:
Table 4-2 Non-transferable Data
Type of Data | Data | Description |
---|---|---|
Administrative Data |
|
|
|
MeetingMaker administrative rights |
These rights must be set manually through Oracle Calendar Server administrative tools. |
User Data |
|
|
Room, Information, City, Zip Code, and Country |
Some of these values are stored in the |
|
|
User-defined labels for meetings and activities |
|
|
User-defined to do priority levels |
|
|
User work days and hours |
|
|
Default notification and reminder preferences |
This data is not exported by the MeetingMaker server. |
|
User-defined contact list |
This data is not imported as invitees of meetings, activities, and to do's nor as group members. |
Resource Data |
|
|
|
Lost user data along with phone, extension, fax number, and title |
The |
|
Resource-defined groups |
The |
|
Resource activities |
Oracle Calendar resources cannot create events. The |
MeetingMaker Activities, Banners, and Meetings Data |
|
|
|
Publishable |
|
|
Flexible |
|
|
Reminders |
This data is not exported from the MeetingMaker server. |
|
Importance Level |
|
|
Label |
|
|
Invitee Comments |
|
|
Meetings and activities that repeat after a specific period from the end of the month |
This data does not have an Oracle Calendar equivalent. |
|
Meeting with start dates before the year 1991 |
|
|
Instances of an event exceeding 60 |
The start date can be limited when exporting from MeetingMaker or the |
MeetingMaker To Do's Data |
|
|
|
Priority level, Private and Publishable |
|
|
Invitee comments |
|
|
Done/Not Done |
|
|
Owner control |
An independent Oracle task is created for each invitee. Only the task details state the creator's name and list of all invitees. |
Migration from Netscape Calendar to Oracle Calendar has to be done through an intermediate migration to CorporateTime. This is because a direct migration from Netscape to Oracle Calendar is not possible.
Although iCalendar standard supports several Calendar components, such as VEVENT
, VCARD
, and VTODO
, uniical
only supports VEVENT
s. Calendar components other than VEVENT
must be removed from the iCalendar data before passing it to uniical
. You can use VEVENT
s to represent meetings, day events, daily notes and holidays. To distinguish between the four events mentioned in the preceding sentence, you should use the X-ORACLE-EVENTTYPE
property with the following values:
APPOINTMENT
(default)
DAILY NOTE
DAY EVENT
HOLIDAY
Refer to "The uniical Utility" in Chapter 8, "Migrating Calendar Data Using the iCalendar Representation" for more information on uniical
.