OCLC recommends that you use the Apache server included with the SiteSearch installation as a dedicated server for your WebZ Z39.50 and non-Z39.50 resources (and the Record Builder application included with OCLC Database Builder, if applicable) to ensure searching efficiency and ease of administration for the following reasons:

• If you use your existing Apache server to host the Open SiteSearch system in addition to hosting other Web resources, the server's performance may be affected.
• For WebZ to function with your existing Apache server, you must place your HTML and image files in directories directly underneath your Web server's document root directory. This may cause confusion if you have additional non-SiteSearch directories at this level.
• If you are using the Record Builder application included with Database Builder, it is not possible to run WebZ and Record Builder on the same Web server port. You can add the WebZ extension to your existing copy of Apache and use this software as Record Builder's Web server, but you must specify another Web server port for Record Builder, use another httpd.conf file (with another name) for Record Builder, and create a separate startup script for Record Builder's Web server. If you use the Apache server included with the SiteSearch installation, the Database Builder installation procedure automatically takes care of all these tasks for you.

1. Edit your existing httpd.conf file:

• Move to the <ExistingServer_root>/conf directory and open the httpd.conf file in a text editor.
• Define the location of the WebSvrExt.ini configuration file. Add the following line to the end of httpd.conf.

WebZIni <WebZ_root>/ini/WebSvrExt.ini



• Save and close httpd.conf.

2. Rename WebZ's index.html file:

• Move to the <WebZ_root>/htdocs/obiv1 directory.
• Rename index.html as sitesearch.html.

3. Edit the appropriate interface style configuration files (pagesFrame.ini and pagesNoFrame.ini) to the change the reference to WebZ's index page (index.html) file to sitesearch.html:

• Move to the <WebZ_root>/ini/interface/obiv1 directory, and open pagesFrame.ini in a text editor. Find the index variable at the top of the [pages] section:

index = index.html

• Change index.html to sitesearch.html. The variable should now look like the following:

index = sitesearch.html

• Save and close the file.
• Repeat the above steps for pagesNoFrame.ini.

4. Move the HTML and image files associated with the OBI, version 1 to the existing Apache server's document root directory. Copy the following directories and files located in the <WebZ_root>/htdocs/obiv1 directory into the <ExistingServer_root>/htdocs/ directory:

• /error
• /help (and its associated subdirectories)
• /html
• /images
• sitesearch.html

5. Configure a new DocumentRoot for the WebZ system to locate the OBI HTML and image files:

• Move to the <WebZ_root>/ini directory.
• Open the JaSSIServer.ini configuration file in a text editor.
• Edit the value of the DocumentRoot variable in the [JaSSI] section to reflect the full path name of the <ExistingServer_root>/htdocs directory.
• Save and close JaSSIServer.ini.

6. Move the WebZ Extension to <ApacheInst_root>.

• Create a new directory named webz in the <ApacheInst_root>/src/modules directory.
• Copy the contents of the <WebZ_root>/httpd/apache_1.3.x/libexec/platform directory, where platform is the type of operating system that your host runs on, into the <ApacheInst_root>/src/modules/webz directory.

7. Create a new file named Makefile in the <ApacheInst_root>/src/modules/webz directory with the following contents:

all: libWebZ.a: echo "libWebZ.a build"

This file allows the server to recompile with the WebZ Extension.

8. Stop the Apache server in <ExistingServer_root>, as described in the server documentation.

9. Create the Apache make files.

• Move to the <ApacheInst_root> directory.
• Type the following at the command prompt, without the continuation characters ("\"), which are only included for readability. If you wish to compile any additional modules, include the appropriate enable-module= statements as part of this command line. See the Apache documentation for information about compiling third-party modules.

./configure \ --with-layout=Apache_install_directory --activate-module=src/modules/webz/libwebz.a \ --enable-module=webz \ --enable-module=log_confide \ --enable-module=usertrack

You see messages like the following:

Configuring for Apache, Version 1.3.6 + using installation path layout: Apache (config.layout) + activated webz module (modules/webz/libwebz.a) Creating Makefile Creating Configuration.apaci in src Creating Makefile in src + configured for Solaris 260 platform + setting C compiler to gcc + setting C pre-processor to gcc - E + checking for system header files + adding selected modules + doing sanity check on compiler and options Creating Makefile in src/support Creating Makefile in src/main Creating Makefile in src/ap Creating Makefile in src/regex Creating Makefile in src/os/unix Creating Makefile in src/modules/standard

11. Type "make" at the command prompt to recompile the Apache server.

Click here for a listing of messages similar to that shown as the server recompiles the modules defined in the config.status file.

13. Verify that the Web sites and resources currently running on the existing server function correctly with the new module(s) before testing the WebZ system:

• Start the existing Apache server in <ExistingServer_root> as instructed in the server documentation.
• Navigate through the resources, making sure that nothing has been affected by the adjustment to the server configuration.
• Pay particular attention to any advanced features implemented in the Web site(s), such as CGI scripts or JavaScript.

14. Add a link on the existing server's index.html page to the OBI logon screen.

• Move to the <ExistingServer_root>/htdocs directory.
• Open the index.html file in a text editor.
• Add a link similar to the following in the index.html file to allow you to test access to the OBI:

<A HREF="sitesearch.html">Search the WebZ System</A>

• Save and close the file.

15. Start the WebZ system.

16. Test the WebZ system through the new server.

• Open the existing server's index.html page in a Web browser.
• Click the WebZ link that you created in step 14. You should see the logon screen for the OBI, version 1:

• Use the default User ID, WebZUser, and password, WebZUser.
• Click to move to the database selection screen.
• Perform several searches and review the search results to ensure that the system functions correctly.

If this test fails for any reason, repeat the steps above to ensure that you have added the WebZ Extension correctly.

This listing includes continuation characters ("\") for long lines. These characters do not appear in the actual messages that you see while you recompile the Apache Web server.