The following procedures outline how to upgrade Calendar Server to version 6, migrate Calendar Server data to version 6, and configure Calendar Server to use Schema 2.
To upgrade Calendar Server 5.x to Calendar Server 6, follow the instructions in ChapterChapter 4, Database Migration Utilities, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
After the upgrade/installation, you must configure Calendar Server and migrate Calendar Server data. For details, see Part II, Postinstallation Configuration, in Sun Java System Calendar Server 6 2005Q4 Administration Guide and Chapter 4, Database Migration Utilities, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
During the upgrade process, you run the Directory Server Setup Perl script (comm_dssetup.pl) to configure Directory Server 5.x for Calendar Server 6 and Messaging Server 6.
The comm_dssetup.pl script asks you to specify which schema version Directory Server is to use by setting the comm_dssetup.pl -t option, as follows:
-t 1— Schema 1
-t 1.5— Schema 2, compatibility mode
-t 2— Schema 2, native mode.
Since you are upgrading your Messaging and Calendar servers before you migrate to Schema 2, you should specify Schema 1 at this stage. If you specify Schema 1 when you run comm_dssetup.pl, the upgraded servers will continue to use the existing schema without interruption.
If you have just installed Messaging Server 6 and have already run comm_dssetup.pl, you do not need to run the script again.
You only need to run comm_dssetup.pl once for each Directory Server used by the Messaging and Calendar servers. However, if you are not sure what to do, it will not hurt your system to run it again. In fact, the script checks to see if the current version has already been installed and will notify you.
For more information about running the comm_dssetup.pl script, see Part II, Postinstallation Configuration, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
To configure Calendar Server to use Schema 2, you must set configuration parameters in the Calendar Server configuration file, ics.conf.
You also must set additional configuration parameters to support hosted (virtual) domains. For details, see Configuring Calendar Server for Hosted Domain Support
(The Calendar Server configuration program, csconfigurator.sh, does not configure Calendar Server to use Schema 2 or to support hosted domains.)
To configure Calendar Server to use Schema 2, edit the following parameters in the ics.conf file:
local.schemaversion
local.schemaversion=”1” specifies Schema 1. If the server is using Schema 1, you also must specify the service.dcroot parameter.
local.schemaversion=”2” specifies Schema 2. If the server is using Schema 2, you also must specify theservice.schema2root parameter.
service.dcroot
Specifies the root suffix of the DC Tree in the LDAP directory.
For example: “o=internet”
service.dcroot is active when the server is using Schema 1. If the server is using Schema 2, service.dcroot is ignored.
service.schema2root
Specifies the root suffix in the Organization (OSI) Tree in the LDAP directory, underneath which all domains are found.
For example: “o=sesta.com”
service.schema2root is active when the server is using Schema 2. If the server is using Schema 1,service.schema2root is ignored.
If you are migrating to Schema 2, compatibility mode, set the local.schemaversion value to 1.
In Schema 2, compatibility mode, the Messaging and Calendar servers continue to use the schema exactly as they did in Schema 1. The servers use the DC Tree to access the correct nodes in the Organization Tree. They use an RFC 2247-compliant search algorithm to look up user entries. From the Messaging and Calendar servers’ perspective, Schema 1 is still in place.
At the same time, Schema 2, compatibility mode enables you to use Access Manager features such as the commadmin utility or single sign-on (SSO). During the migration to Schema 2, compatibility mode, Access Manager object classes, attributes, and ACIs are added to the appropriate nodes in the Organization Tree.
To support Schema 2, Calendar Server also must be configured to support hosted (virtual) domains. This section briefly summarizes the procedures for supporting hosted domains. For more information, see Chapter Chapter 13, Administering Hosted Domains, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
To migrate a site to use hosted domains, you must perform the following tasks:
Run the csvdmig utility. For details, see ChapterChapter 4, Database Migration Utilities, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
Set additional configuration parameters in the ics.conf file.
Configuring Calendar Server for Hosted Domain Support describes the parameters in the ics.conf file used for hosted domain support. If any of the following parameters are not in the ics.conf file, add the parameter and its associated value to the file and then restart Calendar Server for the values to take effect.
For more information about editing the ics.conf file, see AppendixAppendix E, Calendar Server Configuration Parameters, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
Table 4–1 Configuration Parameters for Hosted Domain Support
After you configure Calendar Server to support hosted domains (and after you migrate the directory data to Schema 2), user-developed applications and provisioning tools must use the following rules for provisioning new entries:
User entries must be underneath the people node in the Organization Tree.
Group entries must be underneath the group node in the Organization Tree.
Access Manager requires this hierarchy for provisioning user and group entries. Access Manager-based tools will not recognize users and groups provisioned under different nodes than the people node and group node, respectively.
Calendar Server configuration parameters are stored in the following file:
cal_svr_base/etc/opt/SUNWics5/config/ics.conf
The ics.conf file is an ASCII text file, with each line defining a parameter and its associated value(s). The parameters are initialized during Calendar Server installation. After installation, a user with administrator rights on the system where Calendar Server is running can edit the ics.conf file. You can edit the file by using a text editor such as vi on Solaris Systems.
For more information about editing configuration parameters in the ics.conf file, see Appendix E, Calendar Server Configuration Parameters, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.