| Oracle Calendar Server Reference Manual Release 5.5 Part Number B10094-01 |
|
| View PDF |
| Oracle Calendar Server Reference Manual Release 5.5 Part Number B10094-01 |
|
| View PDF |
This appendix lists and describes all tunable parameters available to configure your calendar server. All parameters listed are located in the initialization file /users/unison/misc/unison.ini.
Each parameter's stated default value is used if that parameter is omitted from its configuration file. These defaults are not necessarily the optimal settings for your installation. The initialization files supplied with the software contain settings that provide a good starting point for further configuration. It is strongly recommended that for reference purposes you keep a copy, in either printed or electronic format, of these files before modification.
The types of behaviour that can be modified fall under the following sections:
The following table lists all parameters alphabetically by section.
unison.ini configuration parameters[PRODUCT]
name
Specifies the name of the product. Set during installation, this value should not be edited or removed.
n/a
n/a
[PRODUCT]
version
Specifies the version number of your calendar server. Do not edit or remove this value.
n/a
n/a
[UTL]
host
Specifies the host name of the system on which your calendar server is running. The server installation script sets this parameter. This parameter must always have a value set for it in the unison.ini file.
A valid (fully-specified) host name
None
[ENG]
calendarhostname
Specifies an alternate host name for the calendar server in cases when the system-defined host name should not be used.
The principal use for this parameter is to identify the calendar server host in UNIX environments using operating system clusters, where multiple hosts are running the calendar server in the same cluster for failover protection. In this case, you should set the value of this parameter to the name of the operating system cluster itself, rather than the name of any physical calendar server host.
A valid (fully-specified) host name
None
[ENG]
standards
A lists of supported Internet standards and related technologies, enclosed in curly braces {} and separated by commas. Do not change the value of this parameter without explicit instructions from application documentation or Oracle support personnel.
{} (no CAPI support)
{CAPI} (CAPI support with support for some ICAL2.0 attributes)
{CAPI, ICAL2.0} (CAPI support and support for all IETF ICAL 2.0 attributes)
{}
[ENG]
capi_storage
Specifies the version of Oracle's Calendar API (CAPI) that the server supports. The server reads this parameter only if the value of [ENG] standards includes ICAL2.0.
BASIC (pre-4.0 support for CAPI)
FH (support for CAPI 1.0)
OPTFH (support for CAPI 1.1 and higher)
OPTFH
[SYS]
sys_owner
For UNIX only, this parameter specifies the user under whom the calendar server processes run. In all cases, the calendar server executes services with the effective user controlling security set to unison.
Under NT all services run as System Account.
(UNIX)
unison
root
(UNIX)
unison
[CWS]
enable
Determines whether unicwsd, the Corporate-Wide Services daemon/service, automatically starts when the calendar server is brought up. You must set this to TRUE if your server configuration has multiple nodes or mail notification.
TRUE (start unicwsd automatically)
FALSE (do not start unicwsd automatically)
TRUE
[SNC]
enable
Determines whether unisncd, the Synchronous Network Connections daemon/service, automatically starts when the calendar server is brought up. You must set this to TRUE if your server configuration contains multiple nodes or uses a directory server.
TRUE (start unisncd automatically)
FALSE (do not start unisncd automatically)
TRUE
[DAS]
enable
Determines whether unidasd, the Directory Access daemon/service, automatically starts when the calendar server is brought up. The unidasd daemon/service is required only for installations that connect to a directory server.
TRUE (start unidasd automatically)
FALSE (do not start unidasd automatically)
FALSE
[CWS]
startupsleep
Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) at start-up before attempting to process any requests. This delay is intended to provide enough time for the SNC daemon/service to start up and establish the necessary connections to nodes. Increasing the value of this parameter may be necessary for servers with many nodes or connections, or where the bandwidth is low.
A positive integer
60
[CWS]
noreqsleep
Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) when there are no requests in the local queue. After that time, the unicwsd again checks its queue for pending requests. This setting affects how long it takes to propagate data, such as remote user invitations, to other nodes. A low value may slow down the uniengd.
A positive integer up to a maximum value of (232 -1)
60
[CWS]
maxtimepernode
Determines the maximum time, in seconds, that the CWS daemon/service spends processing requests for the same node. After it processes each request, the CWS daemon/service checks the total time it has spent processing requests for the node. If the total time exceeds maxtimepernode, the CWS daemon/service moves on to processing requests from another node, even if the current request queue is not empty. This ensures that the CWS daemon/service treats all nodes fairly, and ensures a more uniform replication delay for calendar data.
A positive integer
30
[NOTIFY]
checkreminderinterval
Determines the interval, in minutes, that the CWS daemon/service waits between checks for reminders.
A positive integer
2
[NOTIFY]
ignoreoldreminders
Determines which reminders the CWS daemon/service ignores when it checks for reminders. It ignores all reminders older than the number of minutes (from the current time) specified by this parameter.
A positive integer
30
[NOTIFY]
limitremindercheck
Specifies the maximum amount of time, in seconds, that the CWS daemon/service spends at one time checking a node for reminders.
A positive integer
30
[<YOURHOSTNAME>,unidas]
numconnect
Specifies the number of connections to establish to the directory server. A number of variables must be considered when setting this parameter. Guidelines are provided for installations contained within the following configuration:
[ENG] dac_itemget = FALSEGuidelines:
uninode utility, establish 4 connections each way between a local node and a remote nodeuninode utility, establish 3 connections each way between local nodesnumconnect to 10% of logged-on users (value represented by the [LCK] lck_users parameter)Administrators of installations that do not match the specified configuration should contact Oracle support for further assistance in setting this parameter.
Any positive integer up to a maximum value of 255
5
[<YOURHOSTNAME>,unidas]
connect_timeout
Determines the number of seconds the unisncd will wait before returning a timeout error when attempting to start the unidasd to connect to the directory server.
0 (no timeout)
A positive integer
10
[ENG]
dac_maxretry
Specifies the maximum number of retries the SNC daemon/service makes when attempting to establish a connection to the DAS daemon/service.
0 (no retries)
Any positive integer up to a maximum value of (232-1)
3
[SNC]
max_socket
Specifies the maximum number of connections the SNC daemon/service brokers among nodes in the node network.
Consult Oracle Support before setting this parameter. In most cases you instantiate all of the connections configured in the nodes.ini file. In certain configurations where you have a large number of nodes on the same machine, this parameter reduces the number of connections used, and thereby the amount of memory required, to instantiate the node network. Each connection has a socket and a uniengd process associated with it so the fewer the connections, the fewer the number of processes and sockets required. See "Connecting nodes" in Chapter 6 of your calendar server's Administrator's Guide for guidelines on the number of connections to configure in the nodes.ini file.
Set this parameter high enough to ensure there is at least one connection from each node in the network to every other node in the network. Tune based on usage statistics.
The [<YOURHOSTNAME>, unidas] numconnect parameter configures the total number of connections to the DAS daemon/service that the SNC daemon/service brokers.
(UNIX)
A positive integer up to the maximum imposed by the following equation:
<flimit> - <#nodes> - 5 - numconnect
where:
numconnect is the value of the [<YOURHOSTNAME>,unidas] numconnect parameterThis equation ensures the SNC daemon/service has sufficient resources to establish connections to both nodes and to the DAS daemon/service. A value well under this maximum is recommended to avoid possible problems related to values close to operating system limits.
(NT)
A positive integer up to a maximum value of 250.
(UNIX)
<flimit> - <#nodes> - 5 - numconnect
(NT)
250
[SNC]
wait_sbh
Specifies the number of minutes to wait if the SNC daemon/service is not able to connect to a remote node.
A positive integer
5
[SNC]
request_chunk_size
Specifies the number of requests that are reset at a time by the SNC daemon/service. When the SNC daemon/service establishes a connection, it examines the request queue of each local node and resets all requests labelled CANTSERVICE to NOTSERVICED. To minimize the time that another process may be made to wait for access to the node database while the SNC daemon/service resets the request queue (which is in the node database), this parameter allows the resetting to be performed in "chunks" of requests.
A positive integer
25
[SNC]
snc_tr_block
Specifies the block size, in bytes, to use for communications between a uniengd server and a unidasd server. Do not change this value without first consulting Oracle support.
0 (use internal default value)
A positive integer
0
[SNC]
snc_tr_recv_timeout
Specifies the time-out value, in seconds, for received transmissions.
0 (require an immediate response)
A positive integer
5
[SNC]
snc_tr_send_timeout
Specifies the time-out value, in seconds, for sent transmissions.
0 (require an immediate response)
A positive integer
0
[SNC]
snc_so_rcvbuf
Specifies the size, in bytes, of the socket layer receive buffer. Do not change this value without first consulting Oracle support.
0 (use internal default value)
A positive integer
0
[SNC]
snc_so_sndbuf
Specifies the size, in bytes, of the socket layer send buffer. Do not change this value without first consulting Oracle support.
0 (use internal default value)
A positive integer
0
[SNC]
snc_so_keepalive
Determines whether or not the system keeps idle connections active.
If this parameter is set to TRUE, a network packet is sent periodically to determine whether or not the process on the other end of an idle connection is still running. If no acknowledgement is received from that process within a specified period of time, it is assumed to have terminated and the connection is no longer maintained.
If this parameter is set to FALSE, periodic checking on idle connections is not done, and the connections are maintained indefinitely.
TRUE (check idle connections)
FALSE (do not check idle connections)
TRUE
[ENG]
activity
Specifies whether or not to log signons and signoffs. The resulting log is useful for tracking server usage and for monitoring possible security violations. If you enable logging, you should closely monitor the size of the log file (/users/unison/log/act.log), as it can grow quickly.
TRUE (enable logging)
FALSE (disable logging)
FALSE
[ENG]
stats
Specifies whether or not to log user session statistics (CPU consumption, user wait times, and network traffic). If you enable logging, you should closely monitor the size of the log file (/users/unison/log/stats.log), as it can grow quickly.
TRUE (enable logging)
FALSE (disable logging)
FALSE
[ENG]
localcharset
Defines the character set to use for data in log files. For example, if you set this parameter to MSCP932, the server will print all of the logs in the /users/unison/log directory in MSCP932.
This parameter is only checked if [ENG] utf8_autoconvert is set to TRUE.
It is recommended that you set this parameter to the same character set you use for the client. Using two different character sets increases the amount of memory required (both character sets must be loaded) and can affect performance.
HPROMAN
HPROMAN8
ISO-8859-1
MAC-JAPANESE
MAC-ROMAN
MSCP1252
MSCP932 (MSCP932 is a slight variation on Shift_JIS)
Shift_JIS
T61
UTF8
UTF8
[CWS]
trace
Determines how much information is written to the unicwsd daemon/service log file (/users/unison/log/cws.log).Set this parameter to TRUE to enable a more verbose style of logging whereby each transaction performed by the CWS daemon/service is logged. This causes the log file to grow rapidly and should only be used for a short time for testing or debugging purposes.
TRUE (enable verbose logging)
FALSE (disable verbose logging)
FALSE
[DAS]
stats
Determines whether unidasd statistics are generated and logged to the dasstats.log and the dsstats.log files. If you enable logging, you should closely monitor the size of the log files, as they can grow quickly.
TRUE (enable logging)
FALSE (disable logging)
FALSE
[ENG]
dac_failederrlog
Determines whether errors related to directory server access that appear in the client interface as "unexpected error" are logged to the /users/unison/log/eng.log file.
TRUE (enable logging)
FALSE (disable logging)
TRUE
[ENG]
dac_configerrlog
Determines whether three directory server access errors are logged to the /users/unison/log/eng.log file. The three errors are: "unable to connect to the SNC daemon/service," "no connections to the directory access (DAS) daemon/service are currently available," and "the number of retries to obtain a connection has been attained; no connections to the directory access (DAS) daemon/service are configured."
TRUE (enable logging)
FALSE (disable logging)
TRUE
[ENG]
dac_miscerrlog
Determines whether three types of directory server access errors related to the client are logged to the /users/unison/log/eng.log file. The three errors are: password discrepancy due to changes made in the directory server through another application; an LDAP client-side error; an LDAP server-side error.
TRUE (enable logging)
FALSE (disable logging)
TRUE
[ENG]
dac_ignorederrlog
Determines whether non-critical directory server access errors are logged to the /users/unison/log/eng.log file.
TRUE (enable logging)
FALSE (disable logging)
TRUE
[ENG]
utf8_onfailprintmesg
Determines whether an error message is logged to /users/unison/log/eng.log if the server is unable to instantiate UTF-8 conversion functionality for a given user session. Enough information is logged in the error message to determine why the functionality could not be created.
TRUE (log an error message)
FALSE (do not log an error message)
TRUE
[ENG]
dac_itemget
Determines whether item retrieval (from a search or a signon) is from the directory server or the internal cache. The internal cache gives better performance, but the item may be slightly out of date.
TRUE (retrieve items from the directory server)
FALSE (retrieve items from the internal cache)
TRUE
[ENG]
utf8_autoconvert
Determines whether input data from the client is converted and stored in UTF-8 format by the server.
WARNING: Setting this parameter to FALSE can have adverse effects in installations that support clients on more than one platform or of more than one language.
TRUE (convert input data to UTF-8)
FALSE (do not convert input data)
TRUE
[DB]
db_pages
Specifies the number of pages for the database cache. The greater the value, the greater the amount of memory used and the better the performance. As the number increases beyond a certain point, the performance enhancement returns diminish.
A positive integer
8
[DB]
db_files
Specifies the number of database files that may be open at any time for one user session. Increasing this number can improve performance in cases when this limit is repeatedly encountered.
A positive integer up to the maximum set by the operating system for number of open files per process.
(UNIX)
30
(NT)
170
[DBI]
dbi_name
Specifies the name of an empty node database to use as a template for node creation. Set during installation, this value should not be edited or removed.
n/a
n/a
[DBI]
dbversion
Specifies the node database version number. Set during installation, this value should not be edited or removed.
n/a
n/a
[<YOURNODEID>]
version
Specifies the version of the node database. This is a reference value set automatically during node creation. It must NEVER be manually edited.
n/a
n/a
[UTL]
external_backup
Specifies an alternate backup utility for unidbbackup to invoke. The server uses the value of this parameter to construct the following command line:
<external_backup value> [-f] -s <src> -d <dst>
where
external_backup value> is the value of this parameterThe generated command line must be valid. It may be that you require an intermediate script to take this command line, create one which is valid, and then invoke the valid one. In this case, you set the value of external_backup to the appropriate value for invoking the intermediate script.
A valid path and file name
None
[UTL]
external_restore
Specifies an alternate restore utility for unidbrestore to invoke. The server uses the value of this parameter to construct the following command line:
<external_restore value> [-f] -s <src> -d <dst>
where
external_restore value> is the value of this parameterThe generated command line must be valid. It may be that you require an intermediate script to take this command line, create one which is valid, and then invoke the valid one. In this case, you set the value of external_restore to the appropriate value for invoking the intermediate script.
A valid path and file name
None
[UTL]
backup_timeout
Sets the maximum time, in seconds, that unidbbackup will keep any node database locked when using an external backup utility. If a node database is locked for longer than this value, unidbbackup will abort the entire backup operation. This parameter is only used when an alternate backup utility is specified using the [UTL] external_backup parameter. When the unidbbackup utility backs up the calendar database itself, the node backup time is not limited.
Note that the total backup time can easily exceed this value when multiple nodes are involved, since each individual node can take up to this amount of time.
A positive integer
3600
[UTL]
restore_timeout
Sets the timeout, in seconds, for the restore operation on the database.
A postive integer
3600
[<YOURNODEID>]
aliases
Specifies the name or names of the nodes configured on a server. When multiple nodes are configured on a server, users must indicate to which node they want to connect. Since, in general, a name is easier to remember than a numeric node-ID, aliases can be configured.
WARNING: Administrators of Lexacom Enterprise Calendar Server installations should avoid changing this parameter once set.
A list of one or more aliases to a maximum of 255 characters, where each alias is an alphanumeric string containing at least one letter and no spaces, and each alias in the list is separated from the next by a comma.
None
[<YOURNODEID>]
name
Specifies the name of the root directory for the node database found under /users/unison/db/nodes/<name>. The value of this parameter is automatically generated during node creation. The first node created is labelled `N0', the second `N1', and following up to `N9'. Subsequent nodes continue the cycle through the alphabet from O to Z and then from A to L.
A code composed of a letter (A-Z) and a number (0-9)
n/a
[<YOURNODEID>]
timezone
Indicates the time zone of the node. The server sets this parameter when it creates the node. Its value should never be changed.
The server sets this parameter to either the time zone specified by the administrator upon creation of the node, or, if the administrator does not specify one, the value of the [TIMEZONE] default parameter.
The timezone parameter allows nodes in a node network to have different time zones.
n/a
None
[<YOURNODEID>]
relativedn
Lexacom Enterprise Calendar Server only. Determines a location for the domain associated with this node in the LDAP hierarchy relative to the calendar server base DN.
Any valid DN, to a maximum of 255 characters.
None
[ENG]
dir_internal_nodes
Identifies all nodes with an internal directory in an installation where the network requires the coexistence of nodes using an LDAP directory and those with their own internal directory.
Valid node-IDs, separated by a comma and enclosed within {}. For example: dir_internal_nodes = {10000,10001}
n/a
[ENG]
usermailmap
Specifies the attribute in the user record that contains users' e-mail addresses. For installations using the calendar server's internal directory only.
A valid X.400 key
None
[ENG]
resourcemailmap
Specifies the attribute in the resource record that contains resources' e-mail addresses. For installations using the calendar server's internal directory only.
A valid X.400 key
None
[ENG]
usermobilemap
Specifies the attribute in the user record that contains users' mobile phone numbers. For installations using the calendar server's internal directory only.
A valid X.400 key
None
[ENG]
usermobiletypemap
Specifies the attribute in the user record that contains users' mobile phone types. For installations using the calendar server's internal directory only.
A valid X.400 key
None
[ENG]
usersmscprefmap
Specifies the attribute in the user record that contains users' preferred notification formats. For installations using the calendar server's internal directory only.
A valid X.400 key
None
[ENG]
itemuidmap
Determines which X.400 field(s) holds the calendar server unique UID. Installations requiring 64 bytes for this information can use the two X.400 fields OU1 and OU2. Do not change the value of this parameter once it has been set. Doing so may result in database corruption. For installations using the calendar server's internal directory only.
A valid X.400 field name
OU1_OU2
None
[ENG]
userlookthroughlimit
Specifies the maximum number of items (users or resources) the calendar server searches through before ending a search and returning the results to the client.
A positive integer up to a maximum value of 4294967295
4294967295
[ENG]
usersearchmaxreturn
Specifies the maximum number of items (users or resources) in a search result. Once the search result contains this number of items, the server ends the search and returns the results to the client.
A positive integer up to a maximum value of 4294967295
4294967295
[ENG]
eventsearch_maxlookthroughlimit
Specifies the maximum time in milliseconds to spend searching events. For native clients v. 5.0 or greater.
A positive integer
5000
[ENG]
evsearch_maxcount
Specifies the maximum number of events to return from a search. For native clients v. 5.0 or greater.
A positive integer greater than 10.
25
[ENG]
eventsearch_commentsearchlength
Specifies the maximum number of bytes to search through in an event's comments, starting at the beginning. For native clients v. 5.0 or greater.
0 (Disables searching in comments)
A positive integer
4096
[ENG]
notify
Determines whether or not notification by SMTP-based UNIX mail is performed on event creation. This parameter applies only to pre-3.0 versions of the client.
TRUE (enable notification)
FALSE (disable notification)
TRUE
[CWS]
smtpmail
Determines whether mail notifications are sent using the SMTP mail server. This parameter should always be set to TRUE, regardless of whether mail notification is enabled. Mail notification is enabled or disabled using the [LIMITS] mail parameter.
This parameter supercedes unixmail. For backwards compatibility, if smtpmail is not set, and a value for the unixmail parameter can be found, that value is used.
TRUE (use the SMTP mail server)
FALSE (do not use the SMTP mail server)
FALSE
[CWS]
unixmail
This parameter is superceded by [CWS] smtpmail.
[CWS]
smtpmailprogram
Specifies the mail utility for transferring messages to the SMTP mail server. This parameter supercedes unixmailprogram. For backwards compatibility, if smtpmailprogram is not set, and a value for the unixmailprogram parameter can be found, that value is used.
(UNIX)
sendmail
postmail
(NT)
sendmail.exe
(UNIX)
sendmail
(NT)
sendmail.exe
[CWS]
unixmailprogram
This parameter is superceded by [CWS] smtpmailprogram.
[CWS]
smtpmailpath
Specifies the directory pathname of the local mail utility. This parameter supercedes unixmailpath. For backwards compatibility, if smtpmailpath is not set, and a value for the unixmailpath parameter can be found, that value is used.
A valid pathname
(UNIX)
/usr/lib
(NT)
/users/unison/bin
[CWS]
sendmailpath
This parameter is superceded by [CWS] smtpmailpath.
[CWS]
smtpmailhost
Specifies the name of the host on which the SMTP mail server is running. This parameter is meaningful only under NT. It supercedes [CWS] mailhost. For backwards compatibility, if smtpmailhost is not set, and a value for the mailhost parameter can be found, that value is used.
A valid host name
The host name of the machine on which the calendar server is running.
[CWS]
mailhost
This parameter is superceded by [CWS] smtpmailhost.
[CWS]
smtpmailmaxrecipients
Specifies the maximum number of recipients for a mail message. If a mail is to be sent with more recipients than the value of this parameter, the CWS will split the list of recipients and call the sendmail program multiple times.
See also the [CWS] smtpmailmaxcommandlinesize parameter.
A positive integer
100
[CWS]
smtpmailmaxcommandlinesize
Specifies the maximum size of the buffer passed to the sendmail program as a command-line argument. If the buffer size required is larger than this value, the CWS will split the list of recipients and call the sendmail program multiple times.
See also the [CWS] smtpmailmaxrecipients parameter.
A positive integer
1024
[CWS]
mailfiledelete
Determines whether the temporary file containing the last sent mail message is deleted after the mail is sent. This parameter may be useful to check the calendar server behaviour if you are experiencing a problem with mail delivery.
The temporary file in which the server writes the last mail message can be found at /users/unison/tmp/MAILMSG.
TRUE (delete mail messages automatically)
FALSE (do not delete mail messages automatically)
TRUE
[CWS]
mailhdroriginatorfromuser
Determines whether the "From:" field of the mail header is the e-mail address of the sender.
TRUE ("from" field is same as "reply-to" field)
FALSE ("from" field is set to "unison,unison")
TRUE
[CWS]
mailhdrtoname
Determines whether or not to include names along with addresses in the "To:" field of the mail header. While addresses are constructed using ASCII characters (and hence present no display problem for mail readers), names may contain non-ASCII characters. In cases where the mail reader is unable to display the non-ASCII characters properly, it may be preferable to simply remove the names from the "To:" field altogether.
TRUE (include names)
FALSE (do not include names)
TRUE
[CWS]
mimecontentcharset
Determines the character set to use to encode the content and subject portion of all MIME mail messages sent by the CWS daemon/service. For example, if you set the value of this parameter to MAC-ROMAN, the content and subject portions of all messages sent by the CWS daemon/service will be in MAC-ROMAN.
"CN-GB"
"HPROMAN"
"HPROMAN8"
"ISO-8859-1"
"MAC-JAPANESE"
"MAC-ROMAN"
"MSCP1252"
"MSCP932"
"Shift_JIS"
"T61"
"UTF8"
Note that the enclosing quotation marks must be present.
"ISO-8859-1"
[CWS]
emailcharsetmap
A mapping table determining what client character sets to convert before sending e-mail. If the character set used by a client is not in this list, then the value of [CWS] mimecontentcharset is used for e-mail sent by that client.
If this parameter is left blank, the following mapping table will be used:
MSCP932 --> ISO-2022-JP EUC-JP --> ISO-2022-JP SHIFT-JIS --> ISO-2022-JP ISO-2022-JP --> ISO-2022-JP MSCP936 --> ISO-2022-CN EUC-CN --> ISO-2022-CN HP15CN --> ISO-2022-CN CN-GB --> ISO-2022-CN
In other words, clients with the MSCP932, EUC-JP, SHIFT-JIS and ISO-20220-JP character sets will send e-mail in ISO-2022-JP; clients with the MSCP936, EUC-CN, HP15CN and CN-GB character sets will send e-mail in ISO-2022-CN.
If the [CWS] emailcharsetmap parameter is used to specify a mapping, that value will be added to this default table, overriding the default values only where necessary. For example, if the value of this parameter were set to {"MSCP932": "SHIFT-JIS"}, all clients using the MSCP932 character set would send mail in SHIFT-JIS, overriding the default mapping listed above. All other mappings listed in the table would still be in effect.
A list of charset mappings separated by commas and enclosed in {}, with the following syntax: "<charset used by client>": "<charset used for e-mail>"
See above
[LOCALE]
charset
Determines the character set to use to encode the content portion of the mail message.
HPROMAN
HPROMAN8
ISO-8859-1
MAC-JAPANESE
MAC-ROMAN
MSCP1252
MSCP932
Shift_JIS
T61
UTF8
ISO-8859-1
[CWS]
smsnotifyprogram
Specifies the file name and location of the sendalert utility the calendar server uses to send alerts to Oracle's wireless delivery services.
Any valid path and file name
none
[CWS]
smsnotifyprogramparam
Specifies the command-line argument that will be passed to the sendalert utility configured by the [CWS] smsnotifyprogram parameter.
Use this parameter to indicate to the sendalert utility the host name and port of your Oracle 9iAS PIM Notification Dispatcher. For details on how to find out the host name and port number of your Oracle 9iAS PIM Notification Dispatcher, see the "Alerts" chapter of your calendar server Administrator's Guide.
"-host <hostname> -port <portnumber>"
none
[TIMEZONE]
default
Specifies the local time zone.
Any time zone that appears in the /users/unison/misc/timezone.ini file (e.g. EST-5EDT)
None
[TIMEZONE]
rules
Specifies the name of the file containing time zone rules.
A valid fully-specified file name
/users/unison/misc/timezone.ini
[TIMEZONE]
checksum
Contains the checksum of the time zone rules file. This value is preset and must not be altered under any circumstance.
n/a
n/a
[DOMAIN]
type
Controls the possibility of connecting nodes. When set to corporate or portal, nodes may be connected only in a single network or cluster. When set to asp, all nodes are always disconnected and may not be linked in a node network.
asp
corporate
portal
corporate
[CLUSTER]
masternode
Specifies a master node for the cluster.
A valid node-ID belonging to any node in the cluster
None
[CLUSTER]
remotemasternode
Specifies the master node in the cluster. This parameter speeds up the replication of information to the master node when users are created using uniuser.
A valid node-ID belonging to any node in the cluster
None
[CLUSTER]
excludednodes
Determines what nodes are excluded from on-line user registration. The server will not create users on listed nodes. Use this parameter to avoid registering users on your cluster's master node, or on nodes that are reaching maximum capacity.
A list of valid node-IDs or aliases belonging to any nodes in the cluster, separated by commas and enclosed in {}. For example:
{ 14, 446, 447 }
{ }
[ENG]
allowsysoplogon_uniical
Specifies whether uniical users may log in to the server as SYSOP.
TRUE (SYSOP logons allowed)
FALSE (SYSOP logons not allowed)
TRUE
[ENG]
allowsysoplogon_unicp
Specifies whether users of the unicp* family of utilities may log in to the server as SYSOP.
TRUE (SYSOP logons allowed)
FALSE (SYSOP logons not allowed)
TRUE
[ENG]
allowsysoplogon_capi
Specifies whether applications using Oracle's Calendar API (CAPI) can log in to the server as SYSOP.
TRUE (SYSOP logons allowed)
FALSE (SYSOP logons not allowed)
FALSE
[DAS]
dir_service
Specifies the directory service that the unidasd daemon/service accesses. The value of this parameter is also found as the name of the section in the /user/unison/misc/unison.ini file where the configuration parameters for the directory service are found. For example, if dir_service = LDAP, the [LDAP] section of the unison.ini file contains the LDAP directory service configuration parameters.
LDAP
LDAP
[LDAP]
dsa
Specifies the name of the LDAP directory server. This parameter is set during installation. Changing the value of this parameter may result in directory server corruption.
OID (Oracle Internet Directory)
None
[LDAP]
host
Specifies the name of the machine hosting the LDAP directory server. If failovers for the directory server have been configured, they may be listed here. By default, the calendar server will attempt to establish a connection to the first server listed; if unable to do so, it will try the next.
A valid host name, fully-qualified domain name, or IP address
A list of directory servers, in the form "<hostname>[:<port>] <hostname>[:<port>]" For example:
"host1:389 host2:389"
None
[LDAP]
port
Specifies the port number of the LDAP directory server. If the [LDAP] host parameter contains a port number, the value of the [LDAP] port parameter will be ignored.
A valid port number
389
[LDAP]
charset
Indicates the character set the LDAP directory server uses. This is the character set that the calendar server must use for data destined for the LDAP directory server.
HPROMAN
HPROMAN8
ISO-8859-1
MAC-JAPANESE
MAC-ROMAN
MSCP1252
MSCP932
Shift_JIS
T61
UTF8
UTF-8
[LDAP]
attr_version
Specifies the LDAP protocol version used by the directory server. Set the value of this parameter to 2 only if your LDAP directory server does not support the LDAPv3protocol.
2 (for LDAPv2)
3 (for LDAPv3)
3
[<YOURHOSTNAME>,unidas]
dir_adminmodcalonly
Specifies whether the calendar server's reserved users can modify all directory server attributes or only the calendar attributes in the directory server.
TRUE (permit modifications to calendar attributes only)
FALSE (permit modifications to all attributes)
FALSE
[<YOURHOSTNAME>,unidas]
dir_adminupdcalonly
Specifies whether the calendar server's reserved users can update all directory server attributes or only the calendar attributes in the directory server.
TRUE (permit updates to calendar attributes only)
FALSE (permit updates to all attributes)
FALSE
[LDAP]
attrpreservelist
Specifies a list of attributes (a "preserve list") which are not to be deleted when a calendar user is deleted (i.e. when the user's calendar attributes as well as their ctCalUser object class are deleted). If the calendar user entries also use the inetOrgPerson object class, you should configure this parameter as follows:
{employeeNumber, givenName, initials, mail, ou}
Any fields mapped to attributes outside of the ctCalUser object class (e.g. attr_organization = uid) should also be added to the "preserve list".
A list of strings, separated by commas and enclosed in {}, where each string in the list is the name of a user attribute
{}
[LDAP]
attr_uid
Determines the directory server attribute name that the calendar server uses as a unique user identifier. Do not change the value of this parameter unless you also change the attribute your Oracle Internet Directory uses to authenticate SSO logins. If you change that attribute on your directory server, you must change the value of this parameter.
Any attribute name defined in the LDAP directory server schema
uid
[LDAP]
attr_country
Determines the attribute name that the LDAP directory server uses for the "country" attribute.
Any attribute name defined in the LDAP directory server schema
None
[LDAP]
attr_generation
Determines the attribute name that the LDAP directory server uses for the "generation qualifier" attribute.
Any attribute name defined in the LDAP directory server schema
generationQualifier
[LDAP]
attr_organization
Determines the attribute name that the LDAP directory server uses for the "organization" attribute.
Any attribute name defined in the LDAP directory server schema
None
[LDAP]
attr_givenname
Determines the attribute name that the LDAP directory server uses for the "given name" attribute.
Any attribute name defined in the LDAP directory server schema
givenName
[LDAP]
attr_mail
Determines the attribute name that the LDAP directory server uses for the "mail" attribute.
Any attribute name defined in the LDAP directory server schema
mail
[LDAP]
attr_uid
Determines the attribute name that the LDAP directory server uses for the "uid" attribute.
Any attribute name defined in the LDAP directory server schema
uid
[LDAP]
groupobjectclass
Determines the name of the object class for the group of calendar server administrators.
groupOfUniqueNames
groupOfUniqueNames
[LDAP]
groupmemberattribute
Determines the name of the "member" attribute that is in the object class specified by the groupobjectclass parameter.
uniqueMember
uniqueMember
[LDAP]
admin
Specifies part of the Distinguished Name (DN) of the location under which calendar server administrators will be created. The DN of this location is constructed by appending the value of the basedn parameter to the value of the admin parameter. For example, where admin = "ou=calendar servers" and basedn = "o=acme", the DN for the location under which calendar server administrators will be created is "ou=calendar servers, o=acme".
A valid Distinguished Name or Relative Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
admingroup
Specifies part of the Distinguished Name (DN) of the group entry for calendar server administrators (the administrators are added to this group). The DN of the group entry is constructed by appending the value of the basedn parameter to the value of the admingroup parameter. For example, where admingroup = "cn=calendar server admins" and basedn = "o=acme", the DN for the group entry of calendar server administrators is "cn=calendar server admins, o=acme".
A valid Distinguished Name or Relative Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
cn=Calendar Server Admins
[LDAP]
basedn
Specifies the Distinguished Name of the LDAP directory server subtree containing calendar entries.
A valid Distinguished Name of a maximum of 255 characters (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
resourcerelativedn
Specifies a location for resources in the LDAP directory relative to the calendar server base DN (specified by the value of the [LDAP] basedn parameter).
If a full Distinguished Name is specified when creating a new resource, that value will be used and the value of this parameter will be disregarded.
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
None
[<YOURNODEID>]
resourcerelativedn
For Lexacom Enterprise Calendar Server only. Specifies the Resource Relative DN in which to locate resources for the domain associated with this node. This DN is relative to the domain's Relative DN (see the [YOURNODEID] relativedn parameter).
For all servers, if a full Distinguished Name is specified when creating a new resource, that value will be used and the value of this parameter will be disregarded.
A valid Distinguished Name of a maximum of 255 characters (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
binddn
Specifies the Distinguished Name the LDAP directory server uses for anonymous connections.
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
mgrdn
Specifies the Distinguished Name of the LDAP directory server administrator.
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
bindpwd
Specifies the password for the LDAP user specified by the value of the [LDAP] binddn parameter.
You must encrypt the password using the uniencrypt utility before entering it in the unison.ini file. See the uniencrypt documentation in Appendix C, "Utilities". The encrypted password must be preceded by the encrpytion method used to generate it (acipher in most cases) and enclosed in double-quotes.
"{acipher}<encrypted_value>"
None
[LDAP]
writedn
Specifies the Distinguished Name the calendar server uses for all write operations on the directory server.
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct form)
None
[LDAP]
writednpassword
Specifies the password for the LDAP user specified by the value of the [LDAP] writedn parameter.
You must encrypt the password using the uniencrypt utility before entering it in the unison.ini file. See the uniencrypt documentation in Appendix C, "Utilities". The encrypted password must be preceded by the encrpytion method used to generate it (acipher in most cases) and enclosed in double-quotes.
"{acipher}<encrypted_value>"
None
[UTL]
adm_moduserpassword
Determines whether the calendar server administrator can modify the password of a calendar user.
TRUE (can modify the password)
FALSE (cannot modify the password)
TRUE
[LDAP]
dsausesearchtocompare
Indicates whether the LDAP directory server handles ldap_compare() calls properly or must use ldap_search() calls to simulate ldap compare() calls.
TRUE (uses ldap_search() calls)
FALSE (handles ldap_compare() calls properly)
FALSE
[LDAP]
groupfilter
Specifies the LDAP filter the calendar server uses when searching groups in the directory server.
The default value of this parameter exposes all groups to the calendar client; users will be able to see all groups in the directory server, and any members of those groups who are also calendar users. However, if there are groups in the directory server that consist entirely of non-calendar users, the calendar client will display these groups with no members.
To avoid this, you may wish to create a custom object class such as "calendarGroup", and apply this object class only to the LDAP groups that you wish to be visible through the calendar client. Then, extend the value of this parameter to include that object class. For example, the new value might be:
(&(member=*)(objectclass=groupOfNames)(objectclass=calendarGroup))
For more details, see Chapter 3 of your calendar server Administrator's Guide.
Any valid filter, up to a maximum length of 150 characters
(&(uniqueMember=*)(objectclass=groupOfUniqueNames))
[LDAP]
timelimit
Specifies the maximum time, in seconds, that the server waits on an LDAP call before returning a timeout error to the client. Note that the timeout settings in the directory server take precedence over this parameter.
0 or a positive integer. A value of 0 means no timeout ever occurs and causes the server to wait until the directory server returns either a result or an error.
120
[LDAP]
security
Enables SSL connections to the LDAP directory server. If this parameter is set to TRUE, the calendar server uses the LDAPSSL functions contained in the libraries specified by the [LDAP] ldapssllibname and [LDAP] lberssllibname parameters to connect to the directory server. Otherwise it uses the LDAP functions contained in the libraries specified by the [LDAP] ldaplibname and [LDAP] lberlibname parameters to connect to the directory server.
TRUE (enable SSL connections)
FALSE (disable SSL connections)
FALSE
[LDAP]
secure-port
Determines the port to use for SSL connections. This parameter is only checked if [LDAP] security is set to TRUE.
Any value in the range 1 to 65535
636
[LDAP]
certdbpath
Specifies the path and/or file name of the file containing the certificates used by the SSL. This parameter is only used when the value of the [LDAP] security parameter is set to TRUE.
A valid path and file name
A valid file name
cert7.db (the database file used by Netscape Communicator 4.x and up)
A valid path name. In this case the calendar server adds the file name cert7.db to the path.
Note that on Windows platforms, any path information specified in the value of this parameter must use UNIX syntax, with forward-slashes '/' instead of backslashes '\', and omitting the drive letter from the beginning of the string. The file must also exist on the same drive as the calendar server installation directory.
cert7.db
[LIMITS]
allowattachments
Determines whether or not the client allows attachments for meetings or tasks.
TRUE (allow attachments)
FALSE (do not allow attachments)
FALSE
[LIMITS]
maxattachmentsize
Determines the maximum size, in bytes, for attachments to meetings, tasks and other agenda entries. This parameter is only checked if the [LIMITS] allowattachments parameter is set to TRUE. Suggested value is 102400 (100K).
Any positive integer up to a maximum value of (232-1)
232-1
[LIMITS]
autocontrol
Determines the minimum number of minutes that a user can set as the interval between agenda refresh calls to the server (i.e. between each check for new agenda entries).
If this value is less than lck_users/60, the value of lck_users/60 takes precedence, to a maximum value of 45. For example, if autocontrol = 15 and lck_users = 1200, no refresh occurs before 20 (i.e. 1200/60) minutes has elapsed.
Note that this parameter has been superseded by the [CLIENT] minrefreshrate parameter, which enforces the behaviour on the server side instead of on the client side. It is included here for backward compatibility with older clients.
Any positive integer up to a maximum value of (216-1)
15
[CLIENT]
minrefreshrate
Determines the minimum number of minutes that a user can set as the interval between agenda refresh calls to the server (i.e. between each check for new agenda entries).
Note that this value overrides the [LIMITS] autocontrol parameter, and does not take into account the value of the [LCK] lck_users parameter as autocontrol does.
Note also that setting the value of this parameter too low can have serious consequences upon the performance of the calendar system. The more system resources and database access time are devoted to automatic idle refreshes, the slower the perceived performance of on-demand requests can become. Tune this parameter according to the number of logged-on users you experience at peak hours, and according to the number of database requests per second your hardware can comfortably accommodate.
For example, if testing has established acceptable performance benchmarks at one automatic refresh request per second, then for an environment of 1000 users, this parameter should not be set to an interval lower than 1000 seconds, or approximately seventeen minutes. The value provided at installation time should serve as an acceptable limit for all but the most exceptional installations.
Any positive integer up to a maximum value of (216-1)
15
[LIMITS]
maxrecur
Specifies the maximum number of instances the client allows a user to create for a single repeating meeting, daily note, or day event.
This parameter is now outdated. For Windows and Macintosh clients v. 5.0 and above, use the [ENG] maxinstances parameter instead to control this behaviour. However, it is recommended that you ensure the [LIMITS] maxrecur and [ENG] maxinstances parameters be set to the same value, to ensure full compatibility between all clients.
A positive integer up to a maximum value of (232-1)
60 (60 instances per meeting, note, or day event)
[ENG]
maxinstances
Determines the maximum number of instances of a recurring meeting, daily note, or day event the calendar server can create. It is recommended that you ensure the [LIMITS] maxrecur parameter be set to the same value as [ENG] maxinstances to ensure full compatibility between all clients.
An integer in the range 1-65535
100
[LIMITS]
maxremleadtime
Specifies the maximum number of days in advance of an event that a user can set a reminder to ring.
Any positive integer up to a maximum value of (232-1)
21
[LIMITS]
resourceconflicts
Determines whether the client allows users to double-book resources. This parameter should always be set with the same value as the[ENG] allowresourceconflict parameter.
TRUE (allow double-bookings)
FALSE (do not allow double-bookings)
TRUE
[ENG]
allowresourceconflict
Determines whether the server allows double-booking of resources. This parameter should always be set with the same value as the[LIMITS] resourceconflicts parameter.
TRUE (allow double-bookings)
FALSE (do not allow double-bookings)
FALSE
[LIMITS]
agendaview
Determines the default view in which the client opens agenda windows. For clients 4.1 and above.
0 (day view)
1 (week view)
2 (month view)
0
[LIMITS]
maxwinopen
Determines the maximum number of windows (views) that can be opened at the same time in the user interface.
Any positive integer up to a maximum value of (232-1)
7
[LIMITS]
groupviewmax
Specifies the maximum number of users that the client can display in a group view.
A positive integer up to the value of (232-1)
100
[<YOURNODEID>]
localnodes
Specifies which remote resources to consider local for client scheduling purposes. If you want users on separate but connected nodes to view and treat all resources as local (a common situation when two or more nodes are in close geographic proximity), enter the relevant node-ID(s) after this parameter. Nodes must be connected to enable this feature.
Valid node-IDs, separated by a comma
n/a
[ENG]
passwords
Determines whether client password verification is case-sensitive. Only used for installations using the calendar server's internal directory.
case (case sensitive)
ignorecase (case insensitive)
case
[LIMITS]
ssignin
Determines whether a user can use the desktop clients' automatic sign-in feature to sign in to the calendar server without providing a password. For Windows clients 4.2 and above and Macintosh clients 4.5 and above.
See also the [LIMITS] ssigninrestrictions parameter.
TRUE (allow automatic sign-in)
FALSE (force user to always supply a password)
FALSE
[LIMITS]
ssigninrestrictions
Restricts the automatic sign-in feature of desktop clients to secure operating systems. The automatic sign-in feature will be unavailable for clients running on Windows 95/98 and Mac OS 7/8.
See also the [LIMITS] ssignin parameter.
TRUE (restrict automatic sign-in to secure operating systems)
FALSE (allow automatic sign-in from any operating system)
TRUE
[LIMITS]
maxpasswordage
Controls password aging. The value represents the number of days that a password can exist before users are required to change it.
Any positive integer up to a maximum value of (232-1)
76543 (for all practical purposes, password aging is OFF)
[LIMITS]
signinmaxattempts
Determines how many unsuccessful sign-in attempts are allowed before the client closes. Native clients v. 5.0 and greater only.
An integer between 1 and 232
5
[LIMITS]
userlist_login
Determines whether or not to show a list of matching users when more than one fits the specified sign-in credentials. Native clients v. 6.0 and greater only.
TRUE (Display the list of matching users)
FALSE (Don't display the list)
TRUE
[LIMITS]
secure-login
Determines whether or not to restrict information given about incorrect sign-in credentials. Native clients v. 6.0 and greater and Web clients v. 3.0 and greater only.
TRUE (Display only that the credentials supplied are incorrect)
FALSE (Display more user-friendly error messages on incorrect sign-in)
FALSE
[LIMITS]
singlelst
Disables the client's Different Local Storage dialog. If this parameter is set to TRUE, only one user may access the calendar server from a given client machine. If another user tries to sign in, he or she will be forced to quit the application.
TRUE (disable different local storage)
FALSE (allow different local storage)
FALSE
[DAS]
dir_updcalonly
Determines whether users can update only calendar attributes, or calendar and non-calendar attributes within their entries.
TRUE (permit updates only to calendar attributes)
FALSE (permit updates to any attributes)
FALSE
[DAS]
dir_itembindonread
Forces the Directory Access Server to sign in to the directory server for read-only operations (e.g. searching).
Read operations are carried out using the anonymous profile. If that profile has limited rights, directory server searches will be constrained by those rights.
Note that write operations always require a bind.
TRUE (demand credentials for searches)
FALSE (permit searches without calling credentials)
FALSE
[LIMITS]
pubgroups
Determines whether users holding the necessary access rights can create public groups.
TRUE (permit users to create public groups)
FALSE (do not permit users to create public groups)
TRUE
[LIMITS]
settimezone
Determines whether the user is permitted to save time zone changes for future client sessions.
TRUE (permit users to set a different time zone)
FALSE (do not permit users to set a different time zone)
FALSE
[LIMITS]
mail
Determines whether mail notification is enabled, regardless of how the client is set up.
TRUE (enable mail notification)
FALSE (disable mail notification)
TRUE
[NOTIFY]
sms
Determines whether wireless alerts are enabled. See your calendar server Administrator's Guide for details on the available wireless alert services.
TRUE (enable SMS notification)
FALSE (disable SMS notification)
FALSE
[LIMITS]
maxmaildistr
Specifies the maximum number of users in a mail notification distribution list.
Any positive integer up to a maximum value of (232-1)
30
[LIMITS]
mincharsearch
Determines the minimum number of search characters that the user must supply in the Surname field when performing a directory search from the client. The default value of 0 allows a user to execute a search without limits and retrieve the complete database of users.
0
A positive integer up to a maximum value of (232-1)
0
[LIMITS]
maxsearchresult
Determines the maximum number of items (users or resources) that the search dialogue box lists in both the calendar clients and the Admin GUI. Tune this parameter relative to the size of your installation. If you use an external directory server, tune this parameter to match any search limits configured in the directory server. Consult the relevant CorporateConnect appendix for your directory server, or your directory server documentation to determine what these limits are and how to configure them.
Any positive integer up to the value of (232-1)
100 (list only 100 entries at a time)
[LIMITS]
page-forward
Determines whether the "next" button is enabled in the item search dialogue box for users and resources of the calendar clients and the Admin GUI.
When a search is performed, the [LIMITS] maxsearchresult parameter determines the maximum number of search results to return to the client. Assume page-forward is TRUE, maxsearchresult is set to 100, and you search for all users whose surname begins with "S". If there are 220 such users in the database, the search dialogue will present you with the first 100 users. You may then click on the "next" button to see the next 100 users, and click again to see the last 20.
This functionality is disabled when the server is connected to a directory server.
TRUE (enable the "next" button)
FALSE (disable the "next" button)
TRUE
[LIMITS]
page-backward
Determines whether the "previous" button is enabled in the search dialogue box for users and resources. This button performs the reverse operation of the [LIMITS] page-forward parameter, allowing the user to return to previously-listed entries of the search result.
This functionality is disabled when the calendar server is connected to a directory server.
TRUE (enable the "previous" button)
FALSE (disable the "previous" button)
TRUE
[ENG]
eventsearch_clientwindowsize
Specifies the number of rows in the client's event search result list box. For native clients v. 5.0 or greater.
A positive integer
20
[OUTLOOK_CONNECTOR]
eventselectbegin
For Oracle Outlook Connector only. Sets the number of days preceding the current date that will be searched or returned for all database queries.
Any positive integer up to the value of the number of days between the current date and January 1, 1991.
180
[OUTLOOK_CONNECTOR]
eventselectend
For Oracle Outlook Connector only. Sets the number of days following the current date that will be searched or returned for all database queries.
Any positive integer up to the value of the number of days between the current date and December 31, 2037.
730
[GENPREFS]
offlineab
For native clients 5.1 and above. Enables and disables the use of address books.
TRUE (enable address books)
FALSE (disable address books)
TRUE
[LIMITS]
publishab
For clients 4.1 and above. Enables the publishing of address books.
TRUE (enable the publishing of address books)
FALSE (disable the publishing of address books)
TRUE
[LIMITS]
maxpersabentries
For clients 4.0 and above. Determines the maximum number of personal address book entries.
Any positive integer up to a maximum value of (232-1)
2000
[QUOTA]
maxfolderentryperuser
Determines the maximum number of entries in an address book folder.
0 (no entries)
A positive integer up to a maximum value of (232-1)
2000
[ENG]
eventrefreshintervals
Configures the refresh intervals and agenda ranges, in seconds, that Oracle Outlook Connector uses when it queries the server for new events.
This parameter is a list of intervals, separated by commas and enclosed in {}. Each interval in the list has the following format:
: -<lower bound> +<upper bound>
where <interval>, <lower bound> and <upper bound> are all expressed in seconds. The <interval> determines the refresh interval. The <lower bound> and <upper bound> determine a range of time.
Every <interval> specifies a time when the calendar server should refresh Outlook with the associated range of agenda data. For example, the entry {900: -0 +172800} specifies that every 15 minutes (<interval> of 900 seconds) the server should refresh Outlook with an agenda range beginning at the current time (<lower bound> of 0 seconds) and continuing through 2 days following (<upper bound> of 172800 seconds).
<interval>, <lower bound> and <upper bound> are integers in the range 0-65535
{0: -86400 +518400, 2700: -604800 +10886400, 79200: -0 +0}
The first interval specifies that all client-initiated queries for events have a minimum agenda range of one day previous (-86400) through to six days (+518400) following the time of the query. The second interval tells the client to query the server every 45 minutes (2700) for events in the range of one week previous (-604800) to six weeks (+10886400) from the time of the query. The third interval tells the client to query the server every 22 hours (79200) for all events.
[LIMITS]
browserhelp
For Windows clients version 4.5 or greater. Displays the on-line help in an ordinary web browser rather than the Microsoft HTML Help Viewer. If a browser is specified by the [WEBLINK] browser-path-win parameter, that browser is used.
For best results, please ensure that Java and Javascript are enabled in the browser.
TRUE (Forces on-line help to be displayed in a browser)
FALSE (Displays on-line help in Microsoft's HTML Help Viewer, if installed; if not, displays on-line help in a browser)
FALSE
[WEBLINK]
mode
Determines whether web access is enabled in the client, and how it is configured. This functionality gives Windows and Macintosh clients the ability to access and display a web page.
If this parameter is set to custom, ALL of the other [WEBLINK] parameters must have values specified in the unison.ini file. If this is not the case, the value of this parameter reverts to the default (cst).
off or cst (disable web access)
custom (enable web access and take values for all of the other [WEBLINK] parameters from unison.ini.)
cst
[WEBLINK]
browser-path-win
For Windows clients, this parameter determines which browser to launch for web access. For Windows clients 4.5 and greater, it also determines a browser for the on-line help when [LIMITS] browserhelp is set to TRUE, or when Microsoft HTML Help Viewer is not installed. This parameter determines the location of the web browser on the local machine of each signed-on user.
A valid path and filename
None
[WEBLINK]
command-name
Determines the text string that appears in the Help menu for the web access item, as well as in the pop-up ToolTip accompanying the Toolbar web access icon.
A string with a maximum of 150 characters in length
(when [WEBLINK] mode = cst) Product Information
[WEBLINK]
command-description-online
For Windows clients, determines the description of the web access command that appears on the status bar when the client is on-line. For Macintosh clients 4.2 or earlier, determines the description of the web access command that appears in balloon help when the client is on-line.
A string with a maximum of 150 characters in length
(when [WEBLINK] mode = cst) Click here to access product information on the web.
[WEBLINK]
command-description-offline
For Windows clients, determines the description of the web access command that appears on the status bar when the client is off-line. For Macintosh clients 4.2 and earlier, determines the description of the web access command that appears in balloon help when the client is off-line.
A string with a maximum of 150 characters in length.
(when [WEBLINK] mode = cst) Click here to access product information on the web.
[WEBLINK]
download-mode
Determines the file transfer protocol to use when downloading the web pages for viewing in off-line mode.
file (use the file sharing protocol)
(when [WEBLINK] mode = cst) file
[WEBLINK]
online-url
Determines the web page to load for clients working on-line.
A valid URL with a maximum of 150 characters in length
None
[WEBLINK]
offline-source-win
For Windows clients. Determines the source of the web page to display when working in off-line mode. This parameter is only checked when [WEBLINK] mode = custom.
A valid path and file name with a maximum of 150 characters in length
None
[WEBLINK]
offline-source-mac
For Macintosh clients. Determines the source of the web page to display when working in off-line mode.
A string with a maximum of 150 characters in length which obeys the following format and restrictions:
<user>:<pw>@[<zone>]:<AFP Server Name>[,<ip>[,<port>]];<volume path>:
where:
This parameter is only checked when [WEBLINK] mode = custom.
None
[WEBLINK]
offline-source-version
Determines the version of the off-line web page. This provides a mechanism for the administrator to ensure that the most recent version of the off-line web page is the one being accessed. This parameter is only checked when [WEBLINK] mode = custom.
A character string with a maximum length of 150 characters.
None
[WEBLINK]
download-fail
Determines the error message to display if a download fails.
A character string with a maximum length of 150 characters.
(when [WEBLINK] mode = cst) Your on-line account did not supply all the information needed to support this operation. Please contact your system administrator.
[WEBLINK-FRENCH]
mode
Determines whether French-language web access is enabled in the client, and how it is configured. This functionality gives Windows and Macintosh clients the ability to access and display a web page.
If this parameter is set to custom, ALL of the other [WEBLINK-FRENCH] parameters must have values specified in the unison.ini file. If this is not the case, the value of this parameter reverts to the default (cst).
off or cst (disable web access)
cst (enable web access and take the values for all of the other [WEBLINK-FRENCH] parameters directly from the code; ignore any values set in the unison.ini file for these other parameters)
custom (enable web access and take values for all of the other [WEBLINK-FRENCH] parameters from unison.ini.)
cst
[WEBLINK-FRENCH]
browser-path-win
For Windows clients, this parameter determines which browser to launch for French-language web access. This parameter determines the location of the web browser on the local machine of each signed-on user.
A valid path and filename
None
[WEBLINK-FRENCH]
command-name
Determines the French-language text string that appears in the Help menu for the web access item, as well as in the pop-up ToolTip accompanying the Toolbar web access icon.
A string with a maximum of 150 characters in length
(when [WEBLINK-FRENCH] mode = cst) Information sur le produit
[WEBLINK-FRENCH]
command-description-online
For Windows clients, determines the description of the web access command that appears on the status bar when the client is on-line. For Macintosh clients 4.2 or earlier, determines the description of the web access command that appears in balloon help when the client is on-line.
A string with a maximum of 150 characters in length
(when [WEBLINK-FRENCH] mode = cst) Lancer le navigateur Web pour visualiser l'information sur le produit
[WEBLINK-FRENCH]
command-description-offline
For Windows clients, determines the description of the web access command that appears on the status bar when the client is on-line. For Macintosh clients 4.2 or earlier, determines the description of the web access command that appears in balloon help when the client is on-line.
A string with a maximum of 150 characters in length
(when [WEBLINK-FRENCH] mode = cst) Lancer le navigateur Web pour visualiser l'information sur le produit
[WEBLINK-FRENCH]
online-url
Determines the French-language web page to load for clients working on-line.
A valid URL with a maximum of 150 characters in length
None
[WEBLINK-FRENCH]
download-mode
Determines the file transfer protocol to use when downloading web pages for viewing in off-line mode.
file (use the file sharing protocol)
(when [WEBLINK-FRENCH] mode = cst) file
[WEBLINK-FRENCH]
offline-source-win
For Windows clients. Determines the source of the web page to display when working in off-line mode. This parameter is only checked when [WEBLINK-FRENCH] mode = custom.
A valid path and file name with a maximum of 150 characters in length
None
[WEBLINK-FRENCH]
offline-source-mac
For Macintosh clients. Determines the source of the web page to display when working in off-line mode.
A string with a maximum of 150 characters in length which obeys the following format and restrictions:
<user>:<pw>@[<zone>]:<AFP Server Name>[,<ip>[,<port>]];<volume path>:
where:
This parameter is only checked when [WEBLINK-FRENCH] mode = custom.
None
[WEBLINK-FRENCH]
offline-source-version
Determines the version of the off-line web page. This provides a mechanism for the administrator to ensure that the most recent version of the off-line web page is the one being accessed. This parameter is only checked when [WEBLINK-FRENCH] mode = custom.
A character string with a maximum length of 150 characters.
None
[WEBLINK-FRENCH]
download-fail
Determines the error message to display if a download fails.
A character string with a maximum length of 150 characters.
(when [WEBLINK-FRENCH] mode = cst) Le telechargement s'est acheve correctement. Les fichiers de mode déconnecte ont ete restaures.
[ACE]
frameworkenable
Enables authentication, compression, and encryption. Note that if you disable the ACE module, the calendar server uses the built-in cs-basic authentication method. In other words, the calendar server always uses an authentication method.
TRUE (enable authentication, compression, encryption)
FALSE (disable authentication, compression, encryption)
TRUE
[ACE]
slibcachecount
Determines the number of shared libraries that can be loaded at the same time for each type of method (authentication, compression, encryption).
Due to a limitation of IBM AIX in which shared libraries cannot be reloaded once removed from memory, the default value of this parameter is higher than for other platforms.
A positive integer up to a maximum value of 32768
20 (IBM AIX only)
3 (all other platforms)
[ACE]
minbufsizetocompress
Specifies the minimum size in bytes required in order for a buffer to be compressed.
A positive integer up to a maximum value of 32768
700
[ACE]
workbufsize
Specifies the size, in bytes, of the buffer to allocate for compression and encryption.
A positive integer up to a maximum value of 32768
4096
[AUTHENTICATION]
supported
Specifies a list of the authentication methods the calendar server supports for clients.
Both the cs-basic and the cs-standard methods use the calendar server name and password of a user to authenticate that user. Both encrypt the user password; cs-standard also encrypts the user name. This encryption is independent of the negotiated encryption method. The server applies the negotiated encryption on top of this encryption.
The cs-basic authentication method works with all calendar clients, regardless of client version. It pre-dates the calendar server ACE module.
cs-standard is the recommended authentication method to use where the client supports it. It offers a higher level of security (better authentication and encryption) than cs-basic.
Only the cs-basic and cs-standard methods currently work with LDAP directory servers.
A list of one or more of the following, separated by commasand enclosed in {}:
cs-basic
cs-standard
{cs-basic, cs-standard}
[AUTHENTICATION]
default
Specifies the default authentication method the calendar server uses for clients. See the description of the [AUTHENTICATION] supported parameter for more information on supported methods.
Any method in the list specified by the [AUTHENTICATION] supported parameter.
cs-standard
[AUTHENTICATION]
admindefault
Specifies the default authentication method the calendar server uses for administrative sessions using the Calendar Administrator. See the description of the [AUTHENTICATION] supported parameter for more information on supported methods.
Any method in the list specified by the [AUTHENTICATION] supported parameter.
The value of the [AUTHENTICATION] default parameter
[AUTHENTICATION]
servicedefault
Specifies a default encryption method for the calendar server to use for communications with other calendar servers that request connections.
The server uses this default, along with the list of supported encryption methods, when it negotiates ACE methods with another calendar server initiating a request.
Any method in the list of supported encryption methods specified by the [AUTHENTICATION] supported parameter.
The value of the [AUTHENTICATION] default parameter.
[AUTHENTICATION]
keepresourcepswincaldb
Determines whether resource passwords are stored in the calendar server's internal database or in the database of the configured authentication mechanism.
TRUE (resource passwords stored in the calendar server database)
FALSE (resource passwords stored in the authentication mechanism database)
TRUE
[COMPRESSION]
supported
Specifies a list of the compression methods the calendar server supports. Currently, only the Oracle cs-simple compression method is supported. This method uses simple run-length encoding compression, a very fast and efficient compression method for calendar data.
A list of one or more of the following, separated by commas and enclosed in {}:
cs-simple
none
{cs-simple, none}
[COMPRESSION]
default
Specifies the default compression method the calendar server uses for clients.
Any method in the list specified by the [COMPRESSION] supported parameter.
cs-simple
[COMPRESSION]
admindefault
Specifies the default compression method the calendar server uses for administrative sessions using the Calendar Administrator. See the description of the [COMPRESSION] supported parameter for more information on supported methods.
Any method in the list specified by the [COMPRESSION] supported parameter.
The value of the [COMPRESSION] default parameter
[COMPRESSION]
servicedefault
Specifies a default compression method for communications with other calendar servers that attempt to connect to this server.
The server uses this default, along with the list of supported compression methods, when it negotiates ACE methods with another calendar server initiating a request.
Any method in the list specified by the [COMPRESSION] supported parameter.
The value of the [COMPRESSION] default parameter.
[ENCRYPTION]
supported
Specifies a list of the encryption methods the calendar server supports.
The cs-light method scrambles data with a randomly generated key. It is very fast and offers minimal impact on performance, but is recommended for minimal-security installations.
The cs-acipher1 method is slower than the cs-light method, but offers much more secure encryption.
A list of one or more of the following, separated by commas and enclosed in {}:
cs-light
cs-acipher1
none
{cs-light, cs-acipher1, none}
[ENCRYPTION]
needsauthenticate
Specifies a list of encryption methods that require authentication prior to use. These methods are only available after the calendar client or another server authenticates itself to this calendar server. The initial ACE negotiation cannot include any of the methods listed by this parameter.
A list of any methods in the list specified by the [ENCRYPTION] supported parameter, separated by commas and enclosed in {}.
{}
[ENCRYPTION]
default
Specifies the default encryption method the calendar server uses for clients.
Any method in the list specified by the [ENCRYPTION] supported parameter.
none
[ENCRYPTION]
admindefault
Specifies the default encryption method the calendar server uses for administrative sessions using the Calendar Administrator. See the description of the [ENCRYPTION] supported parameter for more information on supported methods.
Any method in the list specified by the [ENCRYPTION] supported parameter.
The value of the [ENCRYPTION] default parameter
[ENCRYPTION]
servicedefault
Specifies a default encryption method for the calendar server to use for communications with other calendar servers that request connections.
The server uses this default, along with the list of supported encryption methods, when it negotiates ACE methods with another calendar server initiating a request.
Any method in the list of supported encryption methods specified by the [ENCRYPTION] supported parameter.
The value of the [ENCRYPTION] default parameter.
[ACE_PLUGINS_SERVER]
web_CAL_sharedkey
Specifies the shared key to compare with the value of the client webcal.ini [ACE_PLUGINS_CLIENT] web_CAL_sharedkey parameter.
A valid path and file name
None
[LCK]
lck_users
Specifies the maximum number of Engine processes permitted. The value of this parameter should be carefully considered. It must allow for enough Engines to service both client access and SNC connections; however setting the value higher than required wastes system resources.
A positive integer up to 2000 (NT) or 5000 (UNIX)
100
[ENG]
max_userlogons
Specifies the maximum number of concurrent "named" sessions that each user may invoke. A session is "named" if it is associated with a specific user and "unnamed" if it is not associated with a specific user.
0 (no limit)
A positive integer
0
[ENG]
max_addrlogons
Specifies the maximum number of concurrent "unnamed" sessions that can be invoked by a single client, that is, from a single Internet address. A session is "named" if it is associated with a specific user and "unnamed" if it is not associated with a specific user.
0 (no limit)
A positive integer
0
[ENG]
readlocktimeout
Determines the number of consecutive seconds that the server can lock the database for a client read request. If this maximum is exceeded, the uniengd server and the associated user session terminate, and the timeout is logged to eng.log.
0 (no limit)
A positive integer up to the value of (232-1)
60
[ENG]
writelocktimeout
Determines the number of consecutive seconds that the server can lock the database for a client write request. If this maximum is exceeded, the uniengd server and the associated user session terminate, and the timeout is logged to eng.log.
0 (no limit)
A positive integer up to the value of (232-1)
60
[ENG]
readmaxlocktime
For newer operations, determines the number of consecutive milliseconds that an operation can hold a read lock on the calendar database. If this maximum is exceeded, the lock will be released. If the process has not been completed, it will then re-lock the calendar database.
0 (no limit)
A positive integer up to the value of (232-1)
250
[ENG]
writemaxlocktime
For newer operations, determines the number of consecutive milliseconds that an operation can hold a write lock on the calendar database. If this maximum is exceeded, the lock will be released. If the process has not been completed, it will then re-lock the calendar database.
0 (no limit)
A positive integer up to the value of (232-1)
150
[LIMITS]
remotewait
Specifies the number of seconds the client waits before retrying a call to the server for data from a remote server.
A positive integer up to the value of (232-1)
2
[LIMITS]
remotemaxretry
Specifies the number of retries of a request for remote node data that the client makes before returning an error.
A positive integer up to the value of (232-1)
5
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|