Enables server-side logging.

Default is 0 (off).

This property is not used.

This property is not used.

This property is not used.

Delimiter used to separate multiple repository root directories in si.repositoryRoot property.

Default is a comma; otherwise, server uses delimiter specified by you. Spaces not valid delimiters.

Root directories user starts reading repository from.

Default not set.

Specifies whether client is allowed to browse repository.

Default is true.

Default value for given property used by all caches in Integrity Lifecycle Manager server (server or proxy).

Default value for given property used by all proxy caches in Integrity Lifecycle Manager server.

Default value for given property used only by server cache.

Value for given property used by specified proxied server (defined by <alias>).

Maximum memory use for proxy and server bulk data cache. Cache size in kilobytes (k/K), megabytes (m/M), or gigabytes (g/G).

Default is 30M.

Disk hard limit of bulk data cache for software configuration management (server and proxy). The size is specified in megabytes, and must be as large or greater than the value specified for the matching bulkMemSize property. For example, 1000M. Any attempt to add more data to the bulk data cache (that would increase it to be larger than this size) results in a pause while the system waits for content to be removed from the bulk data cache.

The default value is 0, denoting no hard limit.

Disk space allocated to bulk data cache for proxy and server. Cache size in kilobytes (k/K), megabytes (m/M), or gigabytes (g/G).

Default is 25G.

Value should be larger than largest member revision added to archive through Add Member or Checkin commands.

Location of bulk data cache for proxy and server.

The default location is installdir/server/mks/bulk for the server bulkdata cache and installdir/server/mks/<proxyalias>/bulk for proxy bulkdata caches.

You should specify an absolute path.

Maximum memory use for proxy and server cache. Cache size in kilobytes (k/K), megabytes (m/M), or gigabytes (g/G).

Default is 16M. Maximum is 2G/2048M.

Location of metadata cache for proxy.

The default location is installdir/server/mks/<proxyalias>/metadata.

You should specify an absolute path.

Sets high and low marks for journal of events.Integrity Lifecycle Manager server maintains journal of all events to allow for bringing clients and proxies back in sync after disconnect or server reboot. Higher number of journal entries allows longer outage without having to completely clear client or proxy cache.

Defaults are:

Client sync limit. Client caches are cleared when a client reconnects after an outage exceeds this limit. Default is 20000.

Maximum number of users for parallel cache feeds. Default is 30.

Number of events in the event queue that cause a warning to be logged.

Number of events in the event queue that cause the client or proxy to be disconnected.

Defaults for propagating events to client:

Defaults for propagating events to proxy:

Time interval between warnings messages if the queue stays above the warning limit for a period of time.

Default in seconds: 60

If true, causes Integrity Lifecycle Manager to filter the Registered Projects list and display only those users who have permission to open it for the proxy and server. If false, does not filter the Registered Projects list for proxy and server. Default is false.

If true, causes Integrity Lifecycle Manager to filter the Registered Projects list and display only those users who have permission to open it on the specified target server. If false, does not filter Registered Projects list on specified target server.

Default is false.

If true, allows proxy to automatically download bulk data for newly checked-in revisions or added members. If false, bulk data for new revisions not automatically downloaded by proxy.

Default is true.

Specifies whether bulk data for newly checked-in revisions or added members should be automatically downloaded, and overrides default behavior for specific alias.

Default is true.

Controls the resolution of archive-level permissions in the Access Control List (ACL) system.

If true, the FetchRevision permission is controlled at the archive-level.

If false, the server skips the archive-level ACL permission checks and relies on the parent project-level permission.

Default is true.

User name to use when communicating with the workflows and documents server.

Some configuration management operations (for example, change packages) need to communicate with the workflows and documents server.

Password to use when communicating with the workflows and documents server.

Some configuration management operations (for example, change packages) need to communicate with the workflows and documents server.

Name of server used for Integrity Lifecycle Manager workflows and documents.

Some configuration management operations (for example, change packages) need to communicate with the workflows and documents server.

Port of server used for Integrity Lifecycle Manager workflows and documents.

Some configuration management operations (for example, change packages) need to communicate with the workflows and documents server.

Default is listen port of the current server.

Name of the anonymous user in the read-only Web interface. If a user name is specified, that user name (and associated password) is used instead of querying for credentials.

Name of the anonymous user password in the read-only Web interface. If a user name is specified, that user name (and associated password) is used instead of querying for credentials.

Enables Staging and Deploy.

Default is false.

Directory tree used to store all Staging and Deploy application data on the server.

Default is server/mks/sd.

Maximum number of objects to display when performing a search by name for members or subprojects, or when displaying projects that a revision is the member revision in. Default is 5000.

Users can further limit the number of objects displayed when performing a search by name by entering a value in the Number of results field when performing the search.

If you want to vault files that are marked as Store By Reference, set this property to True.

You can configure the file vault location with this property.

Bypass the configuration management file vault sanity check on server startup by setting this property to True. For more information on file vaulting, see File Vaulting for Configuration Management.