The following procedures outline how to upgrade Messaging Server to version 6 and configure it to use Schema 2.
To upgrade Messaging Server 5.x to Messaging Server 6, follow the instructions in Chapter 2, Upgrading to Sun Java System Messaging Server, in Sun Java System Messaging Server 6 2005Q4 Administration Guide.
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 also have installed Calendar Server 6 and have already run comm_dssetup.pl, you might 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.
Edit the LDAP_SCHEMALEVEL option in the option.dat file to support Schema 2.
Change the service.dcroot configuration parameter to point to the root of the Organization Tree (by using the configutil command).
These tasks are further described in the sections that follow.
You can set the following values for the LDAP_SCHEMALEVEL option in the option.dat file:
LDAP_SCHEMALEVEL=1 enables Messaging Server to support Schema 1.
LDAP_SCHEMALEVEL=2 enables Messaging Server to support Schema 2, native mode.
For details about editing and using the option.dat file, see Editing the Option File
This parameter tells Messaging Server where to begin doing lookups in the LDAP directory.
For Schema 1, the value of this parameter is the root of DC Tree in the directory. The default value is o=Internet.
To configure Messaging Server to support Schema 2, change the value of service.dcroot to the root of the Organization Tree in the directory.
For information about using the configutil utility, see Chapter 1, Messaging Server Command-line Utilities, in Sun Java System Messaging Server 6 2005Q4 Administration Reference.
If you are migrating to Schema 2, compatibility mode, Messaging Server should continue to be configured to use Schema 1:
Set the value of the LDAP_SCHEMALEVEL option to 1.
Set the value of the service.dcroot configuration parameter to the root of the DC Tree.
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.
Each line in the option.dat file contains the setting for one option. An option setting has the form:
The option.dat file is the file specified with the IMTA_OPTION_FILE option in the IMTA tailor file (msg_svr_base/config/imta_tailor). By default, it is located in msg_svr_base/config/option.dat
For more information about the option.dat file, see Chapter Chapter 4, MTA Configuration, in Sun Java System Messaging Server 6 2005Q4 Administration Reference.
Other LDAP Schema 2 options in the option.dat file let you customize Messaging Server’s interaction with the LDAP directory.
For example, LDAP_DOMAIN_FILTER_SCHEMA2 lets you set the LDAP search filter used for Schema, 2 domain lookups. (The default value for this option is objectclass=sunManagedOrganization.)
However, to configure Messaging Server to use Schema 2, you only have to set the LDAP_SCHEMALEVEL option. When you migrate to Schema 2, the Schema Migration Utility (commdirmig) automatically migrates all the current domain object classes and domain attributes from the DC Tree to the Organization Tree.
Your option.dat file also might contain options that customize Schema 1 values. After you migrate to Schema 2, these options become irrelevant and are not used. They do no harm. You do not have to delete Schema 1 options from the option.dat file.
For more information about the options available in the option.dat file, see Chapter Chapter 4, MTA Configuration, in Sun Java System Messaging Server 6 2005Q4 Administration Reference.