Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Communication Requirements

    Network Configuration

    The server must have a fully qualified host name (which includes the short hostname and domain name) that is registered in the DNS. This means that the UNIX (short or long) hostname locally defined on the server via the UNIX command “hostname” should be part of the fully qualified name.

    For example, if the hostname is primo1 or, the fully qualified name is

    When performing a distributed installation, all application servers must have DNS entries. The server name must be defined in the /etc/hosts file.

    Both the fully qualified name and the short host name must link to a physical IP address (internal). Use the following command to verify the name:

    grep `eval hostname` /etc/hosts

    This command must return a valid entry with a physical IP address. 

    The internal IP address can be found by using the following commands for the SunOS and Linux operating systems:

    • SunOS: 

      /usr/sbin/ifconfig -a | grep inet | grep -v | awk '{print $2}'

    • Linux: 

      /sbin/ifconfig -a | grep addr: | grep -v | awk '{print $2}'

    The following figure displays a sample /etc/hosts file. The first active line should be configured exactly as shown for the localhost. The second active line should contain the internal IP address, the fully qualified name (host name + domain name), and the short name and possible aliases.

    # Do not remove the following line, or various programs

    # that require network functionality will fail.    localhost.localdomain       localhost    primo1

    Sample /etc/hosts File

    Server Access

    Set up access to the system for Ex Libris via the Internet, with a minimum bandwidth of 64 K.

    Ex Libris requires access to the following:

    • Primo server for installation of the Primo software, setup, support, and troubleshooting during the implementation and maintenance phases. 

    • If a firewall is installed, access should be enabled for Ex Libris support and implementation via the IP address: In addition, where relevant, access should also be enabled for IP addresses of the local Ex Libris office or distributor (for details, contact your Ex Libris representative or distributor).

    Ports and Activity Types

    Verify that the following ports are open and can be used by Primo:

    Port Server Activity Type

    1521 (TCP/IP)


    Provides internal connection between the Oracle database and the FE, BE, and SE servers.

    1601 (HTTP)

    BE (Back Office)

    Provides BE access to the Primo server.

    1443 (HTTPS)

    BE (Back Office)

    Provides BE secure access to the Primo server.

    1701 (HTTP)

    FE (Front End)

    Provides the world FE access to the Primo server.

    8701 (HTTP)


    Provides communication between the FE and SE servers (MDB's).

    5000 (HTTP)

    BE, FE, SE (Search server)

    Used for debugging purposes on the BE, FE, and SE server.

    8991 (HTTP)

    Active PDS server (for world)

    Used for running the PDS server.

    9501 (HTTP)


    Used for running the Primo Search server on all SE servers.

    2000 - 2025 (HTTP)


    Provides communication between the SE servers and the FE server.

    5001 (HTTP)


    Provides SOAP monitoring of Web services between FE and SE servers.

    80 (HTTP)


    Provides BE access to Release Notes at


    BE, FE, SE

    Standard port used for the outgoing mail server; the mail daemon must be installed and tested.


    BE, FE, SE

    Standard port used for SSH connections between all servers and Ex Libris locations.


    BE, FE, SE

    Standard port used for FTP connection between all servers and Ex Libris locations.



    Provides communication between FE and SE machines.



    Provides communication between FE and SE machines.



    Provides communication between FE and BE machines.

    2000 - 2050


    Provides communication between FE and BE machines.

    Include any ports necessary for the creation of shared interfaces with ALEPH, MetaLib, SFX, or any other products with which Primo will communicate. The numbers of these ports depend on the local implementation of ALEPH/MetaLib/SFX.

    Coordinate the use of any other ports with Ex Libris.

    If you have an additional version of Primo (for testing or training purposes) on your server, open additional HTTP ports using the copy number instead of the last digit (number 1). For example, if you have one additional version (copy 2), use port numbers 1602, 2702, 1702, 8012, 8992, and 9502.

    • Was this article helpful?