User Guide > Objects > Alphabetical Listing > Client

 Client

The "Client" objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task defines a self-contained 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. within an AE system. In this environment, you can control and monitor the tasks of the connected computers.

Object class: System object
Object type (short name):
CLNT

A Client object is the first object that must be created before you can start working with AE. Within an AE system, a 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. is clearly identified by its four-digit client number. You can select any number between 0001 and 9999. All other objects of an AE system object (Users, UserGroups, TimeZones, Jobs, Workflows, etc.) are always directly assigned to a particular client.

Clients are defined in the system client 0000. You can create a new client environment by creating a new Client object that must be renamed afterwards. Select a four-digit name for this new Client object.

Note that the Client object is moved to the client environment after it has been renamed. You can edit it subsequently in the System OverviewThe UserInterface window that contains information about the Automation Engine system..  Select "Client" from the context menu and edit the corresponding client using the command "Edit" (right-click the mouse). Alternately, you can log on to the client with a 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. and edit the Client object that is stored in <No 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.>.

When you log on to an AE system's system client 0000 for the first time, you can use the User object "UC/UC" in combination with the passwordA secret combination of characters for a Automation Engine user. "UC". Automic recommends changing this password immediately after you have logged on for the first time.

System Client 0000

Client 0000 of an AE system is also referred to as the system client. You can use this client to administer the system-internal objects and key settings. Some settings affect all existing clients unless they have been excluded by using local settings and options. Only administrators can change or extend system-client settings.

All other clients and selected users with administrative rights for local clients are created in the system client.

Some of the system client's internal objects are overwritten when an AE update installation is made and can disappear.

Local Clients 0001 to 9999

Client numbers that range from 0001 to 9999 are referred to as local clients. Some client settings can also be changed locally (in the client itself). For this purpose, you required the relevant rights. Client numbers cannot be changed within local clients.

Some of the objects that are supplied in system client 0000 can be overridden by objects that exist in local clients of the same name. Therefore, you can define settings for each local client which differ from the system client.

 

See also:

User
User Group

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH