In a production environment consisting of a Windows-based production server or workstation (i.e. Windows Server 2003, Windows Server 2008, Windows XP, Windows Vista or Windows 7), an administrator installs AutoMate either onto an existing server, workstation or onto a standalone computer in which AutoMate tasks will be executed.
From the AutoMate Task Administrator console, a developer can create new tasks by pressing the New button (illustrated below) and place them in descriptive hierarchical folders appropriate to their use.
To aid in task A task is a series of steps designed to achieve some result. A task can be built to automate almost any business process. Tasks can perform file transfers, batch data processing, application testing, e-mail transmissions and much more. A task can be composed of a single step or hundreds of steps. Tasks can be started by a user or set to run automatically when triggered by a particular event. construction, an Add Task Wizard interface is enabled by default (as shown below).
After the developer names the task and clicks Next, the wizard then allows creation of the task steps, which are the step A task consists of a series of actions that are assembled sequentially in order toperform a process. Each action represents one "step" in the process.-by-step instructions made up of actions that are performed during task execution. Clicking the Create Steps button (shown below) launches the AutoMate Task Builder interface which is used to facilitate the construction and testing of task steps.
The Task Builder lets the developer select from a list of over 300 pre-built actions and activities. Actions include starting applications and sending keystrokes to it, transferring files via FTP, performing SQL queries and much more. To add a step, the developer selects it from the list of available actions located in the left window pane and drags it to the top-right window pane (illustrated below). This process is repeated for all the steps in a task. A task may contain an unlimited number of steps. Once this process is complete, the Task Builder can be saved and closed, returning to the Add Task Wizard. More on creating tasks
Thereafter, the wizard provides the developer an option to select which trigger AutoMate events that cause a task to run. These include a schedule, when a file is added, removed or modified, when the system is Idle, when an entry is written to the system event log, when certain hardware performance thresholds are reached, when a hot-key is pressed and much more. When a task is "triggered" the steps within the task are executed.(s) should launch the task automatically (shown below). A trigger is an event or condition that causes an AutoMate task to run. Triggers can be used alone or combined together to cause the task to launch if any of the trigger conditions occur. More on Triggers
After the developer selects the trigger(s) for the task, remaining options are set in the wizard and the task will appear in the list of available tasks in the Task Administrator. The Task Administrator can then be used to perform the following activities:
View and organize current tasks and folder structures.
Manually starting or controlling tasks.
Modify task properties, triggers and/or steps.
View the system Event-Log.
Connect to other AutoMate installations using Remote Administration.
What's New in AutoMate
Contacting Network Automation
Task Administrator Quick Tour
Task Builder Quick Tour
↑ Top of Page