About this task

The planned primary EPM server must have a static IP address and hostname, and it must be able to communicate with all other Experience Portal servers using either:

  • A Domain Name Server (DNS) to translate hostnames to their corresponding IP addresses

  • The /etc/hosts file to map the IP addresses and hostnames

Important:

If the servers cannot communicate with one another, you will encounter installation errors and be forced to rerun the installation.

In addition, the primary EPM server must also be able to communicate with all external servers such as the PBX, application servers, speech servers, and the Communication Manager.

Procedure

  1. Log on to Linux on the Experience Portal Primary EPM server.
  2. Verify the primary EPM server's IP address and hostname:
    1. Enter the hostname -i command.

      This command can return more than one IP address including 127.0.0.1. The IP address of the EPM server is the address other than 127.0.0.1. If this check fails, you must manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.

    2. Enter the hostname -s command.

      This command should return the server’s hostname and not localhost. If this check fails, you need to manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.

  3. Verify that the primary EPM server can communicate with all MPP servers:
    1. Enter the ping -c 4 <mpp_hostname> command, where:

      <mpp_hostname> is the hostname of the MPP server you are testing.

    2. Wait for the system to respond with the contact information.
    3. If both check fails, you need to manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.
    4. If your Experience Portal system contains more than one MPP server, repeat this step for each of the MPP servers.
  4. If this system has an auxiliary EPM server, verify that the primary EPM server can communicate with the auxiliary EPM server by hostname or IP address:
    1. Enter the ping -c 4 <auxiliary_epm_hostname> command, where:

      <auxiliary_epm_hostname> is the hostname of the auxiliary EPM server.

    2. Wait for the system to respond with the contact information.
    3. If this check fails, enter the ping -c 4 <auxiliary_epm_ipaddress> command, where:

      <auxiliary_epm_ipaddress> is the IP address of the auxiliary EPM server.

    4. Wait for the system to respond with the contact information.
    5. If both of these checks fail, you need to manually map the hostnames.
  5. Verify that the primary EPM server can communicate with the external servers by hostname or IP address:
    1. Enter the ping -c 4 <server_hostname> command, where:

      <server_hostname> is the hostname of the one of the following external components attached to your Experience Portal system:

      • A PBX server.

      • An application server.

      • A speech server.

      • Communication Manager.

      • Avaya Aura® Session Manager.

    2. Wait for the system to respond with the contact information.
    3. If this check fails, enter the ping -c 4 <server_ipaddress> command, where:

      <server_ipaddress> is the IP address of the server whose hostname you specified in the previous ping command.

    4. Wait for the system to respond with the contact information.
    5. If both of these checks fail, you need to manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.
    6. Repeat this procedure for each external server in your Experience Portal system.