Skip to main content
OCLC Support

EZproxy for Solaris

The instructions on this page describe how to install and update EZproxy Solaris 10 (x86).

End of support for EZproxy on Solaris platform
OCLC will end support for EZproxy on the Solaris 10 (x86) platform on October 31, 2018. We will no longer provide software for this platform as of that date. We will continue to provide Linux and Windows versions of the software. Customers using EZproxy on Solaris should plan to move their installation of EZproxy to Linux or Windows. If you have questions about this change, please reach out to Customer Support (support@oclc.org). 

Ability versus right

EZproxy allows you to extend your databases to remote users. However, your licensing agreement with database vendors may not authorize you to provide remote access. As an implementer of remote access, it is your responsibility to verify licensing agreements and only permit remote access as authorized.

Install EZproxy for Solaris

EZproxy is a completely stand-alone application. It does not require nor use any existing web server that is already installed on your server.

If you are already running a web server on the system where EZproxy is running, do not attempt to install EZproxy within directories that are used by the web server.

Before getting started

EZproxy 6.4.4 requires users to obtain a WSKey to run the software. Before downloading EZproxy, please request your WSKey. To request and obtain a Key, please see Request a WSKey.

  1. Create a directory for EZproxy and make it your current directory with command such as:

    mkdir /usr/local/ezproxy
    cd /usr/local/ezproxy
    
  2. Download ezproxy-solaris.bin into this directory. If you download this file on a different system and use FTP to move it to your EZproxy server, be sure to perform the transfer using binary.

  3. Rename the download file from ezproxy-solaris.bin to ezproxy and make it executable with the commands:

    mv ezproxy-soaris.bin ezproxy
    chmod 755 ezproxy
    
  4. To create the default version of most of the files mentioned above, issue the command:

    ./ezproxy -m
    

    The "-m" stands for "missing file replacement" and this command can be used at any time to reconstruct any missing files without overwriting existing files that you have changed.

  5. To verify whether EZproxy can automatically detect your host name correctly, as well as to check whether firewalls may interfere with your ability to use EZproxy, issue the command:

    ./ezproxy -c
    

    This command will make your server connect to an OCLC server. Your server will provide its name and IP address, then the OCLC server will attempt to verify this information. Your server will then display various messages to let you know what changes may be required for EZproxy to function properly.

     Note: If you do not like the idea of your server connecting to an OCLC server, you may omit this step.

    If your network requires the use of a standard proxy server to connect out to the Internet, this test will fail. In this case, you will need to configure EZproxy to use your outgoing proxy server using the Proxy directive, and then you can complete the network connectivity test by finishing the installation of EZproxy and using a browser installed either on the same server or within your network to log in to the EZproxy Administration page, where you can use the Test network connectivity option. This performs a more thorough network test, including offering the option to incorporate your outgoing proxy server in the test.

  6. Use a text editor to edit the file config.txt. If suggested from the previous step, manually specify your host name in this file. The file also contains suggestions for other changes.

  7. Use a text editor to edit the file user.txt. To this file, add a line similar to this, changing someuser to the username you want to use for testing and somepass to the password you want to use for testing. In this example, admin should appear literally as shown.

    someuser: somepass:admin
    
  8. Copy and paste your WSKey (obtained by following the instructions at How to Request a WSKey) after the key command as follows, substituting your key for 123456789101112:

    ./ezproxy -k 123456789101112
    
  9. Start the server with the command
    ./ezproxy
    
  10. Using your web browser, connect to your server on port 2048. If your EZproxy server was named ezproxy.yourlib.org, you would use this URL:
    http://ezproxy.yourlib.org:2048/admin
  11. Enter the username and password that you created when you edited the user.txt file. This should bring you to the main server administration page.

    If, instead of the menu page, you end up at a page indicating that the EZproxy cookie was blocked, see EZproxy Cookie Blocked for information on why this happened and how to access it.

 Note: The options presented and how effictively they work will depend on how well you customized config.tt. As you make additional changes to config.txt, you will need to stop and restart ezproxy to make the changes take effect.

After you have completed your installation and are able to log in to the administration page, you can find the database stanzas necessary to configure resources on the Database stanzas page and information about different authentication methods on the Authenticate users page.

System requirements

EZproxy for Solaris (x86) requires Solaris version 10 or later running on Intel Pentium 4 and later processors or on AMD Athlon 64 and Opteron and later processors.

The minimum recommended configuration for an EZproxy for Solaris 10 (x86) server is not defined, although EZproxy's modest processor and memory utilization makes most systems manufactured since 1999 (and many produced prior) suitable for use. For specific guidance, please contact OCLC support. The following is required:

  • 10 MB of disk space for installation
  •  Additional disk space to accommodate user authentication files and server log files

Additional System Considerations

This program can be executed from a non-privileged account, so please consider running it from an account other than root. See RunAs for additional information.

If your site employs a proxy server for all outgoing connections to the Internet, you will need to enter the host and port information for this proxy server into the config.txt file using the Proxy directive.

If your site is protected by a firewall, external users may be unable to connect to EZproxy unless your firewall administrator allows incoming traffic to ports 2048 and above.

User Authentication

EZproxy can be configured to work with a variety of methods for authenticating users. For more information on these options, see Authenticate users.

EZproxy files

EZproxy uses a number of files that are automatically created during the installation process. For a list of those files and their purpose, see EZproxy system elements.

When installing EZproxy for Linux, you will download ezproxy-solaris.bin. This binary file is the download version of the EZproxy program for Linux. It must be renamed to ezproxy.

Technical details

Additional technical information can be found in EZproxy technical details.

Additional commands

The following are additional commands that can be used with EZproxy for Solaris 10.

Resetting all files

If you want to reset all of the files to their original distributed contents, you can use the command:

./ezproxy -r

If you want to restore just one or two of the original files, rename or delete the existing file that you want replaced, then issue the command:

./ezproxy -m

Startup script

To install the system startup script, issue the following command as root:

./ezproxy -si

If you later want to remove the startup script, issue the following command as root:

./ezproxy -sr

Update to EZproxy 6.4.4 GA for Linux

These instructions cover how to update existing Solaris 10 (x86) installations to EZproxy 6.4.4. These instructions are valid to update from any version of EZproxy to this release. This process will preserve all existing configuration files.

Before getting started

EZproxy 6.4.4 requires users to obtain a WSKey to run the software. Before downloading EZproxy, please request your WSKey. To request and obtain a Key, please see Request a WSKey.

If you have already obtained a WSKey for any EZproxy V6.x, you can use this same WSKey to upgrade to the newest version.

  1. Change your current directory to the directory where EZproxy is installed with a command such as:

    cd /usr/local/ezproxy
    
  2. Download ezproxy-solaris.bin (from the Download EZproxy page) into the directory where EZproxy is installed. If you download this file on different system and use FTP to move it to your EZproxy server, be sure to perform this transfer using binary.

  3. Use the following command to stop the old version of EZproxy:

    ./ezproxy stop
    
  4. Rename your existing copy of the program file ezproxy to another name such as ezproxy. yyyymmdd replacing yyyymmdd with the current year, month and day using a command such as:

    mv ezproxy ezproxy.yyyymmdd
    
  5. Rename the program and make it executable with the commands:

    mv ezproxy-solaris.bin ezproxy
    chmod 755 ezproxy
    
  6. During this step, if you are updating from EZproxy 5.0 or earlier, you will be asked to allow ezproxy.cfg to be renamed to config.txt and to allow ezproxy.usr to be renamed to user.txt. See EZproxy 5.1 New Filenames for more information.
    Create any new files required for the updated release with the command:

    ./ezproxy -m
    
  7. Optional. If you are updating from a EZproxy 5.0 or earlier, you can choose to rename your existing ezproxy.msg to messages.txt, or you can leave the existing file alone and EZproxy will create a new messages.txt file.
    If you would like to rename the existing file, issue the command:

    mv ezproxy.msg messages.txt
    
  8. If you are updating from EZproxy V5.7.44 or earlier, copy your new, full WSKey from the OCLC Developer Network WSKeys screen (obtained by following the instructions at How to Request a WSKey), and paste it into your command prompt window with the key command as follows, substituting your complete key for 123456789101112. If you are updating from EZproxy V6.0.8 or newer, you will not need to re-enter your WSKey to update:

    ezproxy -k 123456789101112
    
  9. Start EZproxy with the command:

    ./ezproxy &
    
  • Was this article helpful?