Common Configuration Policy Group (Manager)
The Common Configuration policy group contains the following policies for the common configuration manager. You can modify policy parameter values using either the Common Configuration configuration view or the Setting Properties dialog.
Specifies the time in minutes after which the configuration queues are checked for jobs. Although the common configuration manager is notification-driven, a check of the configuration queues is done at regular intervals. This policy provides a fallback in case notifications get lost.
Limits: 10–1440
Default: 30
Specifies an interval in minutes after which a pending configuration job message is re-sent, even though the common configuration manager typically does not send a message to a target for which a communication error has been reported. This value should be greater than that for the Configuration message retry interval policy.
Limits: 1–172800
Default: 480
Indicates the time in minutes to pass before the common configuration manager resends a configuration job to a target computer that has not yet replied.
Limits: 1–172800
Default: 60
Indicates the time in minutes to pass before the common configuration manager stops attempting to resend a configuration job to a target computer that has not yet replied.
Note: If your system has been upgraded from Unicenter DSM r11.1 to r11.2, the r11.1 default of 10080 minutes (or 7 days) is retained.
Limits: 480–8409600
Default: 86400
Indicates the time in minutes to pass before the common configuration manager stops waiting for a reply from the database.
Limits: 1–20
Default: 10
Indicates the time in hours after which the common configuration manager checks for groups and computers that need configuration updates. Although the common configuration manager is notification-driven, a check for groups and computers that need a configuration update is done at regular intervals. This policy is a fallback in case notifications get lost.
Limits: 1–24
Default: 24
Indicates the time in seconds the common configuration manager waits before starting replication tasks for a new domain. The common configuration enterprise manager receives notifications indicating the linking or unlinking of a domain. However, when a notification is received, it still takes some time until the complete domain information is available.
Limits: 60–3600
Default: 180
Indicates the time in minutes after which the common configuration manager checks for linked or unlinked domains. The common configuration enterprise manager routinely checks at regular intervals for linked or unlinked domains. This policy is a fallback in case a domain linked or unlinked notification gets lost.
Limits: 5–1440
Default: 10
Indicates the time in minutes to pass before the common configuration enterprise manager resends a replication message to a domain manager that has not yet replied.
Limits: 2–1440
Default: 10
Indicates the time in seconds after which the common configuration manager tries again to check for tasks to be processed after having encountered a database access problem.
Limits: 60–1800
Default: 60
Specifies the maximum time in seconds that the common configuration manager spends setting up and activating configurations. It is limited so that other tasks will not be deferred too long. When this time span has expired, the setup or activation of new configurations is suspended until the next scheduled check.
Limits: 1–60
Default: 15
Specifies the maximum time in seconds that the common configuration domain manager spends processing incoming messages before checking for outbound jobs.
Limits: 3–300
Default: 20
Specifies the maximum time in seconds that the common configuration domain manager spends setting up full configuration report requests. It is limited so that other tasks will not be deferred too long. When this time span has expired, the setup of full configuration report requests is suspended until the next scheduled check.
Limits: 1–60
Default: 15
Indicates the cursor location for CSM manager database requests. If True, the cursor location is set to "client side cursor." A client side cursor can be used with a remote database to minimize the number of data transfers. If False, the cursor location is set to "server side cursor."
Default: False
|
Copyright © 2013 CA.
All rights reserved.
|
|
