Modifying the CCS Manager configuration settings for message based data collection
You can change the CCS Manager configuration settings to optimize data collection for message based data in the following scenarios:
If you are using a high configuration or a low configuration computer for CCS Manager, and you want to optimize data collection accordingly.
If your CCS Manager co-exists with other CCS components, or other 3rd party components on a single computer, for example, CCS Manager + CCS Application Server, and you want to optimize the use of system resources during data collection, by the CCS Manager
To modify the CCS Manager configuration settings for message based data collection
Open the CCS Manager configuration file from the following location:
<Install Directory>\Symantec\CCS\Reporting and Analytics\DPS\Symantec.CSM.DPS.exe.config
You can update the following keys in the <appSettings> section of the configuration file. The following table contains the recommended values for message based data collection.
Table: CCS Manager configuration settings for message based data collection
The number of active worker processes. The Worker Process Manager (WPM) starts up to the specified number of worker processes while jobs are awaiting to be processed.
Configure the CCS Manager to have at least 2 active worker processes running in 32 bit mode at any given point of time. If the CCS Manager is installed on a 32 bit operating system, set the value to 2. If the CCS Manager is installed on a 64 bit operating system, set the value to 3.
For each additional ESM Manager configured for the CCS Manager, increase the number of active worker processes by 1.
The number of concurrent worker processes, which includes active and obsolete processes.
Configure the CCS Manager to create maximum 4 worker processes running in 32 bit mode. If the CCS Manager is installed on a 32 bit operating system, set the value to 4. If the CCS Manager is installed on a 64 bit operating system, set the value to 5.
Any change to active worker process limit must be reflected in the worker process threshold limit. For example, if you increase the value of WPM_ActiveWorkerProcessesLimit by 2, you must increase the value of WPM_WorkerProcessesThresholdLimit by 2.
<add key="WPM_CumulativeJobLimit" value="" />
Recommended for message based data: 10
The number of jobs processed, after which a worker process is recycled.
<add key="WPM_MinimumWorkerProcesses" value="" />
Governs the minimum number of worker processes for a 64 bit computer.
Governs the minimum number of worker processes for a 32 bit computer.
WPM_ActiveWorkerProcessesLimit and WPM_WorkerProcessesThresholdLimit are interdependent. The value of WPM_WorkerProcessesThresholdLimit must be greater than WPM_ActiveWorkerProcessesLimit. There must be a significant difference between the two values. If there is no significant difference, the performance is compromised, as large number of worker processes process less number of jobs, and the overall throughput is reduced
For data collection, using a CCS Manager with multiple roles such as collector, evaluation or reporting may affect the data collection performance. For message based data collection, Symantec recommends that you install a CCS Manager only with the Collector role.
Imported Document ID: HOWTO107210
Subscribing will provide email updates when this Article is updated. Login is required.