In order to run EZproxy successfully, you must have staff available who can:
- Understand the operating system where EZproxy will be installed, as well as its file structure and permissions
- Configure your DNS and firewall
- Provide you with your site's IP address ranges
- Assist with configuring EZproxy to work with your existing authentication methods, if applicable, and has basic experience and skills to manage web servers
- Know the user authentication system your library has - or wants to implement - as well as the authentication method used by your database content providers to access to their resources for example IP address recognition
Optionally, your staff will also benefit from having basic knowledge of an IP proxy server and an understanding of URL rewriting and strategies behind using a URL Rewriting program.
You'll want to review all technical requirements and configuration choices with your IT staff.
Hardware and operating system
EZproxy is supported under two different operating systems: Linux and Windows. The supported versions of these operating systems along with their minimum hardware requirements appear in this article.
EZproxy for Linux requires an x86 or x86_64 distribution of Linux running a 2.2 or later kernel. To verify the version of your Linux kernel, use the command:
If you encounter problems running EZproxy on a specific distribution of Linux, please contact OCLC support for further assistance.
The minimum recommended configuration for an EZproxy for Linux server is a Pentium II 400 with 256 MB of RAM. 10 MB of disk space is required for installation. Additional disk space is required to accommodate user authentication files and server log files.
EZproxy runs on all Microsoft Supported versions of Windows and Windows Server. WOW64 may be required when using an EZproxy version prior to 7.0.
The minimum recommended configuration for an EZproxy for Windows server is a Pentium II 400 with 256 MB of RAM. 500 MB of disk space is required for installation. Additional disk space is required to accommodate user authentication files and server log files.