Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.1) Part Number B14486-02 |
|
|
View PDF |
This appendix describes how to migrate a standalone Calendar 10gR1 server with an internal directory to an Oracle Collaboration Suite Calendar server installation.
Note:
This migration procedure assumes all installations are on the same operating system.The appendix has the following sections:
To ensure a successful migration from an internal Oracle Calendar server deployment to Oracle Collaboration Suite Calendar, it is important to take time to carefully plan the migration. If multiple Oracle Calendar servers exist in the standalone deployment, they must all be migrated at the same time, because internal deployments of Oracle Calendar server cannot coexist with Oracle Collaboration Suite Calendar instances. In addition, during the migration process, all Oracle Calendar servers must be stopped. Although a planned outage will be necessary, effective preparation will help minimize migration time.
Migrating the Oracle Calendar server with an internal directory to Oracle Collaboration Suite Calendar also necessitates the creation of user entries in Oracle Internet Directory. Once the user accounts are available in Oracle Internet Directory, other Oracle Collaboration Suite components, including Oracle Calendar, such as Oracle Mail, Oracle Content Services, and Oracle Real-Time Collaboration will be automatically provisioned.
Note:
Creating user accounts in Oracle Internet Directory can trigger an automatic provisioning policy for many Oracle Collaboration Suite components. User provisioning can be customized for different components. For more information on user provisioning to Oracle Collaboration Suite components, see "Provisioning Procedures" in Chapter 4 of Oracle Collaboration Suite Administrator's Guide.Migrating from an internal Calendar server deployment to Oracle Collaboration Suite Calendar can be broken down into four steps:
When installing Oracle Collaboration Suite Calendar, it is important to install a mirror image of the node setup that currently exists in your standalone deployment. This means installing the same number Applications tiers, with the same number of nodes, same node IDs, same alias values, and the same masternode configuration. The first Oracle Collaboration Suite Application tier installed must correspond with the internal Calendar server masternode value, because the masternode condition is assigned by the Oracle Universal Installer.
The node IDs of the Oracle Collaboration Suite Calendar installation should be the same as that of the existing internal Calendar server installation. In order to be able to specify NodeIDs during the installation process, the installation must be run with additional specifications:
In UNIX operating systems:
./runInstaller oracle.cal.server:s_nodeID="nodeid"
In Windows operating systems:
setup.exe oracle.cal.server:s_nodeID="nodeid"
Once all the Oracle Collaboration Suite Calendar servers are installed, it is advisable to create a table. This will facilitate tracking the mapping between the node, host, and port information of the Calendar server internal deployment and the node, host, and port information of Oracle Collaboration Suite Calendar. To find the hostname and port for a Calendar server, see the $ORACLE_HOME/ocal/misc/unison.ini
file and note the [ENG]
calendarhostname and [ENG]
port values. These form the host:port
values listed in the following model table:
NodeID | StandaloneHost | SuiteHost |
---|---|---|
nodeid1 | sa_host1:port | suite_host1:port |
nodeid2 | sa_host1:port | suite_host1:port |
nodeid3 | sa_host2:port | suite_host2:port |
This table will be used later during this migration process to help configure the Calendar node network.
Once all the Oracle Collaboration Suite Calendar servers are installed, you must stop all Oracle Collaboration Suite Calendar servers. For more information on stopping and starting Oracle Calendar, see "Starting and Stopping the Calendar Server" in Chapter 5 of Oracle Calendar Administrator's Guide.
Note:
All the Oracle Collaboration Suite Calendar servers must be running while the Oracle Collaboration Suite installations are performed.This section outlines how to migrate the user and resource entries to Oracle Internet Directory. This procedure involves exporting the user and resource entries from internal Calendar to an LDAP Data Interchange Format (LDIF) file, and then importing the LDIF file into Oracle Internet Directory.
The section contains the following:
Use the unidb2ldif
utility to export the user and resource entries from Oracle Calendar Standalone to an LDIF file. You need to perform this operation against each and every node of your Internal Calendar deployment while both the standalone internal server and the Oracle Collaboration Suite Oracle Internet Directory are active.
The unidb2ldif
utility generates an LDIF file for each node. As a result, if you have a four-node network, you will have four generated LDIF files. Because the content of these files depends on the configuration you supply to unidb2ldif
through its initialization file, it is important that the initialization file is set up properly. In particular, the [LDAP]
dsa
value must be set to unknown
.
See Also:
For more information about theunidb2lidf
utility, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.Note:
Theunidb2ldif
utility is not available with Oracle Collaboration Suite installations. It is intended for use with Oracle Calendar standalone installations only.After you have generated the LDIF files, you must ensure that no new accounts get created, deleted, or modified on any Calendar server standalone internal nodes. Any changes made to the accounts information after the unidb2ldif
is run will not be applied to the Oracle Collaboration Suite accounts.
Format the LDIF entries correctly for use with Oracle Internet Directory. This can be accomplished by running a script against the LDIF file(s) generated. You will need to adjust the SOURCEDN
value according to your installation. The script is as follows:
#!/bin/sh SOURCEDN="cn=<users>,dc=<visioncorp>,dc=<com>" if [ "$1" = "" ] then echo "usage: convert.sh filename" exit 2; fi FILENAME=$1 while read XX do # Apply only to users if [ ! -z "`echo $XX | grep "$SOURCEDN"`" ] then # add "dn: " if necessary if [ -z "`echo $XX | grep "^dn:"`" ] then echo -n "dn: " >> $FILENAME.$$ fi # Append the missing objectclass echo $XX >> $FILENAME.$$ echo "objectclass: orclUser" >> $FILENAME.$$ echo "objectclass: orclUserV2" >> $FILENAME.$$ else # Keep as-is echo $XX >> $FILENAME.$$ fi done < $FILENAME \mv $FILENAME.$$ $FILENAME
After modifying the LDIF file, verify that all the Oracle Collaboration Suite Calendar servers are down. This can be accomplished by running the $ORACLE_HOME/ocal/bin/unistatus
utility. For more information about the unistatus utility, see "Calendar Server Utilities" in Chapter 6 of Oracle Calendar Reference Manual.
Then import the LDIF files into the Oracle Internet Directory server with the following command:
$ORACLE_HOME/bin/ldapmodify -c -h OID_hostname -p OID_port -D "cn=orcladmin" -w orcladmin_password -f LDIFfile
Note:
Importing users into the Oracle Collaboration Suite deployment can also trigger automatic provisioning of Oracle Mail, Oracle Content Services, and Oracle Real-Time Collaboration accounts. For more information on user provisioning to Oracle Collaboration Suite components, see "Provisioning Procedures" in Chapter 4 of Oracle Collaboration Suite Administrator's Guide.Convert the user accounts to the correct format. This is required because unidb2ldif
can not identify the Oracle Internet Directory version being used. To convert the accounts on each of the Oracle Collaboration Suite Calendar server, without starting the server, run the following command:
$ORACLE_HOME/ocal/bin/unioidconf -upgrade
You can safely ignore any warnings, but not errors, generated in the $ORACLE_HOME/ocal/log/unioidconf.log
file.
A number of Oracle Calendar configuration files need to be modified to ensure a successful migration.
For each Oracle Collaboration Suite Applications tier Calendar server installation, copy any customizations that were made in the corresponding Calendar standalone unison.ini
file. However, this is optional.
Caution:
Do not overwrite the destination (Oracle Collaboration Suite)unison.ini
file with the source (Oracle Calendar standalone) unison.ini
file.But you must:
Remove all the numeric sections [number
] along with their keys from the unison.ini
file of Oracle Collaboration Suite. The following is an example of a numeric section:
[1234] name = N1 version = A.06.10 timezone = EST5EDT
Copy the numeric section from the standalone unison.ini
file to the matching Oracle Collaboration Suite server unison.ini
file.
In addition to unison.ini
, other configuration files may have been modified in your Calendar standalone installation. For each Oracle Collaboration Suite Calendar installation, copy the following files (located in $ORACLE_HOME/ocal/misc) of the corresponding standalone installation to the Oracle Collaboration Suite installation:
user.ini
resource.ini
eventcal.ini
categories.ini
categorytype.ini
The most critical part of the migration process is migrating the Calendar database to Oracle Collaboration Suite.
Before the database migration, your Calendar system should be similar to the following:
The Standalone deployment should be up and running, but without any new account creations, modifications or deletions.
The Oracle Collaboration Suite deployment should be inactive, and the appropriate configuration files should be updated.
Oracle Internet Directory should be populated with account information from the Calendar standalone deployment.
The following steps need to be taken for all Calendar standalone instances:
Stop all Oracle Calendar standalone servers by running $ORACLE_HOME/ocal/bin/unistop
.
On the Oracle Collaboration Suite Calendar server, rename the $ORACLE_HOME/ocal/db
directory to $ORACLE_HOME/ocal/db_blank
. In addition, copy the $ORACLE_HOME/ocal/db
directory from the standalone Calendar server into the $ORACLE_HOME/ocal
directory on the corresponding Oracle Collaboration Suite Calendar server.
Each of the Calendar databases stores a record with host information of other servers that are part of the node network. Use the mapping table that you have created in "Installing the Oracle Collaboration Suite Calendar" to apply the appropriate changes to the node network on the migrated Oracle Collaboration Suite Calendar instances.
Follow these steps to update node network information:
On an Oracle Collaboration Suite Calendar server, run the following command:
$ORACLE_HOME/ocal/bin/unidbfix -export -n all
This creates the $ORACLE_HOME/ocal/db/nodes/
N#
/perm/remotenode.ini
file, where N#
is the value of the name
parameter within the node specific section in the $ORACLE_HOME/ocal/misc/unison.ini
file.
The content of remotenode.ini should look like the following with a section for each remote node:
[nodeid2] RN_NUMCONNECT = 3 RN_ACCESSMETHOD = 2 RN_SERVICENAME = "unieng" RN_HOSTNAME = "sa_host1:port"
Modify the generated remotenode.ini
files. Using your mapping table, replace the RN_HOSTNAME
value from the standalone hostname:port
to the new Oracle Collaboration Suite Calendar hostname:port
.
[nodeid2] RN_NUMCONNECT = 3 RN_ACCESSMETHOD = 2 RN_SERVICENAME = "unieng" RN_HOSTNAME = "suite_host1:port"
Note:
You may have several[nodeid]
sections in remotenode.ini
. Each nodeid
section must be adjusted in the same way.If the Oracle Collaboration Suite Calendar server has several nodes, you will have several remotenode.ini
files, one per N#
directory. Update each of the files.
Update the host information using the following command:
$ORACLE_HOME/ocal/bin/unidbfix -import -n all
This must be done on all the Oracle Collaboration Suite Calendar installations to ensure a consistent calendar node network.
After you migrate the Calendar database and update the node network information, you need to update the nodes.ini
file. To do so:
Start all the Oracle Collaboration Suite Calendar servers.
Locate the Oracle Collaboration Suite server with the configured masternode
. The Calendar server with the $ORACLE_HOME/ocal/misc/nodes.ini
file houses the masternode
, and will be on the first Oracle Collaboration Suite Calendar Applications tier that was installed.
Run the following command line utility to update the $ORACLE_HOME/ocal/misc/nodes.ini
file:
$OH/ocal/bin/uninode -init
Edit the $ORACLE_HOME/ocal/misc/nodes.ini
file and verify that all the information matches.
Notify end users of the change in hostname and port. End users will need to reconfigure their Oracle Connector for Outlook, Oracle Calendar desktop clients, Oracle Calendar Sync clients to reflect the new hostname and port information. Additionally, this information may need to be modified for the Oracle Calendar Web client.