Network Ports
Required Network Ports
In order to allow access to ILLiad and its various component parts, the following server ports are required to be open.
SQL Ports | 1433 or 1344 | Port opened outbound from web server and clients to SQL server. This allows the ILLiad client to communicate with the database. This would only need to be open for the webserver (if separate server) and the ILLiad client to access the SQL server. If you have changed the port used by SQL Server, this port number will be different. P ort 1433 is the standard port, but 1344 is set up to use as an alternative if you are having trouble connecting. |
---|---|---|
Public Web Pages | 443 or 80 | Port opened inbound to all or any IP ranges that are allowed access to the ILLiad web forms. This allows customers to access the ILLiad Web pages and receive RSS Feeds. This would need to be open to everyone or could be restricted if you wanted to limit access to the customer interface (not commonly done). ILLiad's Web Platform requires an SSL certificate, so most sites are using SSL for their ILLiad web pages as well. Use port 443 for secure web pages (recommended) or 80 for non-secure pages. |
OCLC Connectivity | 443 | Port opened only outbound from the ILLiad webserver to OCLC's web platform server (webservices.oclc.org). This allows the ILLiad Connection Manager and ILLiad client to contact OCLC for update and download purposes. |
ILLiad Update Server | 443 | The ILLiad server updater now uses secure HTTPS to download updated files. This needs to be open to update.atlas-sys.com. |
ILLiad Client Updates | 443 | Each time it is opened, the ILLiad client checks against the Atlas server to verify the latest version available. If the installed version is older than the latest available, it prompts the user to update and downloads that update from the Atlas server over port 443. This is a direct connection and not through a proxy server. |
ILLiad Web Platform | 443 | Port opened outbound from ILLiad clients to the ILLiad web server. This allows the ILLiad client to communicate with the ILLiad Web Platform API for various operations. The Web Platform requires HTTPS/SSL for secure communication. Many ILLiad components rely on the Web Platform to function properly. |
Odyssey Electronic Delivery | 7968 | ILLiad web server needs to have port opened inbound and outbound to the world as well as inbound from staff clients. Staff clients need the port opened inbound and outbound to the ILLiad web server only. This allows the Electronic Delivery client machines to send electronic documents to the ILLiad Server and the ILLiad Server to send those documents out to other ILLiad Servers using the Odyssey Protocol. The Odyssey Manager service will discard anything sent over this port that is not a recognized TIFF or PDF document with an appropriately formatted header. |
OCLC Article Exchange | 443 | Port opened only outbound from the ILLiad web server to OCLC's Article Exchange web platform server (https://ill.sd00.worldcat.org/articleexchange/). |
tip
To change the port that the ILLiad client uses to connect to Microsoft SQL Server, create or edit your existing logon.dbc file and enter 123.123.123.123,1344 into the Server field, where 123.123.123.123 is your server IP address.
Optional Network Ports
You may want to opening the following ports if you use the services described.
Z39.50 | Varies | If you plan on usingZ39.50 to search your local OPAC from within ILLiad, you will need to check that the ILLiad Client machines have access to the Z39.50 server over that port. This port differs from OPAC to OPAC so you will need to verify that value. The client needs to be able to connect to the port to display local holdings information. |
---|---|---|
ISO ILL | 1611 | The ILLiad web server needs to have this port opened both inbound and outbound. This allows the ILLiad client to send and receive ISO ILL requests. This is generally open to all IP addresses. Note: Alma libraries may also need to open port 9001 for ISO ILL functionality. See the Alma Resource Sharing Partners documentation for more information. |
Innopac PatronAPI | 4500 | The ILLiad web server needs to be able to communicate with the PatronAPI server outbound to authenticate if using PatronAPI authentication. While this port is typically 4500, the port may differ based on your unique setup. |
SIRSI SymphonyAPI | 8080 | The ILLiad web server needs to be able to communicate outbound with the SymphonyAPI server to verify SymphonyAPI authentication into SIRSI. |
LDAP | 389 or 636 | The ILLiad web server needs to be able to communicate with the LDAP server outbound to authenticate if using LDAP authentication. The LDAP server needs to allow traffic from the ILLiad web server's IP to request authentication. Port 389 is used for standard LDAP and 636 is used for SSL. |
Remote Desktop Connection | 3389 | This would be opened only if you wish to allow customer support to access your ILLiad Server via Remote Desktop Connection. |
Windows File Share | 445 | This port is optional and is not required for ILLiad usage. File shares in ILLiad are optional and can be used for sharing print templates or accessing a central store where files for electronic delivery scans are stored. Some ILLiad institutions also will upload PDFs directly (bypassing Odyssey) to the web server’s PDF location and use the “Notify Electronic Delivery” option in ILLiad. While the ILLiad client doesn’t have any direct integrations with the port for printing, it could be used by the underlying Windows system if it uses the Windows printer sharing feature. |