Manually mapping hostnames to connect the Experience Portal server with other servers in the system

About this task

To manually map hostnames to IP addresses without a DNS, you need to edit the /etc/hosts file on the planned Experience Portal server so that it includes an entry for each speech server, application server, and PBX in the Experience Portal system.

Procedure

Log into Linux on the planned Experience Portal server.
Back up the original file prior to editing it by entering the cp /etc/hosts /etc/hosts.bak command.
With the ASCII text editor of your choice, open the /etc/hosts file.
Make sure that the first line contains 127.0.0.1 localhost localhost.localdomain, with the IP address and hostnames separated by spaces or tabs.
Create a new line for each server in the Experience Portal system using the format IP_address hostname1 hostname2... where:
IP_address is the IP address of a server in the Experience Portal system and hostname1 hostname2... is one or more hostnames, separated by tabs or spaces, to associate with the IP address.

You should have one entry for each of the following types of servers used in your Experience Portal system:
- All PBX servers.
- All application servers, unless you plan to install the application server on the Experience Portal server.
- All speech servers.
- Communication Manager
- Avaya Aura® Session Manager
Save and close the file.

Example

The following shows a properly-formatted /etc/hosts file:

127.0.0.1 localhost.localdomain localhost
123.123.123.123 asr_server.domainname.com asr_server
123.123.123.124 tts_server.domainname.com tts_server
123.123.123.125 app_server.domainname.com app_server
123.123.123.126 pbx_server.domainname.com pbx_server