Watch our short JAMS Architecture overview to understand how JAMS fits into your environment. (2:04)
Watch our other JAMS Videos at www.JAMSScheduler.com/videos.
In this video, we will take a look at the JAMS Architecture Diagram. The basic JAMS architecture consists of a Scheduling Engine, JAMS Agents, a SQL Database backend, and the JAMS Client.
The Scheduling Engine is the heart of JAMS. This heart directs all scheduling activities, including
dependency checking, load balancing and resource allocation, sending notifications, and managing the Job Schedule. The Scheduling Engine supports multitenant and clustered configurations.
JAMS Agents are the servers where Jobs run. Agents support installation on a multitude of operating systems and platforms, including virtual, cloud, or on-premises hosting. Agents execute and monitor jobs, capture log information and statistics, and report back to the Scheduling Engine all in real time. The Scheduling Engine may also act as a JAMS Agent.
All objects within JAMS are stored in a Microsoft SQL Database backend. This database feeds the historical reporting, graphical dashboards, and audit trail available for all of the various objects in JAMS.
JAMS Clients are the control centers for JAMS. The JAMS Desktop client is a Graphical user interface with streamlined controls and dynamic highlights. The JAMS Web Client mirrors the features and functionality available in the desktop client while giving users access to JAMS from any device or location, with no installation required.
JAMS also offers a .NET API, RESTful API, and 5 PowerShell modules with over 80 JAMS-specific PowerShell cmdlets, to offer through code the same extensibility available in the GUI.
For instructions and guidance on deploying JAMS, contact the JAMS Support team at support.jamsscheduler.com, or watch our other training videos, available at www.jamsscheduler.com.
The 2 main components of JAMS are the Scheduling Engine and the JAMS Agents.
The JAMS Scheduling Engine is where the schedule for your Jobs is managed, where dependencies are checked, where notifications are sent from, and so on. It can be a multitenant and clustered server.
Jobs can be set to run on the primary engine, though in many cases these Jobs will be offloaded to your remote JAMS Agents.
The JAMS Agents are what actually execute and monitor Jobs, capturing log information and statistics, and then reporting all of that information back to the Primary Engine in real time. The agents can be installed on a multitude of operating systems and platforms, regardless of whether they’re hosted in the cloud or within an on-premises datacenter.
All objects within JAMS are stored in a Microsoft SQL Database backend and JAMS also includes full historical reporting, graphical dashboards, and an audit trail for all of the various objects
JAMS is packaged with multiple client interfaces that give users access into JAMS.
Apart from the Windows GUI Client, there is a web interface with 1:1 FAT Client functionality, which gives you mobile extensibility, and 5 PowerShell modules including over 80 JAMS specific PowerShell cmdlets. This is an ever-growing library for us.
JAMS also includes two API’s; a .NET API and a RESTful API, both of which have 1:1 programmatic functionality, and give you the same extensibility to what’s available in the GUI.