EnterpriseSCHEDULE Job Scheduling Architecture
Client/Server Design
EnterpriseSCHEDULE job scheduling software features a cooperative architecture through heterogeneous or homogeneous servers talking to each other. This distributes processing and is extremely fault tolerant (no single point of failure as in Master/Agent job scheduler architecture).
1. Server to Server design
- Cooperative Architecture
- Fault tolerant (no single point of failure)
- Distributes processing (highly scalable)
2. High Availability fault tolerant server logic
- Multiple level exception handling at code level
- Handles system errors and unforeseen errors
- Server rollover at cluster level
- Definable server activity classes
Examples
Using the Windows Client software, any number of servers can be connected to, in a single or multiple desktop sessions. The client/server architecture allows you to add additional machines to your IT enterprise while easily managing their batch job scheduling from one central client.
Job Scheduling Database
The EnterpriseSCHEDULE job scheduling database is embedded, independent and complete. Support for a third party database is not required.
Object oriented data set makes for better organization
The EnterpriseSCHEDULE job scheduling database is organised to keep jobs, calendar definitions, variables and other data in an object-oriented fashion that makes accessing and modifying data easier. This also helps prevent data redundancy by allowing for a single instance of calendars, variables etc. that can be accessed by multiple jobs. This object approach means that when a calendar is saved in one place, all deployed jobs using that calendar automatically reflect any changes made to the calendar.
Distributed, Centralised or Replicated job scheduling database
1. Distributed database
Allows for individual nodes to store their own scheduling data (jobs, calendars, variables, etc.) in a peer to peer network or limited cluster. The peer to peer relationship allows servers to coordinate batch processing and communicate across platform boundaries – VMS, Windows, Linux and UNIX.
2. Centralized database
Is a single database in an OpenVMS, Microsoft Windows or UNIX cluster, providing a central location for the storage of scheduling data.
3. Replicated database
Is used to maintain a copy of the data set on all nodes in a job scheduling Workgroup, providing excellent fault tolerance.
