Jump to: navigation, search

Configuration Manager

Configuration Manager enables you to create and manage system-level configuration objects such as Alarm Conditions, Business Attributes, Hosts, and more.

Configuration Manager Overview

The Configuration Manager page is a central location for viewing and managing the configuration objects used by your system. Genesys Administrator Extension can manage objects in single-Tenant and multi-Tenant configurations.

Configuration objects, also known as Configuration Database objects, contain the data that Genesys applications and solutions require to operate in a particular environment. These objects are all contained in the Configuration Database.

Configuration Manager lists these objects by type. For example, configuration objects related to outbound campaigns are listed under the Outbound heading.

Click on a configuration object type to view a list of the related configuration objects on your system. From this list, you can edit or delete the existing configuration objects, or you can create a new configuration object.

To view and manage configuration objects for a specific Tenant, click the cube icon and enter the name of the Tenant in the Tenant Directory field. By default, Configuration Manager lists configuration objects for the Tenant to which your user account belongs. When viewing objects by Tenant, if you choose to create a new object, that object is created in the directory for that Tenant.

The Tenant Directory field is not shown in a single-Tenant environment.

Click on a topic below to learn more about Configuration Manager.

Object Hierarchy

[+] Click here to reveal section

Importing/Exporting Data

[+] Click here to reveal section

Required Permissions

[+] Click here to reveal section

Manipulating Multiple Objects

[+] Click here to reveal section

Naming Conventions

[+] Click here to reveal section

Common Object Properties

All objects have the following configuration properties and elements:

  • Name—Names uniquely identify objects within a certain range. Therefore, the name, which can be up to 255 characters, is a required parameter for most types of objects. The exceptions are:

    The way you name objects in your environment is important. Consistent and sensible naming conventions make your configuration environment easier to understand and faster to browse, leading to a more maintainable and usable configuration.

    Although Genesys Administrator Extension supports the full character set in object names, the use of certain characters can cause problems in the behavior of other Genesys applications. Therefore, avoid spaces, dashes, periods, or special characters in object names. Consider using underscores where you might normally use spaces or dashes.
    The names you set for some types of objects must match the names of the entities that those objects represent elsewhere in an environment. For example, the names of Hosts must match the names given to the computers they represent in the data network environment.
  • State Enabled—If checked, indicates that the entity represented by an object is in regular operating condition and can be used without any restrictions. If not checked, indicates that the entity represented by an object is being used in a non-production environment. Customer interactions cannot be directed to this target, even if operating information indicates that this object is available.

    Disabling a folder or an object that is a parent to other objects also disables all objects within the folder or all child objects of that parent object.

    For example:

    • Disabling a Switch disables all DNs and Agent Logins defined within this Switch.
    • Disabling an Agent Group folder disables all Agent Groups configured within this folder.
    However, if you disable a group of objects (for example, an Agent Group), the individual members of this group (in this example, Agents) remain enabled.


The Permissions tab lists the Access Groups and Users that have been configured explicitly with permissions for this object. When you are setting permissions, it is normally performed with the User(s) or Access Group(s) for which you want to grant access. This feature improves the manner in which permissions are set, and the scope is limited to managing permissions for a single database object.

For additional instructions about granting, modifying, and removing permissions, refer to the Genesys 8.1 Security Deployment Guide.

Some configuration objects, such as Tenants and Folders, are parent objects to one or more child objects. When you access the Permissions tab for these parent objects, you can use the following additional options to set permissions:
  • Propagate check box—If Propagate is checked, the permission is propagated to every child object under this parent object. If Propagate is not checked, the permission is removed from every child object under this parent object, unless the permission has been modified in the child object.
  • Replace Recursively button—If Replace Recursively is clicked, the permissions of every child object are removed and replaced with permissions from the parent object.

You can perform the following actions:

Changing Members

[+] Click here to reveal procedure

Changing Access Permissions

[+] Click here to reveal procedure

Removing Access Permissions

[+] Click here to reveal procedure

Configuration Options

Application and Application Template objects have an additional tab, Application Options, to set configuration options specific to these objects. These options are created, updated, or deleted in the same manner as regular options.

The Options tab enables you to set configuration options for the object. You can perform the following actions:

Creating an Option

[+] Click here to reveal procedure

Updating an Option

[+] Click here to reveal procedure

Deleting an Option

[+] Click here to reveal procedure
  • The Section and Key fields are required, and the values for these fields must be unique in the environment.
  • You can click More to import or export options. See the Importing/Exporting Data section in the Overview tab, above, for more information.


The Dependencies tab displays a list of all objects that are dependent on this object, and by what property they are dependent.

For example, consider a scenario in which an Application object, AppA, is running on a Host object, HostA. AppA is dependent on HostA to function, so the Dependencies tab for HostA shows AppA as a dependent object, with the property being Host.

For all Users and Agents, the Dependencies tab also lists the Roles to which they have been assigned.

Click any object in the list to view the properties of that dependent object. You can then modify its properties or create another object of the same type.

Assigning Security Certificates

Genesys supports the optional use of the Transport Layer Security (TLS) protocol to secure data exchange between Genesys components. The TLS protocol is implemented using security certificates, which must be configured in the Host objects and the Application objects representing these components.

Before configuring secure data exchange, make sure that certificates are installed on the host computers on which the Genesys components run, and that the certificate information is available to you.

Security certificates are assigned at the Host level, and optionally at the Application and Port levels. The Host certificate is used by Applications and Ports by default, unless the Applications and Ports specify their own certificates. In this case, those specific certificates override the default Host certificate.

For more information about deploying TLS, refer to the Genesys 8.1 Security Deployment Guide.

Supported File Formats

The CFG/CONF file format is a plain-text format. The CFG format is for use on Microsoft Windows systems, and the CONF format on UNIX systems.

Both formats support only the import and export of string options. Other types of configuration options are ignored and not imported or exported.


The syntax of the .cfg and .conf files is identical. Each section and option appears on a separate line, with section names in square brackets. Each section is followed by a list of options in that section, with the appropriate values:




The following excerpt from a configuration file illustrates the correct syntax in a .cfg or .conf file:




This page was last edited on July 17, 2020, at 15:59.
blog comments powered by Disqus