• Vendor documentation can be found at EZProxy Support

• Suggested definitions for many resources may be found at Database Setup
• Note that in our configuration file Chadwyck-Healey has a special setup because of RefWorks linking issues. See main Chadwyck-Healey entry for instructions. Subsequent entries must be below initial entry.
• Where something is in the file matters. It is read top down.
• When creating a resource configuration stanza, determine whether javascript is used.

• Sample configuration entry without javascript:
• * T Journal Title
• * U URL e.g. http://mainserver.publisher.com
• * H other hosts at resource? e.g. otherserver.publisher.com
• * D top level domain e.g. publisher.com or publisher.ac.uk

• Sample configuration with javascript:
• * T Journal Title
• * U http://mainserver.publisher.com
• * HJ otherserver.publisher.com
• * DJ publisher.com

• Our configuration file is edited using the text editor vi.
• EZProxy processes must be restarted for configuration changes to be operational. At present we must restart from the web admin page.

• Removing unused host log entries
  1. Go to http://silk.library.umass.edu/status [Admin Login required]
  2. In the section entitled Host Maintenance select the radio button for “Remove XXX hosts that have not been used in over 30 days
  3. Select the Process button
  4. Select the Administration link at the top of the page to go to the Admin page.
  5. Select Restart Proxy from the Admin page menu.
• If time permits, review message log (available via Admin page also) for problems. Restarting no longer yields syntax error messages for configuration file as it did in the past, you must look in the message.txt log file.

• Notices of available upgrades to the EZProxy software are announced on the Listserv. Do not be hasty in requesting load of upgrades unless a bug fix is urgently needed. Each upgrade contains all previous upgrades. There is no risk in skipping one.

• Proxy server IP address is 128.119.168.112
• Get the time of the incident from the vendor
• Logfile is visible in web admin for current day only
• Accessing UNIX side saved logs.
  1. Login and change to logs directory e.g. cd logs
  2. View available logs e.g. ls
  3. Saved logs have timestamp of date/time they were saved in filename.
  4. Use UNIX commands to search entries in log to find offending username, below is one way using the more command
     • more filename opens file
     • /20110605:02 goes to that text string timestamp forward in the file
     • h will display a help file of commands
     • q will quit you out of the more function
  5. If using Putty, you can right click on header to copy screen to Clipboard
  6. Alternatively use psftp to ftp the entire logfile to your PC
• Send username and explanation to abuse@umass.edu requesting assistance

Primary Contact: Linda Matson