22 WebCenter Sites User Defined Properties

User defined properties are properties added by WebCenter Sites users (usually administrators or developers) to the WebCenter Sites wcs_properties.json file.

The following topics provide information about user defined properties:

• About WebCenter Sites User Defined Properties

• User Defined Properties for WebCenter Sites

22.1 About WebCenter Sites User Defined Properties

WebCenter Sites user defined properties are properties that can be manually added to the WebCenter Sites wcs_properties.json file to enable optional WebCenter Sites features.

Certain WebCenter Sites features require properties that are not available in the WebCenter Sites wcs_properties.json file by default. In these cases, an administrator or developer must create the property in the wcs_properties.json file, using the Property Management Tool in the WebCenter Sites Admin interface. For example, when you implement resultset caching, you can create up to three properties for any WebCenter Sites database table for which you want to set caching values.

For information about adding properties to the WebCenter Sites wcs_properties.json file, see Adding Properties.

22.2 User Defined Properties for WebCenter Sites

The table below provides a description for each user defined property you can add to the WebCenter Sites wcs_properties.json file.

Table 22-1 WebCenter Sites User Defined Properties

Property	Description
cs.approvalLockStriping	Used to specify whether approval locking is global and default (false) or per target (true), which prevents targets from competing for approval and publishing activities. Setting this property to true requires you to add a non-null column named cs_target to the ApprovalQueue table. The column's data type must match the value of the cc.bigint property (in the WebCenter Sites wcs_properties.json file). If you wish to switch back from approval locking per target to default behavior (that is, global lock), remove the cs_target column from the ApprovalQueue table, and then set cs.approvalLockStriping to false (or remove this property, as by default it is false).
cs.invalMemWindow	This property applies to the inCache framework. It is used to define the size of the FW_InvalidationMemory table in terms of a data storage period, in seconds, for that table. The data storage period is a rolling window. For example, if the property is set to 20000, 20,000 seconds worth of data can be accumulated in the table. As additional data continues to arrive, it is stored, while data older than 20,000 seconds is purged by the table's cleanup mechanism. For more information about the inCache framework and FW_InvalidationMemory table, see Using The inCache Framework in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide. If you wish to use this property, add it to the WebCenter Sites wcs_properties.json file and set it to your required value. If the property is not added, WebCenter Sites uses the default value. Default value: 259200 (that is, 3 days)
cs.childfoldercount	Specifies the maximum number of child folders that WebCenter Sites can generate in parent folders under subdirectories of <wcs_shared>/Shared. Child folders are numbered subfolders that WebCenter Sites generates inside the parent folders. For example, if this property is set to 300, WebCenter Sites will generate no more than 300 child folders in parent folders under <wcs_shared>/Shared/ccurl. If you wish to use this property, you must add it to WebCenter Sites wcs_properties.json file. If it is not added, WebCenter Sites uses the default value. Note that when this property is used, the existing child folder structure remains as is. Child folders that are no longer used will need to be deleted manually. If you also need to specify the maximum number of parent folders that WebCenter Sites can generate, use the cs.parentfoldercount property. Default value: 1024
cs.parentfoldercount	Specifies the maximum number of parent folders that WebCenter Sites can generate in subdirectories of <wcs_shared>/Shared. Parent folders are the first level of numbered folders generated by WebCenter Sites. For example, if this property is set to 500, WebCenter Sites will generate no more than 500 parent folders in <wcs_shared>/Shared/ccurl (where flex assets are stored). If you wish to use this property, you must add it to the WebCenter Sites wcs_properties.json file. If it is not added, WebCenter Sites uses the default value. Note that when this property is used, the existing parent folder structure remains as is. Parent folders that are no longer used will need to be deleted manually. Within the parent folders, WebCenter Sites generates child folders. If you wish to specify the maximum number of child folders that can be generated, use the cs.childfoldercount property. Default value: 1024
cs.TempObjectsDaysToKeep	Used to specify the number of days that data is stored in the TempObjects table. For example, if you specify a value of 7 for this property, then any data stored in the TempObjects table that is older then 7 days is deleted by the CleanTempObjects event (which is specified in the SystemEvents table and runs everyday at midnight to remove old data from the TempObjects table). Legal value: Integer > 0 Default value: 5 Note: By default, this property is not present in the WebCenter Sites wcs_properties.json file and its value is set to 5. To change the value of this property, you must manually add this property to the WebCenter Sites wcs_properties.json file.
cc.tablenameKey	To add a key for a new table in the WebCenter Sites database, add this property to the WebCenter Sites wcs_properties.json file, where tablename is the name of the new table.
ft.servletoutputstream	Default value: false
rtd.choicIdpattern	If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this property to the WebCenter Sites wcs_properties.json file. You can use this property to configure how the RTD dynamic choice ID values are constructed. Choice ID values are used in the RTD Decision Center as choice labels for assets. A choice ID pattern ensures that each asset has a unique choice ID, an asset will not appear more than once in the Decision Center, and that users can easily locate an item (asset) in the user interface of the Decision Center. Default Value: rtd.choiceId.pattern={assettype}:{name} ({assetid} where {assettype} is the type of asset, {name} is the name of the asset, and {assetid} is the numeric ID of the asset.
rtd.host	If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this tag to the WebCenter Sites wcs_properties.json file and set the value as the URL on which Oracle RTD is running.
rtd.inline.service.name	If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this tag to the WebCenter Sites wcs_properties.json file and set the value as the name of the Oracle RTD inline service.
vis.useSessionVisitorConnection	This property determines whether Engage visitors will be tracked through the database- or memory-centric method, which improves the performance of heavily trafficked sites featuring Engage assets. In memory-centric tracking, WebCenter Sites stores visitor scalar attribute values to the add-on repository, and visitor history attribute values to its own database. All computations to determine a visitor's segments are performed in memory; results are cached. By default, this property is not automatically included in the WebCenter Sites wcs_properties.json file, in which case its value is understood to be false (that is, database-centric). This property must be set on the delivery system in one of the following ways: If you wish to enable the database-centric method, set this property to false, leave it blank, or omit it from the file. If you wish to enable the memory-centric method, set this property to true and ensure that supporting template code exists on the delivery system (in its absence, Engage visitors will be incorrectly tracked). For information about required code, see Visitor Tables (Engage) in the Oracle Fusion Middleware WebCenter Sites Developer's Guide. On content management systems, this property must be either set to false or omitted, given that visitor attributes are created and managed only on CM systems that are enabled for database-centric tracking. Management of visitor attributes is not supported on delivery systems; the attributes must be published to the delivery systems.
xcelerate.useDimensionAssets	This property is supported only on delivery systems. This property controls whether a WebCenter Sites delivery system queries the Dim and DimP database tables for Dimension assets. If you do not use Dimension assets (that is, for multilingual support), do the following to prevent your delivery system from unnecessarily querying the Dim and DimP tables: Add this property to the WebCenter Sites wcs_properties.json file and set it to false. Then, set -Dcs.disable.dimensions.in.ui for the JVM to true in the application server startup script.