Automic Supports your processes in several ways. The following listShows entities in a grid view provides an overview of the information and functions that are available.
It is important to plan how you will use the various functions. You can use the standard default values that are preset, or you can change them as desired.
Function |
Description |
---|---|
This chapter introduces the basic principles of AE. |
|
Utilities are provided for administrator activitiesDeployment-related activities. |
Function |
Description |
---|---|
Regular databaseA database is an organized collection of data including relevant data structures. maintenance is essential after AE system installation. |
|
Additional database maintenance activities are described here. |
Function |
Description |
---|---|
Various settings can be used to adjust AE to your environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.. The most important ones affect the whole AE system (UC_SYSTEM_SETTINGS), individual clients (UC_CLIENT_SETTINGS) and agents (UC_HOSTCHAR). |
|
AE processing considers TimeZones. |
|
Some important details should be noted. |
Function |
Description |
---|---|
Several server processes can be operated at once, thereby increasing system stability and distributing the workload. |
|
The number of server processes can be adjusted to your environment. |
|
This type of server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. is exclusively responsible for UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] messages. |
|
This feature focuses on system stability. |
Function |
Description |
---|---|
This clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. serves to administer system-internal objects and central settings. |
|
Includes information about your AE system. |
|
Can be used to stop and restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. processing. |
|
Use the ServiceManagerA program that facilitates the starts and stops of Automation Engine components. to start and stop components manually or via batch call. |
|
Start and stop the AE system in a controlled manner. |
|
Can be used to start, stop and monitor agents. |
|
components can also be started via the command line. |
|
Can be used to trigger external processes in your AE system via CallAPIs. |
Function |
Description |
---|---|
Stores objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task modifications so that they can easily be traced. |
|
Contains detailed information about object modifications and accesses. |
|
Provides an overview about tasks. |
|
Information about taskAn executable object that is running. Tasks are also referred to as activities. executions and reportA report provides more detailed information about a task's execution or a component. contents can be transferred to external Output Management Systems. |
Function |
Description |
---|---|
Provides controlled access to your AE system for users and components. |
|
You can check, admit or reject AE system logins. |
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |