RiskVision uses system jobs to perform a variety of functions, including updating vulnerabilities, summarizing report data, and updating dynamic groups in program assessments. These jobs are scheduled to run automatically in the background on the server, or can be run manually. When dealing with large amounts of data, a particular job may cause services, such as Tomcat, to consume more memory and CPU. To avoid performance issues, you can run system jobs separately on a machine other than your RiskVision server using the RiskVision Job Manager.
When a scheduled job is triggered on the RiskVision server, the scheduler will verify which server the job should run on. When a job is scheduled to run on a separate machine, the RiskVision Server initiates a request to RiskVision Job Manager to run that particular job. The RiskVision Job Manager will process the request by triggering the job to execute on its scheduler. After the completion of job execution, data is saved back to the RiskVision Server. 
Running system jobs on a separate machine.
