Related Topics

HOWTO: Backing Up the ILLiad Database
HOWTO: Breaking the User Link in the ILLiad Database
PROBLEM: Cancellations or OCLC Reasons for No are all updating as Other
HOWTO: Changing the Port for Microsoft SQL Server 2000
HOWTO: Changing the size of a field in the ILLData database
See more

Other Support Options

Contact Atlas Systems
Phone Numbers, Support Options, Online Help, and more.
Listserv
Pose a question to other users.

Page Tools

Print this page Print this page
E-mail this page E-mail this page

Feedback

How helpful was this article?
Suggestions:

Revised:January 6, 2006 (mc)
Version:All versions
Revision:1
HOWTO: Updating Across a Multiple Server ILLiad Installation
January 6, 2006

SUMMARY

Often ILLiad will be installed across multiple servers. Such an installation requires a SQL Server, a Web Server, and a Share Server. Note that these may be installed across two server machines, usually a SQL Server and a Web/Share server, or across three servers, each with it's own component.

To update the ILLiad server(s) to a new released version, perform the following steps:

  1. Run the ILLiad AutoUpdater (ILLiadUpdate.exe) from the Web Server. Note that in a normal ILLiad Server Installation, this file will be located in the Admin folder within the ILLiad share (X:\illiad\Admin\ ).

    All of the directories should point to the local machine except for the ILLiad Backup Directory. That folder should be the local path from the perspective of the SQL Server. For example if you are backing up your database to the E drive on the SQL Server, the ILLiad Backup Directory should be e:\illiad\backup\ regardless of the E drive on the Web/Share server. You would not want to map a drive to the SQL server from the Web/Share server for that folder, because the backup script runs on the SQL Server and executes from its perspective.

  2. The BDE (Borland Database Engine) points any database updates made by the AutoUpdater to the ILLData database on the SQL Server machine. Note that if the BDE does not exist on the web server, or if it is configured improperly, the web pages themselves will not function.
  3. The AutoUpdater will update the Database via the BDE, and the ILLiad share files locally on the web server.
  4. After the update, copy the entire ILLiad share (or selected updated files) to the File Share Server if your ILLiad share is on another machine.

More Related Topics

PROBLEM: Class Not Registered error when trying to initiate Z39.50 Searching
PROBLEM: Incorrect Queues and E-mail Routing Entries in the ILLiad Client for a Shared Server Site
HOWTO: Enabling Logging on the ILLiad Gateway
HOWTO: Enabling Logging on the ILLiad Web DLL
HOWTO: Increasing the Username field in the ILLiad database
INFO: ILLiad and McAfee VirusScan 8
OCLC ILLiad and Windows Server 2003
INFO: ILLiad and the NVTGC Field
HOWTO: Implementing SSL with ILLiad
HOWTO: Importing a Customized List of Addresses to ILLiad
HOWTO: Importing Pre-ILLiad Copyright Information into your ILLiad Database
PROBLEM: Z39.50 Searching Form gives File Not Found error for Yaz.dll
INFO: Z39.50 Profiles in ILLiad
INFO: Z39.50 Compatibility in ILLiad
INFO: What Ports are Required to be Open for General ILLiad Use?
INFO: User Request Limits
PROBLEM: I/O Error 32 or Path not Found when opening the Borrowing Request Form
HOWTO: Migrating an ILLiad Database to a New ILLiad Server
PROBLEM: Error Message "Login failed. Reason: Not associated with a Trusted SQL Server connection"
PROBLEM: SQL Server Agent fails when executing job to run ILLiad Connector
ERROR: SQL ERROR: Unmatched '' near TransactionNumber
PROBLEM: EDBEngine Error: Vendor Initialization Failed
Microsoft SQL Server 2005 Compatibility
HOWTO: Changing the Default Request Type for Manually Entered Transactions
INFO: Required ILLiad Server Permissions
HOWTO: Routing Rules Across Modules
BUG: Routing Rules for Borrowing and Doc Del do not work using the ILLiad Connector