Gathering Your Configuration Information
The Calendar Server configuration program csconfigurator.sh, creates a new ics.conf configuration file in the following directory:
For Solaris: /etc/opt/SUNWics5/config
For Linux: /etc/opt/sun/calendar/config
The configuration program will ask you many questions for which you must enter specific information about your installation.
Before running the configuration program, you should gather the following configuration information:
To help you keep track of the configuration information, use the worksheets in Appendix B, Calendar Server Configuration Worksheet. (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.)
LDAP Server Options
Calendar Server requires a directory server for user authentication and for the storage and retrieval of user preferences. The following table lists the options used to gather host and port information for the LDAP server.
Table 3–1 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=currentdomain. |
Directory Manager Options
The following table lists the options used to gather the name and password of the user that is designated the Directory Manager.
Table 3–2 Directory Manager Options|
Option |
Description |
|---|---|
|
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 overrides any other Calendar Server ACLs. The Calendar Server Administrator user account must exist in your user authentication directory server. It is also used for proxy authentication. The following table lists the options used to gather the Calendar Server Administrator’s user ID and password.
Table 3–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. The following table lists the options used to gather email information.
Table 3–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 3–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 |
For Solaris: Maximum number of Calendar Server processes to run concurrently. The default is the number of CPU's on the server where you are installing Calendar Server. For Linux: Only one process can run at a time. |
|
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 3–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 3–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 |
|
Archive and hot backup Directories |
Directory where the Calendar Server writes archive backups. User defined directory for storing the daily snapshot and transactions logs. If both types of backups are desired, then place them in different directories. If no directory is specified, backups are stored in the current directory. |
Note –
Do not change the location or names of the logs and temporary files directories.
- © 2010, Oracle Corporation and/or its affiliates