Specifies additional characters that are considered part of a search token when breaking up a text search string. This property applies only for Integrity Lifecycle Manager servers that are running on an Oracle database.

If you specify additional characters here, they must be supported by the database lexer (or word breaker) of the underlying Oracle database.

The following characters are ignored if specified in this policy:

The default value of this policy is:

This localization property allows the administrator to set the locale code for which translations are required. The locale code value is a semicolon (;) separated list of supported locales. When the property is set for a locale, it indicates that administrative operations such as create, edit, and view can be performed in that locale for the display name and description attributes of the administrative objects for Fields, Test Result Fields, Types, and States. When the default value for a locale is blank, it means that the administrator does not require translations to be used, and can use any of the PTC supported locales to manage the administrative operations.

Permits you to delete admin objects on a staging server, even if that object has been migrated to the production server. By default, you may only delete admin objects if they have not been migrated to the production server.

Default is false.

Permits you to perform the following operations on a locked server:

This policy is only used if a server is configured to be a staging server. If set to true, when you launch the migration wizard, it searches for Type objects in your workflow that have been created but not yet migrated. You can then choose to not migrate State and Field overrides that refer to one or more of the Types that you select. This allows you to not be forced to migrate newly created Type objects if you want to migrate only States or Fields that reference those Type objects but not those objects themselves. After the migration, the Fields and States that had their overrides suppressed will still contain the original overrides for later migration.

Permits administrators to select specific changes to migrate using Admin Migration Wizard.

Controls the maximum number of threads available to the Integrity Lifecycle Manager server for notifying Integrity Lifecycle Manager clients about cache updates. Cache update notifications ensure that clients update their caches to reflect current data on the Integrity Lifecycle Manager server. If users report that they are not seeing current data on the Integrity Lifecycle Manager server, their clients may not have received cache update notifications yet. You may consider increasing the number of threads to improve the server's ability to handle the rate at which cache notifications are generated and sent to connected clients. Before you increase the number of threads, PTC recommends that you analyze the server statistics for the thread pool to determine if the value needs to be increased.

Default is 50.

Limit number of client connections for Integrity Lifecycle Manager to fixed limit. Setting to 0 means no restriction set.

Default is 0.

Context search indexes. Context search indexes are automatically built for text searches if underlying database supports it; however, text search queries perform differently using context search.

Default is true.

Interval for synchronizing underlying database if that database does not support automatic tracking of text field updates in context search indexes. Forces an update within specified time interval (in seconds).

Default is 30, that is, synchronization every 30 seconds. Minimum is 10 seconds.

The hostname and port for the default configuration management server. If this property is set, users are not prompted to specify a configuration management server. If this property is not set, the mksis.im.promptSourceServer property must be set to true.

Maximum number of values permitted in a field used by a grouping in a distribution chart. A larger number requires more server heap memory.

To improve the performance, a limit can be set, in bytes, for the amount of data that is returned for a document. By default, there is no limit. To set a maximum limit for a document that can be returned by a server, set this property to a specific value (for example, 10000000 for 10 MB). If this limit is exceeded, the user receives an error.

If set to true, the Web interface issues a “heartbeat” to artificially keep the HTTP session active while the browser window is open. If set to false, the HTTP session expires after the time specified in the mksis.im.httpSessionTimeout property.

Sets the timeout for the server’s global HTTP sessions. If an HTTP session remains inactive for longer than the timeout period, the session expires. Sessions associated with the Web interface can avoid this timeout if they are artificially kept active with the mksis.im.httpSessionHeartbeat property. A value of 0 effectively ignores this property and the session timeout for the Web interface becomes the server's configured value. The value is stored as seconds.

Ignores visibility rules in e-mail notifications, allowing anyone receiving e-mail notifications to see all available fields. While this option may improve server performance, it reduces security in e-mail notifications.

Sets the starting value for the first part of the revision number, known as the major revision (the number to the left of the decimal point) for item types that have been enabled for revisioning.

Valid values are 1 and 0. Default is 0.

Set this property in combination with the mksis.im.initialRevisionMinor property to form a revision number schema. Integrity Lifecycle Manager supports four revision number schemas: 0.0, 0.1, 1.0, and 1.1. The default schema is 0.1.

Each revision schema produces a unique revision pattern, as follows:

A major increment sets the first or next major revision as indicated in bold. A minor increment sets the first or next minor revision in the sequence.

Sets the starting value for the second part of the revision number, known as the minor revision (the number to the right of the decimal point) for item types that have been enabled for revisioning.

Valid values are 1 and 0. Default is 1.

Set this property in combination with the mksis.im.initialRevisionMajor property to form a revision number schema. For information about the supported revision schemas and the resulting revision patterns they produce, see mksis.im.initialRevisionMajor.

The time in seconds that the Integrity Lifecycle Manager server is to wait for the release of a database issue lock before timing out. This property applies only for servers that are running on an Oracle database.

The default value is 1, and the maximum value is 30. If an edit times out because of a database lock, an error message displays, indicating that the item is currently locked by another user and to try again later.

Maximum number of items that can be returned by a query in the Items view in order for the text filter to be enabled. If the number of items is greater than the threshold, the text filter is disabled.

Default is 1000.

Maximum file size (in megabytes) users can attach to item. Minimum limit for attachment size is 1 MB, while maximum limit is 250 MB.

Default is 4.

Maximum size for dashboard image in kilobytes. Minimum value is 1 KB, and maximum value is unlimited.

Default is 100.

Prevents an item backed picklist field (IBPL) from being created if it contains more than the specified number of backing items at its creation or modification. Specifying this value prevents the accidental creation of an IBPL with large numbers of entries, which can cause the server and/or clients to run low on memory.

Item number for next item submitted to database. If items have already been submitted, this number must be greater than the next item number or it gets ignored.

Default is 0.

The maximum item number is 1073741824. Keep this in mind when setting this property.

Comma-delimited list of e-mail addresses to be notified when a server lock is released.

Identifier for server when sending out e-mail notifications (that is, e-mail address to use in “From” field). Must specify to enable e-mail notifications, for example: mksis.im.notifieraddress=account@smtp1.abc.com.

Default is "Integrity".

Restricts the number of sessions a user can open at one time. This property is a global value that applies to all users and assists in managing resource allocation for the Integrity Lifecycle Manager server. For example, if you allow users to open 5 sessions at a time, a user can begin a session in the Web interface, and open 5 tabs in a browser to run a chart in each tab. You can specify a maximum of 100 connections and the default is 5.

Note the following:

Prompts users to specify a configuration management server. If a default configuration management server is set, this property should be set to false. If a default configuration management server is not set, this property must be set to true. The default configuration management server is set in mksis.im.defaultSourceServer.

Limit returned item count of query or report. Extremely large queries can demand significant memory resources from both server and client. Property governs computation and return of query, and displays a warning message along with the partial set of results if the number of items returned exceeds the specified limit. This behavior does not apply to queries that are not directly run by a run (for example, a query behind a report). In such cases, Integrity Lifecycle Manager displays an error message.

Minimum value is 100, and maximum value is unlimited.

Default is 10000.

Extremely large queries, or items with large amounts of history, or large text fields can take a lot of memory in both server and client. The full list of all items with their requested information must be constructed in memory on the server before being sent back to the client. This limits the maximum memory, in bytes, that the server can use for a given request. The actual memory usage is estimated for performance purposes. If the limit is exceeded, the user will receive an error. This applies to all requests for item information, whether viewing an individual issue, running a query, a query behind a report, or other methods.

A limit on the execution time in seconds for the running of a database query. The value 0 indicates no timeout.

The default limit on the execution time in seconds for the running of a database query. The value 0 indicates there is no default and the mksis.im.QueryTimeOut will be used.

Used to externalize and localize static reports, and specifies the languages that the report recipe will be saved as (in the database).

The property value is a semi-colon (;) separated list of languages. For example, en;de;ja;zh_CN;zh_TW;ko,fr. The list must only contain languages supported by Integrity Lifecycle Manager.

Setting languages makes the static report generate in those languages for your users, based on the locale. For example, If English and German are specified, then both English and German locale users will run the report in their locale language.

Setting this property to a blank value has the following impact:

Users with a client locale that is not specified in this property will see a report with tokens as the resource. For more information on tokens used in reports, see the documentation for localizing report recipes.

Specifies the maximum amount of memory, in bytes, that the server can use to run a report. Extremely large reports containing a lot of items in the top-level query or large text fields can consume large quantities of memory on the client and server. If the memory limit is exceeded, the user receives an error message.

Default is 10000000 bytes.

External dictionary to use for spell checking in rich content fields. Must be a valid and accessible URL (an http:// URL for a Web service, or a file:// to a UNC path of a known public share). If unspecified, the internal English spelling dictionary is used.

This property value can only be changed for the external spelling dictionary, it cannot be changed for the internal user dictionary.

Workflow SQL generation hints. The general format is a semi-colon delimited list of key=value Valid values are 1 and 0. Default is 1.

.  All hints are undocumented and should only be used on when recommended by Integrity Lifecycle Manager Technical Support.

If true, causes server to send e-mail notifications as blind carbon copies preventing recipients from viewing e-mail addresses not their own. If false, other recipients e-mail addresses appear in To field of e-mail header.

Default is false.

Specifies valid URL prefixes for hyperlinks in rich content fields. You can add URL prefixes, permitting users to include external hyperlinks to third party applications, for example, adding doors:// to allow external hyperlinks to requirements in DOORS. Similarly, you can remove URL prefixes, preventing users from clicking certain types of external hyperlinks.

Default values are http, https, mailto, file, \\, and integrity. Each value is separated by “;”.

Note the following: