test

Sun Java System Communications Services 6 2005Q4 Schema Migration Guide

Configuring Calendar Server to Use Schema 2

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:

Configuring Calendar Server for Compatibility Mode

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.

Configuring Calendar Server for Hosted Domain Support

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:

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

Parameter  

Description 

service.virtualdomain.support

Enables (y) or disables (n) support for hosted (virtual) domain mode. Default is n. 

local.schemaversion

Specifies the version of the LDAP schema: 

  • “1" = Schema 1. See also service.dcroot.

  • “2" = Schema 2. See also service.schema2root.

    Default is “1"

service.dcroot

Specifies the root suffix of the DC tree in the LDAP directory, if local.schemaversion = "1"

For example: "o=internet"

In hosted (virtual) domain mode, Calendar Server uses the service.dcroot parameter and not the local.ugldapbasedn and local.authldapbasedn parameters.

Conversely, in non-hosted (virtual) domain mode, Calendar Server uses the local.ugldapbasedn and local.authldapbasedn parameters and not the service.dcroot parameter.

service.schema2root

Specifies the root suffix underneath which all domains are found, if local.schemaversion = "2"

For example: “sesta.com”

service.defaultdomain

Specifies the default domain for this instance of Calendar Server. Used when a domain name is not supplied during a login. 

For example: “sesta.com"

service.loginseparator

Specifies a string of separators used for the login-separator when Calendar Server parses “userid[login-separator]domain”

 

Calendar Server tries each separator in turn. 

Default is “@+”

service.siteadmin.userid

Specifies the user ID of the domain administrator. 

For example: DomainAdmin@sesta.com

service.virtualdomain.scope = "select"

Controls cross domain searching: 

  • “primary" = Search only within the domain where the user is logged in.

  • “select" = Search in any domain that allows the search.

    Default is “select"

local.domain.language

Specifies the language for the domain. Default is “en" (English).

Provisioning Rules for Hosted Domains

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:

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.

Editing the Configuration File

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.