All the workstations in a distributed HCL Workload Automation network
are organized into one or more domains, each of which consists
of one or more agents and a domain manager acting as the management
hub. Most communication to and from the agents in the domain is routed
through the domain manager. If the agent has the "behind firewall"
designation, all of it is.
All the networks have a master domain where the domain manager
is the master domain manager. It maintains the database of all the
scheduling objects in the domain and the central configuration files.
The master domain manager generates the plan and creates and distributes
the Symphony file. In addition, logs and reports for the network are
maintained on the master domain manager.
You can organize all the agents in your network into a single domain
or into multiple domains.
Single-domain network
A
single domain network consists of a master domain manager and any
number of agents. Single-domain
network shows
an example of a single-domain network. A single-domain network is
well suited to companies that have few locations and business functions.
All the communication in the network is routed through the master
domain manager. With a single location, you are concerned only with
the reliability of your local network and the amount of traffic it
can handle.
Figure 1. Single-domain
network
Multiple-domain network
Multiple-domain
networks are especially suited to companies that span multiple locations,
departments, or business functions. A multiple-domain network consists
of a master domain manager, any number of lower tier domain managers,
and any number of agents in each domain. Agents communicate only with
their domain managers, and domain managers communicate with their
parent domain managers. The hierarchy of domains can have any number
of levels.Figure 2. Multiple-domain
network In Multiple-domain
network, the master
domain manager is located in Atlanta. The master domain manager contains
the database files used to document the scheduling objects, and distributes
the Symphony file to its agents and to the domain managers in Denver
and Los Angeles. The Denver and Los Angeles domain managers then distribute
the Symphony file to their agents and subordinate domain managers
in New York, Aurora, and Burbank. The master domain manager in Atlanta
is responsible for broadcasting inter-domain information throughout
the network.
All the communication to and from the New York domain
manager is routed through its parent domain manager in Denver. If
there are schedules or jobs in the New York domain that are dependent
on schedules or jobs in the Aurora domain, those dependencies are
resolved by the Denver domain manager. Most inter-agent dependencies
are handled locally by the lower tier domain managers, greatly reducing
traffic on the network.
You can change the domain infrastructure dynamically as you develop
your network. You move a workstation to a different domain, by changing
the domain name in its database definition. The change takes effect
when the master generates/extends the plan.
Note: You cannot schedule jobs or job streams to run on all workstations in a domain by identifying
the domain in the job or job stream definition. To achieve this, you must create a workstation
class that contains all the workstations in the domain.
For more information about domain definitions,
see "Defining objects in the database" in the User's Guide and Reference.
For more information about workstation classes,
see Workstation class
