Setting up the sample database system

Introduction

The sample texts referred to are the texts used in the online demonstration of TextServer available at www.textserver.com. This online demonstration software is included with the TextServer distribution under TextServer/webpub. Having installed the sample texts, it should be possible to access these sample texts, using the provided ASP scripts.

Prior Requirements

If you have not done so please ensure that dcQsm2Oledb.dll and dcQsm2Locale.dll are registered, and that the core OLEDB components provided for redistribution by Microsoft are installed.

Ensure that the catalogs directory defined in the NT system registry (typically this is TextServer/Catalogs) does not contain a shortcut named catalog1, and that the file $(SampleCatalog)/catalog1.qsm where SampleCatalog is a path macro specified in the registry does not exist.

If you are the individual who earlier created an existing catalog named "catalog1" you may elect to have TextServer itself delete the above files by simply issuing the SQL command to call_oledb:

drop catalog catalog1 cascade;

If for any reason you are unable to remove these files using TextServer, and are certain that your organisation has not deliberately created a valued TextServer catalog coincidentally named catalog1, the files mentioned above may be safetly deleted if they exist.

Construction

If desired place a shortcut to the program TextServer/Release/call_oledb.exe on your desktop, having the parameters "-t .-E" and starting in TextServer/ddl. Alternatively, manually invoke this program in the fashion described above.

Having invoked the program you should see a prompt inviting input. Type @build to build the entire sample catalog named catalog1. Note that call_oledb.exe will report errors and fail, if the dll's specified above have not been registered.

Permissions

All users (possibly including IUSR_computername) who wish to access the constructed sample catalog must:

• Have NT permissions which allow them to at a minimum read the catalogs directory, the shortcut catalog1.lnk which references the catalog, the catalog file itself, and relevant text indices and external text files.
• Be indentified as a user who may connect to the desired TextServer catalogs.
• Have permissions (assigned through grants) to access the tables of interest within the catalogs being accessed.

To create allow scripts run under IIS to access the sample catalog, issue the following commands to TextServer via the program call_oledb.exe:

SET CATALOG 'catalog1'
create authorization "IUSR_computername@computername";

Repeatability

This installation process is repeatable.