Adlib API home page > Documentation > System requirements

System requirements

  • To wwwopac.ashx 3.6.13277 up to 3.7.15106.2, the same system requirements apply as to wwwopac.exe, with the added requirement of an installed .NET framework version 4.0.3 or higher. (4.0.3 is an update for the .NET Framework 4 and can be downloaded for free from Microsoft.) From wwwopac.ashx 3.7.15106.2, .NET framework version 4.5 is required.
    For information about the system requirements for wwwopac.exe, see the WWWOPAC installation guide which can be downloaded here.
  • Further, Microsoft IIS (Internet Information Services) must be configured on the machine which is going to act as the image server. (The image server is the server on which wwwopac.ashx is going to run.)
  • The wwwopac.ashx must be installed on Windows Server 2003 or higher.
  • The standard wwwopac.ashx has been compiled in any-cpu mode, which allows it to act as a true 64-bit version on 64-bit systems and as a 32-bit version on 32-bit systems. 32-bit software can often be used normally on 64-bit systems, but if you use a 32-bit Oracle client on a 64-bit system, then the standard wwwopac.ashx will run into problems. For this case you will need a version of wwwopac.ashx compiled in 32-bit mode.

No longer supported data structure aspects

  • From wwwopac.ashx 3.7.14032, database structures processed by adlwin.exe versions older than 6.4 are no longer supported. This means that the domain column needs to be present in thesaurus index tables; in older versions, the domain and term were separated by a double colon in the same column. If you have an old data structure and wish to use wwwopac.ashx 3.7.14032 or higher, your database structures need to be converted. Please contact the AIS Helpdesk for more information about this upgrade procedure.
  • From wwwopac.ashx 3.7.14032, internal links need to have been linked on link reference (priref), not on value. This is the case by default in model applications 4.2 and higher. Older applications usually have internal links linked on value. If you have an old data structure and wish to use wwwopac.ashx 3.7.14032 or higher, your database structures and application need to be converted. Please contact the AIS Helpdesk for more information about this upgrade procedure.
  • Binary columns in SQL tables are no longer supported from wwwopac.ashx 3.7.14032: therefore the record data must be stored in XML format. This also means that SQL Server 2000 is no longer supported. If you have a SQL database with binary columns and wish to use wwwopac.ashx 3.7.14032 or higher, your database needs to be converted. Please contact the AIS Helpdesk for more information about this conversion.

Preparing Adlib for image retrieval via wwwopac.ashx

Follow the global steps below to set up your Adlib system for the retrieval of images via wwwopac.ashx:

  1. The wwwopac.ashx is not a standard part of a local Adlib system and won’t be installed automatically. See the WWWOPAC installation guide and the other documentation on this Adlib API website for more information about the installation. The wwwopac.ashx must also be configured so that it knows where to look for the images and how to retrieve them; see the The adlibweb.xml file documentation on this website for instructions.
  2. In Adlib Designer, for the image field in which you link images, set the Storage path, Retrieval path, and/or Thumbnail retrieval path with a call to wwwopac.ashx. (Only fill in the properties which you want to use.) See the Designer Help (unpack the zip file and double-click the resulting Adlib Designer Help.chm file in Windows Explorer to open this Help system) or the Release notes 6.5.1 for an explanation of these options. See the API section on this website for a description of the syntax for calling wwwopac.ashx
  3. By setting the path options above, you have specified a large part of the URL and the path to images in advance, so that in the image field in records only the name of the image for example, without path, has to be present. Therefore, you’ll have to check and adjust all your records with linked images for the correct values. Use search-and-replace to remove any part from a fixed path in all links.
    From now on, when you create links to images, you’ll have to adjust them (if necessary) so that only the file name (or the proper part of the path to the image in your situation) is filled in, not the entire path.