Clients

Clients are the largest logical organizational units within Automic Automation. Each Client represents a self-contained environment, enabling organizations to partition automation resources and administrative domains based on business needs or operational boundaries. This segmentation facilitates clear separation of data, configuration, user management, and security policies.

Every Client is identified by a unique four-digit Client number. Special consideration is given to Client 0 (also known as Client 0000), which is reserved for system-wide administration and global settings applicable across all Clients. Client 0 is always already available in fresh installations.

Purpose and Benefits

• Separation of Environments: Clients allow distinct business units, projects, or departments to operate independently within the same Automic Automation system.

• Customized Configuration: Each client can have tailored settings such as language, templates, and authorizations that suit specific operational requirements.

• Security and Access Control: By assigning users and roles at the client level, administrators can enforce strict access control and isolate client data and objects.

This page includes the following:

There are two types of Clients: Client 0 and the production Clients.

Client 0 (System Client)

A fresh Automic Automation installation already contains a Client 0. Client 0 is the reserved administrative Client that holds system-wide configuration and global settings. It serves as the central management point for administrative functions; In Client 0, administrators perform the following tasks:

• Manage global user accounts, user groups, and their authorizations and privileges across all Clients

• Configure system-wide settings such as default values, calendars, and global variables

• Administer physical infrastructure components like Agents and Agent Groups, including adding, starting, stopping, and upgrading them

• Establish and control connections between Agents and Clients and defining Agent permissions

• Monitor and supervise Automation Engine processes for performance and manage workload queues

• Manage service level objectives, quarantined messages, and object queues to ensure smooth operations

• Configure dashboards and system-wide templates available to all Clients

• Handle security functions including authentication, access control, and password management

Unlike operational clients, Client 0 does not handle workload execution but provides foundational configuration data that is distributed and used across all other Clients.

To log in to Client 0 for the first time you use the default UC/UC User (password UC) that is available by default after installing the system. Change this password immediately after your first login.

Predefined Objects

In a fresh Automic Automation installation, Client 0 includes a set of predefined objects supplied by the system. These objects, such as system and Client variable objects (VARA), Job headers, trailers, and templates, form the foundation for system-wide configuration and management. Administrators can customize these objects to tailor the system to their specific requirements.

It is important to exercise caution when applying system upgrades because overwriting customized objects in Client 0 during an upgrade process will result in the loss of those customizations. Therefore, administrators should avoid replacing customized Client 0 objects with default ones from an upgrade package to preserve their tailored settings and prevent disruption in the automation environment.

This practice ensures that administrative and global configurations unique to the organization's needs remain intact while benefiting from software updates.

Production Clients

Unlike Client 0, which focuses on system-wide administration, operational Clients handle workload automation tasks. For clarity's sake, we call operational Clients simply Clients. They are numbered from 0001 to 9999. Users assigned to these Clients can design, execute, and monitor automation processes tailored to their specific business needs. Permissions and user roles within Clients are scoped locally, restricting access to objects and processes confined to that Client. Administrators can create, enable, disable, or delete these Clients from Client 0.

Administrator users in each Client can also perform day-to-day Client management and change some Client settings locally (in the Client itself). If you customize settings within operational Clients, these Client-specific settings take precedence over equivalent settings defined in Client 0.

A common approach to configuring Clients is to create one Client for each operational area, department, or similar division. For example:

• Client 1 for DEVELOPMENT, containing all developer Users are and the folders and objects they will have to work with.

• Client 2 for HR OPERATIONS with all HR Users as well as their folders and objects.

• Client 3 for FINANCE OPERATIONS

Alternatively, you can configure one Client per customer or customer type, depending on your organizational needs.

No matter how you decide to set up your Clients, bear in mind that Users within a Client can open and work with all the folders and objects in that Client unless you define and manage their authorizations and privileges.

Example: For an example of how to use Clients, read Example: Creating a Basic Client/User Landscape, a Use Case where we describe how to set up a system with Client 0 and other two Clients, how to create User Groups and Users in Client 0 and assign them the rights they will need and how to move Users from Client 0 to the Client on which they will work.

Tip: You may need to work with many objects, lists and monitors simultaneously. To make your work easier, you can open them in different browser windows and arrange them side by side on your screen. For more information about this and other useful functions, see Opening and Arranging Multiple Views.

The list of Clients in Client 0 is different to the list in the other Clients; in Client 0, this list contains all the other Clients available in the system. The list displays the following columns by default:

• Client and Title as defined when you created the Client.

• TimeZone, that is, the Time Zone object that is assigned the Client and that determines the time that will be applied to all the operations performed in the Client.

• Active, whether the Client is currently active or not or if it is being deleted. Active means that it is available for automatic processing.

• Number of objects that are available in the Client.

• Number of activities, that is, tasks that are being executed at this point in time.

• MIB Monitor, that is, whether the Client is subject to SNMP monitoring or not.

• MIB Info of the Client.

The following columns are also available and you can display them by clicking the arrow in the list header and selecting the corresponding column name:

• Number of active users

• Priority as specified in the CLIENT_PRIORITY key in the UC_CLIENT_SETTINGS variable, see CLIENT_PRIORITY . This determines how the system will prioritize the Client for internal processing.

• Task Priority as specified in the TASK_PRIORITY key in the UC_CLIENT_SETTINGS variable, see TASK_PRIORITY. This determines how the system will prioritize the tasks in this Client.

• ID of the Client in the system.

For more information, see Main Page Tables.

Do the following to add more Clients to your system:

1. In the list of Clients in Client 0, do one of the following:

   • Click Add Client in the toolbar.

   • Right-click anywhere in the list and select Add Client.

2. On the Add Client dialog specify the following:

   • The Client ID, which is a number between 0001 and 9999.

   • A Title that helps you identify the purpose of the Client.

3. Click Add Client.

• Defining Clients

• Monitoring the Client History

• User Management: Defining and Managing the Authorization System

• Example: Creating a Basic Client/User Landscape

• Example: Working with Multiple Connections

• UC_CLIENT_SETTINGS - Various Client Settings

• Working with Clients

• Archiving Operational Data