| Oracle® Calendar Reference Manual 10g Release 1 (10.1.1) Part Number B14473-01 |
|
|
View PDF |
| Oracle® Calendar Reference Manual 10g Release 1 (10.1.1) Part Number B14473-01 |
|
|
View PDF |
This chapter lists and describes all tunable parameters available to configure your Oracle Calendar server. All parameters listed are located in the initialization file $ORACLE_HOME/ocal/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 behavior that can be modified fall under the following sections:
The following table lists all parameters alphabetically by section.
Table 3-1 unison.ini configuration parameters
Table 3-2 unison.ini configuration parameters - [PRODUCT] section
Table 3-3 unison.ini configuration parameters - [CLUSTER] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
Master node Indicates that the specified node on this server is the master node for the cluster. Only one node in the cluster can be the master node. This parameter must be set only on one of the networked Oracle Calendar servers and the node must be one that exists on the same host. |
A valid node-ID belonging to any node on this server |
None |
|
|
|
Specifies the master node in the cluster. This parameter speeds up the replication of information to the master node when users are created using For more information about the |
A valid node-ID belonging to any node in the cluster |
None |
|
|
Excluded nodes for on-line registration 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
|
|
Table 3-4 unison.ini configuration parameters - [CSM] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Automatic start of CSM daemon/service Determines whether Note: This parameter applies to Oracle Calendar standalone deployments only. |
|
|
|
Calendar Server Manager password for remote management Specifies the password needed to access the Calendar Server Manager for remote management of the Oracle Calendar server. For standalone Oracle Calendar server installations only. This is not needed if you are using the Oracle Internet Directory as part of the Oracle Collaboration Suite. You must encrypt the password using the |
|
None |
|
|
|
Calendar Server Manager port number Determines the port to use for incoming CSM network connections. This parameter is useful if there are multiple instances of the Oracle Calendar server installed on the same machine. |
A valid port number |
Value entered at installation (usually |
Table 3-5 unison.ini configuration parameters - [CWS] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Automatic restart of CWS daemon/service Determines whether See Also: |
|
|
|
|
Determines how long the server will attempt to restart the CWS daemon/service Determines the time, in seconds, that the [CWS] autorestart_enable mechanism will attempt to restart If this parameter is set to 0, the functionality will be disabled. See Also: |
A positive integer between 60 and 232 -1 |
259200 (3 days)) |
|
|
Enable message banners for mail notifications and reminders Determines whether or not to include message banners at the end of notification e-mail messages sent to users. The default banners are defined in files contained in the The banner files must contain UTF-8 text. To convert strings into UTF-8, use the |
|
|
|
|
Determines times for Common Address Book synchronization Specifies a list of times when the Common Address Book synchronization should be executed. This parameter applies to Oracle Collaboration Suite deployments only. See Also: [ENG] cab_enable, [ENG] cabsyncinterval |
A list of times in 24 hour format, separated by commas and enclosed in
|
{19:00,23:00,03:00,07:00} |
|
|
Enable the continuous consistency scan Specifies whether the Oracle Calendar server's continuous consistency scan is enabled. The continuous scan only scans and fixes inconsistencies in events that have recently been modified. The frequency at which a continuous scan is run is determined by the value of [CWS] cscs_continuousfrequency. Note: This scan is not a replacement for unidbfix. It fixes inconsistencies that cannot be fixed by unidbfix. See Also: |
TRUE (enable continuous consistency scan) FALSE (disable continuous consistency scan) |
TRUE |
|
|
Determine the frequency of the continuous consistency scan Specifies, in seconds, how often the continuous consistiency scan is run. See Also: |
Any integer from 0 to 232-1 |
1380 (23 minutes) |
|
|
Enable full consistency scan Enable the Oracle Calendar server's full consistency scan. The full consistency scan verifies and corrects all of the address books in the local Oracle Calendar server stores. Event and tasks verification are not done with the full consistency scan. See Also: |
|
|
|
|
Determine time of full consistency scan Specify the time when an Oracle Calendar server full consistency scan should be triggered. This parameter works in conjunction with the See Also: |
A valid time in 24 hour format: HH:MM. |
|
|
|
Determine day of full consistency scan Specify the day when an Oracle Calendar server full consistency scan should be triggered. This parameter works in conjuction with the See Also: |
A positive integer equal to or between |
|
|
|
Enable the incremental consistency scan Specifies whether the Oracle Calendar server's incremental consistency scan is enabled. The incremental scan only scans and fixes inconsistencies in events and address book entries that have been modified during the previous day. The frequency at which a continuous scan is run is determined by the value of [CWS] cscs_incrementalfrequency. Note: This scan is not a replacement for See Also: |
TRUE (enable incremental consistency scan) FALSE (disable incremental consistency scan) |
TRUE |
|
|
Determine the frequency of the incremental consistency scan Specifies the times at which the incremental consistiency scan is run. Note: Because the incremental scan looks through large amounts of modifications, Oracle recommends running the scan during off-peak hours. See Also: |
A list of times in 24 hour format, separated by commas and enclosed in
|
|
|
|
Enable Notification-Based User Provisioning Determines whether the Oracle Calendar server allows notification-based provisioning from the Directory Integration Platform. For more information on notification-based user provisioning, see "Calendar Provisioning Models" in Chapter 7 of Oracle Calendar Administrator's Guide. |
|
|
|
|
Migrate directory user preferences Determines whether the user preferences should be migrated from the directory to the calendar database. This parameter will be set and removed automatically during the upgrade process. Do not set this parameter manually unless it's advised by Oracle support personnel, data corruption may occur. |
|
|
|
|
Scheduled times for directory synchronization Specifies a list of times when the automatic directory synchronization should be executed. This should be set to non peak hours as much as possible. |
A list of times in 24 hour format, separated by commas and enclosed in
|
|
|
|
Automatic start of CWS daemon/service Determines whether Note: This parameter applies to Oracle Calendar standalone deployments only. |
|
|
|
|
Set the update frequency for modified calendar data list (for synchronization tools) Determines the interval, in seconds, at which the server triggers updates of the calendar entries synchronization information. This information is used when a synchronization client asks the server for the list of calendar entries that have changed and that need to be synchronized with local client data. |
A positive integer |
|
|
Determines the interval, in seconds, at which the CWS daemon/service triggers updates of the Global Address List (GAL). Note that the server will only generate an update if the current GAL was invalidated, for example in the case where a new node was added to the network, or the current revision is too old (see the |
A positive integer |
|
|
|
Activity logging Determines whether activity information of the The log file is located in the log directory ( |
|
|
|
|
Activity logging: specifying modules Specifies the list of modules for which the logging of activity information should be allowed. By default the list is empty, so, for instance, setting |
A list of one or more of the following, separated by commas and enclosed in
|
|
|
|
|
Automatic deletion of temporary file for last mail message 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 Oracle Calendar server behavior 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 |
|
|
|
|
Content of the "From:" field of the mail header Determines whether the "From:" field of the mail header is the e-mail address of the sender. |
|
|
|
|
UTF-8 for names in "To:" field of mail header Determines whether or not to include names along with addresses in the e-mail address fields ("From:", "To:" and "Reply-To") 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, remove the names from the address field altogether. |
|
|
|
|
Maximum number of nodes a CWS task will manage Determines the maximum number of nodes a Corporate Wide Server task can service. If more than 20 nodes exist, a second unicwsd task will be started. |
A positive integer |
|
|
|
Maximum time spent processing requests for each node 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 |
A positive integer |
|
|
|
Maximum time spent processing messaging requests Determines the maximum time, in seconds, that the CWS daemon/service spends processing messaging (mail, alert, and Real-Time Collaboration, Web conferencing) requests. After it processes each messaging request, the CWS daemon/service checks the total time it has spent processing these types of requests for the node. If the total time exceeds |
A positive integer |
|
|
|
Maximum time spent waiting before processing messaging requests in error state Determines the maximum time, in seconds, that the CWS daemon/service will wait before trying to process a messaging request (mail, alert, or Real-Time Collaboration, Web conferencing) in an error state. |
A positive integer |
|
|
|
Character set for content portion of mail message - Default This parameter determines the default character set to use to encode the content and subject portion of all MIME mail messages sent by the CWS daemon/service. Normally, the character set used for notification mail messages depends on the sending client application or, for mail reminders, the destination user's language. But if the destination language is not supported, the character set defined by this parameter will be used. |
UTF8 WE8ISO8859P1 English: US7ASCII WE8MSWIN1252 AL32UTF8 WE8ISO8859P15 Brazilian Portuguese, French, German, Italian: WE8ISO8859P1 WE8MSWIN1252: AL32UTF8 WE8ISO8859P15 Japanese: ISO2022-JP JA16EUC JA16SJIS AL32UTF8 Korean: KO16MSWIN949 KO16KSC5601 AL32UTF8 Simplified Chinese: ZHS16CGB231280 ZHS16GBK ZHS32GB18030 AL32UTF8 Traditional Chinese: ZHT16MSWIN950 ZHT16BIG5 ZHT16HKSCS AL32UTF8 Other values: "MAC-ROMAN" "ISO-8859-1" Note: The enclosing quotation marks must be present. |
|
|
|
Character set for content portion of mail message - Forced Forces the character set used to encode the content and subject portion of all MIME mail messages sent by the CWS daemon/service to that defined by this parameter. |
See accepted values of |
|
|
|
Sleep time between checks on request queue Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) when there is no work to do. This setting affects how often certain operations, such as server-side reminders and replication, are done. A low value may slow down the uniengd but reduces any delays in processing reminders and Web conferencing replication requests. If no replication requests remain in the CWS replication queue, the number of seconds to wait before checking for new replication requests will be the greater of |
A positive integer |
|
|
Sleep time between checks on request queue for replication requests Specifies the number of seconds the Corporate-Wide Services daemon/service waits (sleeps) when there are no replication requests in the queue. This setting affects how often certain operations, such as remote user replication, are done. A low value may slow down the uniengd but reduces any delays in processing reminders and Web conferencing replication requests. If no replication requests remain in the CWS replication queue, the number of seconds to wait before checking for new replication requests will be the greater of |
A positive integer |
|
|
|
|
Specifies the list of jobs that should have a CWS task associated to it. By default there will be two CWS tasks handling jobs, one dedicated to replication, the other handling all other jobs, including e-mail and server side reminders. For example, in an environment where there are very few replication requests, but many server side reminders to send, the administrator may want to have a CWS dedicated to server side reminders, in which case this parameter should be set to One must be careful when dedicating a CWS task to a particular job, since the CWS would require more engines. Each CWS task will have one process for each prioritized job. Each CWS task will start an engine to each node that it serves. The possible jobs and their meaning are:
|
The list specified must contain valid job names separated by commas and enclosed in |
|
|
|
This parameter is obsolete and has been superseded by |
n/a |
n/a |
|
|
Errors to ignore for (SMS) notification program Specifies the errors to be ignored that the alert utility may return. See also |
A list of error values, separated by commas and enclosed in
|
|
|
|
Short Message Service (SMS) notification program Specifies the file name and location of the utility the Oracle Calendar server uses to send alerts, that is, notifications and reminders, to the Oracle Mobile Collaboration PIM Notification Dispatcher. This functionality is only available with an Oracle Collaboration Suite installation. See Also: |
Any valid path and file name |
|
|
|
Host name of the SMTP mail server Specifies the name of the host on which the SMTP mail server is running. This parameter is meaningful only under Windows. It supersedes |
A valid host name |
The host name of the machine on which the Oracle Calendar server is running. |
|
|
Host name of the SMTP mail server Identify the URL, including host and port, for the SMTP server. Note: If [CWS] smtpmail_url_auto is set to TRUE, this parameter value will be automatically set by the Oracle Internet Directory service discovery. See Also: [CWS] smtpmail_url_auto |
(where <hostname> is a valid host name and <port> is a valid port) Example:
|
|
|
|
Discover the URL for the Oracle Mail Server Determines whether the Oracle Calendar server will automatically discover the URL for the Oracle Mail Server. When set to TRUE, the Oracle Calendar server discovers this value automatically in Oracle Internet Directory and replaces [CWS] smtpmail_url with the value discovered. This discovery is done at server start up, and as such will not take effect until the server is stopped and restarted. This applies to Oracle Collaboration Suite deployments only. See Also: [CWS] smtpmail_url |
|
|
|
|
Maximum size for sendmail command lines 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: |
A positive integer |
|
|
|
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: |
A positive integer |
|
|
|
Specifies the directory path name of the local mail utility. This parameter supersedes |
A valid path name |
(UNIX)
(Windows)
|
|
|
Discover if Oracle Mail is configured Determines whether the Oracle Calendar server will automatically discover from Oracle Internet Directory if Oracle Mail is configured. This discovery is done at server start up, and as such will not take effect until the server is stopped and restarted. This applies to Oracle Collaboration Suite deployments only. Note: When set to See Also: |
|
|
|
|
Specifies the mail utility for transferring messages to the SMTP mail server. This parameter supersedes |
(UNIX:)
(Windows:)
|
(UNIX:)
(Windows:)
|
|
|
Discover if Oracle Mail is configured Determines whether the Oracle Calendar server will automatically discover from Oracle Internet Directory if Oracle Mail is configured. This discovery is done at server start up, and as such will not take effect until the server is stopped and restarted. This applies to Oracle Collaboration Suite deployments only. Note: When set to See Also: |
|
|
|
|
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 |
|
Table 3-6 unison.ini configuration parameters - [DAS] section
Table 3-7 unison.ini configuration parameters - [DB] section
Table 3-8 unison.ini configuration parameters - [DBI] section
Table 3-9 unison.ini configuration parameters - [ENG] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Statistics logging: user connections Specifies whether or not to log signons and signoffs to the Oracle Calendar server. 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 ( |
|
|
|
|
Allow SYSOP logons for Oracle Calendar SDK applications Specifies whether applications using Oracle Calendar SDK can log in to the server as SYSOP. |
|
|
|
|
Allow SYSOP logons from unicp utilities Specifies whether users of the |
|
|
|
|
Allow SYSOP logons from uniical Specifies whether |
|
|
|
|
Specifies an alternate host name for the Oracle Calendar server in cases when the system-defined host name should not be used. The principal use for this parameter is to identify the Oracle Calendar server host in UNIX environments using operating system clusters, where multiple hosts are running the Oracle 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 Oracle Calendar server host. Oracle suggests defining an alias for the calendar host, and using the alias when setting up a node network. If a physical host change occurs in the future, this will facilitate ease of migration and configuration on the new host. |
A valid (fully-specified) host name |
None |
|
|
Enable the Common Address Book Determines whether the Common Address Book is enabled. This parameter applies to Oracle Collaboration Suite deployments only. For more information about the Common Address Book feature, see "About the Common Address Book (CAB)" in Chapter 6 of Oracle Calendar Administrator's Guide. See Also: |
|
|
|
|
Enable a two-way synchronization of the Common Address Book with OiD Specify whether the next Common Address Book synchronization with Oracle Internet Directory (OiD) will be a two-way synchronization. When a typical Common Address Book synchronization occurs, OiD is considered the most up-to-date version of the Common Address Book. As such, contacts that are not present in OiD will be deleted from the Calendar store during the next synchronization. This can cause problems if the Oracle Calendar server is redirected to a new OiD that does not include the Common Address Book data. This parameter exists to prevent such data loss. When When Note: This parameter should only be set to TRUE if the Oracle Calendar server is redirected to a new Oracle Internet Directory that does not include Common Address Book data. See Also: |
|
|
|
|
Specifies the full synchronization interval for the Common Address Book Determines the average interval, in minutes, that the Oracle Calendar server will perform a full synchronization all users' Common Address Books. The value assigned to this parameter will be adjusted by up to plus or minus 50 percent by the Oracle Calendar server. This parameter applies to Oracle Collaboration Suite deployments only. Example: When cab_syncinterval is set to the default value of 10800, we expect that all users' Common Address Books will be fully synchronized between 5400 and 16200 minutes, or 3.5 and 10.5 days. For more information about the Common Address Book feature, see "About the Common Address Book (CAB)" in Chapter 6 of Oracle Calendar Administrator's Guide. See Also: [ENG] cab_enable, [CWS] cabsynctime |
Any positive integer |
|
|
|
Supported Oracle Calendar SDK version Specifies the version of Oracle Calendar SDK that the server supports. The server reads this parameter only if the value of |
|
|
|
|
Use old CWS authentication mechanism Specifies whether coexistence with older Oracle Calendar servers is required. When the complete Oracle Collaboration Suite is installed, the new method called Oracle Trusted Application tier is used for cws authentication. Otherwise, for standalone Oracle Calendar server installations and older versions of the Oracle Calendar server, where this new authentication is not supported, the basic cws authentication needs to continue to be supported. By default the basic authentication is not allowed, but setting this parameter to |
|
|
|
|
Support old non identifying clients Specifies whether the server should refuse unidentified sessions from older clients or older servers. Clients and servers version 9.0.4 and up always identify themselves correctly. |
|
|
|
|
Logging of configuration errors Determines whether three directory server access errors are logged to the |
|
|
|
|
Enable support for access controls set on a per user basis Configure the Oracle Calendar server to respect the access controls (ACLs) set on Oracle Internet Directory and only expose directory entries that the user is entitled to see. This feature is supported for Oracle Collaboration Suite installations where all users use Oracle Calendar Web Client only. Note: Enabling this feature leads to a load increase for Oracle Internet Directory because the Oracle Calendar server binds as a user every time it accesses Oracle Internet Directory instead of binding only once when the session is established. |
|
|
|
|
Determines whether errors related to directory server access that appear in the client interface as "unexpected error" are logged to the |
|
|
|
|
Logging of non-critical errors Determines whether non-critical directory server access errors are logged to the |
|
|
|
|
Specifies the maximum number of retries the SNC daemon/service makes when attempting to establish a connection to the DAS daemon/service. |
Any positive integer up to a maximum value of 231 |
|
|
|
Logging of miscellaneous errors Determines whether three types of directory server access errors related to the client are logged to the |
|
|
|
|
Coexistence of LDAP and non-LDAP 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. This parameter is only used when the Oracle Calendar server is installed in standalone mode. |
Valid node-IDs, separated by a comma and enclosed within |
None |
|
|
Enable searches based on mapped item attributes in the Directory Server Enable searches based on a list of item attributes that may be searched in the Directory Server when no efficient searches can be performed in the calendar database. Using For a list of available attributes, see uniuser -info. These attributes must be mapped in the Directory Server. After specifying the list of attributes, run the unidssync utility to import the attributes. Note: This parameter is not available on Oracle Calendar standalone internal installations. |
Valid calendar account attributes, separated by commas and surrounded by For example:
|
|
|
|
Control the number of client connections from a specific IP address Determines the maximum number of connections to the Oracle Calendar server that can be made from one specific IP address before connections are blocked. |
0 (unlimited connections to the server from one specific IP address) A positive integer |
|
|
|
Restrict connections to the Oracle Calendar server based on IP address Specify a list of IP addresses that will be blocked from connecting to the Oracle Calendar server. Note: Host names are not acceptable values. Only IP addresses will yield the desired effect. |
A list of IP addresses, separated by a comma and enclosed within |
{} |
|
|
Maximum number of client connections from one IP address before a logging begins Determines the maximum number of connections that can be made from one specific IP address to the Oracle Calendar server before an entry is logged in the $ORACLE_HOME/ocal/log/eng.log. |
A positive integer |
300 |
|
|
Specify a list of IP addresses that are exempted from being blocked Define a list of IP addresses that are exempt from being blocked from the Oracle Calendar server. Connections made from the IP addresses in this list will be able to establish an unlimited number of connections to the Oracle Calendar server. Note: Host names are not acceptable values. Only IP addresses will yield the desired effect. |
A list of IP addresses, separated by a comma and enclosed within |
{} |
|
|
Timeout value for non-header data Determines the time, in seconds, that the Oracle Calendar server will wait for non-header data to be received. This parameter exists to protect the server from a denial of service attack. If the data is not received within the specified amount of time, the session will be terminated and logged in the $ORACLE_HOME/ocal/log/eng.log. |
A positive integer in the range of 1 to 65535 |
10 |
|
|
Timeout value for handshake data Determines the time, in seconds, that the Oracle Calendar server will wait for handshake data to be returned from a client. This parameter exists to protect the server from certain types of Denial Of Service (DOS) attacks. If the data is not received within the specified amount of time, the session will be terminated. |
A positive integer in the range of 1 to 65535 |
5 |
|
|
Specifies the maximum number of bytes to search through in an event's comments, starting at the beginning. For Oracle Calendar Desktop Clients version 9.0.4 or greater. |
A positive integer |
|
|
|
Maximum number of events to return Specifies the maximum number of events to return from a search. For Oracle Calendar Desktop Clients only. |
A positive integer greater than 10. |
|
|
|
Specifies the maximum time in milliseconds to spend searching events. For Oracle Calendar Desktop Clients only. |
A positive integer |
|
|
|
Storing Web Client Preferences Specifies the maximum length of the itemextinfo attribute used by the Web client to store calendar account preferences. |
A positive integer larger than 1500 |
None |
|
|
Defines the character set to use for data in log files. For example, if you set this parameter to This parameter is only checked if If this parameter is set to a character set different from the one used for the clients, two character sets will have to be loaded into memory instead of one. Using two different character sets increases the amount of memory required and can affect performance. |
See accepted values of [CWS] |
Note: Initial versions of Oracle Calendar Release 2 (9.0.4) used US7ASCII as the default value for NLS_LANG. US7ASCII does not support several accented characters, so .WE8ISO8859P1 was implemented starting with Patch Set 1. If your version of Oracle Calendar server precedes Patch Set 1 and uses US7ASCII as the default, it is recommended that you set NLS_LANG to .WE8ISO8859P1. |
|
|
Determines whether the on demand provisioning feature is enabled. This feature allows a user to be automatically provisioned when accessing Calendar through Single Sign On for the first time. Note: This parameter applies to Oracle Collaboration Suite deployments only. |
|
TRUE |
|
|
Oracle Calendar server port number Determines the port to use for incoming network connections. This parameter is useful if there are multiple instances of an Oracle Calendar server installed on the same machine. |
A valid port number |
Value entered at installation (usually |
|
|
Session expiry for Calendar SDK Minimum amount of time, in minutes, before connections held by customer-written applications developed using Oracle Calendar SDK will be recycled to release resources. The actual expiry is set within plus or minus 30% of this value. This implies that, with a default setting of 2160 minutes (36 hours), the actual expiry will be within 1 or 2 days of the connection being establised. A value of 0 indicates that no limit should be enforced by the server. Note: If this value is set below 480 minutes, |
Any positive integer |
|
|
|
Session expiry for OCAP Calendar SDK Minimum amount of time, in minutes, before connections held by Oracle supplied applications using Oracle Calendar SDK will be recycled to release resources. The actual expiry is set within plus or minus 30% of this value. This implies that, with a default setting of 2160 minutes (36 hours), the actual expiry will be within 1 or 2 days of the connection being establised. A value of 0 indicates that no limit should be enforced by the server. Note: Client applications are not affected by this connection loss. |
0 (no expiry time) Any positive integer |
|
|
|
Session expiry for Oracle Calendar application system Minimum amount of time, in minutes, before connections held by Oracle Calendar application system will be recycled to release resources. The actual expiry is set within plus or minus 30% of this value. This implies that, with a default setting of 2160 minutes (36 hours), the actual expiry will be within 1 or 2 days of the connection being establised. A value of 0 indicates that no limit should be enforced by the server. Note: Client applications are not affected by this connection loss. |
0 (no expiry time) Any positive integer |
|
|
|
Session expiry for SNC Minimum amount of time, in minutes, before connections held by the |
0 (no expiry time) Any positive integer |
|
|
|
A lists of supported Internet standards and related technologies, enclosed in curly braces |
|
|
|
|
Statistics logging: user sessions 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 ( |
|
|
|
|
Allow SyncML MD5 authenication Determines whether SyncML MD5 authentication is allowed. When set to When set to See Also: |
|
|
|
|
Discover if SyncML MD5 authentication is available At server startup, automatically discover from Oracle Internet Directory if the SyncML MD5 authentication feature is available. Once discovered, the value of the This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Specify SyncML credentials label for authentication Determines the default credentials label to use for SyncML authentication. See Also: [ENG] syncml_basicauthcredlabel, [ENG] syncml_authcredlabel_auto |
|
|
|
|
Specify SyncML credentials label for basic authentication Determines the default credentials label to use for basic SyncML authentication. If a value is not assigned to this parameter, the server will use the value assigned to [ENG] syncml_authcredlabel. See Also: [ENG] syncml_authcredlabel, [ENG] syncml_md5authcredlabel |
|
None |
|
|
Specify SyncML credentials label for MD5 authentication Determines the default credentials label to use for MD5, challenge-response SyncML authentication. If a value is not assigned to this parameter, the server will use the value assigned to [ENG] syncml_authcredlabel See Also: [ENG] syncml_authcredlabel, [ENG] syncml_basicauthcredlabel |
|
|
|
|
Maximum number of items to search Specifies the maximum number of items (users or resources) the Oracle Calendar server searches through before ending a search and returning the results to the client. |
Any positive integer up to a maximum value of (232-1) |
232-1 |
|
|
Maximum number of items to return 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. |
Any positive integer up to a maximum value of (232-1) |
232-1 |
|
|
Enable conversion of data to UTF-8 format Determines whether input data from the clients is converted and stored in UTF-8 format by the server. Caution: Setting this parameter to |
|
|
|
|
Logging of failure to instantiate UTF-8 conversion functionality Determines whether an error message is logged to |
|
|
Table 3-10 unison.ini configuration parameters - [LOG] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Maximum age before deleting log files from the attic Specify the the maximum age of any log file in the attic before it is permanently deleted. The age of the log file is determined by its timestamp. A full set of logs will always remain in the attic. Setting this parameter to 0 will disable the option. |
A positive integer
|
|
|
|
Maximum size of the attic before files are deleted Specify the maximum size, in Megabytes, of the attic directory before logs are deleted. Logs are deleted based on their age. The oldest file, based on the timestamp, will be the first to be deleted. |
A positive integer |
|
|
|
Enable log rotation feature Determines whether the log rotation feature is enabled. When enabled, log files residing in the $ORACLE_HOME/ocal/log directory are monitored and periodically rotated to the attic. For more information about the log rotation feature, see "Managing Log File Rotation" in Chapter 14 of Oracle Calendar Administrator's Guide. See also: |
|
|
|
|
Log files to ignore during log rotation Specify the files to ignore when rotating the logs. Example:
In this example, the act.log and stats.log will not be moved to the attic, regardless of their age, or size. Note: As the |
A list of strings, separated by commas and enclosed in |
|
|
|
Time to rotate logs Specify the time, in 24 hour format, that log files should be rotated. Example:
In this example, logs are rotated at 3:30 am. See Also: |
A valid time, in a 24 hour format (HH:MM, where HH is from 00 to 23, and MM is from 00 to 59) |
|
|
|
Day to rotate logs Specify the day that log files should be rotated. The day can be specified by a character string representing a day of the week, or by an integer representing a date in the month. When specifying a character string representing a day of the week, logs will be rotated on a weekly basis. When specifying a positive integer, logs will be rotated on that day, on a monthly basis. Notes: Abbreviations are ignored when specifying days of the week: If the integer specified falls within the acceptable range but does not exist in that month, the last calendar day of the month will be used. |
A positive integer equal to or between
|
|
|
|
Maximum size before a log file is moved to the attic Specify the maximum size, in Megabytes, of any log file in |
A positive integer
|
|
Table 3-11 unison.ini configuration parameters - [NOTIFY] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Short Message Service (SMS) alert Determines whether Short Message Service alerts are enabled. For more information about the available alert services, see "About Calendar Alerts" in Chapter 13 of Oracle Calendar Administrator's Guide. |
|
|
|
|
Discover if alerts are enabled At server startup, automatically discover if Alerts are enabled. This applies to Oracle Collaboration Suite deployments only. See Also: [NOTIFY] alert_sms, [NOTIFY] alert_url |
|
|
|
|
Specify the URL for the Oracle Mobile Collaboration PIM Notification Dispatcher Identify the URL, including host, port and protocol version for the Oracle Mobile Collaboration PIM Notification Dispatcher. This applies to Oracle Collaboration Suite deployments only. Notes: The protocol version specified can be either 1 or 2. A protocol version set to 1 implies that the Oracle Calendar server will be sending alerts to a Oracle Mobile Collaboration PIM Notification Dispatcher with a version inferior to this Oracle Collaboration Suite deployment. A protocol version set to 2 implies that the Oracle Calendar server will be sending alerts to a Oracle Mobile Collaboration PIM Notification Dispatcher of the same version. |
(where <hostname>, <port> and <protocolversion> are values specific to the deployment) Example: alert_url = x-oracle-calendarNotificationListener://myhost.domain.com:9000?protocolVersion=2 |
None |
|
|
Discover the URL for the Oracle Mobile Collaboration PIM Notification Dispatcher Determines whether the Oracle Calendar server will automatically discover the information required to invoke the Oracle Mobile Collaboration PIM Notification Dispatcher. When set to This discovery is done at server start up, and as such will not take effect until the server is stopped and restarted. This applies to Oracle Collaboration Suite deployments only. See Also: [NOTIFY] alert_sms, [NOTIFY] alert_url |
|
|
|
|
Interval between checks for reminders Determines the interval, in minutes, that the CWS daemon/service waits between checks for reminders. |
A positive integer |
|
|
|
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 |
|
|
|
Maximum time to check a node for reminders 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 |
|
Table 3-12 unison.ini configuration parameters - [OEM] section
Table 3-13 unison.ini configuration parameters - [PROVISIONING] section
Table 3-14 unison.ini configuration parameters - [SNC] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Automatic start of the SNC daemon/service Determines whether Note: This parameter applies to Oracle Calendar standalone deployments only. |
|
|
|
|
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 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 |
(UNIX) A positive integer up to the maximum imposed by the following equation: <flimit> - <#nodes> - 5 - where:
|
(UNIX) <flimit> - <#nodes> - 5 - (Windows)
|
|
|
SNC daemon/service port number Determines the port to use for incoming SNC network connections. This parameter is useful if there are multiple instances of an Oracle Calendar server installed on the same machine. |
A valid port number |
Value entered at installation (usually |
|
|
Number of requests that are reset at a time 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 |
|
|
|
Determines whether or not the system keeps idle connections active. If this parameter is set to If this parameter is set to |
|
|
|
|
Size of the socket layer receive buffer Specifies the size, in bytes, of the socket layer receive buffer. Do not change this value without first consulting Oracle Support. |
A positive integer |
|
|
|
Size of the socket layer send buffer Specifies the size, in bytes, of the socket layer send buffer. Do not change this value without first consulting Oracle Support. |
A positive integer |
|
|
|
Specifies the block size, in bytes, to use for communications between a |
A positive integer |
|
|
|
Time out for received transmissions Specifies the time out value, in seconds, for received transmissions. |
A positive integer |
|
|
|
Time out for sent transmissions Specifies the time out value, in seconds, for sent transmissions. |
A positive integer |
|
|
|
Number of minutes to wait for remote node connection Specifies the number of minutes to wait if the SNC daemon/service is not able to connect to a remote node. |
A positive integer |
|
Table 3-15 unison.ini configuration parameters - [SYS] section
Table 3-16 unison.ini configuration parameters - [TIMEZONE] section
Table 3-17 unison.ini configuration parameters - [UTL] section
Table 3-18 unison.ini configuration parameters - [<YOURHOSTNAME>, unidas] section
Table 3-19 unison.ini configuration parameters - [<YOURNODEID>] section
Table 3-20 unison.ini configuration parameters - [DAS] section
Table 3-21 unison.ini configuration parameters - [LDAP] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Location of the Oracle Calendar server administrators Specifies part of the LDAP directory Distinguished Name (DN) of the location under which Oracle Calendar server administrators will be created. The DN of this location is constructed by appending the value of the This parameter only applies when using an directory server other than the Oracle Internet Directory. It is used when a node is added to determine where to put the node SYSOP. |
A valid Distinguished Name or Relative Distinguished Name (see your LDAP directory server documentation for further information on the correct format) |
|
|
|
Calendar Instance Administrator Distiguished Name Specify the Distinguished Name of the Calendar Instance Administrator. The parameter is used for Calendar Node Administrator password validation. This applies to Oracle Collaboration Suite deployments only. Note: |
A valid Distinguished Name that refers to an existing Calendar Instance Administrator |
None |
|
|
Group entry for Oracle Calendar server administrators Specifies part of the Distinguished Name (DN) of the group entry for Oracle Calendar server administrators (the administrators are added to this group). The DN of the group entry is constructed by appending the value of the This parameter only applies when using an LDAP directory other than the Oracle Internet Directory. It is used when a new node is added to determine where to create the admin group if the group does not exist. If this parameter is changed, the utility |
A valid Relative Distinguished Name (see your LDAP directory server documentation for further information on the correct format). If the value is set to an empty string, the administrator entries will be created directly under the base DN. |
|
|
|
Calendar Application Entity Distiguished Name Specify the Distinguished Name of the Calendar Application Entity . The parameter is used by the Oracle Calendar server to access data in Oracle Internet Directory. This applies to Oracle Collaboration Suite deployments only. Note: |
A valid Distinguished Name that refers to an existing Calendar Application Entity |
None |
|
|
Name of the "address" attribute Determines the attribute name that the LDAP directory server uses for the "address" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Determines the attribute name that the LDAP directory server uses for the "alias" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"uid" |
|
|
Name of the "assistant" attribute Determines the attribute name that the LDAP directory server uses for the "assistant" attribute. If an empty string is used this attribute will not be read or written. See Also: |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Name of the "assistant-phone" attribute Determines the attribute name that the LDAP directory server uses for the "assistant-phone" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Name of the "country" attribute Determines the attribute name that the LDAP directory server uses for the "country" attribute. This parameter is associated with the office address. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "department" attribute Determines the attribute name that the LDAP directory server uses for the "department" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"departmentnumberr" |
|
|
Name of the "displayname" attribute Determines the attribute name that the LDAP directory server uses for the "displayname" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "empl-id" attribute Determines the attribute name that the LDAP directory server uses for the "empl-id" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Determines the attribute name that the LDAP directory server uses for the "fax" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "generation qualifier" attribute Determines the attribute name that the LDAP directory server uses for the "generation qualifier" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "given name" attribute Determines the attribute name that the LDAP directory server uses for the "given name" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "homephone" attribute Determines the attribute name that the LDAP directory server uses for the "homephone" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Name of the "homephone2" attribute Determines the attribute name that the LDAP directory server uses for the "homephone2" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Determines the attribute name that the LDAP directory server uses for the "I" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"middlename" |
|
|
Name of the "job-title" attribute Determines the attribute name that the LDAP directory server uses for the "job-title" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"title" |
|
|
Determines the attribute name that the LDAP directory server uses for the "mail" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Name of the "managerdn" attribute Determines the attribute name that the LDAP directory server uses for the "managerdn" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Determines the attribute name that the LDAP directory server uses for the "notes" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Name of the "office-address" attribute Determines the attribute name that the LDAP directory server uses for the "office-address" attribute. If an empty string is used this attribute will not be read or written. See Also: [LDAP] attr_officecity, attr_officepostalcode, attr_officestate, attr_country. |
Any attribute name defined in the LDAP directory server schema |
"street" |
|
|
Name of the "office-city" attribute Determines the attribute name that the LDAP directory server uses for the "office-city" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"l" (lowercase L) |
|
|
Name of the "office-building" attribute Determines the attribute name that the LDAP directory server uses for the "office-building" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"phyiscalDeliveryOfficeName" |
|
|
Name of the "office-postalcode" attribute Determines the attribute name that the LDAP directory server uses for the "office-postalcode" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"postalcode" |
|
|
Name of the "office-state" attribute Determines the attribute name that the LDAP directory server uses for the "office-state" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"st" |
|
|
Name of the "organization" attribute Determines the attribute name that the LDAP directory server uses for the "organization" attribute. If an empty string is used this attribute will not be read or written. In a standalone Oracle Calendar server installations where some of the nodes have no directory server (internal directory only), this parameter must be set to |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Determines the attribute name that the LDAP directory server uses for the "OU1" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"ou" |
|
|
Determines the attribute name that the LDAP directory server uses for the "pager" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"pager" |
|
|
Determines the attribute name that the LDAP directory server uses for the business telephone number "phone" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
"phone" |
|
|
Name of the "phone2" attribute Determines the attribute name that the LDAP directory server uses for the secondary business telephone number "phone2" attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Name of the time zone attribute Determines the attribute name that the LDAP directory server uses for the time zone attribute. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
None |
|
|
Determines the directory server attribute name that the Oracle Calendar server uses as a unique user identifier (uid). For the Oracle Internet Directory, do not change the value of this parameter unless you also change the attribute your Oracle Internet Directory uses to authenticate Single Sign-On (SSO) sign-ins. If you change that attribute on your directory server, you must change the value of this parameter. If an empty string is used this attribute will not be read or written. |
Any attribute name defined in the LDAP directory server schema |
|
|
|
Specifies a list of attributes (a "preserve list") which are not to be deleted when a calendar user is deleted (for example, when the user's calendar attributes as well as their
Any fields mapped to attributes outside of the This parameter only applies when using an LDAP directory other than the Oracle Internet Directory. |
A list of strings, separated by commas and enclosed in |
|
|
|
Distinguished Name of the subtree containing the Oracle Calendar server entries 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 format) |
Set at installation for the standalone Oracle Calendar server (value entered by the administrator). The default subscriber is used when the Oracle Internet Directory is installed. |
|
|
Distinguished Name used for anonymous connections Specifies the Distinguished Name used for anonymous connections to the LDAP directory server for read operations. Used only for standalone installations of the Oracle Calendar server. |
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct format) |
None |
|
|
Password used for anonymous connections For standalone Oracle Calendar server installations, specifies the password for the LDAP user specified by the value of the You must encrypt the password using the |
|
None |
|
Character set used by the directory server Used for Oracle Calendar server standalone installations only, this parameter indicates the character set the LDAP directory server uses. This is the character set that the Oracle Calendar server must use for data destined for the LDAP directory server. |
|
|
|
|
|
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. |
|
None |
|
|
Relative Distinguished Name for event calendars Specifies a location for event calendars in the LDAP directory relative to the Oracle Calendar server base DN (specified by the value of the If a full Distinguished Name is specified when creating a new event calendar, that value will be used and the value of this parameter will be ignored. |
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct format) |
None |
|
|
Enable support of Oracle Mail distribution lists Enable or disable support for distribution lists. Only available with the Oracle Mail Server and the Oracle Internet Directory. See also |
|
|
|
|
Enforce membership security settings for distribution lists Determines if the Oracle Calendar server should enforce distribution list view membership security settings when expanding distribution list members on behalf of a user . |
|
|
|
|
Resolve foreign members of a distribution list Determines if the Oracle Calendar server should resolve foreign members of a distribution list (DL). A foreign member is defined as somebody who does not have an Oracle mail address. When set to Enabling this parameter will slightly increase the load on the Oracle Internet Directory. |
|
FALSE |
|
|
Filter for Oracle Mail distribution list Specifies the LDAP filter used to locate an Oracle Mail distribution list. |
Any valid LDAP filter |
|
|
Location of Oracle Mail distribution lists Specifies the location where a search for a distribution list should be performed in the Oracle Internet Directory. |
Any valid DIT (Directory Information Tree) |
|
|
|
|
Enable LDAP groups for calendar Enables support for directory groups. If this parameter is set to TRUE, all directory groups that match the filter |
|
If the standalone Calendar Server is installed:
If the complete Collaboration Suite is installed:
|
|
Maximum number of member entries returned when searching for a member Specifies the maximum number of entries the server will return to a client when searching for a member of a group. The parameter |
Any positive integer |
|
|
|
Location of groups Specifies the location where a search for groups should be performed in the directory. This parameter is useful for narrowing down the search to a particular DIT (Directory Information Tree). The parameter |
Any valid DIT (Directory Information Tree) |
The value of the |
|
|
Maximum number of entries returned when searching for a group Specifies the maximum number of groups the server will return to a client when searching for a group. The parameter |
Any positive integer |
|
|
|
|
Specifies the LDAP filter the Oracle Calendar server uses when searching for groups in the directory server. The parameter 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 information, see "Using LDAP Groups and Distribution Lists" in Chapter 6 of Oracle Calendar Administrator's Guide. |
Any valid filter, up to a maximum length of 150 characters |
Critical Path's InJoin:
Others:
|
|
|
List of group membership attributes Specifies a list of attributes that store group membership information. This list of attributes will be passed to the directory server when searching for a group. The values of these attributes should contain information about the members. The parameter To enable dynamic group support, simply add an attribute that contains the URL. Ex: Netscape:
Other:
Custom attributes can also be specified. The value however must be of type dn string or LDAP URL. |
A list of valid LDAP attributes (dn string or LDAP URL) |
|
|
|
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 Oracle 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 separated by a blank space, in the form
|
None |
|
|
Distinguished Name of the directory server administrator Specifies the Distinguished Name of the LDAP directory server administrator. This applies to a standalone installation of the Oracle Calendar server only. |
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct format) |
None |
|
|
Port number of the LDAP directory server Specifies the port number of the LDAP directory server. If the |
A valid port number |
|
|
|
Relative Distinguished Name for resources Specifies a location for resources in the LDAP directory relative to the Oracle Calendar server base DN (specified by the value of the 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 ignored. |
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct format) |
None |
|
|
Port to use for SSL connections Determines the port to use for SSL connections to the directory server. This parameter is only checked if |
Any value in the range 1 to 65535 |
|
|
|
Enables SSL connections to the LDAP directory server. |
|
|
|
|
Maximum time to wait on an LDAP search call Specifies the maximum time, in seconds, that the server waits on an LDAP search call before returning a timeout error to the client. The timeout settings in the directory server take precedence over this parameter. Note: The Oracle Calendar server must be restarted in order for this value to take effect. |
A value of |
|
|
|
Distinguished Name used for write operations Specifies the Distinguished Name the Oracle Calendar server uses for all write operations on the directory server. See Also: |
A valid Distinguished Name (see your LDAP directory server documentation for further information on the correct format). |
None |
|
|
Specifies the password for the LDAP user specified by the value of the You must encrypt the password using the See Also: |
|
None |
Table 3-22 unison.ini configuration parameters - [CLIENT] section
Table 3-23 unison.ini configuration parameters - [CONFERENCING] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Enable the acting host key feature Control whether the acting host key feature for Oracle Real-Time Collaboration Web Conferencing is enabled. If this parameter is set to This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Discover if the acting host key feature is enabled At server startup, automatically discover from Real-Time Collaboration if the acting host hey feature is enabled. When enabled, the value discovered will be assigned to the This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Allow users to modify a Web Conference up until the scheduled end time Determines whether users can modify a Real-Time Collaboration Web Conference until the scheduled start time or the end time. When set to When set to This applies to Oracle Collaboration Suite deployments only. See Also: |
starttime (allow Web Conferences to be modified until the scheduled start time) |
|
|
|
Discover Web Conference modification restrictions At server startup, automatically discover from Real-Time Collaboration whether Web Conferences can be modified only before the starttime, or before the endtime of the scheduled Web Conference. When enabled, the value discovered will be assigned to the This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Allow external attendees to attend public or regular web conferences. Specifies whether external, non Oracle Internet Directory users can be invited to public or regular Web Conferences from a Calendar event. When set to When set to Note: Oracle recommends that the Calendar See Also: For more information about the Web Conferencing |
|
|
|
Redirecting Oracle Web Conferencing URLs Specifies the base URL to use to replace the base URL of the join URL provided by the Oracle Web Conferencing console of Oracle Real-Time Collaboration when a meeting is created. See Also: |
A base URL of the following format: Protocol: HTTP or HTTPS Hostname: hostname value (default = localhost) Port: port value (HTTP default = 80, HTTPS default = 443) If a path is supplied, it is ignored. Examples: HTTP://localhost:80/ HTTPS://myhost.com:7815 |
|
|
|
Disable Oracle Real-Time Collaboration Web Conferencing Notification Specifies whether or not Oracle Web Conferencing sends e-mail notifications of changes made to meetings by Calendar client applications. This parameter applies to Oracle Connector for Outlook only. |
|
|
|
|
Enable Oracle Real-Time Collaboration Web Conferencing for Calendar Enables and disables calendar integration to Oracle Web Conferencing. This parameter can only be set to TRUE if the complete Collaboration Suite has been installed and the Oracle Web Conferencing server enabled. See Also: |
|
If Oracle Calendar server standalone is installed:
If the complete Collaboration Suite is installed:
|
|
|
Discover if Oracle Real-Time Collaboration Web Conferencing is enabled At server startup, automatically discover if Oracle Real-Time Collaboration Web Conferencing is enabled. This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Real-Time Collaboration Web Conferencing account password Specifies the password for the Web Conferencing account used by Oracle Calendar server to access Oracle Web Conferencing. The site ID is specified by the value of the You must encrypt the password using the 1. Cut the first 148 characters in the key and assign that portion to the 2. Assign the subsequent 148 characters to the 3. Continue assigning up to 148 characters until the nth value of The Example: After using siteauthkey=<first148characters> siteauthkey.2=<second148characters> siteauthkey.3=<third148characters> siteauthkey.4=<last27characters> Note: The above example assumes that the values assigned to each parameter include the encryption method. For more information on locating the key value in Oracle Real-Time Collaboration, refer to Chapter 8, "Oracle Real-Time Collaboration Sites" of the Oracle Real-Time Collaboration Administrator's Guide. See Also: |
|
None |
|
|
Discover Real-Time Collaboration key At server startup, automatically discover from Oracle Internet Directory the key required for the Oracle Calendar server to connect to Real-Time Collaboration. When this parameter is set to TRUE, the value discovered from Oracle Internet Directory will replace the value specified in [CONFERENCING] siteauthkey. This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Oracle Web Conferencing site ID Specifies the Oracle Web Conferencing site ID used by the Oracle Calendar server to access the Oracle Web Conferencing Server. See Also: |
Valid Oracle Web Conferencing ID |
|
|
|
Discover Real-Time Collaboration siteid At server startup, automatically discover from Oracle Internet Directory the siteid that the Oracle Calendar server is required to provide to Oracle Real-Time Collaboration in order to exchange information and submit requests. When this parameter is set to TRUE, the value discovered from Oracle Internet Directory will replace the value specified in [CONFERENCING] siteid. This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
URL to Oracle Web Conferencing server Specifies the URL pointing to the Oracle Web Conferencing Server. The Calendar communicates with the Oracle Web Conferencing server through HTTP or HTTPS. For secure communication, an HTTPS URL should be used. |
Valid URL Example: " |
|
|
|
Discover Real-Time Collaboration url At server startup, automatically discover from Oracle Internet Directory the url that the Oracle Calendar server needs to connect to Oracle Real-Time Collaboration. When this parameter is set to TRUE, the value discovered from Oracle Internet Directory will replace the value specified in [CONFERENCING] url. This applies to Oracle Collaboration Suite deployments only. See Also: |
|
|
|
|
Wallet location for connecting to Oracle Web Conferencing Specifies the location of the wallet that the Oracle Calendar server will use when connecting to Oracle Web Conferencing when using SSL. This parameter does not need to be set if SSL is not used. |
Valid path Example: " |
|
|
|
Password of SSL Wallet for connecting to Oracle Web Conferencing server Specifies the password of the wallet that the Oracle Calendar server will use when connecting to the Web conferencing server when using SSL. You must encrypt the password using the This parameter does not need to be set if SSL is not used. |
|
|
Table 3-24 unison.ini configuration parameters - [DAS] section
Table 3-25 unison.ini configuration parameters - [ENG] section
Table 3-26 unison.ini configuration parameters - [LIMITS] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Determines the default view in which the client opens agenda windows. Applies to the Oracle Calendar Desktop Clients. |
|
|
|
|
Determines whether or not the client applications allow attachments for meetings or tasks. Applies to the Oracle Connector for Outlook, the Oracle Calendar Desktop Clients and the Oracle Calendar Web Client. |
|
|
|
|
Minimum interval for checks for new agenda entries (client-side enforcement) Determines the minimum number of minutes that a user can set as the interval between agenda refresh calls to the server (that is, between each check for new agenda entries). If this value is less than See Also: [ENG] maxsessions, [CLIENT] minrefreshrate |
A positive integer up to the value of (216-1) |
|
|
|
Specify if Oracle Calendar desktop clients should use the GAL by default Determines the inital setting of the Global Address List checkbox in the Oracle Calendar desktop client. This is a default setting and can be changed by a user after the first login. For the Oracle Calendar desktop client only. |
|
|
|
|
Specify how often the the GAL should be refreshed Determines how often, in days, the Global Address List (GAL) is automatically refreshed by Oracle Connector for Outlook. For Oracle Connector for Outlook only. |
Any positive integer |
|
|
|
Maximum number of users in a group view Specifies the maximum number of calendar accounts that the client can display in a group view. Applies to the Oracle Calendar Desktop Clients. |
A positive integer up to the value of (232-1) |
|
|
|
Enable mail notification dialog box Determines whether mail notification features are enabled in the client interface. When this is disabled, Oracle Calendar desktop clients will remove access to mail message dialog boxes. This parameter only applies to the Oracle Calendar Desktop Clients. |
|
|
|
|
Determines the maximum size, in bytes, for attachments to meetings, tasks and other agenda entries. This parameter is only checked if the |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Maximum number of people in a mail notification distribution list Specifies the maximum number of users in a mail notification distribution list. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Controls password aging. The value represents the number of days that a password can exist before users are required to change it. Applies to the Oracle Calendar Desktop clients. |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Maximum number of personal address book entries Determines the maximum number of personal address book entries. This parameter applies to the Oracle Calendar Desktop clients. |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Maximum number of instances for a repeating meeting, daily note, or day event (client-side) 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 and should only be used if clients older than version 9.0.4 are used. Use the |
A positive integer |
|
|
|
Maximum lead time on a reminder Specifies the maximum number of days in advance of an event that a user can set a reminder to ring. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Maximum number of LDAP search results Determines the maximum number of entries (users, resources and event calendars) that the LDAP directory will return to the calendar clients making a search request. This parameter applies to the Oracle Connector for Outlook, the Oracle Calendar Desktop clients and the Oracle Calendar Web client. For the Oracle Connector for Outlook, this parameter will determine the maximum number of entries to display in the search results from a "Find" operation on the list of Users and Resources. 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 directory server documentation to determine what these limits are and how to configure them. |
Any positive integer up to the value of (232-1) |
|
|
|
Maximum number of open windows Determines the maximum number of windows (views) that can be opened at the same time in the user interface. Applies to the Oracle Calendar Desktop clients. |
Any positive integer up to a maximum value of (232-1) |
|
|
|
Minimum number of characters in the Surname edit box Determines the minimum number of search characters that the user must supply in the name control field when performing a directory search from the client. This limit applies to a user first name or last name and to a resource name. The default value of 0 allows a user to execute a search without limits and retrieve the complete database of users and resources. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
A positive integer up to a maximum value of (232-1) |
|
|
|
Enables and disables the use of address books. This parameter applies to the Oracle Calendar Desktop clients. |
|
|
|
|
"Previous" button in search dialogue box Determines whether the "previous" button is enabled in the search dialogue box for users and resources. This button performs the reverse operation of the This functionality is disabled when the Oracle Calendar server is connected to a directory server. This parameter applies to the Oracle Calendar Desktop clients. |
|
|
|
|
"Next" button in search dialogue box Determines whether the "next" button is enabled in the item search dialogue box for users and resources of the calendar clients. When a search is performed, the This functionality is disabled when the server is connected to a directory server. This parameter applies to the Oracle Calendar Desktop clients. |
|
|
|
|
Determines whether users holding the necessary access rights can create public groups with the clients. Only applies to the Oracle Calendar Desktop client for the Mac. |
|
|
|
|
Enable publishing of address books Enables the publishing of address books. This parameter applies to the Oracle Calendar Desktop clients for Windows and Mac. |
|
|
|
|
Double-booking resources (client-side) Determines whether the client allows users to double-book resources. In release 5.4 and older, where resource confilcts is a server wide setting, this parameter should always be set with the same value as the [ENG] allowresourceconflict parameter. This applices to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. If a per-resource confilct option is required and older clients are in use, set this parameter to TRUE so that the clients allow double-booking but the server blocks it if the resource does not allow conflicts. This allows for per-resource configuration, however, the older clients may not gracefully handle the errors returned by the server enforcement. See Also: [ENG] allowresourceconflict |
|
|
|
|
Determines whether or not to restrict information given about incorrect sign-in credentials. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
|
|
|
|
Permission to change default time zone Determines whether the user is permitted to save time zone changes for future client sessions. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
|
|
|
Maximum number of sign-in attempts Determines how many unsuccessful sign-in attempts are allowed before the client closes. Applies to the Oracle Calendar Desktop clients version 9.0.4 or greater only. |
An integer between 1 and 232 |
|
|
|
|
Disables the client's Different Local Storage dialog. If this parameter is set to |
|
|
|
|
Determines whether a user can use the desktop clients' automatic sign-in feature to sign in to the Oracle Calendar server without providing a password. Applies to the Oracle Calendar Desktop clients. See Also: |
|
|
|
|
Restrictions on automatic sign-in Restricts the automatic sign-in feature of desktop clients to secure operating systems. When set to See Also: |
|
|
|
|
Show multiple user matches on sign-in Determines whether or not to show a list of matching users when more than one fits the specified sign-in credentials. Applies to the Oracle Calendar Desktop clients and the Oracle Calendar Web client. |
|
FALSE |
Table 3-27 unison.ini configuration parameters - [OUTLOOK_CONNECTOR] section
Table 3-28 unison.ini configuration parameters - [QUOTA] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Maximum number of entries in a folder Determines the maximum number of entries permitted by the server in a user's personal address book. Note: This limit is only enforced when See Also: For more information about managing the maximum number of entries when Oracle Calendar is deployed with Oracle Collaboration Suite, see "Managing Oracle Contacts Maximum Entries" in Chapter 5 of Oracle Collaboration Suite Administrator's Guide. |
A positive integer up to a maximum value of (232-1) |
|
Table 3-29 unison.ini configuration parameters - [RESOURCE_APPROVAL] section
Table 3-30 unison.ini configuration parameters - [URL] section
Table 3-31 unison.ini configuration parameters - [UTL] section
Table 3-32 unison.ini configuration parameters - [<YOURNODEID>] section
Table 3-33 unison.ini configuration parameters - [ACE] section
Table 3-34 unison.ini configuration parameters - [ACE_PLUGINS] section
| Parameter | Description | Accepted Values | Default Value |
|---|---|---|---|
|
|
Kerberos 5 Service Principal Specifies the Kerberos 5 principal name, as defined on the Kerberos server. This parameter is used when Kerberos 5 is being used as an authentication method to the Oracle Calendar server. For more information on Kerberos 5 with Calendar see, "Calendar Security" in Appendix C of Oracle Calendar Administrator's Guide. |
A valid Kerberos 5 principal name |
|
Table 3-35 unison.ini configuration parameters - [ACE_PLUGINS_CLIENT] section
Table 3-36 unison.ini configuration parameters - [ACE_PLUGINS_SERVER] section
Table 3-37 unison.ini configuration parameters - [AUTHENTICATION] section
Table 3-38 unison.ini configuration parameters - [COMPRESSION] section
Table 3-39 unison.ini configuration parameters - [ENCRYPTION] section
Table 3-40 unison.ini configuration parameters - [ENG] section
Table 3-41 unison.ini configuration parameters - [LCK] section
Table 3-42 unison.ini configuration parameters - [LIMITS] section
Table 3-43 unison.ini configuration parameters - [YOURNODEID] section
