Tidal Enterprise Scheduler
Tidal Enterprise Scheduler (TES) is a Job Scheduler originally created by Tidal Software, Inc. It was purchased by Cisco Systems and more recent versions are to be named Cisco Workload Automation (CWA). More recently this category of software is increasingly labeled as 'Workload Automation', which is an industry term for the next generation of job scheduling applications. It is comparable to BMC_Control-M or CA_Workload_Automation_AE.
The core functionality of TES is the ability to schedule batch jobs. It is designed to carry out repetitive tasks as defined in a schedule based upon calendar and event conditions. A calendar can be simple or intricate depending upon design.[1]
Tidal works as a distributed system that can be controlled from a centralized location (master server) which agents connect to. This allows batch jobs to be run, unattended in the background across a list of servers. [2]
Contents
Notability
Cisco Tidal Enterprise Scheduler is one of the oldest enterprise batch schedulers still in active production. It dates back to 1979 when it was originally created by Tidal Software in Palo Alto, California.[3]
It is used by a large distribution of organizations and has helped to define the industry. It is in use by over 400 orgainizations.[4]
In 2009 it was purchased by Cisco Systems where development continues. [5][6] Cisco is one of the largest and most well established organizations in the technology industry. Tidal is now offered as their primary workload automation solution.
Platforms
Batch jobs are scheduled and run across different operating system platforms and business application environments.
Agents are suported on the following platforms:
- Windows
- Linux
- zOS
- Open VMS
Advanced Features
Beyond simply running jobs, in the background, on a schedule, a more elaborate set of functionality is provided:
- Dependencies ( jobs, files, events )
- Users, permissions, authentication
- Master/Agent architecture - distributed environment
- Clustering with Master/Backup/Faultmon to prevent single point of failure[7]
Criticism
GUI Performance
Notable issues may include GUI performance and lag during user interaction. Performance of the interface may degrade when displaying large lists of jobs or agents. [8] No studies or benchmarks showing performance data have been published. Performance concerns may be highly dependent on underlying hardware and architecture implementations.
Bugs and Stability
Bugs and stability issues may exist. One example of these would be [9]
The Future
Tidal is geared towards supporting new technologies including cloud, mobile, and big data. It is designed for scalability and automation. It has been built to work as a component with Cisco's other technologies. [10][11]
See Also
[List of job scheduler software]
References
- ↑ http://www.duke.se/res/Tidal/Tidal-Enterprise-Scheduler-Brochure.pdf
- ↑ http://www.cisco.com/c/en/us/products/analytics-automation-software/tidal-enterprise-scheduler/index.html
- ↑ https://www.crunchbase.com/organization/tidal-software#/entity
- ↑ http://www-ti.informatik.uni-tuebingen.de/~spruth/edumirror/xx059.pdf
- ↑ https://www.bloomberg.com/research/stocks/private/snapshot.asp?privcapId=35569
- ↑ http://www.cisco.com/c/en/us/about/corporate-strategy-office/acquisitions/tidal.html
- ↑ http://www.cisco.com/c/dam/en/us/td/docs/data_virtualization/TES/TES-AAG.pdf
- ↑ http://tidal-enterprise-scheduler.com/what-is-tidal
- ↑ http://seclists.org/bugtraq/2017/Mar/60
- ↑ https://stackoverflow.com/tags/tidal-scheduler/info
- ↑ http://www.cisco.com/c/en/us/products/analytics-automation-software/tidal-enterprise-scheduler/index.html
