The system requirements for HAN

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • CPU: quad core recommended
  • 8 GB RAM minimum, depending on your subscription type/organization's needs:
    • Entry & Small: 8 – 12 GB
    • Large: 12 – 16 GB
    • Infinite: 16 – 24 GB
  • 150 GB available disk space minimum, depending on your subscription type/organization's needs:
    • Entry & Small: 150 – 200 GB
    • Large: 250 GB
    • Infinite: 500 GB
  • Wildcard DNS record (HAN server FQDN) pointing to the HAN server in the local DNS1
  • Wildcard SSL certificate (HAN server FQDN) 2
  • IP adress with the free ports 80 and 443 for HTTP and HTTPS
  • Prerequisite for hypervisors: Paravirtual network adapter
  • Up-to-date PDF reader

Please take care that there are no additional roles or functions, such as Remote Desktop Services, IIS, other web servers or similar, may be installed on the server.

The HAN update feature updates the integrated Apache installation.

HAN administration

  • PC with 64bit Windows 7 or later and the latest service pack

Clients for e-jornal access

For the devices on which the E-journals are to be called, no special requirements with respect to the operating system or the equipment are needed, accept of a modern web browser. To use the Search or e-journal access no additional program or plugin need to be installed.

1 Wildcard DNS record

An important part of managing e-resources is the statistical evaluation of the content offered and its usage.

This is made possible through use of the reverse proxy technique, so that online resources are retrieved over the HAN server rather than directly from the provider. The technical implementation involves parsing the source text of the online resource to route the connection through the HAN server. Starting with HAN v3 the required data, such as the target server and the selected resource (specified by its HAN ID), is integrated in the name of the HAN server.
The resulting URL takes the following form:

http://<provider server name>.<HAN ID>.<FQDN of the HAN server>/<URL>

This modification of the URL necessitates a wildcard DNS record in the host server to enable retrieval of the resource.



is rewritten as follows when called over HAN:

HAN ID: nytinternal
FQDN HAN Server:

2 Wildcard SSL Certificate

When online resources are called over SSL, the following problem arises: The address of a server certificate made out to the FQDN of the HAN server does not match the server name in the address used for retrieval. The user receives a certificate warning stating that, although the certificate is valid, the address does not match.

This problem is eliminated by using a wildcard certificate, which allows one (and only one) variable position preceding the server name.
Starting with HAN v3.1, a dot (.) is no longer required between the provider-server name and the HAN ID; a different character may be used instead. As a result, the variable part preceding the HAN server name is accepted as a match and thus is covered by the certificate.

Wildcard certificates are specified in RFC 2818 ( and RFC 2459 ( spezifiziert.