Server group naming
This documentation assumes that if there is more than one pointing to the same database, that work is directed to the individual servers via some automated functionality (such as a hardware or software load balancer), or through manual configuration (such as directing some users to one server and other users to another server). It is also possible that one server is used primarily for users while the other server is used for automations and integrations. In any case, the actual configurations for various settings, such as the server name alias, need to be considered for the specific environments.
Server name alias
All s in a group must have the same server name parameter. This is specified in the Administration Console as the Server Name Alias field. This field is located in AR System Administration Console > General > Server Information, on the Platform tab. Clients can, therefore, be directed to the load balancer by using the server name parameter.
If your server group uses a load balancer, the common server name parameter must be the same as the short DNS name of the load balancer. Make sure that you use a name that will be translated to the IP address of the load balancer. So, either the DNS should resolve the name or you must map the name in the etc/hosts file.
If the server name alias setting is not the same as the load balancer short DNS name, ARTask email attachments generated by the server might not work. When generating an ARTask attachment, the server generates a reference to itself by using the server name parameter with the domain name appended. Clients opening the ARTask will then use the fully qualified domain name to be routed to the server group through the load balancer.
A server name alias that is always interpreted as the current server. This option is used in multiple server installations to differentiate servers. In a server group, Server-Name refers to the load balancer name.
If a server belongs to a server group and you use a common server alias, you must also specify the Server-Connect-Name option. For more information, see Server-Connect-Name.
Server-Connect-Name
Name of the computer where the is installed. By default, a server in a server group uses a fully qualified server name with domain to identify itself. Other servers in the group use this name to communicate.
To change the server name, add the following option to the configuration file:
- Server-Connect-Name—<mycomputername>
- Server-Connect-Name—<myComputerName.domain.com>
This option is required if you specify a common server alias.
This name must be resolvable by DNS and is used exactly as specified. For more information, see Configuring-server-groups.
Unique names for each server
Each server in a server group needs a uniquely defined name to identify itself to other servers in the group. Usually this is the host name of the computer where the server is installed.
To identify the unique name for each server in the group, the following line is added to each server's configuration file:
DNS must be able to resolve this name, and it is used exactly as specified (that is, no domain name is appended). Each server uses this name to register as a server group member. Other servers in the group use the name when communication between servers is required. In addition, various external server components use the name when connecting to the local server. This name can be specified as either the short name or the fully qualified name.
Server group name
The server group name was used in some earlier releases in relationship to licensing, but it is no longer necessary to set this value. In release 7.5.00 and later, this setting is not used. However, there is still a field for it in the Administration Console. The field can be left blank.
(For On-premises deployments only) To configure in a server group environment, you need to specify a server group name.