1. Do you want to install bug fixes only or bug fixes and enhancements? OCLC recommends that you upgrade to a complete 4.1.2a environment.

• Bug fixes and enhancements. Go to Question 2.
• Bug fixes only. Go to Applying 4.1.2a Bug Fixes to an Existing SiteSearch Environment.

3. Have you customized SiteSearch in ANY way?

• Yes. Go to Upgrading from Version 4.1.2 to a Complete 4.1.2a SiteSearch Environment.
• No. Install SiteSearch 4.1.2a in a separate environment, as if you are installing the software for the first time. See Installing and Configuring the Open SiteSearch Suite Then test the 4.1.2a installation, as described in Testing the Open SiteSearch Suite Installation. Finally, make 4.1.2a your production environment.

1. Have you downloaded any patches or bug fixes with .class files from the SiteSearch FTP site for Java classes for which we do also not provide the .java source files?

• Yes. Delete these .class files before proceeding to step 2.
• No. Go directly to step 2.

2. Back up your existing environment in a separate directory.

• Stop the Web server, the WebZ system, and, if you are providing user authorization through the WebZ interface, the SQL server.
• Copy the <WebZ_root> environment into a backup directory. This backup directory is a safeguard only; you do not use it in this procedure.

3. Create a temporary directory (<TempDir_root>) and install the SiteSearch 4.1.2a WebZ component in this directory.

4. Copy the SS4_1_2a.jar file from the <TempDir_root>/classes/lib directory into the <WebZ_root>/classes/lib directory. There should now be two SS*.jar files in the <WebZ_root>/classes/lib directory, SS4_1_2.jar and SS4_1_2a.jar.

5. Edit your CLASSPATH environment variable to read the SS4_1_2a.jar file.

An example of the required CLASSPATH statements follows.

.:<fullpath to JDK>/lib/classes.zip:<WebZ_root>/classes/: \
<WebZ_root>/classes/lib/pears.jar: \
<WebZ_root>/classes/lib/SS4_1_2a.jar: \
<WebZ_root>/classes/lib/mail.jar: \
<WebZ_root>/classes/lib/activation.jar

UNIX Administrators: After you edit your CLASSPATH variable, log out of your UNIX session and log back in to activate the new settings.

6. Edit the ssmgr.hostname file (in the <WebZ_root>/scripts directory), where hostname is the name of the host system where your existing Open SiteSearch environment is installed, in a text editor. You must change the following item, which is above "DO NOT edit below this line" statement, to reflect the 4.1.2a version of the software.

# What version of SiteSearch is installed
SSVERSION=4_1_2a

7. Edit the ssadmin file (in the <WebZ_root>/scripts directory) in a text editor. Change the item shown in to reflect the 4.1.2a version of the software:

SSVERSION=4_1_2a

8. Use a text editor to edit the SSVERSION line (as you did for ssadmin in Step 7) in the following files in <WebZ_root>/scripts:

• ber2marc
• ber2txt
• bounce
• mysql
• mysql_rb (if applicable)
  
• ssadminbatch
• zclient

9. Test the <WebZ_root> environment. Start the Web server, SQL server (if necessary), and the WebZ system. Start a new WebZ user session in a Web browser, and perform several searches. Make sure to check all of the WebZ functionality through the interface, such as:

• Interlibrary Loan (ILL)
• record bookmarking, e-mail, and display
• record formats
• browse searching
• advanced searching
• user authorization
• local holdings
• vocabulary-assisted searching (without a thesaurus database)
• combined result sets

Debug any problems that have been introduced with this integration using the Troubleshooting the WebZ System document.

1. Make a copy of your existing 4.1.2 environment in a new directory (<NewWebZ_root>).

• Stop the Web server, the WebZ system, and, if you are providing user authorization through the WebZ interface, the SQL server in your <WebZ_root> environment.
• Copy the <WebZ_root> environment into the <NewWebZ_root> directory.
• Restart the Web server, SQL server, and WebZ system in <WebZ_root>.

You will work in the <NewWebZ_root> directory during this procedure, while still providing patron access to the <WebZ_root> environment until you complete the upgrade.

2. Create a new directory (<TempDir_root>) and install the SiteSearch 4.1.2a WebZ component in this directory.

4. Edit your CLASSPATH environment variable for the 4.1.2a environment. Your CLASSPATH must contain the following information:

    .: <fullpath to JDK>/lib/classes.zip:\
    <NewWebZ_root>/classes/:\
    <NewWebZ_root>/classes/lib/pears.jar:\
    <NewWebZ_root>/classes/lib/SS4_1_2a.jar:\
    <NewWebZ_root>/classes/lib/mail.jar:\
    <NewWebZ_root>/classes/lib/activation.jar

UNIX Administrators: After you edit your CLASSPATH variable, log out of your UNIX session and log back in to activate the new settings.

5. Edit the ssmgr.hostname file (in the <NewWebZ_root>/scripts directory), where hostname is the name of the host system where your existing Open SiteSearch environment is installed. Change the values of the ROOTDIR and SSVERSION variables at the top of the file to reflect the 4.1.2a version of the software, as follows:

# Where SiteSearch is installed
ROOTDIR=<NewWebZ_root>

# What version of SiteSearch is installed
SSVERSION=4_1_2a

6. Edit the ssadmin file (in the <NewWebZ_root>/scripts directory) in a text editor. Change the values of the ROOTDIR, CLASSES, and SSVERSION variables to reflect the 4.1.2a version of the software, as shown below:

ROOTDIR=<NewWebZ_root>

JAVAHOME=<fullpath to JDK> 

CLASSES=<NewWebZ_root> 

SSVERSION=4_1_2a 

7. Use a text editor to edit the ROOTDIR, CLASSES, and SSVERSION variables (as you did for ssadmin in Step 6) in the following files in <NewWebZ_root>/scripts:

• ber2marc
• ber2txt
• bounce (has only ROOTDIR and SSVERSION variables)
• mysql (UNIX only) (has only ROOTDIR and SSVERSION variables)
• ssadminbatch
• zclient

8. Which operating platform are you using?

• UNIX. Are you using the Apache Web server?
  • Yes. Go to step 9.
  • No. Make any modifications necessary to the Netscape Web server to run the SiteSearch 4.1.2a environment in <NewWebZ_root>. Then go to step 11.
• No.
  • Make any any modifications necessary to your Web server to run the WebZ 4.1.2a test environment in <NewWebZ_root>.
• Are you using the WebZ Access component and a corresponding SQL database?
  • Yes. Make sure that the SQL database can run the Access database for the <NewWebZ_root> environment without interfering with the Access database in your production environment. Then go to step 11.
  • No. Go to step 11.

9. Edit <NewWebZ_root>/httpd/apache_1.3.11/conf/httpd.conf:

• Modify the variables with path references in <NewWebZ_root>/httpd/conf/apache_1.3.11/conf/httpd.conf so that they refer to <NewWebZ_root> instead of <WebZ_root>. Appendix B lists these variables.
• Select a different Web server port for testing the <NewWebZ_root> environment than the one used for the 4.1.2 production environment and modify the Port variable in httpd.conf accordingly.

10. Edit the HTTPDROOTDIR line in the apache script in <NewWebZ_root>/scripts so that it refers to the apache_1.3.11 directory in <NewWebZ_root>, like this:

# Where SiteSearch is installed
HTTPDROOTDIR=<NewWebZ_root>/httpd/apache_1.3.11

11. Copy these database conversion scripts from <TempDir_root>/scripts to <NewWebZ_root>/scripts:

• updateSQL.pl
• chg411DumpFiles.pl

12. Edit updateSQL.pl as follows:

• Edit the value of the $sourceDir variables so that they contain <NewWebZ_root> in the path.
• Edit the $perlPath variable so that it refers to the location of the Perl interpreter on your system.

13. Which operating platform are you using?

• UNIX. Is your operating system Solaris?
  • Yes. Copy these files from <TempDir_root>/mysql/lib/mysql to <NewWebZ_root>/mysql/lib/mysql:
    • mysqlclient.so
    • libmysqlclient.so.10
    • libmysqlclient.so.10.0.0
      
      

    Note:

    If you subsequently want to run mysqladmin from the UNIX command line, you must set this environment variable: LD_LIBRARY_PATH=<NewWebZ_root>/mysql/lib/mysql

  • No.
    • Copy the 4.1.2a version of the accessdb sample database file, <TempDir_root>/mysql/accessdb.dump to <NewWebZ_root>/mysql, thus overwriting the 4.1.2 version of this file.
    • Go to step 14.
• Windows NT.
  • Copy the 4.1.2a version of the accessdb sample database file, <TempDir_root>/accesssql/accessdb.sql to <NewWebZ_root>/accesssql, thus overwriting the 4.1.2 version of this file.
  • Go to step 16.

14. Edit the <NewWebZ_root>/mysql/data/my.cnf file as follows:

• Change the value of the socket variable in the [client] and [mysqld] sections of so that it contains the path to the mysql.sock file in <NewWebZ_root>:

  socket = <NewWebZ_root>/msql

• Change the value of the port variable in the [client] and [mysqld] sections. Use a different MySQL port than the one you are using in your 4.1.2 production environment.

15. Edit the <NewWebZ_root>/mysql/bin/mysqlaccess file. Change the path to the mysql executable in the $MYSQL varaible to that it reads: as follows: so that it refers to <NewWebZ_root>, like this:

$MYSQL = '<NewWebZ_root>/mysql/bin/mysql'

16. Edit the <NewWebZ_root>/ini/servers/AccessServer.ini file:

• Change the value of the URL variable in the [JDBC] section of <NewWebZ_root>/ini/AccessServer.ini so that it contains the SQL port number you are using to test the <NewWebZ_root> environment. For MySQL, you changed this port in step 14 and the syntax of the variable is as follows:

  [JDBC]
  SQLDriver=org.gjt.mm.mysql.Driver
  URL=jdbc:mysql://hostname:mysql_port/accessdb

  For Windows NT, you changed this port in step 8.

• Add the lines shown in dark blue bold print to the [ColumnPurpose] section:

  [ColumnPurpose]
  authos.autho=AUTHORIZATION
  authos.pwd=PASSWORD
  authos.sessions=MAX_SESSIONS
  userdb.userdbkey=USERDBKEY
  dbs.dbname=DBNAME
  dbs.dbid=DBID
  resources.resourceid=RSRCID
  resources.resourceautho=AUTHORIZATION
  resources.resourcepwd=PASSWORD
  resources.resourcename=RSRCNAME
  userresource.resourceid=RSRCID
  userresource.dbid=DBID
  userresource.db_autho=AUTHORIZATION
  userresource.db_password=PASSWORD

17. Change the path from <WebZ_root> to <NewWebZ_root> in the configuration (.ini) files listed in Appendix C. Appendix C lists the variables in each .ini file for which you need to modify the path.

18. Verify that these configuration files contain a carriage return or line break after the last line:

• <NewWebZ_root>/ini/dbs/PapersFirst.ini
• <NewWebZ_root>/ini/format/obiv1/PapersFirstFormats.ini
  (this file may also reside in a directory for your customized formatting configuration files)

19. Edit <NewWebZ_root>/ini/servers/OclcISOILL.ini. Change host to hostname, as follows:

#host and port for OCLC prod
hostname = isoill.oclc.org

20. Edit <NewWebZ_root>/ini/servers/MnScuISOILL.ini. Change the value of the hostname variable, as follows:

hostname = mirage.pals.msus.edu

21. Have you modified any of the interlibrary loan (ILL) formatting configuration files listed in Appendix D (located in <NewWebZ_root>/ini/format/obiv1 or the directory that contains your customized versions of these files)?

• Yes. For each file you have modified, edit the file as shown in Appendix D. For the files you did not modify, overwrite the <NewWebZ_root> version of each file with its <TempDir_root> counterpart.

• No. Overwrite the <NewWebZ_root> version of each file with its <TempDir_root> counterpart.

22. Have you modified any of the vendor-specific ILL formatting configuration files listed in Appendix A in your 4.1.2 environment?

• Yes. For each file you have modified:
  • Use the UNIX diff utility (or another utility that can identify the differences between two files) to identify the differences between the 4.1.2a version in <TempDir_root> and the customized 4.1.2 file in <NewWebZ_root>.
  • Edit the customized file in <NewWebZ_root> accordingly.
    
    

  For the files you did not modify, overwrite the <NewWebZ_root> version of each file with its <TempDir_root> counterpart.

• No. Overwrite the <NewWebZ_root> version of each file with its <TempDir_root> counterpart.

23. Edit <NewWebZ_root>/ini/interface/obiv1/BaseStyle.ini. Modify the BookMarkFullText variable in the [anchors] section so that it reads as follows (the changes appear in dark blue bold text):

BookMarkFullText = <a href="&StyleTable.DEFAULTS.NAMESPACE; \
BookMark?&context; &resultset=&resultset; \
&recno=&fullrecno;&numrecs=1 \
&format=T&next=currentstate&entitytarget=main" \
&StyleTable.targets.searchResults;> \
<img src="&StyleTable.images.savedisplayed; \
"border="0" alt="Save Displayed Record"></a>

24. Review the Java classes modified in SiteSearch 4.1.2a, as listed in Appendix A. Have you modified any of these classes in any way in your 4.1.2 environment?

• Yes. For each file you have modified:
• Use the UNIX diff utility (or another utility that can identify the differences between two files) to identify the differences between the 4.1.2a version in <TempDir_root> and the customized 4.1.2 file in <NewWebZ_root>.
• Edit the customized class in <NewWebZ_root> accordingly.
• Recompile the customized class.

For the files you did not modify, overwrite the <NewWebZ_root> version of each file in Appendix A that you did not customize (and its corresponding .class file ) with its <TempDir_root> counterpart.

• No. Overwrite the <NewWebZ_root> version of each file (and its corresponding .class file) in Appendix A with its <TempDir_root> counterpart.

26. Test the <NewWebZ_root> environment. Start the Web server, SQL server (if necessary), and the WebZ system. Start a new WebZ user session in a Web browser, and perform several searches. Make sure to check all of the WebZ functionality through the interface, such as:

• Interlibrary Loan (ILL)
• record bookmarking, e-mail, and display
• record formats
• browse searching
• advanced searching
• user authorization
• local holdings
• vocabulary-assisted searching (without a thesaurus database)
• combined result sets

Debug any problems that have been introduced with this integration using the Troubleshooting the WebZ System document.

27. When you are satisfied that the <NewWebZ_root> environment is functioning properly, make it your new production environment.

WebZ-only sites: Change the Web server port and SQL database port in <NewWebZ_root> to the ports that you use in the production environment. Recall that you modified these ports so that you could upgrade and test the <NewWebZ_root> environment without interfering with your production environment.

• In a UNIX environment with the Apache Web server, change the Web server port for WebZ in <NewWebZ_root>/httpd/apache_1.3.11/conf/httpd.conf.
• In a UNIX environment where you are using MySQL, change the MySQL port in <NewWebZ_root>/mysql/data/my.cnf (port variable in the [client] and [mysqld] sections) and <NewWebZ_root>/ini/AccessServer.ini (URL variable in the [JDBC] section).
• For other Web servers or SQL databases, see the appropriate documentation for port changes or other modifications necessary to make <NewWebZ_root> your new production environment.

28. Are you using Database Builder?

• Yes. Go to the Database Builder upgrade procedure.
• No. You have completed the upgrade procedure.