Multi-machine Execution

A multi-machine workflow is a workflow that is designed to execute on more than one machine. Unlike the common idea of being able to assign an individual task to execute on remote machines, AutoMate BPA Server 9 carries the concept to a higher level by allowing a developer to assign each distinct event, condition, task or process residing in the same workflow to execute on different machines.

In this concept, the workflow itself is always managed by the BPA Server 9 component, however, the objects, such as tasks, events and conditions, which are contained inside the workflow can be allocated to run on different machines by means of assigning an Agent or Agent Group to each object. This permits a single workflow the capability to monitor for certain events or conditions to occur and execute tasks on separate machines located in different physical locations, while all being a part of the same process.

AutoMate BPA Server 9's multi-machine execution capability is made possible in part by Agents that are deployed or installed on remote machines and their facility to interact with the server component. Once installed or deployed, the server component can connect with the Agent via TCP/IP (whether that machine is local or situated remotely), and notify it of what system conditions or network events to monitor along with what tasks to execute as a result of such conditions or events.

The Workflow Designer is the key component that enables developers to specify which AutoMate Agent(s) to monitor assorted conditions and execute various tasks within a given workflow. Upon adding a workflow object to the WFD's Workspace, the names of connected Agents appear in a list (directly below the object's assigned name) and the developer basically selects the appropriate Agent in which to run that task or evaluate the specified event or condition.

An example of a multi-machine workflow is shown below. Within each task, a separate Agent name is allocated under the task name (circled in red). In this scenario, the initial task (named Select Machine) set to run on one Agent is followed by an Evaluation object that determines which of three other Agents should execute its assigned task depending on which evaluation amounted to TRUE.

An example of a multi-machine workflow is shown below. Within each task, a separate Agent name is allocated under the task name (circled in red). In this scenario, the initial task (named Select Machine) set to run on one Agent is followed by an Evaluation object that determines which of three other Agents should execute its assigned task depending on which evaluation amounted to TRUE.

The server component can communicate and perform a number of procedures on multiple Agents, all within the same time frame, allowing the ability for large enterprises to streamline numerous processes and operations in diverse locations with reliable, repeatable and error-free automation.

Any actions performed by Agents are communicated in detail back to the Server component in real time. In accordance, the Server component relays the information to the end-user via the SMC’s Output/Execution Status window and logs the data into a comprehensive set of reports which can be viewed from the SMC’s Reports section. This provides the ability for end-users to monitor the status of any jobs performed in a timely manner, whether locally or remotely.

See Also


Workflows | Workflow Logic | Building a Workflow | Workflow Logic