Chapter 1 Planning for Installation and Configuration

Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems

Chapter 1
Planning for Installation and Configuration

The installation and configuration of Sun ONE Calendar Server 6.0 on Solaris Systems has significant changes from previous Calendar Server releases. To install Calendar Server 6.0 on Solaris systems, you must use the Sun Java Enterprise System installer, which also installs other Sun component products.

To install and configure Sun ONE Calendar Server 6.0, follow these steps:

"Gather Your Directory Server Configuration Information".

"Gather Your Calendar Server 6.0 Configuration Information".

"Install Calendar Server Using the Java Enterprise System Installer".

"Configure Calendar Server 6.0".

For the most recent information about Calendar Server 6.0, see the Release Notes on the following documentation Web site:

http://docs.sun.com/coll/S1_CalendarServer_60

Caution

If you have Sun™ ONE or iPlanet™ Calendar Server 5.x installed at your site, see Appendix C, "Calendar Server 5.x to 6.0 Upgrade/Migration Process" for information about upgrading to the 6.0 release.

If you need to uninstall Calendar Server 6.0, see "Uninstalling Calendar Server 6.0".

Gather Your Directory Server Configuration Information

The Directory Server Setup (comm_dssetup.pl) Perl script configures Sun ONE Directory Server 5.x for Calendar Server 6.0 (and Messaging Server 6.0). When you run comm_dssetup.pl. you will need to provide the following information. To help you keep track of this information, use "Directory Server Setup Script Worksheet".

What is the Directory Server root path name? The default is /var/mps/serverroot.

If you have multiple instances of Directory Server, which instance do you want to use for Calendar Server 6.0?

What is the Directory Manager Distinguished Name (DN) and password? The default DN is "cn=Directory Manager".

Will the Directory Server be used for Users and Groups. That is, do you want to use Directory Server to store both configuration and user data (yes) or configuration data only (no)? The default is both (yes).

If the Directory Server will be used for Users and Groups, what is the User and Group root suffix? The default is o=usergroup.

Which version of the Sun ONE LDAP Schema do you want to use?

Option 1– LDAP Schema, v.1 (the default)

Option 1.5–ONE LDAP Schema v.2 Compatibility Mode

Option 2–LDAP Schema, v.2 Native Mode

For more information, see Deciding Which Schema to Use.

In you plan to use LDAP Schema, v.1, what is the DC Tree root suffix? The default is o=internet.

Do you want to update the schema (yes/no)? The default is yes. If you answer yes, you must have a config directory with the schema files.

Do you want to configure new Directory Server indexes (yes/no)? The default is yes. For Calendar Server 6.0, comm_dssetup.pl adds indexes for the icsCalendar and icsCalendarOwned attributes.

What is the path to the directory where the schema files are located? The default is ./schema.

Deciding Which Schema to Use

Calendar Server 6.0 supports Sun ONE LDAP Schema, v.1 and Sun ONE LDAP Schema, v.2 Native Mode.

Use the following guidelines to choose the schema to use for your installation.

Table 1-1  Deciding Which Schema to Use

Scenario

Use This Schema

You are installing Calendar Server 6.0 for the first time.

Sun ONE LDAP Schema, v.2 Native Mode

You plan to integrate Calendar Server 6.0 with other Java Enterprise System products such as Sun ONE Portal Server.

Sun ONE LDAP Schema, v.2 Native Mode

You plan to use either of these Sun ONE Identity Server 6.1 features:

CLI utilities for provisioning (for example, domains and users)

Single sign-on (SSO)

Sun ONE LDAP Schema, v.2 Native or Compatibility Mode

You are upgrading Calendar Server to 6.0 from a 5.x version?

Sun ONE LDAP Schema, v.2 Native Mode

or

Sun ONE LDAP Schema, v.2 Compatibility Mode, if you plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products

or

Sun ONE LDAP Schema, v.1, if you don’t plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products

You want to use Calendar Server 6.0 csdomain utility for provisioning domains.

Sun ONE LDAP Schema, v.2 Native or Compatibility Mode

or

Sun ONE LDAP Schema, v.1 if you don’t plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products

You don't plan to use either the Identity Server 6.1 or Calendar Server 6.0 CLI utilities for provisioning because you have other tools you prefer to use.

Sun ONE LDAP Schema, v.2 for new Calendar Server 6.0 installations

or

Sun ONE LDAP Schema, v.1 or v.2 Compatibility Mode for existing Calendar Server installations

Gather Your Calendar Server 6.0 Configuration Information

Before configure Calendar Server 6.0 using, you should gather the following configuration information:

Administration, User Preferences and Authentication Options

Email and Email Alarms Options

Runtime Configuration Options

Database, Logs, and Temporary Files Directories

You will need this information when you run the Calendar Server configuration program, which is described in Chapter 2, "Configuring Calendar Server 6.0." However, you should determine this information before you run the Java Enterprise System installer to avoid conflicts (such as port numbers) with other component products.

To help you keep track of the configuration information, use the worksheets in Appendix A, "Configuration Worksheets".

Administration, User Preferences and Authentication Options

User Preferences Directory

Sun ONE Calendar Server requires a directory server for user authentication and for the storage and retrieval of user preferences.

Table 1-2  User Preferences Directory Options

Option

Description

LDAP Server Host Name

Host name of the LDAP directory server you are using for user authentication and user preferences. The default is the current host.

LDAP Server Port

Port number that the LDAP directory server listens on. The default is 389.

Base DN

Entry in the LDAP directory used as the starting point from which searches will occur. The default is o=host.com.

Directory Manager DN

User name that can make changes in the directory server schema. The default is cn=Directory Manager.

Directory Manager Password

Password of the Directory Manager DN. There is no default.

Calendar Server Administrator

The Calendar Server Administrator is the user account that can manage Calendar Server. For example, this account can run the Calendar Server administration utilities to perform functions such as starting and stopping Calendar Server, backing up the calendar database, enabling or disabling users, and so on. The Calendar Server Administrator user account must exist in your user authentication directory server.

Table 1-3  Calendar Server Administrator Options

Option

Description

Administrator User ID

User ID of the Calendar Server Administrator; must be a user in the above LDAP directory server. The default is calmaster.

Administrator Password

Password of the Calendar Server Administrator. There is no default.

Email and Email Alarms Options

You can configure Calendar Server to send an email alarm message to a Calendar Server Administrator in case a server problem occurs.

Table 1-4  Email and Email Alarms Options

Option

Description

Email Alarms

Enables or disables email alarms. The default is Enabled.

Administrator Email Address

Email address of the Calendar Server Administrator who will receive the email alarm messages.

SMTP Host Name

Host name of the SMTP server where Calendar Server sends the email alarm messages. The default is the current host.

Runtime Configuration Options

You can configure the following Calendar Server runtime and system resource options.

Table 1-5  Runtime Configuration Options

Option

Description

Service Port

Port number that Calendar Server listens on to provide Web (HTTP) access to users. The default is 80.

Maximum Sessions

Maximum number of Calendar Server sessions to allow concurrently. The default is 5000.

Maximum Threads

Maximum number of Calendar Server threads to allow concurrently. The default is 20.

Number of Server Processes

Maximum number of Calendar Server processes to run concurrently. The default is the number of CPUs on the server where you are installing Calendar Server.

Runtime User ID

UNIX user name under which Calendar Server will run. This user name should not be root. If the account does not exist, the configuration program will create it. The default is icsuser.

Runtime Group ID

UNIX group under which Calendar Server will run. If the group does not exist, the configuration program will create it. The default is icsgroup.

Calendar Server Startup

You can configure the following options to automatically start Calendar Server.

Table 1-6  Calendar Server Startup Options

Option

Description

Start after successful installation

Whether to start Calendar Server automatically after a successful installation. The default is checked.

Start on system startup

Whether to start Calendar Server automatically after a system startup. The default is checked.

Database, Logs, and Temporary Files Directories

Calendar Server creates and stores information in calendar database files, log files, and temporary files in specific directories.

Table 1-7  Database, Logs, and Temporary Files Directories Options

Option

Description

Database Directory

Directory where Calendar Server should create and store the calendar database (*.db) files. The default is:

var/opt/SUNWics5/csdb

Logs Directory

Directory where Calendar Server writes log files. The default is:

var/opt/SUNWics5/logs

Temporary Files Directory

Directory where the Calendar Server writes temporary files. The default is:

var/opt/SUNWics5/tmp

Install Calendar Server Using the Java Enterprise System Installer

On Solaris systems, the Java Enterprise System installer installs the Sun component product packages, including Calendar Server 6.0, and the shared components that are used by the various products.

The Java Enterprise System installer installs Calendar Server 6.0 in the following directory:

cal_svr_base/opt/SUNWics5/cal

Caution

If you have a previous version of Calendar Server 6.0 installed at your site, the Java Enterprise System installer will overwrite existing Calendar Server files, including any files you have customized.

If you have customized any files, such as XSL, XML, GIF, HTML, configuration (.conf), or time-zone files, back up those files before you run the installer.

For information about the Java Enterprise System installer, refer to the Sun Java Enterprise System Installation Guide.

Configure Calendar Server 6.0

After you install Calendar Server 6.0 using the Java Enterprise System installer, you must run the Calendar Server configuration program using the information from "Gather Your Calendar Server 6.0 Configuration Information". If you filled out the worksheets in Appendix A, "Configuration Worksheets," use that information to supply values to the configuration program.

For information about the configuration program, see Chapter 2, "Configuring Calendar Server 6.0."

Uninstalling Calendar Server 6.0

To uninstall Calendar Server 6.0 (as well as other component products), you must use the Java Enterprise System uninstaller, which is located in the following directory:

/var/sadm/prod/entsys/uninstall

For information about running the uninstaller, refer to the Sun Java Enterprise System Installation Guide.

When you uninstall Calendar Server 6.0, the uninstaller stops all Calendar Server processes (if they are running) and then removes the SUNWics5 and SUNWica5 packages.

If you are uninstalling only Calendar Server 6.0, the uninstaller does not remove other installed packages or components because they might be shared by other products.

The uninstaller also generates a log file in the following directory:

/var/sadm/install/logs/

An example of a log file is:

Java_Enterprise_System_uninstall.Btimestamp

where timestamp identities when the uninstaller was run.

Previous      Contents      Index      Next

Copyright 2003 Sun Microsystems, Inc. All rights reserved.


Caution	If you have Sun™ ONE or iPlanet™ Calendar Server 5.x installed at your site, see Appendix C, "Calendar Server 5.x to 6.0 Upgrade/Migration Process" for information about upgrading to the 6.0 release.

Scenario	Use This Schema
You are installing Calendar Server 6.0 for the first time.	Sun ONE LDAP Schema, v.2 Native Mode
You plan to integrate Calendar Server 6.0 with other Java Enterprise System products such as Sun ONE Portal Server.	Sun ONE LDAP Schema, v.2 Native Mode
You plan to use either of these Sun ONE Identity Server 6.1 features: CLI utilities for provisioning (for example, domains and users) Single sign-on (SSO)	Sun ONE LDAP Schema, v.2 Native or Compatibility Mode
You are upgrading Calendar Server to 6.0 from a 5.x version?	Sun ONE LDAP Schema, v.2 Native Mode or Sun ONE LDAP Schema, v.2 Compatibility Mode, if you plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products or Sun ONE LDAP Schema, v.1, if you don’t plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products
You want to use Calendar Server 6.0 csdomain utility for provisioning domains.	Sun ONE LDAP Schema, v.2 Native or Compatibility Mode or Sun ONE LDAP Schema, v.1 if you don’t plan to use Identity Server 6.1 features or integrate Calendar Server with other Java Enterprise System products
You don't plan to use either the Identity Server 6.1 or Calendar Server 6.0 CLI utilities for provisioning because you have other tools you prefer to use.	Sun ONE LDAP Schema, v.2 for new Calendar Server 6.0 installations or Sun ONE LDAP Schema, v.1 or v.2 Compatibility Mode for existing Calendar Server installations

Option	Description
LDAP Server Host Name	Host name of the LDAP directory server you are using for user authentication and user preferences. The default is the current host.
LDAP Server Port	Port number that the LDAP directory server listens on. The default is 389.
Base DN	Entry in the LDAP directory used as the starting point from which searches will occur. The default is o=host.com.
Directory Manager DN	User name that can make changes in the directory server schema. The default is cn=Directory Manager.
Directory Manager Password	Password of the Directory Manager DN. There is no default.

Option	Description
Administrator User ID	User ID of the Calendar Server Administrator; must be a user in the above LDAP directory server. The default is calmaster.
Administrator Password	Password of the Calendar Server Administrator. There is no default.

Option	Description
Email Alarms	Enables or disables email alarms. The default is Enabled.
Administrator Email Address	Email address of the Calendar Server Administrator who will receive the email alarm messages.
SMTP Host Name	Host name of the SMTP server where Calendar Server sends the email alarm messages. The default is the current host.

Option	Description
Service Port	Port number that Calendar Server listens on to provide Web (HTTP) access to users. The default is 80.
Maximum Sessions	Maximum number of Calendar Server sessions to allow concurrently. The default is 5000.
Maximum Threads	Maximum number of Calendar Server threads to allow concurrently. The default is 20.
Number of Server Processes	Maximum number of Calendar Server processes to run concurrently. The default is the number of CPUs on the server where you are installing Calendar Server.
Runtime User ID	UNIX user name under which Calendar Server will run. This user name should not be root. If the account does not exist, the configuration program will create it. The default is icsuser.
Runtime Group ID	UNIX group under which Calendar Server will run. If the group does not exist, the configuration program will create it. The default is icsgroup.

Option	Description
Start after successful installation	Whether to start Calendar Server automatically after a successful installation. The default is checked.
Start on system startup	Whether to start Calendar Server automatically after a system startup. The default is checked.

Option	Description
Database Directory	Directory where Calendar Server should create and store the calendar database (*.db) files. The default is: var/opt/SUNWics5/csdb
Logs Directory	Directory where Calendar Server writes log files. The default is: var/opt/SUNWics5/logs
Temporary Files Directory	Directory where the Calendar Server writes temporary files. The default is: var/opt/SUNWics5/tmp


Caution	If you have a previous version of Calendar Server 6.0 installed at your site, the Java Enterprise System installer will overwrite existing Calendar Server files, including any files you have customized. If you have customized any files, such as XSL, XML, GIF, HTML, configuration (.conf), or time-zone files, back up those files before you run the installer.