Web Pages Folder Structure

Follow

The ILLiad web site folder structure is set up in two main configurations, the Single Server and the Shared Server. The default location for the folder is c:\illiad\inetpub\wwwroot\illiad.

Single Server Configuration

The main folder in the Single Server configuration is the ILLiad folder. Information for both Borrowing and Document Delivery live in the ILLiad folder. The ILLiad folder also contains subfolders for CSS, Images, Lending, and Web reports. Within both the Lending and Web Reports folders are a CSS and Images folder:

  • CSS
    • Images
  • Lending
    • CSS
      • Images
  • Testweb
    • CSS
      • Images
    • Lending
      • CSS
        • Images
  • WebCirc
    • CSS
      • Images
  • Web Reports
    • CSS
      • Images

Shared Server Configuration

On a Shared Server there is only one Web Reports folder per server; they are not listed under each NVTGC Code folder.

  • ABC (NVTGC Code)
    • CSS
      • Images
    • Lending
      • CSS
        • Images
    • Testweb
      • CSS
        • Images
      • Lending
        • CSS
          • Images
    • WebCirc
      • CSS
        • Images
  • Web Reports
    • CSS
      • Images

Shared Server Web Site Structure

Single server installations of ILLiad generally have one Borrowing/Document Delivery interface for all customers. The directory is set by the WebPath customization key and allows customers to still choose a delivery location (if applicable) from the registration and change user information web pages.

Shared server installations can choose to share a web interface for all customers or have a separate web interface for each processing site. By default, new shared server ILLiad installations get both sets of web pages so that you can choose your setup more easily.

For example, if your shared server installation has two site codes called ABC and XYZ, you can have one set of web pages under the default location of c:\illiad\inetpub\wwwroot\illiad where the NewUserRegistration.html and ChangeUserInformation.html pages allow customers to edit their processing site code.

The value the customer chooses determines which processing site will view and process his or her requests as well as process his or her registration. But the customer who chooses ABC would see all the same pages as the customer who chooses XYZ.

If you would like the two sites to have separate web interfaces, you can have two sub-directories under the illiad web folder: c:\inetpub\wwwroot\illiad\ABC and c:\inetpub\wwwroot\illiad\XYZ.

The NewUserRegistration.html and ChangeUserInformation.html pages would not let sites choose between ABC or XYZ, but would have that value as a hidden field so that the pages under ABC were set to ABC and the pages under XYZ were set to XYZ.

The sub-directories would also have a logon.txt file that contained two lines:

ABC

ABCPassword

Where ABC is the processing site code (NVTGC).

The web interface for ABC and XYZ can then be customized completely independent of each other with different layouts, request types and required fields on web forms.

Web Pages and RemoteAuth Authentication

If you are a Shared Server installation with multiple sites using RemoteAuth authentication (a single sign-on form of authorization), all of your institution's sites must use the same set of shared web pages.

With Remote Auth, the ILLiad DLL recognizes existing ILLiad users and routes them automatically to the proper website based on the NVTGC value attached to the user record.

However, new ILLiad users require ILLiad registration, so the NVTGC value does not yet exist in the user record. The ILLiad DLL does not know to which website pages the user should be returned to register, and therefore will consistently default to one set.

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.