An AE system's 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. 0000 is also referred to as the system client. It is used to administer system-internal objects and central settings. Some settings affect all existing clients if there are no local specifications that have been made. Only the administrator is authorized to make modifications and extensions.
When you log in to the to the system client for the very first time, you use the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. "UC" (departmentDepartment name to which the Automation Engine user belongs. and passwordA secret combination of characters for a Automation Engine user. are also "UC"). This user has all authorizations and privileges. For security reasons Automic recommends changing the password immediately.
When you have logged on, you can create new clients and their first users only in the system client. Then you use the context menu command Move user to client ... and assign the users to the related clients. Provided that the individual user has sufficient rights, s/he can create all other users directly in the relevant client.
The system client 0000 includes many system objects such as attribute dialogs, calendarsShows a calendar overview of activities, releases or reservations., headers and trailers for jobs and variables. You use the variables to configure your AE system. Other important system objects are the ERP_LOGIN that contains the central loginAn Automation Engine object type that stores account credentials used by agents on target systems. information for SAP and PeopleSoft, and the individual Agent objects.
Folder |
Description |
---|---|
ATTRDIA |
Attribute dialogs for file transfers and jobs. |
CODETABLE |
CodeTables for file transfers and jobs. |
CONNECTIONS | Connection objects |
DIV_VARIABLES |
Various variables |
EX_VARIABLES |
variables especially for agents. |
HEADER |
Header includes for jobs. |
HOLIDAY_CALE |
Calendars that include holidays and other useful calendar keywords. |
HOST |
Objects of the installed agents and standard templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion.. |
HOST_VARIABLES |
variables especially for computers. |
PREP_PROCESS |
|
RA_SOLUTIONS | RA Solution objects. |
RESTART |
Restart includes for jobs. |
STYLESHEETS | Stylesheetsfor XML reports. |
TEMPLATE |
Templates for objects. |
TRAILER |
Trailer includes for jobs. |
Do not move the supplied folders. All the supplied objects of system client 0000 will be deleted when you update your system regardless of where they are stored in the folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. structure. A new folder structure will be created during the updating process that includes the supplied objects. This means that you cannot permanently change this part of the folder structure.
The system client has a monitoring functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,…. Therefore, you cannot run objects in it. It includes the following additional functions that can be used to administer your AE system:
Note that searching and selecting Agent objects and Server objects will only be successful in the system client.
If you delete or rename an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task in the system client, the system will not check whether the affected object is also used in other clients.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |