System Client 0 - Administration Client

Client 0 is an administration Client available when you first install Automic Automation and contains some basic pre-configurations.

Only Automic Automation administrators should have access to Client 0.

This page includes the following:

Overview

Also referred to as the system Client, Client 0 is the administration Client used to manage internal objects and system-wide settings. As a system administrator, you use Client 0 to manage system-wide settings, that is to create, change and/or maintain login information, Calendars, Variables, other Clients, Users and User Groups and so on.

When you log in to for the very first time, you log in to Client 0 using the standard AWI login and the following login credentials for an on-premises or AAKE system:

  • User name: UC
  • Department: UC
  • Password: UC

Once logged in, you can only create new Clients and their first users in the system Client. You can later on move the Clients and assign them their respective users. Users that have sufficient rights can create all other users directly in the relevant Client.

Client 0 by default includes predetermined folder structures, different system Objects and Variables and so on, which are relevant for different components such as attribute dialogs, Calendars, headers and trailers for Jobs and variables, Agents and such.

The system Client has a monitoring function. Therefore, you cannot run objects in it. As an administrator, you will use the following AWI areas to monitor and administering the system:

  • Administration perspective 

    The Users section category contains all the AE users. As an administrator, you can process data and interrupt sessions from this central point.

    The Client section is only available in the system Client.

  • Process Monitoring perspective

    Lists the activities of all Clients depending on the specified filters.

  • Search

    You can only search and select Agent and Server objects in Client 0.

  • Selective Statistics

    You can use this function's numerous settings in order to search for statistical records across Clients.

Important!

  • Do not move the folders that contain the objects supplied with the Automation Engine. They are overwritten during a system upgrade regardless of where they are stored in the folder structure. The folders supplied by default are overwritten during an upgrade, which means that you cannot permanently change the default folder structure.

  • If you delete or rename an object in Client 0, the system will not check whether the affected object is also used in other Clients.

For more information, see:

Folders in Client 0

By default, Client 0 has multiple folders that contain objects and variables necessary for the configuration of the system. These are the folders:

Objects in Client 0

Certain objects contain data that is required by executable objects. For example, Connection and Login objects, which contain the necessary credentials and logging data that Job objects need to communicate with the target system. Or Calendars and Time Zones, which provide time frames that allow developers and object designers to build accurate schedules and time conditions.

These objects are created and maintained centrally in Client 0 by users with specific privileges. However, they are also available in the Combo Boxes of all other Clients so that developers and object designers can select them when they configure the objects, provided they have at least Read rights to those objects. It is also possible to open Client 0 objects in read-only mode from other Clients.You can use the OBJECT_ACCESS_CLIENT_ZERO key in the UC_SYSTEM_SETTINGS variable to grant User access to objects in Client 0 from other Client in protected mode.

Client 0 objects can be referenced in scripts in other Clients.

For more information, see:

The following list gives an overview of the types of objects that are relevant in Client 0:

  • Object types available only in Client 0

    Agents (HOST), Agent/Client Assignment (HSTA) and RA-Solution objects exist only in Client 0 and their configuration affects the whole system. They cannot be transferred to other Clients.

    The default Agent and RA-Solution objects available are delivered in their corresponding folder. Since there is no default Agent/Client assignment, the system includes a template of the Agent/Client Assignment (HSTA) object in the TEMPLATE folder for further use.

    For more information, see:

  • Predefined Calendar and Code Table Objects

    By default, Automic Automation includes predefined standard Holiday Calendars (CALE) for most national holidays and predefined Code Tables (CODE) for standard character conversion. You can use them as they are, or edit them to fine tune the system to your needs. These predefined objects are delivered in their corresponding folder.

    For more information, see:

  • Variables (VARA Objects)

    Automic Automation supplies system and Client VARA objects in Client 0 by default. Their configuration dictates the behavior of your system.

    Some of them must remain in Client 0 because they affect the entire system. Others can be transferred to other Clients because they contain Client-specific settings. If one of these VARA objects is not available in a Client (other than 0), the settings of that VARA object in Client 0 apply.

    The DIV_VARIABLES, EX_VARIABLES, and HOST_VARIABLES folders contain different variables by default.

    For more information on which VARA objects exist only in Client 0, which can be transferred to another Client, which are filled automatically and so on, see List of VARA Objects for System and Client Values.

  • Includes

    Client 0 provides predefined Job headers and trailers for different OS, platforms and applications that can be integrated with Automic Automation. They are supplied in Include (JOBI) objects which are delivered in the HEADER and TRAILER folders respectively. You can also use Includes (JOBI) to modify object attributes. Those Include objects are provided in the ATTRDIA folder.

    Use Include objects (JOBI) to store script blocks that you want to insert into the Process pages of different objects. This allows you to insert reusable script directly into the object properties.

    These objects are overwritten during an upgrade .

    Tip! It is best practice to work with User Includes to adapt the Job processing to your environment. These are not provided in Client 0 by default.

    For more information, see:

  • Object Templates

    Client 0 supplies a template object for each object type in the system in the TEMPLATE folder. Additionally, it includes the UC_OBJECT_TEMPLATE variable which allows you to specify which templates to use to create particular object types. The variable can be copied to other Clients and adjusted as needed making creating objects easier.

    This Variable (VARA) object specifies the templates to be used to create particular object types. It is supplied with Client 0 and can be copied to other Clients and customized as needed.

    For more information, see UC_OBJECT_TEMPLATE - Object Types and Templates.

  • System Objects: usually do not require configuration, see UC_ECC_PLUGINS (there is no doc here? because not user facing?)

  • Storage and Login Objects

    The UC_TRUSTEDCERTS Storage object is delivered by default with Client 0. It allows you to save the certificates that the Agents need in the Automation Engine.

    The UC_SMGR_LOGINS Login object is also delivered with Client 0. It stores the passwords that the Automation Engine uses when connecting to password-protected Service Managers. If this Login object is not defined, you cannot use AWI to start Agents or Server Processes controlled by the Service Manager.

    Both objects are stored in the DIV_VARIABLES folder.

    For more information, see:

Client 0 in AAKE

The Automic Automation Kubernetes Edition is an additional deployment option and gives you the same functionality as a regular on-premises system.

However, there are some configuration options that are not available for AAKE; therefore, all Objects, Variables, etc. pertaining to those configuration options are not relevant for an AAKE system.

These are:

  • Databases

    AAKE supports only Oracle and PostgreSQL databases. Therefore, all configuration options provided in Client 0 for DB2 and MSSQL databases are not relevant for AAKE.

  • Single sign-on

    You can set up LDAP or SAML for AAKE. Kerberos authentication is only supported in on-premises systems.

  • Password Vaults

    AAKE supports only CyberArk password vaults. CA PAM is only supported in on-premises systems.

  • Upgrade

    You can only upgrade an AAKE system manually. Zero Downtime Upgrade is not supported.

See also: