|
Description
of the Open SiteSearch 4.1.2a Patch Release
Table
of Contents
Introduction
Document Conventions
Software Enhancements
Bug Fixes
Introduction
This document
describes the software enhancements and bug fixes included with the OCLC
SiteSearch suite 4.1.2a patch release.
Read this document
before upgrading an existing version of the Open SiteSearch software to
version 4.1.2a. SiteSearch 4.1.2a includes the functionality of versions
4.0.0, 4.0.0a, 4.0.1,
4.0.2, 4.1.0,
4.1.1, and 4.1.2,
as well as new software features, enhancements, and bug fixes. At this
time, it was not technically feasible to produce a software patch with
only the new and modified files in SiteSearch 4.1.2a.
Important Note:
After you carefully review this document, refer to these documents for
specific instructions about upgrading your current SiteSearch environment
to version 4.1.2a:
Document
Conventions
Throughout this
document:
- <WebZ_root>
refers to the location of your WebZ environment
- 4.0.x
refers to any SiteSearch 4 version prior to 4.1.0; that is, 4.0.0, 4.0.0a,
4.0.1, or 4.0.2.
- 4.1.x
refers to SiteSearch 4.1.0 or 4.1.1.
- OBI, version
1, refers to the WebZ Out-of-the-Box Interface, version 1.
- A
continuation character (\) sometimes appears in examples for readability.
- (new)
after a file or directory name indicates a new
file or directory introduced in version 4.1.2a.
Software Enhancements
Important Note:
The SS4_1_2a.jar contains the software byte code and replaces the .jar
file(s) included in previous versions of the Open SiteSearch suite.
Affected
Component: WebZ
Interlibrary
Loan (ILL)
Description
|
Affected
Files
|
Easier
Maintenance for Vendor-Specific Interlibrary Loan (ILL) Formatting
Configuration Files
The vendor-specific
ILL formatting configuration files now contain an [isoill] display
specification that contains only rule lines (rule* = rule_specification)
unique to a specific vendor, the following #include reference,
#include "format/obiv1/MarcCatalogILLFormat.ini"
and rule
specifications unique to this vendor's ILL formatting requirements.
These rule specifications override those in <WebZ_root>/ini/format/obiv1/MarcCatalogILLRules.ini.
This #include
statement picks up the remaining rule lines from the [isoill]
display specification in <WebZ_root>/ini format/obiv1/MarcCatalogILLFormat.ini.
MarcCatalogILLFormat.ini, in turn, has an #include statement that
references MarcCatalogILLRules.ini, which stores ILL rule specifications
for catalog databases.
Previously,
each vendor-specific file had its own entire [isoill] display specification,
even though they were nearly identical. This enhancement eliminates
duplication in vendor-specific files and makes them easier to update
and maintain.
|
<WebZ_root>/ini/format/obiv1
DRAILLFormat.ini
IIIILLFormat.ini
LIASILLFormat.ini
NotisILLFormat.ini
OpacILLFormat.ini |
Return
to Contents
Access
Component
Description
|
Affected
Files
|
Support
for Database-Specific Multiple Server Authorizations
The Access
component in SiteSearch 4.0.x and higher for WebZ allows
you to:
- store
more than one authorization (user name/password combination) for
a database server (resource)
- specify
which server authorization to use for a given autho/pwd, Internet
Procotol (IP) address range, or Domain Name Server (DNS)
You provide
this information in the authos,
resources, and userresource
tables in accessdb, the Access component
database for WebZ. Each row in the authos table has a userresourcekey
value, which associates the row with a particular user group and
with one or more servers, as defined in the resources table. The
same server can have multiple rows in the resources table, each
with a different authorization.
This solution
assumes that all users associated with a particular server authorization
use this authorization for all databases they can access on this
server.
SiteSearch
4.1.2a provides another level of specificity in multiple server
authorizations. It allows you to define a user or user group's
authorization for a database on a particular server. This user group
may have access to several databases on the same server and use
different authorizations to access them. When a user from a particular
user group accesses a database, the Access component retrieves this
user's authorization for this database from accessdb and ZBase passes
this authorization to the server where this database resides.
You define
these authorization/database combinations in three new columns in
the userresource
table in accessdb dbid, db_autho, and db_password. Because
these columns contain this information, you should leave the autho
and password variables blank in the server's
configuration file.
|
<WebZ_root>/classes/lib/SS4_1_2a.jar
<WebZ_root>/ini/AccessServer.ini
<WebZ_root>/mysql/accessdb.dump
(UNIX)
<WebZ_root>\accesssql\accessdb.sql (Windows NT)
|
Return
to Contents
WebZ
Server Configuration
Description
|
Affected
Files
|
Garbage
Collection for Idle Servers
The HouseKeepingInterval
variable in the [Timers] section of the JaSSI,
Access, or ZBase
server configuration files defines how often these servers perform
the following housekeeping tasks:
- ensuring
that rolling intervals for servers, users, and statistics logs
function correctly
- flushing
the logs if necessary
- cleaning
up inactive threads and sessions
- reporting
current system load statistics to the OpServe.
These housekeeping
tasks do not include sending a system garbage collection call (System.gc())
to the Java Virtual Machine (JVM). Garbage collection disposes of
objects no longer being used by the system and reallocates memory
for other system processes. Garbage collection is resource-intensive
and may affect system performance, particularly if you have numerous
active user sessions active when garbage collection occurs.
In contrast,
the ssadmin housekeeping command
performs all of the tasks in the above list AND sends a system garbage
collection call to the JVM. The JVM determines when to execute the
garbage collection. After issuing the housekeeping command, you
often see a drop in the memory usage of the affected server(s).
SiteSearch
4.1.2a enhances WebZ's housekeeping options. It allows you to
indicate that OpServe should submit a garbage collection call for
a particular server after the server has been idle (has had no active
sessions) for a specified time period. You specify this interval
in a new optional variable for internal server configuration files,
idleGCTimer.
The OpServe
detects when a server has no active sessions and stores this information.
When the OpServe polls servers, it checks the length of time a server
has been idle. The OpServe compares the idleGCTimer value to the
amount of time the server has been idle.
If
the server's idleGCTimer value
|
the
OpServe...
|
is
less than or equal to the length of time the server has been
idle |
issues
a system garbage collection call to the JVM for the server. |
is
greater than the length of time the server has been idle |
does
nothing. |
is
null or is -1 |
does
nothing. |
is
0 |
issues
a system garbage collection call to the JVM for the server. |
Example
1. The OpServe polling period is 300 seconds (5 minutes) and
the server's idleGCTimer is 0. OpServe issues a system garbage collection
for this server if it is idle when OpServe checks the server's state.
Example
2. The OpServe polling period is 300 seconds (5 minutes) and
the server's idleGCTimer is 900 (15 minutes). OpServe issues a system
garbage collection for this server if it is has been idle for at
least 15 minutes when OpServe checks the length of the server's
idle time.
|
<WebZ_root>/ini
AccessServer.ini
JaSSIServer.ini
ZBaseServer.ini
<WebZ_root>/classes/lib/SS4_1_2a.jar
|
Return
to Contents
Bug
Fixes
Return
to Contents
See Also
Upgrading
from Open SiteSearch 4.1.2 to SiteSearch 4.1.2a
Upgrading from Open SiteSearch 4.1.1 to SiteSearch
4.1.2a
Description of the Open SiteSearch 4.1.2 Release
Description of the Open SiteSearch 4.1.1 Release
Description of the Open SiteSearch 4.1.0 Release
Description of the Open SiteSearch 4.0.2 Release
Description of the Open SiteSearch 4.0.1 Release
Description of the Open SiteSearch 4.0.0a
Patch
Open SiteSearch Suite Known Bug List (by Category)
|