Main -> Documentation -> OCLC SiteSearch Record Builder -> Configuring the Access Component for Record Builder (Windows NT)

Configuring the Access Component for Record Builder (Windows NT)

This document explains how to configure the Access component for Record Builder using a third-party relational database management software (RDBMS) package (i.e., Sybase or Microsoft SQL Server) for the Windows NT operating system.

The instructions below describe how to create a database called rbdb from a sample data file and configure the Access component to start when Record Builder starts. rbdb is a sample database for testing your Access component configuration that illustrates some of the possibilities for Record Builder staff authentication, authorization, and initialization.


Requirements

Before completing the steps below, you must:

Refer to your RDBMS documentation for instructions regarding database creation and administration.


Document Conventions

  • <WebZ_root> refers to the location of your installed WebZ environment.

Procedure

Follow the instructions below to configure the Access component to work with Record Builder and to set up a sample database for testing the configuration.

1. Start your RDBMS software.

2. Create a new database called rbdb.

3. Import the rbdb.sql sample data file into the rbdb database. You can find this file in the <WebZ_root>\accessdb\rbv0 directory.

4. Retrieve the contents of the rbdb database to ensure that the sample data imported correctly. The database should contain the ten database tables that comprise rbdb.

5. Turn on user name and password authorization for the JaSSIRB Access client in the Access_rb.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 Database Builder 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_rb.ini file in the <WebZ_root>/ini directory.

Important Notes:

(1) The port value included in the URL variable in AccessServer_rb.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) The port must also have the same value as the URL variable in the [JDBC] section of the AccessServer.ini configuration file, the access server configuration file for WebZ. In other words, the port must have the same value in your RDBMS server configuration, AccessServer_rb.ini, and AccessServer.ini.

7. Shut down both Record Builder and WebZ.

If Record Builder or WebZ is running, stop all of the servers (JaSSIRB, ZBaseRB, JaSSI, ZBase,and OpServe).

Note:

You do not need to stop the Web server(s) or the SQL server.

8. Start Record Builder and WebZ.

9. Test the Access configuration for Record Builder.



Using the Access Component with Your Record Builder User Data

After you successfully test your Access component configuration with the sample rbdb database, use the schema specified in the rbdb.sql data file or the rbdb Database topic to create a new instance of the rbdb database. Then populate the database with user access data for your Record Builder users and retest the Access configuration. See the section named Sample Data for rbdb in the rbdb Database topic for ways that the sample data illustrates possible uses of the Access component.


See Also

Access Component Overview
Access Server Configuration Files

Access Client Configuration Files
rbdb Database
Operating Record Builder on Windows NT
The updateSQL.pl Utility


[Main][Documentation][Support][Technical Reference][Community][Glossary][Search]

Last Modified: