Option
| Valid
Arguments
| Behavior
|
-threads
| number
| Use a thread pool of the specified size. The default is one thread per request.
|
-reinitializedb
|
| Cause the CMS to delete the system database and recreate it with only the default system objects.
|
-quit
|
| Force the CMS to quit after processing the -reinitializedb option.
|
-receiverPool
| number
| Specify the number of threads the CMS creates to receive client requests. A client may be another Crystal server, the Report Publishing Wizard, Crystal Reports, or a custom client application that you have created. The default value is 5. Normally you will not need to increase this value, unless you create a custom application with many clients.
|
-maxobjectsincache
| number
| Specify the maximum number of objects that the CMS stores in its memory cache. Increasing the number of objects reduces the number of database calls required and greatly improves CMS performance. However, placing too many objects in memory may result in the CMS having too little memory remaining to process queries. The upper limit is 100000.
|
-ndbqthreads
| number
| Specify the number of CMS worker threads sending requests to the database. Each thread has a connection to the database, so you must be careful not to exceed your database capacity. In most cases, the maximum value you should set is 10.
|
-AuditInterval
| minutes
| Specify interval at which the CMS requests audit information from audited servers. The default value is 5 minutes. (Maximum value is 15 minutes, and minimum value is 1 minute.)
|
-AuditBatchSize
| number
| Specify the maximum number of audit records that the CMS requests from each audited server, per audit interval. The default value is 200 records. (Maximum value is 500, and minimum value is 50.)
|
-auditMaxEventsPerFile
| number
| Specify the maximum number of records in the audit log file. The default value is 500. If the number specified by -auditMaxEventsPerFile is exceeded, the server opens a new log file.
|
-AuditeeTimeSyncInterval
| minutes
| Specify the interval between time synchronization events. The CMS broadcasts its system time to audited servers at the interval specified by -AuditeeTimeSyncInterval . The audited servers compare their internal clocks to the CMS time, and then adjust the timestamps they give to all subsequent audit records so that the time of these records synchronizes with the CMS time. The default interval is 60 minutes. (Maximum value is 1 day, or 1440 minutes. Minimum value is 15 minutes. Setting the interval to 0 turns off time synchronization.)
|