In a production environment consisting of a Windows-based production server or workstation (i.e. Windows Server 2003, Windows Server 2008, Windows XP or Windows Vista), an administrator installs AutoMate either onto an existing server, workstation or onto new hardware in which AutoMate tasks will be executed on.
From the AutoMate Task Administrator console (shown below), the task developer can create new tasks and place them in descriptive hierarchical folders appropriate to their use.
To create each task, a wizard interface is used (as shown below). More on creating tasks using the wizard
After the developer names the task, the wizard then allows the creation of the task steps. Task steps are the step-by-step instructions (also known as actions) that AutoMate performs during task execution. Clicking the Create Steps button (shown below) launches the AutoMate Task Builder interface which is used to facilitate the construction of the task steps.
The Task Builder allows the developer to select from a list of over 230 available actions. Actions include starting applications, transferring files via FTP, performing SQL queries, sending keystroke 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 task steps
Thereafter, the wizard provides the developer an option to select which trigger(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
Schedule: Provides functions similar to a job-scheduler software. More Info
Event Watcher: Monitors the Windows Event-Log for specific events. More info
Process Watcher: Monitors an application’s state (i.e. process started, stopped or not responding). More info
Service Watcher: Monitors the state of a Win32 Service (i.e. service stopped or started). More info
Window Watcher: Monitors the system for the appearance/disappearance of certain windows or dialog boxes (such as error message dialogs or application windows). More on Window trigger
File Watcher: Monitors a folder for file system changes/additions and other attributes. More on File System trigger
Performance Watcher: Monitors critical system performance thresholds such as CPU usage or memory consumption. More on Performance trigger
SNMP Trap Watcher: Monitors for SNMP traps; useful for integration with other tools such as Microsoft MOM. More on SNMP Trap trigger
Key Watcher: Monitors for a certain hot-key combination to be entered. More on Key trigger
WMI Watcher: Monitors for a WQL query to return TRUE or more than zero rows. More on WMI trigger
Idle Watcher: Monitors for system idle states (i.e. no mouse or keyboard usage). More on Idle trigger
Startup Watcher: Monitors for the AutoMate task service to start or when a user logs onto the system. More on Startup trigger
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 7
Contacting Network Automation
Task Administrator Quick Tour
Task Builder Quick Tour