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 Server 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 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.

The Pending Messages icon displays above this screen when the Enterprise Manager is processing configuration changes. For more information, see The Configuration Messages Status icon.

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.

Type the name of the server being added. This name is at your discretion.

This name is associated with a server icon in the Installations tree.

To describe the new server, add text such as TDM Recorder or IP Recorder.

This field is optional.

Read-only field that shows the serial number of the recorder server from the installation process. The serial number can be any six-digit number.

This field is populated if you are editing an existing server, but empty if you are creating a server. The system automatically assigns this serial number to a server when you activate any of these recording server roles on the server: IP Recorder, TDM Recorder, Screen Recorder, or Recorder Ingestion Web Service.

The recorder server uses the serial number to generate unique identifiers (or INUMs), which are used to identify each unique call recorded by the server.

There is a limit to the number of INUMs a single serial number can generate. When this serial number approaches the limit of INUMs that it can generate, a new serial number is automatically assigned to the server. For more information, see "Additional Serial Numbers."

Read-only field that lists additional serial numbers that are assigned to a recorder server.

The system automatically assigns an additional serial number to a recorder server. The system assigns this serial number when the current serial number has generated 75% of the maximum number of INUMs it can generate.

When the current serial number generates 100% of the INUMs it can generate, that serial number is exhausted. The additional serial number then becomes the current serial number.

Each serial number that appears here has one of these statuses:

• Current - This serial number currently generates the INUMs for the recorder server.

• New - This serial number becomes the new current serial number, and begins generating INUMs, once the current serial number reaches the Exhausted status.

• Exhausted - This serial number has generated 100% of the INUMs it can generate, and is no longer used to generate INUMs.

Note: A single serial number can generate one billion INUMs. In busy recording environments, a serial number can exhaust one billion INUMs in approximately two years.

Read-only field that indicates the last time the Enterprise Manager performed the server discovery Process performed by the Enterprise Manager application in which the application regularly communicates with each server in the system to determine whether any new software (new release, service pack, hot fix, or patch) or server roles have been added or installed on the server. process on this server.

This field appears if you are editing a server, but not if you are creating a server.

Every minute Enterprise Manager polls the servers to determine whether anything has changed on the server. If Enterprise Manager detects a change, it performs the server discovery process. This process detects the following on the server:

• Discovers if any server roles were added or updated on the server

• Discovers server roles that have been activated but not configured and supplies the default settings for these server roles

• Deletes any cached or stored data pertaining to server roles that are deactivated

• Automatically creates any one-to-one, or one-to-all 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. associations for active server roles

• Checks for server roles that require specific server role associations but do not have them and reports these roles in the Configuration Status tab

• Detects any new alarms triggered on the server and updates the alarm summary information for the server in Enterprise Manager

You can also perform server discovery manually by clicking the Save button on the Server screen (this screen) for any server.

For more information, see Server Discovery.

The icon displayed here indicates whether the application servers are able to connect to this server's Enterprise Manager Agent Web application installed on every system server that communicates with the Enterprise Manager regarding any configuration changes or alarm messages for the relevant server. (EMA). The EMA runs on the Tomcat service. A blue check mark icon indicates the application servers can connect to the EMA. A red X icon indicates the application servers cannot connect to the EMA.

The icon displayed here indicates whether configuration messages intended for this server are hung up or not up-to-date. The blue check mark icon indicates the configuration changes are being successfully processed. The red X icon indicates the configuration changes are out of synch (that is, hung up or not up-to-date). Typically, the red X icon appears when 15 minutes or more elapses without the changes being updated.

This field is relevant only in a Multi-Tenant SaaS environment. This field is read-only and its value is inherited from the Site node.

If this field specifies Shared, the server processes data for all tenants.

If this field specifies a particular tenant, the server is dedicated to processing data solely for that tenant. Typically, such a server is a Site server such as a recorder server or transcription Process in Speech Analytics of converting audio files of the recorded agent-customer conversation to text. server.

Enter either the Host Name, FQDN, or IP address of the server in this field. Enterprise Manager uses this name to connect to this server.

The name entered in this field cannot include an underscore character (_).

The name entered in this field automatically appears in the HTTP Alias field.

Important:Enterprise Manager can communicate with this server using HTTPS. In this case, this field must specify the exact same server name that is specified in the common name field of the server TLS server certificate. For more information, see the Security Configuration Guide.

Shows the port number (default 80) to be used for HTTP communication between Enterprise Manager and the server.

If you are adding an Avaya Contact Recorder (ACR) server, change this port number to 8080. For all other servers, including other recorder servers, accept the default port of 80.

Shows the port number (default 443) to be used for HTTPS communication between the Enterprise Manager and the server.

If you are adding an Avaya Contact Recorder (ACR) server, change this port number to 8443. For all other servers, including other recorder servers, accept the default port of 443.

Read-only field that indicates whether HTTPS secures the server. Possible values are Yes or No.

The HTTP Alias field defaults to the same server name that is entered in the Server Name field.

You can use this field to specify any alternate name of the server that is used to point to this server as a host.

The name entered in this field cannot include an underscore character (_).

This field is used primarily to support application server clusters that support Enterprise Manager.

The following statement is true when the Enable Data Center SSL Offload setting is not selected. If this server is part of an application server cluster, this field must specify the HTTP address of the load balancer that handles connections to the cluster.

This field displays for a data center server only when the Enable Data Center SSL Offload setting is selected. This field specifies the host name or IP address of the load balancer that handles connections to an application server cluster. Site servers and desktop applications on networks outside the data center network firewall use this address to connect to the load balancer. The site servers and desktop applications connect using encrypted HTTPS.

This field displays for a data center server only when the Enable Data Center SSL Offload setting is selected. This field specifies the host name or IP address of the load balancer that handles connections to an application server cluster. Servers inside the data center network (behind the firewall) use this address to connect to the load balancer. The servers connect using unencrypted HTTP.

This check box is visible when creating a server, but not when editing an existing one.

To prevent (block) configuration messages from being communicated from Enterprise Manager to the newly created server, select this check box. In this case, the new server cannot receive configuration changes from Enterprise Manager.

This option is usually selected when you are adding a server to a Site that is currently blocked from receiving configuration changes. Selecting this option also prevents the newly added server from receiving configuration changes.

If a Site is blocked, and you add a new server to the Site, block the server after adding it to the Site. If you do not block the server, the server receives configuration changes from Enterprise Manager even though the Site is blocked.