In a multi-tenant enabled environment, Tenant: tenant value appears at the top of the screen next to the screen title. The tenant value can be either the name of a tenant or Shared. If the tenant value specifies a tenant name, it is the name of the tenant to which the selected Installations node is associated. The term One to five words that are meaningful to a specific type of business, or phrases that stand out in interactions in Speech and Text Analytics. Shared appears as the tenant value for the Enterprise, Site Group, and Site nodes that contain servers that process data for all tenants in the system. Typically, these servers are hosted servers or data center zone Logical deployment zone that serves as the centralized, single point of access where application data and content metadata is accessed, managed and maintained. servers.

For more information about the Shared value, see "Tenant (on Site Group settings screen)" and "Tenant (on Site Settings screen)" below.

The Pending Messages icon displays above this screen when the Enterprise Manager is processing configuration changes.

The Installations tree appears in the left pane of the screen and shows the existing Site Group, Site, Server, and Server Role nodes.

Note: In a Multi-Tenant SaaS environment, the tenant that is associated to a Site, Site Group, or Server displays when you hover over the Site, Site Group, or Server name with your mouse. The tenant name also displays if you expand the Installations pane to a full screen by clicking on the small right pointing arrow in the slim divider that separates the Installations tree from the right pane.

Specifies the name displayed for the Enterprise, Site Group, or Site node in the Installations tree.

You can edit this field when a Site Group or Site node is selected.

You cannot edit this field when the Enterprise node is selected.

This field displays only when the Enterprise node is selected.

This field shows the FQDN (fully qualified domain name), IP address, or Server name for the Enterprise Manager (EM) Primary administration tool for all of the managed servers deployed in an enterprise, including those deployed both in the Data Center and in remote geographical locations (or sites). server.

The EM Server is the server on which the Enterprise Manager application is installed. This server has the Framework Applications Server role in the Data Center that provides the system’s core applications. It is a mandatory server role in the system and required for all packages. server role Entity that contains a logical, predefined set of components (system software or certified third-party software) deployed in the Data Center and Site Zones that provide specific functionality for the system. activated. You use the Enterprise Manager to manage all Site Groups, Sites, and Servers.

All Installations in the enterprise use the value specified in this field to connect to and communicate with the Enterprise Manager application.

This field displays only when the Enterprise node is selected.

Shows the port number of the Enterprise Manager server discussed in EM Server Name.

(Optional) Type descriptive text about the node.

You can edit this field for any node type: Enterprise, Site Group, or Site.

This field displays only when the Enterprise node is selected.

When the application server is clustered, examine the logs from this server to troubleshoot problems related to the Enterprise Manager application.

Explanation:

If you have a cluster of application servers, one server in the cluster is designated as the Master Enterprise Manager Server. By default, the Master Enterprise Manager server is the first server started in the cluster.

The Enterprise Manager application residing on this server is the master instance of the Enterprise Manager application. There is only one master instance of the Enterprise Manager application in the cluster. This instance runs Enterprise Manager operational processes and background tasks such as alarm collection Group of back-office Contributions from one or more employees connected to a single customer or account captured by DPA. Collections are used for analyzing and improving back-office efficiency and quality. and message distribution.

When troubleshooting problems related to Enterprise Manager operational processes and background tasks, collect logs from the Master Enterprise Manager server.

If you have only a single application server in your environment (a non-clustered environment), that server name displays here.

This field displays only when a Site Group or Site node is selected. This value is used by internal system components.

This setting appears for the Site Group node only in a Multi-Tenant SaaS environment.

You can specify the tenant to which you want to associate the Site Group. You have these options when specifying a tenant:

• Shared - Select this setting for Site Groups that will contain hosted servers or data center zone servers. When this setting is selected, the servers in the Site Group will process data for all tenants in the system. Examples include the core database servers and application servers. Typically (and when the relevant components fully support it), most servers actually in the cloud are shared by tenants regardless of what component they are running.

• Tenant Name - Select a specific tenant name to assign the Site Group to that tenant. The tenant names that appear here depend on the tenants that are defined in the Organization Management Module in WFO that allows administrators to set up different hierarchies to manage users from a single, unified, Web interface., Hierarchies, Tenant Settings screen. All Sites created beneath this Site Group inherit the tenant name value. The servers contained in the Sites process data for only one tenant. Examples of servers assigned to a specific tenant include any Site servers hosted on premise at a specific tenant, such as recorders or transcription Process in Speech Analytics of converting audio files of the recorded agent-customer conversation to text. servers.

Once you specify a tenant and save the tenant setting, you can no longer edit the tenant setting.

When configuring the tenant setting for a Site Group, note that you cannot have multiple tenants in a single Installations tree hierarchy.

If you specify a tenant for a Site Group, the same tenant must be specified for every child Site Group and child Site of that Site Group.

If you specify Shared for a Site Group, you can have child Site Groups or Sites beneath that Site Group that specify different tenants. For example, assume you have a parent Site Group (Site Group A) beneath the Enterprise node and Shared is specified for Site Group A. You can have two child Sites (Site T1 and Site T2) beneath Site Group A where Site T1 is associated to tenant 1 and Site T2 is associated to tenant 2. This configuration is allowed because Site T1 and Site T2 are sibling sites and you do not have multiple tenants in the same hierarchy. In such a scenario, you cannot assign a specific tenant to Site Group A because you would then have multiple tenants in a single Installations tree hierarchy.

In another example, assume you have Site Group A beneath the Enterprise node where Site Group A is assigned to tenant 1. In this example, all Sites under Site Group A must be also be assigned to tenant 1. With this configuration only one tenant exists in the Installations tree hierarchy.