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

Setting up the Electronic Delivery Utility

This page is for fresh installs β€” a new ILLiad site, or a new EDU workstation. It walks through first-run setup and the settings you'll configure once. If you're updating an existing site to ILLiad 10, start with Upgrading the EDU instead.

Already running ILLiad and updating to 10?

Follow Upgrading the EDU for the migration steps (stopping the old EDU, deploying the new files, decommissioning), then come back here for the settings detail.

Prerequisites​

  • Windows desktop OS.
  • .NET 10 desktop runtime β€” installed as part of the ILLiad 10 install; install it from Microsoft if a standalone workstation doesn't already have it.
  • Network connectivity from the workstation to the ILLiad Web API (HTTPS), destination libraries' Odyssey listeners (TCP, port 7968), and OCLC Article Exchange if you'll use it.
  • A staff account with ILLiad Web API credentials, or a configured SSO identity provider.

First run​

  1. API URL setup (Step 1 of 2). On first launch EDU opens the ILLiad API Setup window. Enter your ILLiad Web API URL; EDU auto-corrects it (adds https://, trims trailing slashes, appends /illiad/api when appropriate). Click Test Connection β€” Next enables only after a successful test.
  2. Sign in (Step 2). Enter a username/password or use SSO. On a shared/multi-tenant server a site picker appears. A Change button lets you reopen the API URL setup without restarting.
  3. Add watch directories. After sign-in, if no watch directory is configured, EDU first tries to default one from the server's image-path keys; if none resolve on this machine, it prompts you to open Settings β†’ File Processing and add one. See below.

Adding watch directories​

Set your watched folders on the Settings window's File Processing tab, in the Watch Directories box. You can either:

  • type or paste one or more folder paths, separated by commas, semicolons, or new lines, or
  • click Add… to browse and pick a folder (each pick is appended to the list).

Each folder must already exist β€” EDU does not create them. Click OK to save. Recursive watching is always on, so subfolders under each watched folder are monitored too; folders named Backup (and dot-prefixed folders) are skipped.

Choose what EDU processes​

On the same Settings β†’ File Processing tab, make two choices before you start:

  • Process types. Check Process Lending Requests and/or Process Document Delivery Requests. Lending is on by default; Document Delivery is off by default, so if your site does Document Delivery, turn it on here.
  • Sending mode. Leave Auto Mode off to have staff review and click Send Selected Files for each batch (the default), or enable it to send documents automatically as they arrive.
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 want it to launch unattended, create a Windows Task Scheduler task (or a Startup-folder shortcut) that runs ElectronicDeliveryUtility.exe at user logon.

Ports

EDU uses the standard Odyssey port 7968, which is already documented in ILLiad's Network Ports page as required inbound/outbound. There's no new port to open for the .NET EDU.

Finish setup​

  1. Verify Article Exchange keys (if used). If this workstation will deliver via Article Exchange, verify the site's OCLC Article Exchange keys are populated. These are existing ILLiad OCLC keys that EDU reads β€” it doesn't create them β€” so EDU needs no key setup of its own. If you're turning on Article Exchange for the first time, populate them as part of ILLiad's OCLC configuration. If any is blank, Article Exchange is unavailable and EDU names the missing keys in its Activity Log. The five keys are OCLCILLAuthorization, OCLCILLPassword, OCLCWebServiceV2APISecret, OCLCWebServiceV2APIKey, and ILLiadWebPlatformConfig β€” see the EDU Administrator Guide for detail on how EDU uses them.
  2. Billing runs in Odyssey Manager. EDU doesn't bill on send β€” Odyssey Manager handles billing centrally. If your site bills for document delivery, configure the corresponding billing customization keys in Odyssey Manager.
  3. Run a test transaction. Drop a PDF named after a real lending transaction number into a watch directory and confirm the file grid row reaches Sent, the transaction records the delivery in history, and the source file moves into the Backup subfolder.

For the full settings reference β€” configuration files, every settings tab, authentication detail, logging β€” see the EDU Administrator Guide.