Content Manager service advanced settings

This section describes advanced settings for the Content Manager service.

Parent topic: Advanced settings reference

CM.CMSync_CheckActiveTime

Specifies the period within which an active Content Manager enters standby mode if another Content Manager becomes active.

Data type:
Integer
Default:
10000

CM.CMSync_NegotiationTime

Specifies failover election time in milliseconds.

The election time is the wait period after a Content Manager instance fails, before other Content Manager instances attempt to become the active service. This period ensures that another Content Manager service instance does not become active unless the original Content Manager is truly failing.

Data type:
Integer
Default:
2000

CM.CMSync_NegotiationTimeForStartUp

Specifies startup election time in milliseconds, after a computer shutdown.

This election time is the wait period during which the default Content Manager is expected to start before other standby Content Manager instances try to start. This ensures that the preferred Content Manager is started after a computer shutdown.

Data type:
Integer
Default:
60000

CM.CMSync_PingTimeout

Specifies maximum time, in milliseconds, within which a busy Content Manager should send a response.

After the timeout period, the election process begins to select a new Content Manager from the standby Content Manager instances, if any instances exist.
Data type:
Integer
Default:
120000

CM.CMSync_ShortNetworkInterruptionTime

Specifies a short network interruption time, in milliseconds, within which failover will not occur.

Data type:
Integer
Default:
3000

CM.DbConnectPoolMax

Specifies the maximum number of concurrent database connections allowed to the content store.

Valid settings are -1, or 5 to 2147483647, or the database setting; whichever value is less.

A setting of -1 means connections are unlimited.

This setting applies to Content Manager connection pool settings only. If you have other services that access the same content store, there may be more concurrent database connections than specified in this parameter.

Data type:
Integer
Default:
-1

CM.DbConnectPoolTimeout

Specifies the maximum time, in milliseconds, that a thread waits for a connection to be available from the pool.

A setting of 0 specifies that threads never wait for a connection if one is not available immediately. A setting of -1 means the wait time is unlimited.

Data type:
Integer
Default:
-1

CM.DbConnectPoolIdleTime

Specifies the minimum time, in milliseconds, that a connection stays idle in the pool.

This setting is valid only if the value of DbConnectPoolCleanUpPeriod setting is positive.

A setting of 0 or -1 specifies that idle connections are closed when Content Manager restarts.

Data type:
Integer
Default:
300000

CM.DbConnectPoolCleanUpPeriod

Specifies the time, in milliseconds, between invocations of a cleanup thread that closes idle connections in the pool that exceed the setting of DbConnectPoolIdleTime.

A setting of 0 or -1 specifies no cleanup thread.

Data type:
Integer
Default:
300000

CM.DeploymentIncludeConfiguration

Specifies if configuration objects should be imported from the entire content store archive during deployment.

These objects include dispatchers and the configuration folders used to group dispatchers. For example, you may want to import the configuration because you have a series of advanced settings for your services that you want to bring in from the source environment.

For best results, do not import configuration objects. Configure dispatchers in your target environment before you import data from a source environment.

Data type:
Boolean
Default:
false

CM.DeploymentSkipUserReportOutput

If this setting is set to true, report outputs and their child objects (graphic and page) under user accounts are not exported or imported. Use this setting to reduce the size of the content store archives and improve deployment performance.

Data type:
Boolean
Default:
false

CM.DeploymentDetailErrorsOnly

If set to true, this setting generates only summary and error information for package and folder deployments. By default, Content Manager generates full details for package and folder deployment histories. Use this settting to reduce the size of the content store archives and to improve deployment performance.

Data type:
Boolean
Default:
false

CM.DeploymentDetailEntireContent

If set to true, this setting generates full details for an entire content store deployment history. By default, Content Manager generates only summary and error information for an entire content store deployment.

Data type:
Boolean
Default:
false

CM.DeploymentUpdateScheduleCredential

If set to true and the takeOwnership option is used during the import of a deployment archive, the credential property of all imported schedule objects is changed to reference the credential contained in the account used to import the deployment.

Data type:
Boolean
Default:
false

CM.OutPutLocation

Specifies the file system location where generated report outputs will be saved.

Each output file also has an output descriptor of the same name, with an XML extension.

Old report versions are not deleted when a new one is saved. You must manage the content of the output directory to keep only the report versions that you want.

Data type:
String
Default:
none

CM.OutputScript

Specifies the location and name of an external script that runs each time a report output is saved.

The script parameters are the report output and output descriptor file names.

Data type:
String
Default:
none

CM.OutputByBurstKey

Specifies whether or not the outputs should be organized on the file system by burst key.

If set to true, the output is placed in a subdirectory of the same name as the burst key.

Data type:
Boolean
Default:
false

CM.SecurityQueryRequiresRead

Controls whether Content Manager forces a read permission filter for external namespace query results.

When enabled, Content Manager can prevent browsing of external namespaces, if the external namespace policy is also updated to deny read permission to users or groups.

Data type:
Boolean
Default:
false

CM.SortCollation

The name of the database-specific collation used for sorting in some databases, such as Oracle and SQL Server.

If left empty, the database uses its default collation.

For example, in Oracle, if you specify the collation sequence as Binary at the database level, you must provide the same collation sequence value in the connection string.

An example connection string for an Oracle database that uses the sample gosl database is: ORACLE@GOSL0703@GOSL/GOSL0703@COLSEQ=Binary

For information about supported collations, see the Oracle and SQL Server documentation.

The CM.SortCollation value has no effect on Content Managers running against DB2 or Sybase databases.

Data type:
String
Default:
none

CM.UpdateInitialContentNamesAfterImport

Adds localized object names for previously unsupported locales.

In some locales, if you want to upgrade IBM Cognos Business Intelligence to version 10.1.1 or later, and you plan to import a content store that was created with an older version of Cognos BI, use this advanced setting to ensure that all object names are properly localized.

The following locales are affected: Catalan, Croatian, Danish, Greek, Kazakh, Norwegian, Slovak, Slovenian, and Thai. Support for these locales was added in Cognos BI versions 10.1.1 and 10.2. If your content store was created with an earlier version of Cognos BI, and the CM.UpdateInitialContentNamesAfterImport setting was not specified before importing the content store, some object names in your Cognos BI software might appear in English, and not in the specified language.

Specify the affected locales, separating each with a comma. For example, for Slovenian and Croatian content locales, type: sl,hr

Note: Remove this advanced setting when support for the older content store is no longer needed because there is a performance impact associated with this setting.
Data type:
String
Default:
none