HCL Workload Automation, Version 9.4

Considerations in planning domains

There are a number of considerations that are to be taken into account when planning domains.

In planning your HCL Workload Automation network, consider the following:
Number of workstations, applications, and jobs
Consider the number of workstations that comprise the network and the number of applications and jobs that the network runs. If you have a small number of workstations, or a small number of applications to control, you do not need multiple domains.
Number of geographic locations
Consider the number of geographic locations covered by your network and the reliability and efficiency of communication between the locations. Multiple geographic locations is one of the primary reasons for choosing a multiple domain architecture. One domain for each geographical location is a common configuration. A single domain architecture relies on the network maintaining continuous processing.
Time zones
When your network is spread across multiple geographic locations in different time zones, decide whether to activate the time zone feature. See Time zone considerations.
Centralized or decentralized management
You can manage single or multiple domain networks from a single master domain manager. If you want to manage multiple locations separately, you can consider the installation of a separate HCL Workload Automation network at each location. Some decentralized management is possible in a stand-alone HCL Workload Automation network by mounting or sharing file systems.
Types of applications
Consider the types of applications that are run by HCL Workload Automation. If you have multiple applications that are distinctly separate from each other, you might choose to put them in separate domains.
Windows network
When you have a Windows network, you might want your HCL Workload Automation domains to mirror your Windows domains.
System performance and other criteria
You can define multiple domains to localize systems based on performance or operating system type.
Amount of network traffic
If your network traffic is manageable, having multiple domains is less important.
Dependencies between jobs
Consider if you need to plan for job dependencies that cross system boundaries, geographical boundaries, or application boundaries. For example, does the start of Job1 on workstation1 depend on the completion of Job2 running on workstation2. The degree of interdependence between jobs is an important consideration when planning your network. If you use multiple domains, try to keep interdependent objects in the same domain to decrease network traffic and improve the use of the domain architecture. See User's Guide and Reference.
Level of fault-tolerance required
A disadvantage of the single domain configuration is the reliance on a single domain manager. In a multi-domain network, the loss of a single domain manager affects only the agents in its domain.
When your network contains firewalls, plan the structure of your domains around the firewalls. See Administration Guide.
Secure Sockets Layer (SSL) or IBM® Global Security Kit (GSKit) encryption
If you want to use SSL or GSKit encryption in your network, plan your domains in accordance with the protocol.
Note: If you want to be compliant with Federal Information Processing Standards (FIPS), you must use GSKit. See Administration Guide.