Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems |
Chapter 1
Planning for Installation and ConfigurationThe 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:
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 InformationThe 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?
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.
Gather Your Calendar Server 6.0 Configuration InformationBefore configure Calendar Server 6.0 using, you should gather the following configuration information:
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.
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.
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.
Runtime Configuration Options
You can configure the following Calendar Server runtime and system resource options.
Calendar Server Startup
You can configure the following options to automatically start Calendar Server.
Database, Logs, and Temporary Files Directories
Calendar Server creates and stores information in calendar database files, log files, and temporary files in specific directories.
Install Calendar Server Using the Java Enterprise System InstallerOn 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
For information about the Java Enterprise System installer, refer to the Sun Java Enterprise System Installation Guide.
Configure Calendar Server 6.0After 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.0To 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.