Sizing

As each customer typically has different scheduling requirements, it can be difficult to recommend specific configurations of hardware and software. That said, this section provides a representative example of the average resources needed for a production server.

 

Job Scheduler System

 

The configuration below assumes that the Job Scheduler will communicate with its backend database and distribute jobs to their associated Execution Agents based on the various triggers available within the system. We further assume that small to minimal job execution will occur on this machine (excluding the normal ActiveBatch housekeeping jobs such as DBPurge). For an environment running 15,000-30,000 Job Instances per day, the Job Scheduler machine, running a Windows Server platform, in a production environment will need:

 

• CPU: 4 CPUs (Quad core or greater)

• Memory: 8Gb RAM or greater

• Storage: 1-5Gb

 

Backend Database

 

The ActiveBatch Backend Database stores all ActiveBatch object, history, audit and revision information. The database software can be any supported Microsoft SQL Server Standard Edition or Oracle (as noted and supported in the sections above). Database requirements for the Job Scheduler load listed above is:

 

• CPU: 4 CPUs (Quad core or greater)

• Memory: 8Gb RAM or greater

• Storage: 200Gb

   

Execution Agent

 

The Execution Agent is responsible for the execution of ActiveBatch jobs. The CPU and storage footprint is minimal and therefore no special consideration is required for that machine based on the Job Scheduler load listed above.