Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.1) Part Number B14486-02 |
|
|
View PDF |
This chapter describes how to migrate calendar data from MeetingMaker. The chapter contains the following sections:
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:
Planning the deployment of the Calendar server. Refer to "Planning Calendar Server Deployment" in Chapter 4, "Calendar Migration Planning".
Exporting MeetingMaker data into .dat
files:
Migrating the data to the planned Calendar nodes.
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.
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.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
You need to export MeetingMaker data before starting migration. To do this:
Back up each MeetingMaker server that will be exported.
Purge all unnecessary data from each MeetingMaker server that will be exported.
Use the MeetingMaker Administrator utility to export each MeetingMaker database to a *.dat
binary file.
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 |
---|---|---|
|
|
Defines the list of MeetingMaker server files to import. Multiple entries must be separated by commas and should have the braces. |
|
|
Oracle Calendar node |
|
|
Calendar server host name. |
|
|
Specifies whether or not the meeting location gets imported. |
|
|
Specifies whether or not the attendance status is updated during import. |
|
|
Specifies whether or not the utility displays the usernames being imported while it is running. |
|
|
Specifies if the accounts get created without importing calendar data. |
|
|
Specifies the display of counters during migration. |
|
|
Setting this value to |
|
Calendar attribute |
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. |
|
Calendar attribute |
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. |
|
Calendar attribute |
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. |
|
|
Specifies whether or not holidays are migrated. |
|
{ |
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. |
|
|
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. |
|
|
Specifies whether or not to import item password. If the value is set to |
|
Calendar attribute |
In MeetingMaker, users log in with the unique attribute |
|
Calendar attribute |
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. |
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 ......
The following are the steps of migrating calendar data from MeetingMaker:
Start the Oracle Calendar server by running the unistart
command-line utility.
$ $ORACLE_HOME/ocal/bin/unistart
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>
Initiate the MeetingMaker migration by running the unimmimpsrv
command-line utility.
$ $ORACLE_HOME/ocal/bin/unimmimpsrv
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.
Stop the Oracle Calendar instance by running the unistop
command-line utility.
$ $ORACLE_HOME/ocal/bin/unistop
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