CA Workload Automation DE Solution Overview
The functionally rich multi-tiered architecture of the CA Workload Automation DE (dSeries Edition) solution aims to eliminate the complexity and cost associated with the management of multiple and differing job scheduling solutions. It assists with reducing the amount of manual intervention associated with workload management and job scheduling through some key differentiating capabilities.
The terminology, basic components, and architecture of the CA Workload Automation DE Framework are as follows:
image to go here...
CA Workload Automation DE Server (the “Manager):' A CA Workload Automation DE Server runs on a distributed platform and serves as the central point of control for all workload on all the other platforms/servers in the enterprise. CA’s Workload Automation Server is aware of the global environment, make decisions and issue commands. It serves as the decision-maker, determining when a job is eligible to run based on predecessor requirements, available logical resources, date/time, and feedback from System Agents, file or database activities, etc. The CA Workload Automation Server is responsible for orchestrating all of the workload through the Agent Technology and as such is able to monitor SLAs and proactively raise alerts when business processes start to go wrong. An optional High-Availability Server provides seamless failover and fall back capabilities should the primary scheduling server fail for any reason.
System Agents: The CA Workload Automation ''System Agent'' is an intentionally small program that resides on any server platform (real or virtualised) that needs to orchestrate business process workloads. The agent is aware of the local environment, acts on commands received by the ''CA Workload'' ''Automation'' ''Server'' and forwards status information back to the Server. A wide range of CA dSeries Agents exist covering most commercially available computing platforms.
CA Workload Automation DE Desktop Client GUI: The CA Workload Automation Desktop Client GUI is an Eclipse-based interface. As the primary user interface, it is used to define, monitor, and manage the organisation’s workloads. A Command Line interface allows commands to be invoked from command lines or scripts, and a Web User Interface allows monitoring of workloads from a web browser.
All components within this Automation Framework communicate through TCP/IP. These “plain text” messages are encrypted for security purposes. At installation time, each site selects a unique encryption key to be used for the encryption of all these messages. Agents listen on a TCP/IP port waiting for instructions to perform some type of work. Once a job starts executing, the agent formats and transmits a message back to the CA Workload Automation Server so that the job’s status can be updated. It uses the same encryption method, via TCP/IP, that sent the message to the agent in the first place.
Workload Objects: Workload Objects are a representation of the managed work, such as the execution of a program or a script, the detection of a row added to a database, the presence/absence of specific information in a file, the invocation of a session bean, the expansion of a file by a certain percentage, and many other conditions.