System Requirements
Minimum Software Prerequisites
The values listed below are the minimum requirements for running JAMS. These values may need to be adjusted based on the types of Jobs running in your environment due to the complexity of each Job.
When assessing performance in moderate and high-volume implementations, we recommend working with your Account Representative to define optimized specifications.
| JAMS Scheduler | JAMS Agent | JAMS Client | |
|---|---|---|---|
| Software Prerequisites |
|
|
|
| Hardware Server (minimum) |
|
|
|
| Hardware Server (50,000 to 100,000 Jobs per Day) |
|
|
|
| Hardware Server (>100,000 jobs per day) |
|
|
|
Permissions
To install JAMS, ensure that the user performing the installation is logged in as an account with administrator privileges to the server where JAMS will be installed. In addition, the account performing the install must have the ability to create a database on the database server. JAMS creates the database locally by default.
Prerequisites
Before installing JAMS, review the prerequisite software and minimum hardware requirements. The JAMS installer checks for all prerequisites.
.NET Requirements
The JAMS Client, JAMS Scheduler, and JAMS Windows Agent require .NET Framework 4.8. The JAMS Scheduler and JAMS Agent require the .NET 8 Hosting Bundle if they are running PowerShell Core Jobs.
If the .NET version is not installed, the JAMS installer displays a message, and you will need to manually download and install the correct .NET version. Go to the .NET Framework download site or .NET 8 download site to download the correct version.
Microsoft Message Queue (MSMQ)
The JAMS Scheduler requires the Microsoft Message Queue (MSMQ). When installing the JAMS Scheduler, the installer checks for the MSMQ and, if it's not installed, will enable it.
Microsoft SQL Server
The JAMS Scheduler requires Microsoft SQL Server 2022, 2019, 2017, or 2016. The SQL Server does not need to be installed on the same machine as the JAMS Scheduler. The database is fully supported in a clustered configuration.
JAMS Services rely on a connection to SQL to start properly, and they will fail to start if a SQL connection to a valid JAMS database cannot be made. When installing or updating your SQL Instance, review the startup sequence of the MSSQL Services and ensure they are set to an appropriate startup type, such as Automatic.
If you or your DBA choose to install the JAMS Scheduler component, the installer first checks for a connection to a SQL Server. If SQL Server is not installed locally, the installer prompts you to install the SQL Server 2022 Express Edition if the operating system is Windows Server 2016/Windows 10 or higher.
You also have the option of using SQL Server on a different machine. When the installer checks for the SQL Server, it only looks for the default instance names of MSSQLSERVER and SQLEXPRESS. If you have a different instance preference, decline the SQL Express installation (clear the check box) and specify your preferred instance in the SQL Server\Instance field.
If you have a different instance preference, decline the SQL Express installation and specify your preferred instance when the JAMS installer asks for the SQL server name and instance.
In order to create/update or run SSISDirect, SQLStoredProc, SQLAgent or SSRS Execution Method Jobs, the Client Tools Backwards Compatibility and Client Tools SDK Shared Features are required. Microsoft SQL Server 2019, 2017, or 2016 Shared Features are supported.
The Shared Features are required on the machine where the JAMS Client is running to create/update the Job Definitions and the machine where the Job executes to run the Job.
It’s best practice to run SSISDirect, SQLStoredProc, SQLAgent or SSRS Execution Method Jobs on the Server where those Jobs reside and the SQL Libraries are present.
PowerShell
JAMS Supports PowerShell V3 and higher.
The JAMS Client component includes a JAMS PowerShell Module that contains JAMS cmdlets and a JAMS Provider. PowerShell is not required, but you must install PowerShell before installing JAMS to use the JAMS PowerShell Module. If you install PowerShell after installing the JAMS Desktop Client, reinstall the JAMS Desktop Client to access the JAMS PowerShell Module.
Hardware Server Specifications for the JAMS Scheduler
- Processor: Dual Core ~2.5 GHz (x64)
- Memory: 8 GB
- Disk Space: 10 GB in addition to the disk space required by the OS.
These are the minimum system requirements that can support running thousands of Jobs per day. Heavy loads, for example, over 100,000 Jobs per day, require more resources.
For database planning, the JAMS test lab runs approximately 1,000 Jobs per day using one instance of JAMS. Retaining 30 days of information generates a database approximately 110 MB in size.
For Sites Running Over 100,000 Jobs Per Day
Based on customer implementations where more than 100,000 Jobs are executed each day, the JAMS installation should include:
- Two Windows servers, each with Dual Quad 3.2 GHz CPUs and 64 GB of RAM (or more).
- Specifically, one of the above servers hosting the JAMS Scheduler and the second server reserved for the SQL Server with multiple high-speed SCSI drives.
Hardware Server Specs for JAMS Agents
- Processor: 1 GHz (x64)
- Memory: 1 GB
- Disk Space: 300 MB in addition to the disk space required by the OS.
Hardware Server Specs for the JAMS Client
- Processor: 1 GHz (x64)
- Memory: 1 GB
- Disk Space: 500 MB in addition to the disk space required by the OS.
Supporting JAMS in a Virtual Environment
You can run JAMS on any supported operating system in a virtualized environment, such as VMware and HyperV. JAMS is supported in cloud-based environments such as AWS or Microsoft Azure. The JAMS database can be deployed into Microsoft Azure SQL Database or AWS RDS services.