Differences

This shows you the differences between two versions of the page.

Link to this comparison view

72:dimensions_config_host_prop [2018/07/25 18:53] (current)
bkkr created
Line 1: Line 1:
 +[[:​72:​dimensions_config|Dimensions Configuration]]
 +
 +====== Host-specific Properties ======
 +
 +**DatabaseName**
 +
 +   * Default Value: N/A
 +  * Description:​ The name of the Dimensions database to connect to.
 +
 +**DatabaseConnection**
 +
 +  * Default Value: N/A
 +  * Description:​ The name of the Dimensions database connection.
 +
 +**User**
 +
 +  * Default Value: N/A
 +  * Description:​ You may enter the Dimensions username for the Stages system account here instead of the corresponding field //Username //in the CMS profile. If both values exist, the username from the CMS profile is preferred.
 +
 +**Password**
 +
 +  * Default Value: N/A
 +  * Description:​ You may enter the Dimensions password for the Stages system account here instead of the corresponding field //​Password// ​ in the CMS profile. If both values exist, the password from the CMS profile is preferred.
 +
 +**Date.format**
 +
 +  * Default Value: dd-MM-yyyy and HH:mm:ss
 +  * Description:​ The localized date format Dimensions is using.
 +
 +**Date.language**
 +
 +  * Default Value: en
 +  * Description:​ The language of the localized date Dimensions is using.
 +
 +**Connection.max.wait**
 +
 +  * Default Value: 3000
 +  * Description:​ Maximum waiting time for a Dimensions connection in milliseconds.
 +
 +**Request.timeout.short**
 +
 +  * Default Value: 3000
 +  * Description:​ Maximum waiting time in milliseconds for a short-running Dimensions operation. Currently only requests for metadata (e.g. for the determination of the revision history) are considered as short-running operations. A timeout normally leads to an error message in Stages.
 +
 +**Request.timeout.long**
 +
 +  * Default Value: 120000
 +  * Description:​ Maximum waiting time in milliseconds for a longrunning Dimensions operation. Currently all modifying file operations (create, checkout, checkin, revert, change state) and file downloads are considered as long-running operations. A timeout normally leads to an error message in Stages.
 +
 +**Default.item.type**
 +
 +  * Default Value: DOC
 +  * Description:​ This type will be preselected when a new file/item is created via Stages. It will only be used when Dimensions does not provide other information which item type is appropriate with regard to the extension of the uploaded file.
 +
 +**Related.requests.required**
 +
 +  * Default Value: false
 +  * Description:​ Specifies if one ore more request ids must be entered for a modifying file operation (e.g. checkout, checkin, change state). If the value is false, entering request ids is still possible but not enforced by Stages.
 +
 +**View.baselines.enabled**
 +
 +  * Default Value: false
 +  * Description:​ Specifies if the baselines to which a Dimensions item revision belongs shall be displayed in the corresponding file revision history in Stages (column is named "​labels"​ by default). Moreover the property defines if it will be possible to filter file revisions in the Overview application by baseline.
 +      * Setting this to true will slow down many file operations in Stages.
 +