6 Migrating Calendar Data from MeetingMaker

This chapter describes how to migrate calendar data from MeetingMaker. The chapter contains the following sections:

• Migration Process

• System Requirements for unimmimpsrv

• Migration Guidelines

• Exporting MeetingMaker Data

• Editing unimmimpsrv.ini

• Performing Migration

• Verifying Migration

Migration Process

The migration process from MeetingMaker requires the use of the following command-line utilities, which are found in the $ORACLE_HOME/ocal/bin directory:

• unimmimpsrv

• unistart

• unistop

• uniaddnode

For more information about these utilities, see the Oracle Calendar Reference Manual.

By default, you can migrate data from MeetingMaker to a standalone internal Calendar server. So you need to perform extra steps to complete the migration if your goal is to migrate to Oracle Collaboration Suite or a standalone external Calendar server. The high-level migration process is as follows:

1. Planning the deployment of the Calendar server. Refer to "Planning Calendar Server Deployment" in Chapter 4, "Calendar Migration Planning".

2. Exporting MeetingMaker data into .dat files:

3. Migrating the data to the planned Calendar nodes.

4. Migrate to an external Calendar or an Oracle Collaboration Suite installation.

   
   

   See Also: Appendix B, "Migrating from A Standalone Internal Calendar Server To Oracle Collaboration Suite" for more information on upgrading from internal Calendar to Oracle Collaboration Suite installation and Appendix C, "Migrating from Internal Calendar Server to External" for more information on upgrading from internal Calendar to external Calendar installation.

   
   

To begin migrating data from MeetingMaker to Oracle Calendar, you need to obtain the MeetingMaker server export file. You can use MeetingMaker servers to export the MeetingMaker database to a binary file format (*.dat). This file is used to upgrade server versions and archive the database. The .dat file format is standard for the current MeetingMaker server versions, so the unimmimpsrv utility reads this file to get the current MeetingMaker information.

MeetingMaker also has a server-database topology similar to the Oracle Calendar node topology. MeetingMaker servers are connected so that the local and remote users can collaborate. The servers connect using a MeetingMaker hub. When the servers are connected, each server has a list of users connected to the same hub. If you import only one MeetingMaker server that is connected to other servers, the unimmimpsrv utility creates accounts in Oracle Calendar for all the users that are connected to the hub. Refer to Figure 6-1.

Figure 6-1 Migrating Using unimmimpsrv

Description of "Figure 6-1 Migrating Using unimmimpsrv"

System Requirements for unimmimpsrv

A sample $ORACLE_HOME/ocal/misc/unimmimpsrv.ini.sbs is provided with the utility. Use that file to create your customized configuration file, unimmimpsrv.ini before starting the migration.

Note: Oracle Calendar has been certified with the following MeetingMaker versions: 5.x, 6.x, 7.0, 7.0.1, 7.0.2, 7.1, 7.2, and 7.5.3.

Migration Guidelines

Adherence to the following guidelines will help facilitate the successful migration of calendar data:

• During migration, the unimmimpsrv utility creates accounts for the users from MeetingMaker. You cannot append to accounts already created in Oracle Calendar.

• The utility appends information to a node by creating new accounts. You can run the utility more than once on a node to add MeetingMaker servers at different times.

• Running the utility more than once on the same MeetingMaker server and node creates duplicates. Always create a backup of the node prior to importing data.

• You can import more than one MeetingMaker server into a single node, but you cannot import one MeetingMaker server into more than one node.

• You can import more than one MeetingMaker server into a node, simultaneously, if the servers are connected to a MeetingMaker hub and are in sync.

• You can configure the unimmimpsrv utility to import multiple MeetingMaker servers into multiple nodes.

• The Oracle Calendar server must be up to run the unimmimpsrv utility. The migration tool logs onto the server to add accounts and entries much like any other utility such as uniuser.

• The unimmimpsrv utility can run only in non-LDAP environments.

The MeetingMaker server export files need to be placed on the drive of the workstation or server that will be running the utility. The utility comprises the following:

• The binary file, unimmimpsrv on UNIX, or unimmimpsrv.exe on Microsoft Windows

• The unimmimpsrv.ini

• The data files to be imported from the MeetingMaker servers

Exporting MeetingMaker Data

You need to export MeetingMaker data before starting migration. To do this:

1. Back up each MeetingMaker server that will be exported.

2. Purge all unnecessary data from each MeetingMaker server that will be exported.

3. Use the MeetingMaker Administrator utility to export each MeetingMaker database to a *.dat binary file.

Editing unimmimpsrv.ini

Edit the $ORACLE_HOME/misc/unimmimpsrv.ini file to specify which MeetingMaker files to import, which Calendar nodes to receive the data, and other migration settings. The following is a sample unimmimpsrv.ini file:

[node-ID] 
mmexportfilelist={<Meeting Maker .dat file(s)>} 
sysoppwd=<SYSOP password> 
host=<hostname> 
location=<TRUE or FALSE> 
attendance=<TRUE or FALSE> 
usernameprint=<TRUE or FALSE> 
usersonly=<TRUE or FALSE> 
printcounters=<TRUE or FALSE> 
noimport=<TRUE or FALSE>
orgunit1=TRUE/FALSE 
privdomain=TRUE/FALSE
admindomain=TRUE/FALSE 
holidays=FALSE/TRUE

[node-ID] indicates the Calendar node number. Table 6-1 describes the properties of the unimmimpsrv.ini file:

Table 6-1 Properties of unimmimpsrv.ini

Entry	Permitted Values	Description
mmexportfilelist	{Meeting Maker .dat files}	Defines the list of MeetingMaker server files to import. Multiple entries must be separated by commas and should have the braces.
sysoppwd	SYSOP password	Oracle Calendar node Sysop password.
host	hostname	Calendar server host name.
location	TRUE or FALSE	Specifies whether or not the meeting location gets imported.
attendance	TRUE or FALSE	Specifies whether or not the attendance status is updated during import.
usernameprint	TRUE or FALSE	Specifies whether or not the utility displays the usernames being imported while it is running.
usersonly	TRUE or FALSE	Specifies if the accounts get created without importing calendar data.
printcounters	TRUE or FALSE	Specifies the display of counters during migration.
noimport	TRUE or FALSE	Setting this value to TRUE will allow the utility to read the unimmimpsrv.ini file and the MeetingMaker export files, but not import any data or create accounts. There will be no change to the Oracle Calendar node.
mapdepartment (orgunit1)	Calendar attribute OU1	Determines the calendar attribute to which the department name should be transferred. If this field is set to an empty string, the department name will not be imported.
mapservername (privdomain)	Calendar attribute OU4	Determines to which calendar attribute the server name should be transferred. If this field is set to an empty string, the server name will not be imported.
mapcompany (admindomain)	Calendar attribute A	Determines to which calendar attribute the company name should be transferred. If this field is set to an empty string, the company name will not be imported.
holidays	TRUE or FALSE	Specifies whether or not holidays are migrated.
mmtimezonelist	{timezone}	Specifies the time zone of the MeetingMaker server file being migrated. The number of the time zones listed should match with the number of MeetingMaker import files. If multiple files are imported, the time zone values should be separated by commas.
importproxy	TRUE or FALSE	Specifies whether or not to import proxies (viewing right/designates). All proxies, regardless of read/write access, are granted only viewing rights to the Oracle Calendar agenda.
importpassword	TRUE or FALSE	Specifies whether or not to import item password. If the value is set to FALSE, item passwords are set to NULL. The password may be truncated if it is longer than 15 characters.
mapsignin	Calendar attribute	In MeetingMaker, users log in with the unique attribute signin. In unimmimpsr.ini, mapsignin maps signin to a calendar attribute. Generally, this calendar attribute is UID, but it could instead be an attribute such as email. If mapsignin is left empty in unimmimpsr.ini ([mapsignin = ""]), the signin attribute is not imported. If mapsignin is left out of unimmimpsr.ini altogether, signin is mapped to UID by default.
mapemail	Calendar attribute MAIL	Determines the calendar attribute to which the e-mail should be transferred. If this field is set to an empty string, the e-mail address will not be imported.

Preparing the Calendar Server for Migration from MeetingMaker

To ensure a smooth upgrade of MeetingMaker information, some Calendar server configuration settings need to be modified. MeetingMaker, by default, allows double booking of resources, which leads to a resource conflict. However, Oracle Calendar does not allow double booking. In Oracle Calendar, resource access is "first-come first-served." So, there is no possibility of a resource conflict. Before migrating existing MeetingMaker data to Oracle Calendar, you need to temporarily configure Oracle Calendar to allow double booking.

To do so, you need to edit the ORACLE_HOME/ocal/misc/unison.ini file, and add or modify the allowresourceconflict key in the [ENG] section of the file. The modified section should look like the following:

[ENG]
.......
allowresourceconflict=TRUE
......

Performing Migration

The following are the steps of migrating calendar data from MeetingMaker:

1. Start the Oracle Calendar server by running the unistart command-line utility.

   $ $ORACLE_HOME/ocal/bin/unistart
   
   

2. Create a Oracle Calendar node to store the MeetingMaker data by running the uniaddnode command-line utility:

   $ $ORACLE_HOME/ocal/bin/uniaddnode -n <Calendar_node_number>
   
   

3. Initiate the MeetingMaker migration by running the unimmimpsrv command-line utility.

   $ $ORACLE_HOME/ocal/bin/unimmimpsrv
   
   

4. Obtain the list of users and resource identifiers for LDAP setup with the uniuser command. Use these lists later for LDAP integration of existing MeetingMaker users and resources.

5. Stop the Oracle Calendar instance by running the unistop command-line utility.

   $ $ORACLE_HOME/ocal/bin/unistop
   

Sample Output for unimmimpsrv

The following is a sample output returned by a successful MeetingMaker migration:

Importing User Proxies...
329
Importing User Agendas:
1 Vicky Groups: 2 Tasks: 1 Meetings: 594 insts: 0 atts: 0
2 Susan Groups: 2 Tasks: 18 Meetings: 391 insts: 0 atts: 0
 3 TBV Groups: 2  Meetings: 2231 insts: 0 atts: 0
 4 Dorothy Groups: 2  Meetings: 257 insts: 0 atts: 0
 5 JAZ Groups: 2  Meetings: 2487 insts: 0 atts: 0
 6 Nothing to import for user Margo Carter
 7 Nothing to import for user Christine Dyck
 8 Nothing to import for user Karen Merritt
 9 Nothing to import for user Harold Leece
 10 Nothing to import for user Marie Lococo
 11 Nothing to import for user Pauline McCormack
 12 Nothing to import for user Susan Mifsud
 13 Nothing to import for user Pat Miller
 14 Nothing to import for user Bridgette Gauthier
 15 Nothing to import for resource HR-Small Mtg Room
 16 Nothing to import for user Nina Slack
 17 Nothing to import for user Val Wolfe
 18 Nothing to import for user David Atkinson
 19 Nothing to import for user Luaine Hathaway
 20 Nothing to import for user Darren Harper
 21 Sharon Groups: 1  Meetings: 92 insts: 4 atts: 0
 22 TerryBoak Groups: 1  Meetings: 3393 insts: 69 atts: 0
 23 Nothing to import for resource HR-Large Mtg Room
 24 Nothing to import for user Ruth Esau
 25 Nothing to import for user Marg Skeoch
 26 Nothing to import for user Marilyn Chute
 27 MKoop Groups: 1 Tasks: 1 Meetings: 124 insts: 0 atts: 0
 28 resource Finance Mtg Room
 29 Nothing to import for user Joyce Samuels
 30 Nothing to import for user Jack Miller
 31 Ron Groups: 1  Meetings: 8 insts: 0 atts: 0
 32 Nothing to import for user Karen Wright
 33 kepp Groups: 1  Meetings: 82 insts: 0 atts: 0
 TOTAL of 11 agendas out of 33 users
Meeting Maker DataBase succesfully

Verifying Migration

View the $ORACLE_HOME/ocal/logs/unimmimpsrv.log file. This file will contain the start and end times and duration of the MeetingMaker migration utility. It will also contain the steps that the utility has performed as well as any errors it has encountered.