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-directory would also have a logon.txt file that contains one line:

ABC

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.

Test Web

Within the default web structure folder, there is also a Test Web folder containing default web pages, lending web pages, CSS, and javascript files. Feel free to rename the folder to accommodate your site needs. If you choose to rename or move the Test Web folder, then the Webpath.txt file inside the Test Web folder will provide the location of that directory. For example, if you put your test web in c:\inetpub\wwwroot\illiad\testweb, the webpath.txt file inside that folder would have one line that says c:\inetpub\wwwroot\illiad\testweb for the DLL to know where to look for those pages.

If you have a separate set of web pages then you may have to consider placing the Webpath.txt in a separate directory depending on where your web pages are located. During user registration, if you don't have a Webpath.txt file, then the dll will direct back to the default directory set in WebPath customization key. This could cause a user to be directed to the wrong set of web pages or even an error page. Ideally, if the separate web pages are in c:\inetpub\wwwroot\illiad\NVTGC\ then the WebPath.txt file should have that path specified and the file placed in that folder. As a result, the dll will keep the user to that particular web directory.