	Site Search:
Home Products Products Overview adTempus Report Commander Arcana Scheduler Support Support Home Knowledge Base License Management Contact Support Community Purchase Pricing and Ordering Additional Purchasing Information Contact About Us

adTempus

Job Scheduling and System Automation

System Requirements

This page discusses system requirements for adTempus 3.0. System requirements and supported platforms are the same for earlier versions of adTempus, except that no 64-bit version of adTempus is available before adTempus 3.0.

The 64-bit version of adTempus supports x64 platforms only; adTempus is not available for Itanium platforms.

Operating System

adTempus can be installed on computers running any of the following operating systems.

Windows XP. Windows XP Professional is supported. Other editions (Home, Tablet, Media Center) are not supported. 32-bit and 64-bit versions are both supported
Windows Vista. All 32-bit and 64-bit editions supported
Windows 7. All 32-bit and 64-bit editions supported
Windows Server 2003. All 32-bit and 64-bit editions supported
Windows Server 2008. All 32-bit and 64-bit editions supported.

Windows NT 4.0 is no longer supported by Arcana Development. Versions of adTempus through 2.0.4 function without know issues on Windows NT 4.0; customers may install adTempus on NT 4.0 at their own risk. Arcana Development no longer tests its software on this platform, and will not provide support for issues that are or may be related to running the software on Windows NT 4.0.

Windows 2000 is no longer supported by Arcana Development. Versions of adTempus through 3.0 function without know issues on Windows 2000; customers may install adTempus on Windows 2000 at their own risk. Arcana Development no longer tests its software on this platform, and will not provide support for issues that are or may be related to running the software on Windows 2000. Windows 2000 Requires service pack 4 or later. If you will be using the default SQL Server Express database provided with adTempus, make sure the following software is installed before you install adTempus, or the SQL Server Express portion of the adTempus installation will fail:

Internet Explorer 6.0 SP1 or later
Microsoft Data Access Components (MDAC) 2.8 SP1 or later. You can download MDAC 2.8 SP1 here

Database

adTempus uses a Microsoft SQL Server database to store data. By default adTempus will install and use an instance of Microsoft SQL Server 2005 Desktop Edition. You can also choose to use an existing SQL Server instance on the adTempus server or on a remote server.

Additional Software

The following additional software is also required:

Internet Explorer 6.0 or later (see http://www.microsoft.com/windows/ie to download).
The Microsoft Windows Installer (version 3.1 or later), which will be automatically installed or updated if necessary.
The Microsoft .NET Framework (version 2.0 or later), which will be automatically installed or updated if necessary.

Hardware Requirements

Following are the minimum hardware requirements for adTempus:

Processor: Intel Pentium class 133 MHz or greater (or equivalent). See performance note below.
RAM: 128 MB. 256 MB or greater recommended. See performance note below.
Disk space required for installation: 400 MB
Disk space required by application:
- Server installation: 70 MB, plus approximately 270MB for the SQL Server Express database engine.
- Client-only installation: 70 MB

Disk space notes:

The .NET Framework requires an additional 70 MB of disk space for either a server or client-only installation. This space must be available on the partition where the operating system resides.
adTempus can be installed to any hard disk partition, but includes many shared software components that will always be installed to the system partition. 50 MB free space (plus 70 MB for the .NET Framework, if it is not already installed) is required on the system partition.

Application Performance

As with most applications, the performance of adTempus will be greatly affected by the processor speed and available memory. Conversely, the resources required to support adTempus will depend on your scheduling load.

The main factors that affect performance are:

The total number of jobs configured
The frequency of job execution (this is the most significant)
The number of adTempus clients connected to the adTempus server

Each of these is discussed below.

Total number of jobs configured

The total number of jobs you have defined in adTempus will affect the size of the adTempus database. The job definitions ("templates") generally will not add significantly to the database size. However, the job history can greatly increase database size.

As the number of jobs increases, the performance of the adTempus Console (the client application) may degrade, resulting in processor usage spikes when the Console refreshes data from the server.

The total number of defined jobs does not, by itself, affect the performance of the adTempus server, as jobs do not consume processor resources except when they are being executed (see next section).

Frequency of job execution

Job definitions require disk space for storage, but do not consume processor resources (and therefore do not affect performance of the adTempus server) except when they are executing.

More specifically, adTempus performs processor-intensive work at four key points for each job: when the job starts; at the start and end of each step in the job; and at the end of the job. Outside these times, no processor resources are devoted to a job. For example, if you have a one-step job that runs for 3 hours, adTempus will use processor resources when it starts your program and when your program ends, but for the 3 hours in between the job will not consume processor resources.

Therefore the most significant determinant of the load placed on the adTempus server is the number of jobs that are being started at the same time. For example suppose you have 20 jobs that need to be run every hour. If all 20 of these jobs are scheduled to start at 5 minutes past the hour, the load on the server would be roughly 20 times the load that would occur if you staggered these jobs to start one to two minutes apart.

Number of adTempus clients connected to the adTempus server

Each adTempus client that connects to an adTempus server puts a small load on the server each time the client refreshes data from the server. With a large number of clients refreshing frequently (the default setting is every 5 seconds), this may become a significant factor.