9 futuretense.ini

The futuretense.ini file is the main property file for WebCenter Sites. Its properties are organized by function on the following tabs in the Property Editor:

9.1 App Server Tab

The App Server tab holds the futuretense.ini properties that supply information to WebCenter Sites about the application server.

Table 9-1 Properties in futuretense.ini: App Server Tab

Property Description

cs.eventhost

The host string for running the event engine on application servers. In a clustered environment, this property must be set on each cluster member and point to either the primary cluster member or to the cluster member, itself. The second option provides for failover.

Legal value: http://<hostname>:<port_number>

ft.cgipath

The web server CGI directory where WebCenter Sites objects are installed.

Used in the constructions of URLs and form actions.

Be sure the value ends with a forward slash ( / ).

Possible values:

/NASApp/CS/ – when using the Sun ONE application server (iAS); the path is defined to be the path used when installing Sun ONE.

/servlet/ – in http servlet application environments (such as WebLogic).

9.2 Authentication Tab

The Authentication tab holds user authentication properties that are configured during installation based on the user manager plug-in in use on your WebCenter Sites system. Some of these properties apply no matter which user management module you are using, while others apply only if you are using NT authentication.

See also, the main configuration file for the user manager plug-ins is the dir.ini file. See Chapter 7, "dir.ini."

Table 9-2 Properties in futuretense.ini: Authentication Tab

Property Description

cs.manageACL

Specifies the class that replaces the default WebCenter Sites ACL name-to-privilege mask function.

Do not change the value of this property.

cs.manageproperty

Specifies the name of the appropriate property file that configures the LDAP plug-in or the NT authentication plug-in, depending on whether you are using either of these user manager modules.

  • For LDAP, set the value to: dir.ini

  • For NT, set the value to: futuretense.ini

cs.manageUser

Specifies which user manager plug-in to use with this WebCenter Sites system.

  • If you are using the default WebCenter Sites plug-in, the value is blank. WebCenter Sites will use database authentication and authorization.

  • If you are using LDAP, the value is: com.openmarket.directory.jndi.auth.JNDILogin

  • If you are using NT authentication, the value is: com.FutureTense.NTUserGroups.ValidateLogin.NTUserGroupsLogin

This property is set when your WebCenter Sites system is integrated with LDAP or a different external system. Do not change its value after installation. By default, the value is blank.

Note: When this property is set, the cs.manageproperty must also be set.

cs.manageUserAccess

Specifies the class that replaces the default WebCenter Sites user-to-privilege-by-resource lookup functionality.

Do not change the value of this property.

cs.manageUserSystem

Applies only when your WebCenter Sites system is using NT authentication (that is, cs.manageUser points to the NT plug-in).

Specifies a comma-separated list of NT domain names that WebCenter Sites uses to authenticate users.

Authentication is done in the order specified by the list of domains. A user is declared a valid user if his username/password combination is found in any of those domains.

Specify the local system with a period (.) character.

If the cs.manageUser points to the NT plug-in, but there are no domain names set for this property, WebCenter Sites attempts authentication on the local NT domain only.

This value was set during installation.

cs.ssovalidator

This property points to the SSO validator plug-in.

Given that the WEM Framework is installed by default, the default value is:

com.fatwire.wem.sso.cas.cs.plugin.SSOValidatorPlugin

ntlogin.DefaultACL

NT user manager plug-in only.

A comma-separated list of any ACLs that should be assigned to all users by default.

By default, this value is blank.

ntlogin.DefaultReaderACL

NT user manager plug-in only.

The ACL list to be assigned to the account that is used as the default reader account.

By default, this value is blank.

ntlogin.DefaultReaderID

NT user manager plug-in only.

The user name to be used as the default reader account.

By default, it is set to DefaultReader.

This value can be blank.

ntlogin.DefaultReaderPW

NT user manager plug-in only.

The password for the user name that the NT authentication module uses as the default reader account. Required if there is a value for ntlogin.DefaultReaderID.

By default, it is set to SomeReader. The value is encrypted.

ntlogin.LogFile

NT user manager plug-in only.

The complete path to the file where debug information from the NT authentication module should be written. (Used only when ntlogin.Logging is set to true.)

ntlogin.Logging

NT user manager plug-in only.

Enables or disables debugging for the NT authentication module.

Possible values: true | false

singlesignon

If set to true, enables single sign-on for an authentication plug-in that supports single sign-on.

Because the WEM Framework is installed by default, this property is set to true.

9.3 Basic Tab

The Basic tab holds the futuretense.ini properties that control such things as security settings, session timeouts, and Global Unique Identifiers that the WebCenter Sites servlets use.

Table 9-3 Properties in futuretense.ini: Basic Tab

Property Description

bs.security

Specifies whether the BlobServer servlet checks security before allowing database access and image retrieval. If security is on, images cannot be cached in memory.

If you enable BlobServer security, the BlobServer servlet serves the data only if the csblobid parameter exists in the URL and its value matches a session variable of the same name, as in the following example: <IMG SRC="BlobServer?blobtable=MovieImages&#38;blobcol=urlimage&#38;blobkey=id&#38;csblobid=SessionVariables.blobid&#38;blobwhere=25"/>

Possible values: true | false

cc.security

Specifies whether WebCenter Sites checks security before allowing database access. This property should always be set to true except in special cases.

Possible values: true | false

cs.barEqualsSlash

Specifies whether an Internet Explorer browser should interpret the bar (|) character as a forward slash (/) when it is included in a page name.

Possible values: true | false

For example, when set to true, Internet Explorer interprets pagename=folder|subfolder|page as the same page as pagename=folder/subfolder/page

Default value: false

cs.session

Specifies whether WebCenter Sites starts and maintains a browser session for each user.

Possible values: true | false

Cannot be set to false when the cc.security property is set to true.

cs.timeout

Specifies the number of seconds a connection can remain idle before the application server logs out this connection, which ends a browser session. Idle time is the time between WebCenter Sites http requests.

Default value: 300 (5 minutes)

Note: When the approval system approves assets, it is not a background process. Therefore, if you use the Approve Multiple Assets feature, be sure to set this property to a value that is greater than the amount of time it takes to approve a batch of asset so that the browser session does not time out. You will have to experiment with this setting, but you can start by setting it to 1800 seconds (30 minutes).

cs.uniqueidpoolsize

Specifies the number of unique and cluster-safe ID numbers that are cached at one time. (WebCenter Sites generates unique IDs for every row in any database table.)

Default value: 100

cs.wrapper

Deprecated. Specifies whether the WebCenter Sites HTML wrapper pages should (can) be used.

Default value: true

Set this value to false on a WebCenter Sites system in which the application server does not have HTTP access to the web server, or, if you have removed the directory that holds the wrapper pages for security reasons.

See also "Setting up External Security" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

ft.version

Specifies the version number of the WebCenter Sites application.

Do not modify this value.

secure.CatalogManager

Specifies whether the DefaultReader user can access the CatalogManager servlet.

Possible values: true | false

During installation, this property is set to false. Be sure that this value is changed to true after the installation.

For more information, see "Setting Up External Security" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

secure.DebugServer

Controls whether DefaultReader can connect to the specified servlet when security is on. If set to true, DefaultReader cannot connect.

Possible values: true | false

secure.TreeManager

Specifies whether the DefaultReader user can access the TreeManager servlet.

Default value: true

For more information, see "Setting Up External Security" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

9.4 Blob Server Tab

The BlobServer tab holds properties that configure the BlobServer servlet. BlobServer serves blobs. It gathers a blob from a table and performs all the necessary security checks. When BlobServer serves a blob, it caches it in both WebCenter Sites and Satellite Server.

Table 9-4 Properties in futuretense.ini: Blob Server Tab

Property Description

bs.bCacheSize

Specifies the default number of blobs that can be cached (to memory).

Default value: 100

bs.bCacheTimeout

Specifies the number of seconds that a blob will remain cached in memory. Note that the memory cache is cleared whenever the BlobServer servlet is restarted.

This property affects the operation of CacheManager as follows:

When compositional dependencies are recorded against a blob in the SystemItemCache table, they are configured such that they will be removed from the table after the blob expires from the cache. This prevents excessive growth of the SystemItemCache table. However, removing the entry from the table disables CacheManager from removing the corresponding blobs from the Tier 2 cache, and users will view stale data.

Possible values: negative integer, 0, positive integer

Default value: -1

The blob will remain cached in memory forever, unless it is evicted because more recently used blobs have filled the cache.

Note: The value of this property affects cs.manage.expired.blob.inventory as follows:

  • A value of 0 or less causes cs.manage.expired.blob.inventory to have no effect.

  • A positive integer with cs.manage.expired.blob.inventory set to true ensures that CacheManager operates correctly, but at the cost of growth in the SystemItemCache table.

For more information, see cs.manage.expired.blob.inventory.

bs.invalidheadernames

Comma separated list of invalid headers which are ignored by BlobServer.

Default value: Set-Cookie

Note: If headers are specified as both valid (bs.validheadernames) and invalid (bs.invalidheadernames), the headers specified in bs.validheadernames take precedence.

For more information, see bs.validheadernames.

bs.validheadernames

Comma separated list of valid headers which are allowed by BlobServer.

Note: If headers are specified as both valid (bs.validheadernames) and invalid (bs.invalidheadernames), the headers specified in bs.validheadernames take precedence.

For more information, see bs.invalidheadernames.

cs.recordBlobInventory

Specifies whether compositional dependencies should be recorded against blobs. This property must be set to true (the default) for CacheManager to operate on blobs.

Possible values: true|false

Default value: true

9.5 Cluster Tab

The Cluster tab holds the properties that WebCenter Sites uses to communicate with all the servers in a cluster when a WebCenter Sites system is installed in a cluster.

Table 9-5 Properties in futuretense.ini: Cluster Tab

Property Description

cc.cacheNoSync

Specifies whether the system allows the database query transaction data cached by WebCenter Sites to persist even if a cluster member updates the table.

Default value: false

You can set table-specific values for individual tables by adding a property in the following format:

cc.<sometable>CSync=<true or false>

ft.sync

An identifier or value that defines the synchronizer key for clustered servers; for example, the DSN that cluster members use for their shared database. Each cluster member must have the same ft.sync value.

When set to true or yes, sync is enabled and extra asset-level locking is in effect. This mode is intended for clustered editorial systems, as it uses an asset-locking mechanism designed for frequent changes to assets.

When set to a value other than true or yes, sync is enabled but extra asset-level locking is not in effect. This mode is intended for clustered delivery systems, as it enables an asset-locking mechanism designed for infrequent changes to assets.

Note: Oracle recommends that you specify a value for ft.sync.

Legal values: <string> | <blank>

ft.usedisksync

Specifies a shared file system folder to synchronize data across a cluster.

Set this property to a valid folder when synchronization is turned on with the ft.sync property. For example, set it to a directory where you have read/write access.

9.6 Compatibility Tab

The Compatibility tab holds properties that set values necessary for backward compatibility with earlier versions of WebCenter Sites.

Table 9-6 Properties in futuretense.ini: Compatibility Tab

Property Description

cs.cookievariables

Specifies if cookie variables should be created for servlet request information.

Generating cookie variables can confuse page criteria for page requests and works only for outer pages.

Legal value: false

cs.dataindatabase

Specifies whether large data should be saved in the database or in the file system as an upload column.

cs.httpvariables

Deprecated.

Specifies whether the WebCenter Sites variables that contain HTTP header information are created on each page request, as was necessary in pre-4.0 versions of the product. Starting with 4.0, FatWire Content Server provides built-in variables that perform the same function.

Default values: false

For best performance, leave this value set to false. If developers need to retrieve an http variable for a site page, they can retrieve the value of the ones they need by using the built-in variables.

cs.satellitehosts

Specifies the host names of the servers that are hosting Satellite servlets that the CacheManager on this server (the one that hosts WebCenter Sites) needs to communicate with.

Enter a comma-separated list of host names. The value for each host must include the path to the WebCenter Sites servlets.

Use the following format:

http://<hostname:port>/<servlet>/

You can use https or special ports, if necessary. If required by your configuration, be sure to specify a fully-qualified domain name.

The Satellite servlet that resides on this server is listed by default.

cs.satellitepassword

Specifies the passwords for the user accounts specified by the cs.satelliteusers property. Note that the password for the Satellite servlet on this server is listed by default.

The value of this property is encrypted as a single string. Therefore, when you edit the value of this property, you must enter all the passwords for all the Satellite servlet hosts, including the comma delimiter.

Enter a comma-separated list of passwords in the order that matches the order in which you enter the corresponding users for the cs.satelliteusers property. Be sure that the order of this list also matches the order of the list of host names provided for the cs.satellitehosts property.

cs.satelliteusers

Specifies the user names for the Satellite Server hosts. Note that the user name for the Satellite servlet on this server is listed by default.

Enter a comma-separated list of user names in the order that matches the list of passwords that you specified for the cs.satellitepassword property.

cs.selfmodify

Specifies a comma-separated list of attributes that a user is allowed to modify.

Currently, only password is supported.

For complete backward compatibility, set the property to blank to ensure that the user has write privileges to the SystemUsers table.

cs.xmlHeaderAutoStream

Tells WebCenter Sites whether it should stream the XML header as defined in the property cs.xmlHeader as the first content of the response, automatically, or not.

If this property is set to true, then WebCenter Sites will automatically insert the header into the response. If it is set to false, then WebCenter Sites will not do anything. If the response is not a SOAP response, this property is ignored entirely and the header is never inserted.

Default value: false

ft.approot

Deprecated.

This property is no longer used. In some cases, it may be required for backward compatibility.

ft.catalogmanager

Defines the Global Unique Identifier (GUID) for the CatalogManager service. It is provided for reference only.

Default value: {40DD4E30-8DE2-11D1-8599-0080C7D07E91}

Do not modify this value.

ft.contentserver

Defines the GUID for the ContentServer servlet. It is provided for reference only.

Default value: {29434AD0-8DE2-11D1-8599-0080C7D07E91}

Do not modify this value.

ft.treemanager

Defines the GUID for the Treemanager servlet.

Do not modify this value.

security.checkpagelets

Specifies whether WebCenter Sites checks security before allowing a user to view a pagelet that is nested in an enclosing page.

Note that the cc.security property must also be set to true for security to be implemented.

Default value: true

If set to false, the following occurs:

  • On systems with co-resident Satellite Server, security is not checked on any pages or pagelets, even with cc.security set to true.

  • On systems with stand-alone Satellite Server or with WebCenter Sites only, security is checked on the first or outermost page but security is not checked on nested pagelets.

9.7 Content Tables Tab

The Content Tables tab holds a property that specifies the default primary key column for all of the content tables (as opposed to object tables) in your WebCenter Sites database.

If you or your developers create any content tables to support your online sites, you can specify that a column other than the one specified by the default is the primary key column for those content tables by creating table-specific properties. Use the following format:

cc.<name of table>Key=<name of column>

For example, when WebCenter Sites installs the Category table (which is used by basic asset types), it creates a property named cc.CategoryKey. The cc.CategoryKey property and any new property that you create appears on the User Defined tab rather than the Content Tables tab.

Caution:

Do not change the key value specified for any of the WebCenter Sites content tables.

Table 9-7 describes the property in the Content Tables tab:

Table 9-7 Properties in futuretense.ini: Content Tables Tab

Property Descriptions

cc.contentkey

Specifies the name of the column that serves as the primary key for content tables in the WebCenter Sites database. This is a default setting that applies to any content table that does not have a table-specific property that sets a different primary key for it.Value set during installation of the WebCenter Sites content applications: id

Caution: Do not change the value of this property. If you change it, the WebCenter Sites content applications will not function. To specify a different primary key for an individual content table, create a table-specific key property as described in the paragraphs preceding this table.

9.8 Database Tab

The Database tab holds both the general database configuration properties such as database name and user access properties, and vendor-specific properties such as how the database interprets date/time values.

Database properties must be set to the same values on each of the systems in your WebCenter Sites system—development, management, and delivery—so that you can move assets and other work from one system to another.

Note:

Database properties are set during the WebCenter Sites installation process. If you need assistance with determining property values or setting them during the installation process, contact Oracle Technical Support. Do not change the values of these properties after WebCenter Sites is installed.

If you are unsure about how property values were determined, check with your database administrator or the individual who installed WebCenter Sites.

Table 9-8 Properties in futuretense.ini: Database Tab

Property Descriptions

cc.bigint

Specifies the SQL string for defining a 64-bit integer field.

Possible values:

  • Oracle: NUMBER(38)

  • SQL Server: BIGINT

  • DB2: BIGINT

See also the note above this table.

cc.bigtext

Specifies the SQL string for defining a large text field.

Possible values:

  • Oracle: CLOB

  • SQL Server: TEXT

  • DB2: LONG VARCHAR

See also the note above this table.

cc.blob

Specifies the SQL string for defining a BLOB (binary large object) field.

Possible values:

  • Oracle: BLOB

  • SQL Server: IMAGE

  • DB2: LONG VARCHAR FOR BIT DATA

See also the note above this table.

cc.char

Specifies the SQL string for defining a CHAR data type.

Possible values:

  • Oracle: CHAR

  • SQL Server: CHAR

  • SQL Server, multi-lingual Unicode: NCHAR

  • DB2: CHAR

See also the note above this table.

cc.datepicture

Specifies how WebCenter Sites creates a date/time literal.

Default values: {ts '$date'}

See also the note above this table.

cc.datetime

Specifies the SQL string for defining a date/time field.

Possible values:

  • Oracle 8: DATE

  • Oracle 9: TIMESTAMP

  • SQL Server: DATETIME

  • DB2: TIMESTAMP

See also the note above this table.

cc.double

Specifies the SQL string for defining a double field.

Possible values:

  • Oracle: NUMBER(38,10)

  • SQL Server: NUMERIC(28,10)

  • DB2: FLOAT

See also the note above this table.

cc.forcelower

Specifies whether the column names for the tables that WebCenter Sites creates have all lowercase letters.

Possible values:

  • Oracle: true

  • SQL Server: false

  • DB2: true

See also the note above this table.

cc.ignoreTblCase

Determines whether WebCenter Sites ignores case when assessing table names.

Possible values:

yes | no

For example, if "tablename" and "TABLENAME" would be considered different tables in your database, set this value to no.

Possible values:

  • Oracle: yes

  • SQL Server: yes

  • DB2: yes

See also the note above this table.

cc.integer

Specifies the SQL string for defining a 32-bit integer field.

Possible values:

  • Oracle: NUMBER(10)

  • SQL Server: INT

  • DB2: INTEGER

See also the note above this table.

cc.maxvarcharsize

Specifies the maximum size of a varchar column for your database.

Possible values:

  • Oracle: 2000

  • SQL Server: 8000

  • DB2: 4000

See also the note above this table.

cc.null

Specifies the SQL string for defining a field which allows NULL values; this is nonstandard, though most databases support NULL.

Possible values:

  • Oracle: NULL

  • SQL Server: NULL

  • DB2: blank

See also the note above this table.

cc.numeric

Specifies the SQL string for defining a numeric field.

Possible values:

  • Oracle: NUMBER

  • SQL Server: NUMERIC

  • DB2: NUMERIC

See also the note above this table.

cc.primary

Specifies the SQL string that defines a primary key.

Possible values:

  • Oracle: PRIMARY KEY NOT NULL

  • SQL Server: PRIMARY KEY NOT NULL

  • DB2: PRIMARY KEY NOT NULL

See also the note above this table.

cc.queryablemaxvarcharlength

Specifies the maximum size of a varchar column that can be queried based on the database driver in use.

  • Oracle Thin: 255

  • Oracle TypeII: 2000

  • SQL Server: 255

  • DB2: 255

cc.rename

Specifies the SQL string that renames a table in the database, as required by your database vendor.

Possible values:

  • Oracle: rename %1 to %2

  • SQL Server: execute sp_rename %1,%2

  • DB2: rename %1 to %2

See also the note above this table.

cc.smallint

Specifies the SQL string for defining a 16-bit integer field.

Possible values:

  • Oracle: NUMBER(5)

  • SQL Server: SMALLINT

  • DB2: SMALLINT

See also the note above this table.

cc.stringpicture

Specifies how WebCenter Sites creates a string literal.

Possible values:

  • Oracle: '$string'

  • SQL Server: '$string'

  • SQL Server, multi-lingual Unicode: N '$string'

  • DB2: '$string'

See also the note above this table.

cc.unique

Specifies the SQL string for defining a unique field.

Possible values:

  • Oracle: UNIQUE NOT NULL

  • SQL Server: UNIQUE NOT NULL

  • DB2: UNIQUE NOT NULL

See also the note above this table.

cc.varchar

Specifies the SQL string for defining a VARCHAR data type.

Possible values: VARCHAR, for all supported databases except SQL Server, multi-lingual Unicode which is set to NVARCHAR

See also the note above this table.

cs.dbconnpicture

Specifies the format of the database connection string used by JNDI datasources:

See also the note above this table.

cs.dbtype

Defines the type of database to which you are connecting.

See also the note above this table.

cs.dsn

Contains the database JNDI data source name for connecting to your database.

See also the note above this table.

cs.privpassword

Specifies the password for the database account name used for read/write access (cs.privuser). The value is encrypted.

cs.privuser

Specifies the database account name to use for read/write access to the database. For security reasons, be sure that your system is not using the default user name/password combination.

Possible values: ftuser (set during the installation process)

9.9 Debug Tab

Note:

For information about enabling debug logging, see Chapter 5, "commons-logging.properties." See also "Error Logging and Debugging" in the Oracle Fusion Middleware WebCenter Sites Developer's Guide.

If you enable debug logging, note the following:

  • Delete or archive the WebCenter Sites log file frequently, because a large log file can affect WebCenter Sites performance.

  • By default, all debug log messages go into a single log file, which can make debugging more difficult. To place debug messages into a separate log file, set the logging.per-client-log property to true. The property is defined in Table 5-4.

Table 9-9 Properties in futuretense.ini: Debug Tab

Property Description

ft.debugport

Deprecated. Specifies the port that DebugServer uses to communicate with the template debugger utility. The port number must be greater than 1024.

Default value: 1025

ft.suppressPasswords

Prevents any input or session variables containing the strings "password" or "PASSWORD" in their names from being logged.

Default value: true

Specify false to include passwords in the log.

ft.suppressPasswordNames

Specifies variable names that are used as passwords and should be suppressed when ft.suppressPasswords is set to true.

The Cheetah installer now sets this property to: REMOTEPASS;pubtgt:factors;factors to suppress its mirror publish target passwords in the log.

9.10 Email Tab

The Email tab holds the properties that configure the WebCenter Sites e-mail system features. Note that in futuretense_xcel.ini, an additional property, xcelerate.emailnotification, on the Preference tab enables the WebCenter Sites workflow e-mail system to send notices to workflow participants when they are assigned assets through a workflow process.

Table 9-10 Properties in futuretense.ini: Email Tab

Property Description

cs.emailaccount

Specifies the user account name to be used for sending outgoing mail. This is the account name on the SMTP server.

If SMTP authentication is required, you must set a value for this property.

cs.emailauthenticator

Specifies the class that is used as the authenticator for mail operations.

Default value: com.openmarket.framework.mail.ICSAuthenticator

cs.emailcharset

Specifies the default character set that is used for the text in the subject of an e-mail message.

Examples:

  • Latin1: ISO-8859-1

  • Japanese (Shift_JIS): Shift_JIS

  • UTF-8: UTF-8

If this property is blank, its value reverts to the default UTF-8.

cs.emailcontenttype

Specifies the default character set that is used for the text in the body of an e-mail message.

Examples:

  • Latin1: text/html; charset=ISO-8859-1

  • Japanese (Shift_JIS): text/html; charset=Shift_JIS

  • UTF-8: text/html; charset=UTF-8

If this property is blank, its value reverts to the default text/plain.

cs.emailhost

Defines the SMTP (e-mail server) host that is used by the ContentServer servlet to create and deliver e-mail messages.

A valid value is required to send or receive mail.

cs.emailpassword

Specifies the password for the e-mail account used by WebCenter Sites (specified by cs.emailaccount).

A valid value is required to receive mail.

cs.emailreturnto

Specifies the e-mail address from which mail is sent. That is, the e-mail address that appears in the From field of an e-mail message.

Use one of the following formats:

user@domain.com

Full Name <user@domain.com>

A valid value is required to send mail.

9.11 Export/Mirror Tab

The Export/Mirror tab holds the properties that configure the WebCenter Sites Export and Mirror APIs used by the WebCenter Sites publishing system. These properties work in conjunction with the properties located on the Publishing tab in the futuretense_xcel.ini file.

When configuring publishing operations for your WebCenter Sites systems, think of your individual systems (development, management, delivery) in the following terms:

  • Source, which denotes the WebCenter Sites database that is the source for a publishing session. Because you can mirror assets and site configuration information from any WebCenter Sites system to any other WebCenter Sites system, the source is not necessarily the WebCenter Sites management system.

  • Target, which denotes either the WebCenter Sites database to which you are mirroring, or the file server to which are exporting.

For more information about publishing, see the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

Table 9-11 Properties in futuretense.ini: Export/Mirror Tab

Property Description

cs.mirrorhttpversion

Specifies the HTTP protocol version to use to communicate with the WebCenter Sites target databases.

Default value: 1

cs.mirrorpassword

Specifies the password for the mirror user on the target systems to which this system publishes. You set this value when you set up your WebCenter Sites system for publishing.

For information, see "The Mirror to Server Publishing Process" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

cs.mirrorproxyserver

Specifies the firewall server's IP address or name for the target system that this (source) system publishes to when the target and the source are separated by a firewall. You set this value when you set up your WebCenter Sites system for publishing.

Possible values:

your_server_name or

your_server_ip_address

For information, see "The Mirror to Server Publishing Process" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

cs.mirrorproxyserverport

Specifies the port number of the firewall server for the WebCenter Sites system that this system publishes to when the target system is separated from the source with a firewall. You set this value when you set up your WebCenter Sites system for publishing.

Possible values: port_number

For information, see "The Mirror to Server Publishing Process" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

cs.mirrorrowsperpost

Specifies the number of table rows that can be mirrored during each HTTP POST during a mirror operation

If you are mirroring data that contains URL fields, you should set this to a low number because web servers impose a limit on the size of post packets.

If you are mirroring data that contains only text, you can set this to a higher number.

Default value: 6

Note: For best performance, do not increase the value above 12. If your database is configured for UTF-8 and holds non-ASCII content, you must set this value to 4 or lower.

cs.mirrorthreads

Specifies the number of threads to allocate to a mirror operation.

Default value: 2

Note: For best performance, do not increase the value above 8.

cs.mirroruser

Specifies the name of the mirror user on the target system that this (source) system publishes to. You set this value when you set up your system for publishing.

For information, see "The Mirror to Server Publishing Process" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

cs.pgexportfolder

Specifies the base export directory for the HTML files that are created when assets are published with the Export to Disk delivery type.

  • Windows NT example: c:/FutureTense/export

  • Solaris example: /export/home/FutureTense/pgexport

9.12 JSP Tab

The JSP tab holds the properties that supply information that WebCenter Sites references when serving JavaServer Pages files.

Table 9-12 Properties in futuretense.ini: JSP Tab

Property Description

cs.jspclear

Configures the WebCenter Sites engine to delete any previously deployed JSP files and clear the application server's working folder (temp and class files) when the WebCenter Sites engine executes the first JSP deployed by WebCenter Sites.

The working folder is defined by the application server.

Possible values: true | false

cs.jsppath

Specifies the virtual root (zone) for executing deployed JSP pages. This property is used in conjunction with cs.jsproot, so the two properties must be in sync.

Default value: synchronized with the WebLogic setting for cs.jsproot and is set at installation.

Note: Do not change the value of this property after installation.

cs.jsprefresh

When the WebCenter Sites engine deploys a new or changed JSP element, the application server may require special processing to complete the deployment of the JSP. In those cases, this property specifies the name of the class which completes the deployment. In other cases, it is left blank.

cs.jspresponsewrapper

Specifies whether the application server requires the PrintWriter when it runs a JSP element. The WebCenter Sites installation sets this to an appropriate value based on the type of application server you are using.

Do not change the value of this property.

cs.jsproot

Specifies the directory where the application server expects to find JSP files. Some application servers allow this value to be modified by using property settings. WebLogic defines weblogic.httpd.initArgs for its JSPServlet object.

The cs.jsproot property is used in conjunction with cs.jsppath, so the two must be in sync and both are set at installation.

Do not change the value of this property after installation.

cs.jspwork

Specifies the directory where class files are created by the application server when executing JSP pages. This is not a required property and can be left blank, but it is normally set at installation.

For more information, see cs.jspclear.

cs.use.short.jsp.names

Some file systems impose a limit on the length of absolute paths. Using long JSP names on such file systems can result in file system errors.

If you are using such a file system, set this property to true to use shortened JSP names.

When this property is set to false, the JSP name will correspond to the element name.

This property is set automatically by the WebCenter Sites installer; it should be changed only when absolutely necessary.

Default value: false

9.13 Misc Tab

The Misc tab holds miscellaneous properties such as the amount of idle time a connection can have before WebCenter Sites logs out of a connection and whether WebCenter Sites loads cache synchronization processing.

Table 9-13 Properties in futuretense.ini: Misc Tab

Property Description

cs.charset

Specifies a variable that can be included in HTML forms as a hidden variable. The variable, which gets set by the browser, specifies the text encoding of the form data that WebCenter Sites must process.

Default value: _charset_

Do not change the value of this property.

cs.contenttype

Specifies the default character set to use for HTTP headers (streaming text).

Default value: text/html; charset=UTF-8

Specify a value that is appropriate for the online site that your WebCenter Sites system is delivering.

Examples:

  • Latin1: text/html; charset=ISO-8859-1

  • Japanese (Shift_JIS): text/html; charset=Shift_JIS

cs.disksize

Specifies the size limit in bytes for keeping uploaded files in memory while they are being posted. If an uploaded file is larger than the value specified, WebCenter Sites streams it to a temporary file until it is finished evaluating a page. This prevents excessive memory use and helps to prevent denial-of-service attacks.

Default value: 102400

cs.documentation

Specifies the URL of the WebCenter Sites documentation.

By default, this property is set to an Oracle documentation web site.

If you prefer, you can download the most recent documentation kit from that web site, install it somewhere on your network, and then set this property to point to that location rather than to the Oracle documentation web site.

cs.HTTP_HOST

Specifies the HTTP host for WebCenter Sites systems on which the web server does not reside on the application server machine (that is, it is a web connector installation), or in cases where an alternative web server is used to serve pages.

Use one of the following formats:

<hostname>:<port>
<IPaddress>:<port>

Default value: blank

cs.HTTP_PROTOCOL

Specifies the HTTP protocol for WebCenter Sites systems where the web server does not reside on the application server machine (that is, it is a web connector installation), or in cases where an alternative web server is used to serve pages.

Possible values: http or https or blank

Default value: blank, which means the protocol is assumed to be http.

cs.sitepreview

This property is used to control the behavior of Site Preview functionality. The value of this property determines the output of the filter tag (asset:filterassetsbydate) as explained below.

Note: To use Site Preview on a content management environment, you must set this property to contentmanagement.

Possible values: disabled, contentmanagement, delivery

  • If the value is disabled:

    The filter tag will not filter. It will simply return the set of input assets.

    Caching will not factor in start/end dates in the expiry time calculations. Date inputs to the templates will have no effect.

  • If the value is contentmanagement:

    The filter tag will filter the input set of assets according to the given date. If the given date is null, the tag will use the current server date.

    Pages whose rendering templates use the filter tag will not be cached.

    For pages that do not use the filter tag, caching will work in the default manner and expiry time calculations will not factor in start/end dates.

  • If the value is delivery:

    The filter tag will ignore all dates passed to it and will use the current server date for filtering.

    For pages that use the filter tag, caching will factor in start/end dates in the expiry time calculation.

    For pages that do not use the filter tag, caching will work in the default manner and expiry time calculations will not factor in start/end dates.

Default value: disabled

cs.urlfilerollup

Determines how changes to the files for URL columns are tracked.

When this property is set to true, the previous versions of the related file are tracked in a name sequence. For example, if a file called filename.txt has been edited three times, filename.txt is the oldest, filename,1.txt is the next oldest version, and filename,2.txt is the current version.

When this property is set to false, the file name toggles between filename.txt and filename,0.txt on alternate updates.

cs.xmlfolder

Specifies the working directory for HTML filtering. That is, if elements on your system use the XMLFILTER tag, temporary files are written to this directory.

Default value: $HOME/FutureTense/xmltemp

cs.xmlHeader

This is the XML Header streamed out for SOAP responses.

9.14 Page Cache Tab

The Page Cache tab holds the properties that configure the page cache settings for WebCenter Sites. WebCenter Sites page caching is monitored and maintained by the CacheManager. WebCenter Sites caching enables you to cache both complete web pages and their individual components (or pagelets).

To set up page caching on a WebCenter Sites system, you configure properties for the CacheManager and the Satellite Server servlets. In addition, there are properties for configuring BlobServer, the servlet that serves blobs and caches blobs both through WebCenter Sites and the Satellite servlet.

For more information:

  • Page caching – see the "Page Design and Caching" chapter in the Oracle Fusion Middleware WebCenter Sites Developer's Guide. This chapter describes how the WebCenter Sites CacheManager, the Satellite servlets, and the BlobServer servlet interact and work together.

  • Satellite Server properties – see Section 9.16, "Satellite Server Tab" and Chapter 15, "satellite.properties."

  • Resultset caching properties – see Section 9.15, "ResultSet Cache Tab."

  • BlobServer properties – see Section 9.4, "Blob Server Tab."

    Table 9-14 Properties in futuretense.ini: Page Cache Tab

    Property Description

    cs.alwaysusedisk

    Specifies the default cache setting for page entries in the SiteCatalog table that have no information in their cacheinfo column.

    If set to yes, then each page served from WebCenter Sites is cached to disk (the database), unless the value in that page entry's cacheinfo column specifies that it not be cached.

    Default value: no

    cs.expireonly

    Controls how outdated pages are expunged from the cache.

    When this property is set to false, pages that need to be expunged from the cache are deleted immediately and synchronously, that is, the user must wait until all pages are deleted.

    When this property is set to true, pages that need to be expunged from the cache are marked for deletion, taken out of service, and then deleted at a later time by a cache cleanup event.

    Default value: true

    Possible values: true | false

    cs.freezeCache

    Specifies whether a cache maintenance event should regularly remove expired pages from the cache, or whether the expiration date of a page should be checked only when that page is requested.

    Set the value to yes if you do not want an event to regularly remove expired pages from the cache.

    Default value: no

    cs.IItemList

    Defines the file that is used for the ItemList interface that is used by the CacheManager.

    The IItemList interface is used to record compositional dependencies in the page cache. When this property is set to a legal class, dependency items will be recorded against a page id in the SystemItemCache table. This enables CacheManager. An illegal value results in CacheManager having no effect.

    Default value: com.openmarket.xcelerate.publish.MyItemList

    Note: The default value is provided for reference only. Do not change the value of this property.

    cs.manage.expired.blob.inventory

    Controls whether the CacheServer servlet removes blobkey/compositional dependency mappings from the SystemItemCache table after the blobs expire from the local blobserver cache. (The CacheServer servlet is typically invoked every five minutes by the event engine.)

    Possible values: true|false

    • true disables the CacheServer servlet from removing blobkey/compositional dependency mappings from the SystemItemCache table when the blobs expire.

    • false enables the CacheServer servlet to remove expired blob references from the SystemItemCache table when the blobs expire.

    Default value: false (to support backward compatibility)

    Note: How this property takes effect depends on the value of the bs.bCacheTimeout property in Table 9-4.

    cs.nocache

    Provides you with the ability to disable all disk-based page caching (pages will still be cached in memory). Use this property to temporarily shut down page caching when you are debugging your site, but do not leave this value set to true on a live system.

    Default value: false

    cs.pgCacheTimeout

    Specifies the number of minutes that a page will exist in the page cache. A value of 0 (zero) disables timeout, which means pages never expire. However, no matter what the setting for this property, CacheManager refreshes a cached page if the publishing system reports that it published any of the assets on that page.

    Note: For CacheManager to work properly, this property must be set to 0. Otherwise, pages will expire, making it impossible for CacheManager to remove the corresponding entries from the Satellite Server cache, and users will view stale data.

    Default value: 0

    cs.recordBlobInventory

    Allows users to work with blob dependencies. To record blobs inventory, set the value of this property to true.

    cs.requiresessioncookies

    Specifies whether session ID information can be held in cookies or whether WebCenter Sites must encode session data into the links.

    Set to true (the default) if WebCenter Sites expects session cookies to be enabled. This allows all pages to be cached and does not encode the session id into any links. A value of false enables URL rewriting, with a negative effect on page caching performance.

    Default value: true

    cc.BlobServerTimeout

    Specifies the default lifetime (in minutes) of a cached blob in memory. If memory is at a premium, you may reduce the value of this property.

    Default value: 1440 (that is, 24 hours)

    cc.BlobServerCacheCSz

    Specifies the maximum number of blobs that will be cached in memory. If memory is at a premium, you may reduce the value of this property.

    Default value: 1000

    cc.SystemPageCacheTimeout

    Specifies the number of minutes a cached page is held in memory (cached pages are cached both to disk and to memory).

    Default value: 1440 (that is, 24 hours)

    cc.SystemPageCacheCSz

    Specifies the maximum number of pages that can be cached in memory. Pages are cached both in memory and to disk (database). This property specifies the number of pages cached to memory, not to disk.

    Note: This property must not be set to -1.

    Default value: 10000

    ss.flushall

    Controls how Satellite Server cache is flushed.

    When this property is set to false (default), only outdated pagelets are flushed from the Satellite Server cache.

    When this property is set to true, the Satellite Server cache is flushed completely (when a single asset is updated).

    Default value: false

    Possible values: true | false

9.15 ResultSet Cache Tab

The ResultSet Cache tab holds properties that configure resultset caching for WebCenter Sites. For information about resultset caching and queries on your WebCenter Sites system, see the Oracle Fusion Middleware WebCenter Sites Developer's Guide.

The ResultSet Cache tab holds the following properties:

  • Global resultset caching properties, which are set during the WebCenter Sites installation process to enable resultset caching for all tables in the WebCenter Sites database. The same properties will be automatically applied to all tables that are subsequently created. The properties are:

    • cc.cacheResults: number of resultsets to cache in memory

    • cc.cacheResultsTimeout: length of time to keep resultsets cached in memory

    • cc.cacheResultsAbs: method of calculating expiration time for resultsets in the resultset cache

  • Table-specific resultset caching properties for system tables. These properties are automatically set during the WebCenter Sites installation process to override the global resultset caching properties named above.

    For example, the following table-specific properties are set for the ElementCatalog table: cc.ElementCatalogCSz and cc.ElementCatalogTimeout. The property values can be changed, or the properties can be removed (the resultset cache for the table will then use the values of the global properties).

    Note:

    If you wish to override global resultset caching properties, you must do so on a per-table basis by creating the following table-specific properties in the futuretense.ini file for as many tables as necessary to implement your resultset caching strategy for each of your WebCenter Sites systems:

    cc.<tablename>CSz=<number of resultsets> 
cc.<tablename>Timeout=<number of minutes>
cc.<tablename>Abs=<true or false>

    If an asset type is enabled for revision tracking, and you wish to cache the resultsets of asset versions, use the properties above, but add _t after <tablename>:

    cc.<tablename>_tCSz=<number of resultsets> 
cc.<tablename>_tTimeout=<number of minutes>
cc.<tablename>_tAbs=<true or false>

    When you create resultset caching properties that are specific for any user-defined table in the WebCenter Sites database, those properties are displayed on the User Defined tab.

For information about page caching properties, see Section 9.14, "Page Cache Tab." For information about BlobServer caching properties, see Section 9.4, "Blob Server Tab."

Note:

WebCenter Sites stores resultsets within the inCache framework instead of hash tables. Both caching frameworks use Java memory. You can switch between frameworks by setting the rsCacheOverinCache property in futuretense.ini to either true or false. For more information, see "rsCacheOverinCache" in Table 9-17.

Table 9-15 provides a description for each of the properties in the ResultSet Cache tab.

Table 9-15 Properties in futuretense.ini: ResultSet Cache Tab

Property Description

cc.cacheResults

Specifies the default number of resultsets to cache in memory. Note that this does not mean the number of records in a resultset, but the number of resultsets.

Caution: Unless you are debugging, do not set this property to 0 or -1. If you do, WebCenter Sites will fail to save assets properly. (Setting this property to 0 or -1 disables resultset caching for all tables that do not have their own caching properties configured.)

Possible values: <n> (number of resultsets)

Default value: 500

Note: To set a different value for a specific table, create a property for that table using the following format: cc.<tablename>CSz=<number of resultsets>

cc.cacheResultsAbs

Specifies how expiration time for resultsets in the resultset cache is calculated.

  • If this property is set to true, the expiration time for a resultset is absolute. For example, if cc.cacheResultsTimeout is set to 5 minutes, then 5 minutes after the resultset was cached, it is flushed from the cache.

  • If this property is set to false, the expiration time for a resultset is based on its idle time. For example, if cc.cacheResultsTimeout is set to 5 minutes, the resultset is flushed from the cache 5 minutes after the last time it was requested rather than 5 minutes since it was originally cached.

Note: To set expiration time for a specific table, create a property for that table using the following format: cc.<tablename>CAbs=<true or false>

cc.cacheResultsTimeout

Specifies the number of minutes to keep a resultset cached in memory.

Setting this property to -1 means that there is no timeout value for tables that do not have their own caching properties configured.

Possible values: <n> (in minutes), or -1 to disable timeout for tables that use this default property.

Default value: 5

Note: To set timeout for a specific table, create a property for that table using the following format: cc.<tablename>Timeout=<number of minutes>

cc.ElementCatalogCSz

Specifies the number of resultsets to cache against the ElementCatalog table.

For best performance this value should be set to the number of rows in the table.

Default value: 1000

cc.ElementCatalogTimeout

Specifies the number of minutes to keep idle resultsets for the ElementCatalog table in the resultset cache.

Use -1 to disable timeout.

Default value: 60

cc.SiteCatalogCSz

Specifies the number of resultsets to cache against the SiteCatalog table.

For best performance, this value should be set to the number of rows in the table.

Default value: 1000

cc.SiteCatalogTimeout

Specifies the number of minutes to keep idle resultsets for the SiteCatalog table in the resultset cache.

Use -1 to disable timeout.

Default value: 60

cc.SystemACLCSz

Specifies the number of resultsets to cache against the SystemACL table.

For best performance, this value should be proportional to the number of rows in the table.

Default value: 25

cc.SystemACLTimeout

Specifies the number of minutes to keep idle resultsets for the SystemACL table in the resultset cache.

Default value: -1 (which disables timeout for this table)

cc.SystemInfoCSz

Specifies the number of resultsets to cache against the SystemInfo table.

For best performance, this value should be set to the number of rows in the table.

Default value: 500

cc.SystemInfoTimeout

Specifies the number of minutes to keep idle resultsets for the SystemInfo table in the resultset cache.

Default value: -1 (which disables timeout for this table)

cc.SystemUsersCSz

Specifies the number of resultsets to cache against the SystemUsers table.

For best performance, this value should be proportional to the number of rows in the table.

Default value: 100

cc.SystemUsersTimeout

Specifies the number of minutes to keep idle resultsets for the SystemUsers table in the resultset cache.

Default value: -1 (which disables timeout for this table)

ft.filecheck

Specifies whether WebCenter Sites verifies the timestamp on data held in an upload field each time an item (like an element) with uploaded data is requested.

On a management or delivery system, the same items are requested repeatedly and setting this value set to yes can slow the performance of the system. Set this property to no on management or delivery systems. You can set it to yes on a development system.

Default value: no

9.16 Satellite Server Tab

The Satellite Server tab holds properties that describe how to communicate with any of the Satellite servlets (Satellite Server), whether they are running locally or on remote servers.

Additionally, because Satellite Server is installed by default on the server that hosts your WebCenter Sites application, each WebCenter Sites system also has a satellite.properties file that configures the local Satellite servlet. (Note that when Satellite Server is also running on a remote server, that server also has a satellite.properties file.) For information about the properties in that file, see Chapter 15, "satellite.properties."

The following table describes the properties on the server that hosts WebCenter Sites that support communications with all Satellite servlets.

The value for each property is a comma-separated list. The ordinal position of an item in the list is what associates the host, user name, and password for each Satellite servlet. For example, the third host named in cs.satellitehosts is accessed using the third user account named in cs.satelliteusers, giving the third password listed in cs.satellitepassword.

Table 9-16 Properties in futuretense.ini: Satellite Server Tab

Property Description

cs.PastramiEngine

Defines the name of the implementing class of the PastramiEngine interface. Leave this property null to disable this feature entirely. The standard value for this property is: com.divine.pastrami.PushEngine

satellite.blob.cachecontrol.default

Specifies a default value for the cachecontrol parameter for the satellite.blob, and RENDER.SATELLITEBLOB tags and their JSP equivalents.

Default value: blank

Set this property to a value that is appropriate for the majority of your blobs, and then use the cachecontrol parameter with the satellite.blob and RENDER.SATELLITEBLOB tags to override this value for individual blobs.

Use the following format to set a value:

hours:minutes:seconds daysOfWeek/daysOfMonth/months

For more information about this format, see the description of the expiration property in Chapter 15, "satellite.properties."

satellite.page.cachecontrol.default

Deprecated.

Specifies a default value for the cachecontrol parameter for the satellite.page, and RENDER.SATELLITEPAGE tags and their JSP equivalents.

Default value: blank

Set this property to a value that is appropriate for the majority of your pages and pagelets, and then use the cachecontrol parameter with the satellite.page and RENDER.SATELLITEPAGE tags to override this value for individual pages and pagelets.

Use the following format to set a value:

<hours>:<minutes>:<seconds> <daysOfWeek>/<daysOfMonth>/<months>

For more information about this format, see the description of the expiration property in Chapter 15, "satellite.properties."

9.17 Search Tab

Properties on the Search tab are deprecated and unsupported.

9.18 User Defined Tab

The User Defined tab displays custom properties, which are not created by the core WebCenter Sites product but are used by WebCenter Sites and its content applications.

This tab displays the following kinds of properties:

The following table lists all of the properties that any of the WebCenter Sites products create in the futuretense.ini file, which means that they appear on the User Defined tab. Note that your system may have additional properties that are not included in this list.

Table 9-17 Properties in futuretense.ini: User Defined Tab

Property Description

analysisconnector.version

Deprecated.

The version number of Analytics Bridge, if it is installed.

Do not change the value of this property.

catalogcentre.version

Deprecated.

The version number of CS-Direct Advantage, if it is installed. CS-Direct Advantage was named Catalog Centre in early versions of the product.

Do not change the value of this property.

cc.AssetTypeCSz

The number of resultsets to cache against the AssetType table, an object table that is created by the WebCenter Sites installation.

Default value: 50

cc.CategoryCSz

The number of resultsets to cache against the Category table, an object table that the WebCenter Sites installation creates for asset types.

Default value: 50

cc.ComparatorsKey

The primary key of the Comparator table, a content table that the WebCenter Sites installation creates to hold field comparator classes.

Default value: name

Do not change the value of this property.

cc.FiltersKeyXX

Default value: name

cc.MimeTypeKey

The primary key of the MimeType table, a content table that the WebCenter Sites installation creates to store the mimetypes of the documents that it handles.

Default value: mimetype

Do not change the value of this property.

cc.PreviewgenKey

Default value: name

cc.SourceKey

The primary key of the Source table, a content table that the WebCenter Sites installation creates for asset types.

Default value: source

Do not change the value of this property.

cc.StatusCodeCSz

The number of resultsets to cache against the StatusCode table, a content table that the WebCenter Sites installation creates for asset types.

Default value: 10

cc.StatusCodeKey

The primary key of the StatusCode table.

Default value: statuscode

Do not change the value of this property.

commerceconnector.version

The version number of the Commerce Connector utility, if it is installed.

Do not change the value of this property.

contentcentre.version

Deprecated.

The version number of CS-Direct, if it is installed. CS-Direct was named Content Centre in previous versions of the product.

Do not change the value of this property.

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 futuretense.ini).

If you wish to switch back from approval locking per target to default behavior (i.e., global lock):

  1. Remove the cs_target column from the ApprovalQueue table.

  2. Set cs.approvalLockStriping to false (or remove this property, as by default it is false).

cs.parentfoldercount

Specifies the maximum number of parent folders that WebCenter Sites can generate in subdirectories of <cs_install_dir>/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 <cs_install_dir>/Shared/ccurl (where flex assets are stored).

If you wish to use this property, you must add it to futuretense.ini. 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.childfoldercount

Specifies the maximum number of child folders that WebCenter Sites can generate in parent folders under subdirectories of <cs_install_dir>/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 <cs_install_dir>/Shared/ccurl.

If you wish to use this property, you must add it to futuretense.ini. 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.dbencoding

Default value: UTF-8

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 "inCache Framework" in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

If you wish to use this property, add it to the futuretense.ini 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.requestfactory

Default value: com.fatwire.cs.portals.portlet.PortletRequestFactory

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 futuretense.ini file and its value is set to 5. To change the value of this property, you must manually add this property to the futuretense.ini file.

ft.servletoutputstream

Default value: false

image.time

Deprecated.

Default value: 5:0:0 */*/*

marketingstudio.version

The version number of Engage.

Do not change the value of this property.

page.time

Deprecated.

Default value: *:0,5,10,15,20,25,30,35,40,45,50,55:0 */*/*

propagatecache

Used to enable the propagation of pages among nodes that are enabled for the inCache page caching framework. Information about inCache can be found in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide.

rsCacheOverinCache

Used to switch between resultset caching media. This property is set to true by default, in which case WebCenter Sites caches resultsets in the inCache framework. When this property is set to false, WebCenter Sites caches resultsets in hash tables. Both caching media use the JVM memory.

This property is set to true during the WebCenter Sites installation process. The process also completes following steps:

  • Places the linked-cache.xml configuration file in the application server's classpath (WEB-INF/classes directory).

  • Sets the following resultset caching properties (see Section 9.15, "ResultSet Cache Tab"): cc.cacheResults cc.cacheResultsTimeout cc.cacheResultsAbs

When the installation process is complete, the System Tools node (on the Admin tab of the Admin interface) displays the resultset over inCache tool, which provides statistical information about the caches and their contents.

Note: Resultset caching over inCache works independently of page and asset caching over inCache. Information about the inCache framework, its caching models and system tools is available in the "System Tools" chapter in the Oracle Fusion Middleware WebCenter Sites Administrator's Guide. Additional information about resultset caching is also available in the "Resultset Caching and Queries" chapter in the Oracle Fusion Middleware WebCenter Sites Developer's Guide.

Default value: true

Possible values: true | false

rtd.choiceId.pattern

If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this property to the futuretense.ini 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 futuretense.ini 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 futuretense.ini file and set the value as the name of the Oracle RTD inline service.

soap.binaryRowsType

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.iList

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.likeConstraint

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.listRowsType

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.nestedConstraint

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.rangeConstraint

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.richTextConstraint

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.searchstate

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.standardConstraint

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.stringRowsType

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.stringVarsType

Default value: com.openmarket.basic.objects.StringVarsType

soap.urlRowsType

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.

soap.URLType

A WebCenter Sites system property used to instantiate server-side objects in response to SOAP requests made by web services.

Do not change the value of this property.