Cisco Tidal Enterprise Scheduler Essential Knowledge Guide
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- June 8, 2015
Chapter: Product Overview
Product Overview
The purpose of this guide is to help you get started using TES after you’ve installed it using the Cisco Tidal Enterprise Scheduler Installation Guide. This guide provides information about getting help if you have problems, how to help yourself, the basics of starting/stopping components, and some of the basic tasks you perform when you start using TES to schedule and monitor jobs.
This chapter gives you a quick overview of the TES components.
Note
Before you start to work through this document, use the Cisco Tidal Enterprise Scheduler Installation Guide to install TES.
About TES
Cisco Tidal Enterprise Scheduler is an automation platform for cross-application and cross-platform enterprise workloads, batch job scheduling, and data and application integration. Cisco TES can easily configure and run scheduled batch workloads and event-based business processes, integrate the commercial and custom applications these processes use, and determine which tasks to run, as well as where and when to run them, without the need to manage scripts or customize existing tools. Additionally, the enterprise scheduler provides a single view and point of control over business processes and the jobs they comprise.
Based on a highly scalable multi-tier Java architecture, Cisco TES can scale to deliver the most demanding SLAs, because it is capable of handling hundreds of concurrent users, managing thousands of connections, and running hundreds of thousands of jobs a day. The TES enterprise scheduler offers a distributed management architecture that works across many popular OS platforms and integrates with major enterprise applications and technologies.
Cisco TES can also manage complex application integrations that connect through web services and enterprise service bus (ESB) protocols. Cisco TES can be implemented quickly, allowing users to maximize time to value, build momentum across their organizations, and quickly simplify their entire workload processing environment.
TES Components
As described in the Cisco Tidal Enterprise Scheduler Installation Guide, a basic TES system is composed of a number of required, optional, and 3rd-party components as shown here:
Figure 1-1 Basic TES Components
For the purposes of this document which is focused on giving you the basic information you need to get started and be successful with TES, the components you will be working with are the TES Web or Java Client, the Primary Master, the Client Manager, and the Agents and Adapters. A brief description of these components is described below. See the Cisco Tidal Enterprise Scheduler Installation Guide for descriptions of all components.
Master (or Primary Master)
The Master is the primary TES component that conducts all scheduling tasks. You can have one or more Masters in your network. The Master can be installed on either the Windows platform or the Unix platform. The basic functionality of TES remains the same regardless of the platform of the Master.
Each Master computer must supply a unique port number to which Client Managers connect. This port number ensures that communication between the Client Manager and Master is clear.
Client Manager
The Client Manager allows the Master to achieve higher performance and scalability. The purpose of the Client Manager is to service requests from user initiated activities, such as through the TES Web Client, Tidal Transporter and from other external sources that utilize the Command Line Interface (CLI) or published TES Web services. The Client Manager allows the TES Master to focus more capacity on core scheduling needs related to job execution and job compilations, while the Client Manager addresses demands from activities such as users viewing/configuring scheduling data and output. The Client Manager constantly syncs the information from the Master database into its own TESCache database that it then uses to provide all TES Web Client users with current information. Multiple Client Managers connected to the same Master can be deployed to address additional performance needs.
The Client Manager is required if you want to use the TES Web Client, the Transporter, the Command Line Interface (CLI), REST, or mobile applications. The Client Manager is not required if you are only using the Java Client.
TES Web Client
The TES Web Client is the main user interface for managing TES jobs, scheduling, connections, configuration, and so on. The TES Web Client connects to the Client Manager using a browser.
You can use both the TES Web Client and the TES Java Client with the same Master.
TES Java Client
The TES Java Client is a standalone application that provides the same user interface as the TES Web Client to manage TES jobs, scheduling, connections, configuration, and so on. However, the Java Client connects directly to the TES Master and not through the Client Manager. You can run the Java Client as an application, or you can launch it using a browser.
The TES Java Client is typically more responsive than the TES Web Client because it is connected directly to the Master. However, this increases the RAM used by the Master process as the Master is now doing the work instead offloading it to the Client Manager.
You can use both the TES Java Client and the TES Web Client with the same Master. Note that an environment exclusively using the TES Java Client will not be able to utilize features that require the Client Manager like the Transporter, Command Line Interface, and the WebService API.
Agents
An agent is a separate installation of TES that runs jobs on behalf of the Master. Agents help you to automate the execution of jobs that you know need to be performed on a regular basis, Offloading jobs to agents frees the Master for intensive scheduling tasks such as production compiles. Agents exist for various platforms. The Windows Agent and the Unix Agent are the two most commonly used agents.
Each agent can connect to a Master by specifying the Master-to-agent communication port and the Master-to-agent file transfer port numbers.
Adapters
TES provides adapters for many software products to enable connectivity to and access by TES. The Master has an Adapter Host it uses to manage the adapters and is the interface that the adapters use to connect to the Master. Adapters are provided with the base TES installation but must be licensed. In some cases, adapters need to be installed or configured.
Feedback