for
the following:Your installation may include more than one Content Manager, each on a different computer. One Content Manager computer is active and one or more Content Manager computers are on standby. The standby Content Manager computers are for failover protection. If the active Content Manager computer is not available because of a software or hardware failure, a standby Content Manager computer becomes active and requests are directed to it.
When the active Content Manager fails, unsaved session data is lost. When another Content Manager becomes active, users may be prompted to log on.
Ensure that the clocks on each computer where Content Manager is installed are synchronized. If they are not, you may experience odd behavior if a failover occurs. For example, there may be a delay before the status of a newly disabled server is updated in Cognos Administration.
You can set advanced Content Manager parameters for
the following:
database connection pool settings
sorted entries for non-English locales
Content Manager synchronization
control browsing of external namespaces
For more information about Content Manager, see the Installation and Configuration Guide.
You must have the required permissions to access Cognos Administration functionality. See Secured Functions and Features.
Content Manager uses database connections to access the content store. You can change connection pool settings for Content Manager to increase performance.
With pooled connections, Content Manager does not have to create and open connections for new requests. This provides faster response times. However, pooled connections reserve database resources, so idle connections should be closed if they are not needed.
You can manage the number of connections to the content store by limiting the maximum number of connections and by specifying how long connections stay in the pool before they are automatically closed.
The following table lists the available parameters.
Parameter | Purpose |
CM.DbConnectPoolMax | The maximum number of concurrent database connections that are allowed to the content store. Valid settings are -1, or 5 to 2147483647, or the database setting, whichever is less. This setting applies only to Content Manager connection pool settings. If you have other services that access the same content store, there may be more concurrent database connections than specified in this parameter. Default: -1 (unlimited) |
CM.DbConnectPoolTimeout | Maximum time in milliseconds that a thread waits for a connection to be available from the pool. Valid settings are -1 to 2147483627. A setting of 0 specifies that threads never wait for a connection if one is not available immediately. Default: -1 (unlimited) |
CM.DbConnectPoolIdleTime | Minimum time in milliseconds that a connection stays idle in the pool. Only valid if the value of DbConnectPoolCleanUpPeriod setting is positive. Valid settings are -1 to 2147483647. A setting of 0 or -1 specifies that idle connections are closed when Content Manager restarts. Default: 300000 (5 minutes) |
CM.DbConnectPoolCleanUp Period | Time in milliseconds between invocations of a cleanup thread that closes idle connections in the pool that exceed the setting of DbConnectPoolIdleTime. Valid settings are -1 to 2147483647. A setting of 0 or -1 specifies no clean up thread. Default: 300000 (5 minutes) |
If you use a locale other than English, entries in Cognos Connection may not be sorted correctly. You can correct this problem for an Oracle or Microsoft SQL content store by using the CM.SortCollation setting.
For example, to sort entries in an Oracle database using a Chinese phonetic collation, set CM.SortCollation parameter to SCHINESE_PINYIN_M.
For information about supported collations, see the Oracle and SQL Server documentation. Setting the CM.SortCollation value has no effect on Content Manager running against DB2 or Sybase databases.
If your installation includes standby Content Manager computers, you can set parameters that specify Content Manager standby activities. You can specify how often checks occur to ensure that the active dispatcher has not failed, how long it takes to determine which Content Manager is active when failover occurs and at startup, how often an active Content Manager sends a response when it is busy, and how long a short network interruption can be without causing a failover.
The following table lists the available parameters.
Parameter | Purpose |
CM.CMSync_NegotiationTime | Time in milliseconds that it takes to determine the active Content Manager when a failover occurs. Valid settings are 1 to 9223372036854775807. Default: 2000 |
CM.CMSync_NegotiationTimeForStartUp | Time in milliseconds that it takes to determine the active Content Manager at startup. Valid settings are 1 to 9223372036854775807. Default: 60000 |
CM.CMSync_CheckActive Time | Time in milliseconds for an active Content Manager to become standby when another Content Manager becomes active. Default: 10000 |
CM.CMSync_PingTimeout | Time in milliseconds that a busy Content Manager sends a response if it is running. Valid settings are 1 to 9223372036854775807. Default: 120000 |
CM.CMSync_ShortNetwork InterruptionTime | Time in milliseconds that a short network interruption can occur without causing a failover. Valid settings are 1 to 9223372036854775807. Default: 3000 |
You can control whether users can browse external namespaces.
When the CM.SecurityQueryRequiresRead setting is set to true, the Content Manager prevents browsing of external namespaces when the external namespace policy is updated to deny read permissions to users or groups. This setting controls whether the Content Manager forces a read permission filter for external namespace query results. The default is false.
You can set advanced Content Manager parameters. For
information about parameters, see .
Start Cognos Connection.
In the upper-right corner, click Launch, Cognos Administration.
On the Status tab, click System.
In the upper-left corner of the Scorecard pane, click the arrow to view the Change view menu. Click Services, and then click Content Manager.
Click the arrow next to ContentManagerService to display the Actions menu, and then click Set properties.
Click the Settings tab.
Click Edit next to Advanced Settings.
Select Override the settings acquired from the parent entry.
In the Parameter column, enter the parameter name.
For example, enter CM.DbConnectPoolCleanUpPeriod.
In the Value column, enter the associated value for the setting.
Continue entering setting names and values as required.
Click OK.
On the Set properties page, click OK.
