TWS is composed of three major parts:

1. IBM Tivoli Workload Scheduler engine. This is local client installed on

every workstations which belong to the scheduling network (UNIX,
Windows). When the engine is installed on a workstation, it can be
configured to play a specific role in the scheduling network. For example,
the engine can be configured to be a master domain manager, a domain
manager, or a fault-tolerant agent. In an ordinary Tivoli Workload Scheduler
network, there is a single master domain manager at the top of the network.  
 
2. IBM Tivoli Workload Scheduler connector. The connector "connects" the
Job Scheduling Console to Tivoli Workload Scheduler, routing commands
from JSC to the Tivoli Workload Scheduler engine. It is usually installed on
the master domain manager (MDM).  
 
3. Job Scheduling Console (JSC). JSC is a primitive, low quality Java-based
graphical user interface. It is typically installed on Windows workstations.
Installation usually causes no problems.  It provides, through the Tivoli
Workload Scheduler connector, a very limited subset of functions of the
command-line programs conman and composer.

Components

A Tivoli Workload Scheduler network is made up of two main components:

 Master Domain Manager (MDM) The master domain manager is

centerpiece of TWS network. It contains the centralized database files used
to document scheduling objects. It creates the production plan, distributes it
to all the agents in the network at the start of each production day, and
performs all logging and reporting for the network.
 Fault-tolerant Agent (FTA) A client capable of resolving local
dependencies and launching its jobs in the absence of a domain manager.
 Standard Agent A client that launches jobs only under the direction of its
domain manager.

The workstation types can assume the following roles:

 Domain Manager A fault-tolerant agent that is the management hub in a

domain. All communications to and from the agents in a domain are routed
through the domain manager.
 Backup Domain Manager A fault-tolerant agent capable of assuming the
responsibilities of its domain manager.
 Backup Master A fault-tolerant agent capable of assuming the
responsibilities of the master domain manager.
  Host The scheduling function required by extended agents. It can be
performed by any Tivoli Workload Scheduler workstation, except another
extended agent.
 Extended Agent A logical workstation definition that enables you to launch
and control jobs on other systems and applications.
 Network Agent A logical workstation definition for creating dependencies
between jobs and job streams in separate Tivoli Workload Scheduler
networks.
 Connector. The Job Scheduling Console connects to the engines through
the Job Scheduling Services and the relevant connector.  The Job
Scheduling Console communicates with the system through so called
Connector, a protocol converter that translates the instructions entered
through the Job Scheduling Console into scheduler commands.

The Most Important TWS Scheduling Terms

The following four terms are frequently used in TWS documentation:

 Workstations. Workstations represent the physical or logical nodes where

jobs are to be scheduled.
 Jobs A job is an atomic unit representing  executable process (OS
command, executable or script) that is controlled by the Tivoli Workload
Scheduler. Jobs, their scheduling data, and their dependencies are grouped
together in job streams.
 Job streams. Job streams are a collection of jobs together with their
scheduling and dependency information.
 Resources. In the Job Scheduling Console, resources are the physical or
logical elements that are used by jobs. You need to define resources in the
database prior to defining the jobs that will use them.
 Production day  and production plan.  Production day define the main
repeatable cycle used by TWS with particular start time and length (the
default is start at 6am and length 24h).  The production plan is the master
control for the current production day and physically corresponds to so
called Sinfonia file on the master domain manager. See TWS Scheduling
Concepts

Additional TWS Terminology

Like most IBM products TWS uses  a lot of somewhat strange additional
terminology

Workstation Classes

A workstation class is a group of workstations. For example you can have

 Classes based on type of OS installed: Solaris, AIX, HP-UX, Linux  and
Windows. Any number of workstations can be placed in a class.  

Job streams and jobs can be assigned to run on a workstation class, creating
possibility to use different jobs for different types of operating systems and
like.

 Note: If a job stream is defined on a workstation class, each job added to the job
stream must be defined either on a single workstation or on the exact same
workstation class that the job stream was defined on.

Domains
A domain is a named group of Tivoli Workload Scheduler workstations,
consisting of one or more workstations and a domain manager acting as the
management hub. All domains have a parent domain, except for the master
domain. 
 
Calendars
A calendar is a list of scheduling dates defined in the scheduler database.
Assigning a calendar run cycle to a job stream causes that job stream to be
run on the days specified in the calendar. Since a calendar is defined to the
scheduler database, it can be assigned to multiple job streams.  
 
Prompts
Prompts are used as dependencies for jobs and job streams. A prompt must
be answered affirmatively for the dependent job or job stream to launch. For
example, you can issue a prompt to make sure that a printer is online before
a job that prints a report runs. 
 
Parameters
Parameters are used to substitute values in jobs and job streams. Since
parameters are stored in the Tivoli Workload Scheduler database, all jobs
and job streams that use the particular parameter are updated automatically
when the value changes. For scheduling, a parameter can be used as a
substitute for all or part of:

 File dependency path names

 Text for prompts
 Logon, command, and script file names
 

Files
Files are dependencies whose existence a job or job stream must verify
before they can start.
Lists
Lists are filters that allow objects in the database and in the plan to be filtered. There are standard
default lists available in the Job Scheduling Console, or you can create lists that are specific to your
needs.

Database
The scheduler database stores scheduling object definitions. Examples of common scheduling object
definitions are:

 Workstations
 Resources
 Job Streams