Sun ONE Calendar Server 6.0 Installation Guide for Solaris Operating Systems |
Chapter 2
Configuring Calendar Server 6.0After you install Sun ONE Calendar Server using the Sun Java Enterprise System installer, you must configure Calendar Server as follows:
- Run the Directory Server Setup Script (comm_dssetup.pl) to configure Sun ONE Directory Server 5.x (if the script has not already been run during the configuration of Messaging Server 6.0).
- Run the Calendar Server Configuration Program (csconfigurator.sh) to configure your site’s specific requirements.
Directory Server Setup Script (comm_dssetup.pl)The Directory Server Setup Perl script (comm_dssetup.pl) configures Sun ONE Directory Server 5.x for Calendar Server 6.0 and Messaging Server 6.0. The comm_dssetup.pl script prepares the Directory Server by setting up new schema, index, and configuration data. This section describes:
Functions of comm_dssetup.pl
Specifically, comm_dssetup.pl allows you to specify these options:
- Directory Server 5.x installation directory path and instance you want to use for Calendar Server 6.0 and Messaging Server 6.0.
- Directory Manager Distinguished Name (DN) and password.
- Whether Directory Server 5.x will be used for users and groups. If yes, you must also specify the DC Tree base suffix and a User and Group base suffix for your Organization Tree.
- Whether to use Sun ONE LDAP Schema v.1 or v.2.
- DC Tree base suffix, if you have selected LDAP Schema v.1
- Whether to update your schema according to the version you have selected.
- Whether to add Directory Server indexes to improve the efficiency of directory searches.
Requirements to Run comm_dssetup.pl
The requirements to run comm_dssetup.pl include:
- Sun ONE Directory Server 5.x must be installed, configured, and running.
- You must run comm_dssetup.pl on the same server where Directory Server 5.x is running.
- To use LDAP Schema, v.2, Sun ONE Identity Server 6.1 must be installed and configured.
- You must run comm_dssetup.pl as superuser (root).
- If your directory server is split into separate directory instances, run comm_dssetup.pl on all instances.
- If you are running a replicated directory server, run comm_dssetup.pl against the master and replica (slave) directories.
- You must run comm_dssetup.pl before you run the Calendar Server 6.0 Configuration Program.
Running comm_dssetup.pl
To run comm_dssetup.pl, follow these steps:
- On the server where Directory Server 5.x is installed, login as or become superuser (root).
- Start Directory Server 5.x, if necessary.
- If Calendar Server 6.0 is installed on this same server, change to the /opt/SUNWics5/cal/sbin directory.
Or, if Calendar Server 6.0 is not installed on this server, you must copy the dssetup.zip file (which includes the comm_dssetup.pl script and supporting files) from the server where Messaging Server 6.0 is installed:
- Run the comm_dssetup.pl script in either Silent Mode or Interactive Mode. To run this script, Sun recommends using the version of Perl included with Directory Server 5.x:
ds_svr_base/bin/slapd/admin/bin/perl
Silent Mode
To run comm_dssetup.pl in silent mode, use the following syntax. You must provide all of the required arguments, as described in Table 2-1.
Table 2-1 Directory Server Setup Script (comm_dssetup.pl) Options
Option
Description
-i yes|no
Answers the question: “Do you want to configure new indexes?”
yes–Add new Directory Server indexes. For Calendar Server 6.0, comm_dssetup.pl adds indexes for the icsCalendar and icsCalendarOwned attributes.
no–Do not add indexes.
-c DirectoryServerRoot
Directory Server root path name.
For example: /usr/sunone/servers-d DirectoryInstance
Directory Server instance subdirectory.
For example: slapd-varrius-r DCTreeSuffix
DC Tree root suffix. For example: o=internet
-u UserGroupSuffix
User and Group root suffix. For example: o=isp
-s yes|no
Answers the question: “Do you want to update the schema?”
yes–Update the schema. You must have a config directory with the schema files.
no–Do not update schema.
-D DirectoryManagerDN
Directory Manager Distinguished Name (DN). The value must be enclosed by double quotation marks (") to allow comm_dssetup.pl to interpret a value with a space correctly.
For example: "cn=Directory Manager"
-w DirectoryManagerPassword
Directory Manager DN password.
-b yes|no
Answers the question: “Will this directory server be used for users and groups?”
yes–Use this directory to store both configuration and user group data.
no–Use this directory to store only configuration data.
-t 1|1.5|2
Sun ONE LDAP Schema version:
-m yes|no
Answers the question: “Do you want to modify the directory server?”
yes–Modify the directory server without prompting the user.
no–Do not modify the directory server without prompting the user.
-S PathtoSchemaFiles
Path to the directory where the schema files are located. For example: ./schema
Example
perl comm_dssetup.pl -i yes -c /var/mps/serverroot -d slapd-ketu -r o=internet -u o=usergroup" -s yes -D "cn=Directory Manager" -w password -b yes -t 1 -m yes
When you run in silent mode, comm_dssetup.pl displays a summary similar to Step 11. Summary of Settings for Interactive Mode before making actual changes to your Directory Server.
Interactive Mode
To run in interactive mode, you run the comm_dssetup.pl script without any arguments and then enter your choices as you are prompted.
1. Welcome and Introduction
# perl comm_dssetup.pl
Welcome to the Directory Server preparation tool for Sun ONE Messaging Server.
(Version 6.0 Revision 0.004)
This tool prepares your directory server for Sun ONE Messaging Server install.
The logfile is /var/tmp/dssetup_YYYYMMDDHHSS
Do you want to continue [y]:
Press Enter to continue, or type no and then press Enter to exit.
Note
Although the welcome message refers only to Sun ONE Messaging Server, comm_dssetup.pl also applies to Sun ONE Calendar Server.
2. Installation Root of Directory Server
Please enter the full path to the directory where the Sun ONE Directory Server was installed.
Directory server root [/var/mps/serverroot]
Specify the location of the installation root of the Directory Server.
3. Directory Server Instance
Please select a directory server instance from the following list:
[1] slapd-varrius
Which instance do you want [1]:
If multiple instances of Directory Server reside on the server, choose the one that will be configured with Calendar Server.
4. Directory Manager Distinguished Name (DN)
The Directory Manager DN (cn=Directory Manager) is the administrator who is responsible for the user and group data in the Organization Tree. Be sure that the Directory Manager DN you specify in this script is the same DN that you set up for your Directory Server installation as well for as your Calendar Server configuration.
5. User and Group Directory Server
If you answer Yes, you must also specify a DC Tree base suffix and a User and Group base suffix for your Organization Tree.
If you answer No, it is assumed that this directory instance is used to store only configuration data, and you will skip to the question about updating schema files. After you finish running this script against the configuration directory instance, you need to run this script against the directory instance that stores user and group data before you configure Calendar Server.
6. User and Group Base Suffix
The User and Group base suffix is the top entry in the Organization Tree that holds the name space for user and group entries. Be sure that the User and Group base suffix you select is the same as what you specified for Directory Server and Calendar Server.
If you installed Identity Server, be sure the suffix specified in Identity Server installation is the same as what you specify for this question. If you do not use the same suffix, Calendar Server will not recognize your Identity Server installation.
7. Schema Type
There are 3 possible schema types:
1 - schema 1 for systems with iMS 5.x data
1.5 - schema 2 compatibility for systems with iMS 5.x data that has been converted with imsdirmig
2 - schema 2 native for systems using Identity Server
Please enter the Schema Type (1, 1.5, 2) [1]:
Choose the version of the schema you are planning to use:
To use Sun ONE LDAP Schema, v.2 (options 1.5 or 2) Sun ONE Identity Server 6.1 must be installed and configured; otherwise, comm_dssetup.pl will terminate. You must then rerun the script after Identity Server is installed.
8. Domain Component (DC) Tree Base Suffix
In Step 7. Schema Type, if you choose Option 1 or 1.5, you will be asked to provide your DC Tree Base Suffix. If you choose Option 2, you will not be asked this question.
The DC Tree mirrors the local DNS structure and is used by the system as an index to the Organization Tree that contain the user and group data entries. The DC Tree base suffix is the name of the top entry on the DC tree. You can either choose the default (o=internet) or another name.
9. Updating Schema Files
If you answer Yes, comm_dssetup.pl adds new elements to your schema. It is recommended that you update the directory with the new schema files each time you install a new version of Calendar Server or Messaging Server.
10. Configuring New Indexes
If you answer Yes to Step 5. User and Group Directory Server, you will be asked if you want to configure new indexes, which can improve the performance of directory searches.
For Calendar Server 6.0, comm_dssetup.pl adds indexes for the icsCalendar and icsCalendarOwned attributes. It is recommended that you answer Yes.
11. Summary of Settings
Before comm_dssetup.pl updates the Directory Server configuration, it displays a summary of your settings and then asks if you want to continue.
Here is a summary of the settings that you chose:
Server Root : /var/mps/serverroot/
Server Instance : slapd-varrius
Users/Groups Directory : Yes
Update Schema : yes
Schema Type : 1
DC Root : o=internet
User/Group Root : o=usergroup
Add New Indexes : yes
Schema Directory : ./schema **
Directory Manager DN : cn=Directory Manager
Now ready to generate a shell script and ldif file to modify the Directory.
No changes to the Directory Server will be made this time.
Do you want to continue [y]:
If you chose Option 2 (Sun ONE LDAP Schema, v.2 - Native Mode) in Step 7. Schema Type, the DC Root will be the same value that you entered for the User/Group Root.
To change any of your settings, enter No and re-run the script.
If you continue, comm_dssetup.pl creates the following LDIF file and shell script to update the Directory Server indexes and schema:
/var/tmp/dssetup_timestamp.ldif
/var/tmp/dssetup_timestamp.shAgain, comm_dssetup.pl asks if you want to continue. Enter Yes to run the dssetup_timestamp.sh script now or No to exit. If you exit, you will need to run the /var/tmp/dssetup_timestamp.sh script later.
Calendar Server Configuration Program (csconfigurator.sh)The Calendar Server 6.0 configuration program (csconfigurator.sh) allows you to configure Calendar Server. The configuration program creates a new ics.conf configuration file in the following directory:
/etc/opt/SUNWics5/config
The configuration program performs minimal configuration. After you run the program, you might need to perform additional configuration, as described in the Sun ONE Calendar Server Administrator’s Guide.
The configuration program uses a graphical user interface (GUI). If you run the program remotely, you must set your DISPLAY environment variable properly and allow X-Windows connections from the server to display on your computer. For example, to use the xhost utility, execute the following command on your computer: xhost +.
To run the configuration program, login as or become superuser (root) and change to the /opt/SUNWics5/cal/sbin directory. Then, issue this command:
# sh ./csconfigurator.sh
The configuration program displays the following series of panels:
Welcome PanelFigure 2-1 Calendar Server Configuration Program Welcome Panel
Click Next to continue or Cancel to exit.
Administration, User Preferences and Authentication PanelFigure 2-2 Calendar Server Configuration Program Administration, User Preferences and Authentication Panel
User Preferences Directory Options
- LDAP Server Host Name–Host name of the LDAP directory server you are using for user authentication. Default: current host
- LDAP Server Port–Port number that the LDAP server listens on. Default: 389
- Base DN–Entry in the LDAP directory used as the starting point from which searches will occur. Default: o=host.com.
Calendar Server Administrator Options
Click Next to continue, Back to return to the previous panel, or Cancel to exit.
Email and Email Alarms PanelFigure 2-3 Calendar Server Configuration Program Email and Email Alarms Panel
- Email Alarms–Specifies whether Calendar Server should send an email alarm message to a Calendar Server administrator in case a server problem occurs. Default: Enabled.
- Administrator Email Address–Email address of the Calendar Server Administrator who will receive the email alarm messages. Default: None.
- SMTP Host Name–Host name of the SMTP server where email alarm messages should be sent. Default: current host.
Click Next to continue, Back to return to the previous panel, or Cancel to exit.
Runtime Configuration PanelFigure 2-4 Calendar Server Configuration Program Runtime Configuration Panel
- Service Port–Port number that Calendar Server listens on to provide Web (HTTP) access to users. Default: 80.
- Maximum Sessions–Maximum number of concurrent Calendar Server sessions. Default: 5000
- Maximum Threads–Maximum number of concurrent Calendar Server threads. Default: 20
- Number of Server Processes–Maximum number of Calender Server processes to run on the server. Default: 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 name should not be root. If the account does not exist, the configuration program will create it. Default: icsuser
- Runtime Group ID–UNIX group under which Calendar Server will run. If the group does not exist, the configuration program will create it. Default: icsgroup
- Calendar Server Startup Options
Click Next to continue, Back to return to the previous panel, or Cancel to exit.
Select Directories PanelFigure 2-5 Calendar Server Configuration Program Select Directories Panel
- Database Directory–Directory where Calendar Server should create and store the calendar database files. Default: /var/opt/SUNWics5/csdb
- Logs Directory–Directory where Calendar Server writes log files. Default: /var/opt/SUNWics5/logs
- Temporary Files Directory–Directory where the Calendar Server writes temporary files. Default: /var/opt/SUNWics5/tmp
For each directory, you can accept the default directory, type the full path of another directory, or click Browse... and choose a directory. Then, Click Next to continue, Back to return to the previous panel, or Cancel to exit.
Ready to Configure PanelFigure 2-6 Calendar Server Configuration Program Ready to Configure Panel
Click Configure Now to configure Calendar Server, Back to return to the previous panel, or Cancel to exit.
Configuration Summary PanelFigure 2-7 Calendar Server Configuration Program Summary Panel
Click Details... to view the details of the configuration summary or Close to exit the configuration program.