Scalability Server Policy Group (Software Delivery)
The Scalability Server policy group contains the following policies for software delivery scalability servers. You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
This policy group contains the following policy folder:
Backwards Compatibility
The Scalability Server policy group also contains the following policies:
Specifies the maximum number of job result messages (in-progress and completion) you want to include in the body of a single message. For example, the default value 300 implies that 300 job result messages are included in a single message. This policy is applicable only when the Bulk Update: Run in bulk update mode policy is set to True, that is, the bulk update mode is enabled.
Default: 300
Limits: 50 to 5000
Specifies the maximum number of units for which you want to include the software detection records and software job records in the body of a single message. For example, the default value 50 implies that software detection records and software job records for 50 units are included in a single message. This policy is applicable only when the Bulk Update: Run in bulk update mode policy is set to True, that is, the bulk update mode is enabled.
Default: 50
Limits: 5 to 500
Specifies whether to run the scalability server in the bulk update mode. You can set the value to True or False. Setting the value to True enables the bulk update mode. The scalability server caches all the job status messages and the software records until the scheduled time, or until the manual execution of the bulkupdate (sd_sscmd bulkupdate) command.
Default: True
Note: If you enable the bulk update mode, that is, set the value to True, you might experience some delay (up to the maximum wait time) while updating the job status or software record messages. The reason is that the scalability server caches the messages for the bulk update.
Specifies the time in minutes between two bulk updates. This policy is applicable only when the Bulk Update: Run in bulk update mode policy is set to True, that is, the bulk update mode is enabled.
Default: 5
Limits: 1 to 360
If True, the calendar is not checked when an agent job is scheduled for execution.
Default: False
Specifies the numbers of hours before messages from the server to its manager are discarded. When the message is discarded, it is resent to the manager, and an entry is added to the event manager system.
Default: 48
Specifies the maximum number of simultaneously connected agents that may report data to the server.
Default: 100
Specifies the maximum number of simultaneously executing agents on the server that are allowed to execute jobs. The minimum is 1.
Default: 25
If True, enables the server to send events, reflecting agent job activity and registering and deregistering software.
Default: False
Indicates whether important status messages from the server to the manager are prioritized. Valid values are True and False.
Default: True
Indicates whether Wake-on-LAN (WOL) functionality for physical computers, or virtual Wake-on-LAN (vWOL) for virtual machines, is disabled. If True, no WOL string is set in the job check trigger message.
Default: False
Specifies the wait time interval in seconds before triggering a non-responding agent again. If a job has not started within this time, the job check at the agent is triggered again to contact the server and start the job.
Default: 600
Specifies the delay in minutes to wait between triggering jobs again under one of the following conditions:
Default: 60
Specifies the interval in seconds to wait before triggering any agent to avoid triggering multiple agents at the same time (limited by the Concurrency: Maximum number of simultaneously executing agents on Scalability Server policy). This policy is used to avoid congestion when jobs are queued for multiple agents.
Default: 0
From Unicenter DSM r11 onward, software jobs in containers of type no linkage will always be executed according to their activation times regardless of container membership. To specify pre-r11 behavior, set this value to True.
Default: False
Adds an additional library section to the agent container file if True. This library accesses the server SW export library without the fully qualified domain name (FQDN).
Default: False
Enables consistency checking of the packages that the scalability servers deploy to agents. If False, consistency checking at the scalability server is disabled.
Default: True
Indicates whether a scalability server runs in stage check mode. If set to True, job result reporting to the upstream manager takes place only when the command, sd_sscmd stagecheck, is executed or when the Wait between stage checks policy is also set to a value greater than zero (0).
Default: False
Specifies the time in minutes between stage checks. If set to zero (0), automatic stage checks are not performed.
Default: 720
Note: Irrespective of whether the Stage Check: Run in stage check mode policy is enabled or disabled, a stage check is performed regularly based on the interval (value greater than zero) specified in the Stage Check: Wait between stage checks policy, and reports the availability of the unregistered units. The stage check checks for the unregistered units at the scalability server and sends a query to the domain manager to resolve the unregistered units. For the registered units, the stage check sends the information present in the cachedAgData.xml file.
For information on how the stage check behaves in the bulk update mode, see the How the Scalability Server Handles Messages when Only Bulk Update Mode Is Enabled section.
If True, agent job progress messages are not sent to the manager. However, all job completion messages will be sent.
Default: False
If True, job staged messages are not sent to the manager.
Default: False
|
Copyright © 2013 CA.
All rights reserved.
|
|
