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.
- For SunOS, enter the following commands to find the internal IP address:
/usr/sbin/ifconfig -a | grep inet | grep -v 127.0.0.1 | awk '{print $2}'
- For Linux, 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 of /etc/hosts configuration:
|
# 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 above 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 Rosetta server – for the installation of the Rosetta software, setup, support, and troubleshooting during the implementation and maintenance phases
- If a firewall is installed, access must be enabled for Ex Libris Support and Implementation staff via the Ex Libris gateway IP address, 212.179.71.70. 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).
- At the post-installation stage, it is recommended that you permit access to http://exlibris-public.exlibrisgroup.com/ in order to be able to access the service pack release via the Help menu in the Rosetta application.
Ports and Activity Types
Verify that the following ports are open and can be used by Rosetta:
| Port | Server | Access |
|---|---|---|
| 8182 (HTTP) | All | Cantaloupe Image Server |
| 8183 (HTTPS) | All | Cantaloupe Image Server |
| 1521 (TCP/IP) | Oracle | Deposit, Staging, and Permanent servers; Ex Libris Support (jdbc) |
| 1801 (HTTP) | Deposit | Internet |
| 1801 (HTTP) | All | Internet (for delivery of objects to the end user); Ex Libris Support |
| 8443 (HTTPS) | All | Native SSL access |
| 8991 (HTTP) | Deposit (PDS Port) | Internet; Deposit and Staging servers
Only relevant if PDS is in use.
|
| 5001 (HTTP) | Deposit, Staging, Permanent | Ex Libris Support, for remote Java debugging |
| 80 (outgoing HTTP) | Staging | To http://www.exlibris-public.exlibrisgroup.com, for access to release notes and updates |
| SFTP - 10022 | Deposit, Staging, Permanent, Oracle | downloads-na.hosted.exlibrisgroup.com downloads-eu.hosted.exlibrisgroup.com downloads-ap.hosted.exlibrisgroup.com downloads-ca.hosted.exlibrisgroup.com downloads-cn.hosted.exlibrisgroup.com |
| 22 | Deposit, Staging, Permanent, Oracle | SSH connection from Ex Libris Support |
| 25 (outgoing) | Deposit, Staging | SMTP outgoing mail (the mail daemon must be installed and tested) |
| 8983 (HTTP) | Index server (IDX) | Solr index standalone server (internal communication only) |
| 5811 5821 5831 | SolrCloud | SolrCloud index standalone server internal communication between ZooKeeper(s) and IDX server(s) |
Use of other ports must be coordinated with Ex Libris.