Chatta subito con l'assistenza
Chat con il supporto

ControlPoint 8.7 - Administration Guide

Preface Configuring the Environment in Which ControlPoint Will Run The ControlPoint Configuration Site Managing Your Farm List Managing Your ControlPoint License Granting ControlPoint Access to Web Applications and Content Databases Configuring ControlPoint Services Using Discovery to Collect Information for the ControlPoint Database Cache Using Sensitive Content Manager Services Setting Sensitive Content Manager EndPoints and Managing Scanning Preferences Managing ControlPoint Configuration and Permissions Modifying ControlPoint Configuration Settings
Changing Default Settings for Actions and Analyses Changing Default Settings to Improve Application Performance Audit Log Configuration Settings Changing Settings for Anomalous Activity Detection Restricting Functionality for Members of the Business Administrators Group Changing Default Settings for ControlPoint User Groups Changing Settings to Improve Discovery Performance Changing Settings to Accommodate Special Environmental Factors Changing Default Settings for Navigation Managing Site Provisioning Settings Specifying Global Settings for ControlPoint Policies Setting Preferences for the ControlPoint Scheduler Miscellaneous and Custom Configuration Settings Special-Purpose Configuration Settings
Changing Trace Switch Logging Levels Archiving SharePoint Audit Log Data Troubleshooting
ControlPoint Log Files Troubleshooting Configuration Errors Troubleshooting the ControlPoint Application Interface Troubleshooting Discovery Troubleshooting SharePoint Users and Permissions Troubleshooting Site Provisioning Troubleshooting ControlPoint Operations

Operations Using Parallel Processing (ParallelProcs)

By default, ControlPoint Discovery processes up to two site collections/sites simultaneously, for improved performance over sequential processing.  For actions and reports, sequential processing is used by default (that is, the objects involved (site collection, site, subsite, lists, and so on) are processed one at a time, in hierarchical order).  ControlPoint Application Administrators may, however, choose to

·increase or decrease the maximum number of objects that should be processed simultaneously (i.e., in parallel), and/or

·specify the operation(s) (Actions, and/or Reports) for which parallel processing should/should not be used.

Specify the operations for which parallel processing should be used by completing the Value of the ControlPoint Setting ParallelProcs with one or more of the following values:

·A (Actions)

·R (Reports)

Enter multiple values as a comma-separated list.  

Config Setting ParallelProcs

For this setting to be operational, the Value of the setting Maximum Number of Objects to Processed in Parallel.

 

Objects Subject to Parallel Processing (ParallelProcSites)

By default, when Maximum Number of Objects to Process in Parallel is set to a value greater than 1, ControlPoint processes operations in parallel at the site collection level.  ControlPoint Application Administrators can, however, have parallel operations processed at the site level by changing the Value of the ControlPoint Setting Objects Subject to Parallel Processing from false to true.

NOTE:  This is an Advanced Setting.

Config Settings ParallelProcsSites

SQL Command Timeout Value (COMMANDTIMEOUT)

By default, the ControlPoint SQL Command timeout value is set to 300 seconds. This value represents the amount of time that ControlPoint will wait for a SQL command to run before issuing the following message:  

[Method Name]Timeout Exception:  The server has timed out.

The default value should be sufficient in most cases.  However, for an exceptionally large or busy farm, the ControlPoint Application Administrator may need to increase the Value of the ControlPoint Setting SQL Command Timeout Value.

NOTE:  This is an Advanced Setting.

Config Setting COMMANDTIMEOUT

NOTE:  Remember, this value is specified in seconds.

 

Maximum Number of Objects to Pass to the Selection Builder (MaxObjectsForSelection)

By default, when a ControlPoint user wants to initiate an operation from search or data analysis results, an unlimited number of SharePoint sites can be added to the Selection Builder.

Selection Builder

A large number of objects passed to the Selection Builder may, however, significantly drain system resources.  ControlPoint Application Administrators can limit the number of sites that are added to the SelectionBuilder by changing the Value of the ControlPoint Setting Maximum Number of Objects to Pass to Selection Builder.  (Note that 0 is used as the default value to represent "unlimited.")

Config Setting MaxObjectsforSelection

If the specified number is met, no additional sites will be added to the Selection Builder and the user will be presented with a warning message.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione