Communication Requirements

Network Configuration

The server must have a fully qualified hostname (include short hostname and domain name) that is registered in the DNS.

When performing a distributed installation, all application servers must have DNS entries.

The server name must be defined in /etc/hosts as follows:

Both the fully qualified name and the short host name must be linked to a physical IP address (internal). In order to make sure the correct name is defined, use the following commands:

grep `eval hostname` /etc/hosts

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

Enter the following commands to find the internal IP address:

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

See the following example for /etc/hosts:

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 localhost.localdomain localhost

10.1.222.22 ml-inst.corp.metalib.com ml-inst

The first active line should be configured exactly as shown in the example.

The second line should contain the internal IP address, followed by the fully qualified name (hostname + domain name), the short name, and any possible aliases.

Server Access

Ex Libris access to the system via the Internet is required, with a minimum bandwidth of 64 KBp.

Ex Libris staff will require access to the following:

The Aleph server – for the installation of the Aleph software, setup, support, and troubleshooting during the implementation and maintenance phases
If a firewall is installed, ssh access must be enabled for Ex Libris Support and Implementation staff for the following IP addresses:
- HQ Jerusalem Israel:
  - 212.179.71.70
- Local Ex Libris office ‐ Australia:
  - Adelaide 14.203.6.142
- Local Ex Libris office – China:
  - Beijing 106.37.165.166
- Local Ex Libris office – Germany:
  - Hamburg 54.217.102.245 (replacing 195.37.97.145 and 195.37.234.234 on September 11, 2022)
- Local Ex Libris office – South Korea:
  - Seoul 112.217.228.186
- Local Ex Libris office – USA:
  - Chicago 54.85.221.162
  - Fort Collins 4.34.54.50

In addition, where relevant, access must be enabled for IP addresses of the local Ex Libris office or distributor (for details, refer to your local Ex Libris representative or distributor).

Ports and Activity Type

The following ports are required:

Aleph

Telnet or SSH standard port
FTP or SFTP standard port
HTTP port 8991 for the main Aleph installation. We recommended that you switch to port 80 for the main Aleph installation close to STP (Switch To Production).
TCP/IP port 7991 for running Aleph Z39.50 gate
TCP/IP port 9991 for running Aleph Z39.50 server
TCP/IP port 6991 for running Aleph PC server
For a TWO TASK installation, port 1521 is open between the database server and the Aleph 24 application server.

Aleph 24 Installed in Parallel with Existing Aleph Versions

HTTP port 899x (with x is the instance copy number to install)
TCP/IP port 799x for running Aleph Z39.50 gate (with x = instance copy number)
TCP/IP port 999x for running Aleph Z39.50 server (with x = instance copy number)
TCP/IP ports 699x and 6993 for running Aleph PC server
For a TWO TASK installation, port 1521 is open on the database server allowing remote access from the Aleph application server.

Use of other ports must be coordinated with Ex Libris.
If SSL installation is required, then HTTPS port 443 must also be open. It is the customer's responsibility to purchase an SSL certificate before Aleph is installed.
The settings for all ports, except the HTTP and Z39.50 ports, must be defined so that they can only be accessed from outside the firewall by valid Ex Libris IPs.

E-Mail Setup

For normal Aleph functionality, the ability to send e-mail from the server via SMTP is required. The sendmail routine is recommended.

Aleph can be configured to use secure communications (TLS/SSL) for sending E-mails to the SMTP server.

The configuration of secured communications between Aleph and the SMTP server is done in the E-Mail Settings section of the ALEPHADM GUI module or in Alephcom.ini in the [Mail] section.