EnterpriseSCHEDULE
Database

The EnterpriseSCHEDULE database is embedded, independent and complete. There is no need for a third party database support necessary

Object oriented data set makes for better organization

The EnterpriseSCHEDULE database is organized to keep jobs, calendar definitions, variables and other data in an object oriented fashion that makes accessing and modifying data easier. All objects are organized in easy to access directories (folders in Windows) that classify all objects by type. In the Windows Explorer, all objects are subcategorized in a folder according to type. Jobs can be stored by category, job stream or whatever means desired.

Object oriented categorization also helps prevent data redundancy by alowing for a single instance of calendars, variables etc. that can be accessed by multiple jobs. This object approach means thatwhen a calendar is saved in one place, all deployed jobs using that calendar automatically reflect any changes made to the calendar

A configurable central database

Distributed or centralized support means the EnterpriseSCHEDULE database can be configured across a network of systems either as a centralized network with satellites or as a group of peer-to-peer databases. The entire EnterpriseSCHEDULE database is organized into directories. Any number of directories can be created. Any number of concurrent users can use the system. Access to the job database is controlled from platform-dependent security methods and platform spanning ACLs.

Distributed, Centralized or Replicated database

1. Distributed database allows for individual nodes to store their own data (jobs, calendars, variables etc.) in a peer to peer network or limited cluster
2. Centralized database is a single database in a cluster providing a central location for the storage of data
3. Replicated database is used to maintain a copy of the data set on all nodes in a job scheduling Workgroup thus providing excellent fault tolerance

Database Design

1. Embedded data
   The EnterpriseSCHEDULE database is embedded, independent and complete. There is need for third party database support necessary
2. Object oriented data set
   Database is organized to keep jobs, calendar definitions, variables and other data in an object oriented fashion that makes accessing and modifying data easier
3. Comprehensive Data set security
   Allows the assignment of multiple levels of access to the jobs, directories, calendars etc. to determine who can submit or modify jobs