Monitor service advanced settings

This section describes advanced settings for the monitor service.

Parent topic: Advanced settings reference

enable.session.affinity

Indicates whether session affinity is enabled.

This setting is used in conjunction with the session.affinity.services advanced setting.

Data type:
Boolean
Default:
false

event.check.active

Specifies whether the consistency check is active.

Possible values: 1 for true, 0 (or anything else) for false

Data type:
Integer
Default:
0

event.check.interval

Specifies the interval, in minutes, when a consistency check is made to ensure that the monitor service record of events matches that in Content Store.

An event consistency checker thread cleans up any discrepancies.

Data type:
Integer
Default:
10

primary.wait.ms

Specifies the primary wait threshold, in seconds, for the monitor service.

This setting is used if a value is not set in the request.

Data type:
Integer
Default:
120

session.affinity.services

If enable.session.affinity is set to true, this setting specifies the services to configure for session affinity.

In an N/N-1 scenario, this setting is supported by the following IBM Cognos Planning services only: planningAdministrationConsoleService, planningDataService, planningRuntimeService, and planningTaskService. Otherwise, in a homogeneous distributed environment, this setting is supported by all services.

To specify the service(s), use the mandatory serviceName parameter. To configure multiple services, separate each with a semi-colon (;). Here are two examples:

  • serviceName=planningTaskService
  • serviceName=planningTaskService;serviceName=planningDataService

Two optional parameters provide more specific configuration choices:

  • serverGroup: Specifies the name of the server group.
  • numThreads: Specifies the maximum number of concurrent tasks allowed. Default is 2.

Parameters must be separated by a comma (,). For example,

serviceName=planningTaskService,serverGroup=mygroup,numThreads=4
Data type:
String
Default:
None

sds.instance.interval

Specifies the update interval, in seconds, for service instances to register that they are running.

The monitor service uses this mechanism to determine that other monitor services are active. If a monitor service fails, another monitor service can elect to clean up on behalf of the failed service, including updating the history for tasks that failed.

Services can elect to clean up on behalf of another service if that service has not updated its registration within a reasonable time limit. Currently that limit is twice the sds.instance.interval setting.

Data type:
Integer
Default:
30
Note:

You must restart the service for this setting to take effect.

enable.tide.metrics.taskqueue

Enables the collection and display of specific metrics for the monitor service in IBM Cognos Administration.

The following metrics are included:

  • Time in queue high water mark

  • Time in queue low water mark

  • Time in queue

  • Number of queue requests

  • Queue length high water mark

  • Queue length low water mark

Data type:
Boolean
Default:
false

sdk.service.poll.interval

The length of time in seconds that the monitor service waits before retrying a client application request to a reconnecting service.

Data type:
Integer
Default:
30

advanced.history.write

Indicates whether final histories are written using the advanced (enhanced) thread pool.

If true, the final histories are written using multiple threads. If false, the final histories are written on a single thread.

Data type:
Boolean
Default:
true

advanced.parent.history.threads

The number of worker threads used to create root history objects in the content store.

Set advanced.history.write to true to enable this setting.

Data type:
Integer
Default:
2
Note:

You must restart the service for this setting to take effect.

advanced.child.history.threads

The number of threads used to create child history objects for steps in the content store.

Set advanced.history.write to true to enable this setting.
Data type:
Integer
Default:
5
Note:

You must restart the service for this setting to take effect.

write.child.histories

Controls the writing of child history objects to the content store.

When true, the final history objects for all child tasks are written. When false, only the final history object for the root task is written and the history objects for the child tasks are discarded. You can use this setting to improve performance for tasks where child history object write time is very high.

Data type:
Boolean
Default:
true
Note:

You must restart the service for this setting to take effect.

write.child.histories.during.failover

Specifies whether final history objects for a task are written to the content store during a failover.

If the value of write.child.histories is set to true, child history objects and history objects for root tasks are written.

Data type:
Boolean
Default:
true
Note:

You must restart the service for this setting to take effect.

connection.tracker.use

Tracks connection usage.

When true, java proxy objects are used to track the activities of JDBC objects.

Data type:
Boolean
Default:
false
Note:

You must restart the service for this setting to take effect.

connection.write.maxwaittime

The maximum period of time, in seconds, that an object waits to get a read-write connection from the JDBC connection pool.

Data type:
Integer
Default:
10
Note:

You must restart the service for this setting to take effect.

connection.write.maxConnections

The maximum number of read-write JDBC connections used in the connection pool.

Any value set that is less than the minimum has no effect and the minimum value that is specified is applied.

Minimum value: 5

Data type:
Integer
Default:
10

connection.read.maxwaittime

The maximum period of time, in seconds, that an object waits to get a read-only connection from the JDBC connection pool.

Data type:
Integer
Default:
10
Note:

You must restart the service for this setting to take effect.

connection.read.maxConnections

The maximum number of read-only JDBC connections that are used in the connection pool.

Any value that is set less than the minimum has no effect and the minimum value that is specified is applied.

Data type:
Integer
Default:
8
Note:

You must restart the service for this setting to take effect.