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

Upgrading to the .NET Electronic Delivery Utility

In ILLiad 10 the Electronic Delivery Utility's underlying components were updated from Delphi to .NET. EDU is now a .NET desktop application that reaches ILLiad through the Web API instead of a direct database connection. This page is for sites that already run ILLiad and the EDU and are updating to ILLiad 10 — it covers what to do on each EDU workstation right after the update.

Setting up EDU for the first time?

If this is a fresh install rather than an update, follow Setting up the EDU instead. For a summary of what changed, see What's new in the EDU Administrator Guide.

Before you start​

  • .NET 10 desktop runtime — this is installed as part of the ILLiad 10 installation, so most workstations will already have it. If a workstation doesn't (for example, EDU runs on a machine that isn't a full ILLiad install), install the .NET 10 Desktop Runtime from Microsoft before launching EDU.
  • The ILLiad Web API running and reachable from each EDU workstation.
  • Your ILLiad Web API base URL (typically your ILLiad site URL with /illiad/api).

Post-update steps (per workstation)​

  1. Verify Article Exchange keys (if used). If this workstation will deliver via Article Exchange, verify the site's OCLC Article Exchange keys are already populated. These are existing ILLiad OCLC keys — EDU reads them, it doesn't create or change them — so this is a check, not a setup step. If all are set EDU picks them up automatically; if any is blank, Article Exchange is unavailable and EDU names the missing keys in its Activity Log at startup. The five keys are OCLCILLAuthorization, OCLCILLPassword, OCLCWebServiceV2APISecret, OCLCWebServiceV2APIKey, and ILLiadWebPlatformConfig — see the EDU Administrator Guide for detail on how EDU uses them.
  2. Move billing to Odyssey Manager (if you used EDU billing). EDU no longer bills on send; Odyssey Manager handles billing centrally. Configure the corresponding billing customization keys in Odyssey Manager so billing continues.
  3. Stop the legacy Delphi EDU. The legacy EDU is a desktop application running on the workstation. Close the application, and disable any auto-start you set up for it — a shortcut in the Windows Startup folder or a Windows Task Scheduler task — so it doesn't relaunch and process the same files alongside the new EDU.
  4. Deploy the .NET EDU files. Obtain the .NET EDU distribution and copy its files into a new install directory on the workstation (don't overwrite the Delphi EDU's folder). The install directory contains:
  • ElectronicDeliveryUtility.exe — the main application
  • appsettings.json — machine-wide default settings
  • log4net.config — log output configuration

Keep the two EDUs in separate folders until you've verified the new one. 5. Complete first-run setup. The new EDU walks you through setup the first time it launches:

  1. API URL. Enter your ILLiad Web API URL (typically your site URL + /illiad/api), click Test Connection, then Next — enabled only after a successful test.
  2. Sign in. Enter a username/password or use SSO. On a shared/multi-tenant server, pick your site.
  3. Add watch directories. On Settings → File Processing, add one or more watch folders (each must already exist) — type or paste paths separated by commas, semicolons, or new lines, or use Add… to browse. Confirm the status bar shows Monitoring.
  4. Choose what EDU processes. On the same tab, check Process Lending Requests and/or Process Document Delivery Requests — Lending is on by default, but Document Delivery is off by default, so enable it if your site does Doc Del. Leave Auto Mode off for staff-triggered Send Selected Files, or enable it to send automatically as files arrive.

For the full first-run detail, see Setting up the EDU. 6. Run a test transaction end-to-end: drop a PDF named after a real lending transaction number into a watch directory and confirm the transaction records the delivery in history and the source file moves into the Backup subfolder. 7. Decommission, then uninstall, the legacy Delphi EDU.

  • Decommission first — take the old EDU out of service: stop it, remove it from staff workflow and any auto-start, and confirm the new EDU is handling deliveries. The old files can stay in place for a while as a fallback, so this step is reversible.
  • Uninstall later — once you're confident the new EDU is working, remove the legacy EDU software from the workstation entirely. This is the final cleanup and isn't easily reversed.
Two behavior changes to plan for
  • Billing moved. EDU no longer bills on send — billing is handled centrally by Odyssey Manager. Set the billing keys in Odyssey Manager if you relied on EDU billing.
  • Success status changed. On a successful send EDU now leaves the transaction at its Awaiting …Scanning status for your routing rules / Odyssey Manager to advance, rather than setting an "Electronic Delivery - Sent" status.
Settings and logs carry forward automatically

On first launch the new EDU performs a one-time migration that copies your earlier per-user settings forward, so you don't have to re-enter them. Logs don't move — they stay under %APPDATA%\ILLiad\ElectronicDeliveryUtility\Logs\. No action required.

Optional: launch EDU automatically at logon

EDU doesn't auto-start and has no service mode — a user must be signed in and EDU running for files to process. If you ran the legacy EDU unattended, recreate that with a Windows Task Scheduler task (or a Startup-folder shortcut) that runs ElectronicDeliveryUtility.exe at user logon.