Skip to main content
Version: ILLiad 10.0 (Pre-release) 🚧

Updating ILLiad to Version 10.0

ILLiad 10 is a major release. Most day-to-day workflows are unchanged, but there are a few things administrators must do before and after upgrading, and a few changes staff will notice. This page pulls those together; each item links to fuller documentation.

The one hard prerequisite​

Upgrade your database first — SQL Server 2019 minimum

ILLiad 10 requires Microsoft SQL Server 2019 or later. A site on an older SQL Server must upgrade the database before upgrading to ILLiad 10. See Hardware and Software Requirements.

For administrators​

Before you upgrade​

  • Confirm the environment meets the v10 minimums: SQL Server 2019, Windows Server 2019, and — for the new components — the .NET 10 ASP.NET Core Hosting Bundle on the server. .NET Framework 4.6.2 is still required and is kept alongside .NET 10.
  • Custom log configs: if you hand-edited the SystemManager or RapidManager log configuration files, keep a copy — the update replaces those files with a new shipped version, so any customizations must be re-applied afterward.

After you upgrade — verify​

  • Web API URL (WebApiUrl). The upgrade sets this for you automatically for most sites, deriving it from your existing WebURL. It deliberately skips sites it can't resolve confidently (for example a missing or loopback WebURL) and leaves the https://127.0.0.1/ILLiadApi placeholder for those, logging which sites. If you use DOCLINE, confirm WebApiUrl (under Web Interface > General) is your real server address before configuring DOCLINE. See Docline API Configuration.
  • Web Client address. The installer writes your Web API address into the Web Client's configuration from the IIS site binding, but falls back to localhost if it can't detect it. After upgrading, open the Web Client from a normal staff workstation and confirm it loads. See the note on the Web Client requirements.

What the upgrade changes automatically​

  • ILLiad DLL logs now roll: when DLL logging is enabled, the update rewrites each log4d.props in place (backing up the original) so the log rolls at 4 MB with 9 backups instead of growing without bound. See ILLiad DLL Log Rolling.
  • Client updates are matched to your server version: a Client build that needs a newer server is not offered until the server is upgraded. See Client Auto-Update and Server Version Matching.

New server components you now run​

ILLiad 10 adds .NET 10 components installed by the ILLiad server install/update:

  • Odyssey Manager — rebuilt as a .NET 10 Windows Service; PDF/TIFF conversion and automatic Odyssey billing are now built in. The Windows Service name changed from ILLiadOdysseyManager to ILLiad Odyssey Manager — update any service monitors or scripts that reference the old name. See Odyssey Manager Administrator Guide.
  • ILLiad Web Client — a new staff web interface hosted on the ILLiad server under IIS.
  • ILLiad Indexing Service — a background service that powers Web Client search.
  • ISO 18626 Manager — supports the ISO 18626 interlibrary loan standard (off by default until enabled). See ISO 18626 Overview.

The Electronic Delivery Utility is also rebuilt on .NET in v10, but it is a client application, not a server component — it runs on a staff workstation and connects through the ILLiad Web API. See Electronic Delivery Utility (.NET) Administrator Guide.

For staff​

  • Windows 10 is past Microsoft's end of support and should be upgraded. This is not a hard ILLiad requirement — nothing inside ILLiad forces it. The v10 requirements were updated to reflect Microsoft ending support for Windows 10, so workstations should move to a supported version of Windows.
  • DOCLINE works differently. The old embedded DOCLINE browser and downloaded scripts are gone; DOCLINE now connects directly through its API, and importing/receipting is automated. If your library used custom DOCLINE field mappings, note that the old FieldTranslation.xml file is gone in v10 — mappings now live in a database table and any custom ones must be re-created. See Docline API Field Translation.
  • The ILLiad Web Client is a new, browser-based way to do day-to-day processing, alongside the Windows client.
  • PDFs open natively in the Windows client instead of being converted first.
  • Add-ons that open a web page now render on Microsoft Edge WebView2 instead of the old embedded Chromium engine. They keep working, and the WebView2 Runtime is installed for you with the client. If you maintain custom browser-hosting add-ons, test them after upgrading — see Converting Add-ons to Use the Chromium Browser.