|
Configuring
the Access Component for WebZ (Windows NT)
Contents
Introduction
Document Conventions
Requirements
Procedure
Using the Access Component with Your Patron Data
Introduction
This document
explains how to configure the Access component
using a third-party relational database management software (RDBMS) package
(i.e., Sybase or Microsoft SQL Server) with the Open SiteSearch WebZ system
for the Windows NT operating system.
The instructions
below describe how to create a database called accessdb
from a sample data file and configure the Access component to start with
the WebZ system. This is a sample database for testing your Access component
configuration that illustrates some of the possibilities for patron authentication,
authorization, and initialization.
Document
Conventions
- <WebZ_root>
refers to the location of your installed WebZ environment.
- Version 4.0.x
refers to any SiteSearch version prior to 4.1.0; that is 4.0.2,
4.0.1, 4.0.0a,
and 4.0.0.
Requirements
Before completing
the steps below, you must
Refer to your
RDBMS documentation for instructions regarding database creation and administration.
Procedure
Follow the instructions
below to configure the Access component to work with the WebZ system and
to set up a sample database for testing the configuration.
1. Start
your RDBMS software.
|
2. Create
a new database called accessdb.
|
3. Import
the accessdb.sql sample data file into the accessdb database.
- Version
4.1.0 and higher: You
can find this file in the <WebZ_root>\accesssql directory.
- Version
4.0.x: You
can find this file in the <WebZ_root>\accesssql\bin
directory.
|
4. Retrieve
the contents of the accessdb database to ensure that the sample
data imported correctly. The database should contain these tables:
authos, dbs, inst, resources, userdb, userresource, beginning with
version 4.1.2, instdbill, as described in the accessdb
Database topic.
|
5. Turn
on user name and password authorization for the JaSSI Access client
in the Access.ini configuration
file.
|
6. Verify
the URL and driver for the RDBMS Java Database Connectivity (JDBC)
driver.
You were
prompted for the SQLDriver Classname and the JDBC driver URL during
the WebZ installation.
The SQLDriver
Classname specifies the fully qualified class name of the RDBMS
driver, and the JDBC URL defines the Uniform Resource Locator (URL)
and protocols that the JDBC driver uses to locate the RDBMS server.
You can find the values for both the SQLDriver Classname and JDBC
URL in your RDBMS software documentation.
Ensure that
the SQLDriver and URL variables are correctly defined in the [JDBC]
section of the AccessServer.ini file in the <WebZ_root>\ini
directory.
Important
Notes: |
(1)
The port value included in the URL variable in AccessServer.ini
MUST equal the port number defined for your RDBMS server configuration.
If you change the port, you may need to stop and restart your
RDBMS server.
|
|
(2) If your SiteSearch environment includes Record Builder,
the port must also have the same value as the URL variable in
the [JDBC] section of the AccessServer_rb.ini configuration
file. In other words, the port must have the same value in msql.conf,
AccessServer.ini, and AccessServer_rb.ini. |
|
(3)
If you change the port, you
may need to stop and restart your RDBMS server. |
|
7. Shut
down the WebZ system.
If the WebZ
system is running, stop all of the servers (JaSSI, ZBase, and OpServe).
Note: |
You
do not need to stop the Web server or the SQL server.
|
|
8. Start
the WebZ system.
|
9. Test
the Access configuration.
|
Return
to Contents
Using
the Access Component with Your Patron Data
After you successfully
test your Access component configuration with the sample accessdb database,
use the schema specified in the accessdb.sql data file or the accessdb
Database topic to create a new instance of the accessdb database.
Then populate the database with patron access data relevant to your site
and retest the Access configuration. See the section named Sample
Data for accessdb in the accessdb Database topic for ways that the
sample data illustrates possible uses of the Access component.
Return
to Contents
See Also
Operating
the WebZ System on Windows NT
Access Server Configuration Files
Access Client Configuration Files
accessdb Database
Testing the Access Component Configuration
for WebZ
The updateSQL.pl Utility
|