|
JaSSI
Server Configuration Files
The JaSSIServer.ini
file contains configuration information for the Java Server Side Interpreter
(JaSSI) component of the Open SiteSearch WebZ
software. JaSSI processes WebZ requests (routed to it from the WebZ
Extension), executes the necessary Java classes to carry out the request,
sends a response to the HTTP server, and maintains persistent state information
for each user.
The JaSSIServer_rb.ini
file contains similar configuration information for the JaSSIRB component
of the Record Builder application
included with Database Builder. JaSSIRB processes Record Builder requests
(routed to it from its WebZ Extension), executes the necessary Java classes
to carry out the request, sends a response to the HTTP server, and maintains
persistent state information for each Record Builder user.
This document
describes the sections and variables in the JaSSIServer.ini and JaSSIServer_rb.ini
files, with a separate table devoted to each section. A JaSSIServer.ini
file example appears after the tables.
Document
Conventions
- <WebZ_root>
is the location of your WebZ environment.
- <Document_root>
is the location of the HTML and image files used by the WebZ system
and the Web server or the HTML and image files used by Record Builder
and the Web server.
- <WebServer_root>
is the location of your Web server
- "Default value"
is the value of a variable when WebZ (or Record Builder) was initially
installed on your system.
- The default
value shown in the Default column applies to both JaSSIServer.ini and
JaSSIServer_rb.ini unless otherwise indicated, even when it refers to
version 4.1.0.
- Unless otherwise
specified, all variables must contain a value; their value cannot be
left empty.
- Version 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.
File Location
The JaSSIServer.ini
and JaSSIServer_rb.ini files are located in the <WebZ_root>/ini
directory of your installation.
Sections
and Variables in JaSSI Server Configuration Files
JaSSIServer.ini and
JaSSIServer_rb.ini each the following sections (shown as [section name]):
[JaSSI]
Section
|
Variable
|
Description
|
Default |
|
port
|
Defines
the port that the JaSSI or JaSSIRB server runs on. The default value
of 0 allows the Java Virtual Machine interpreter to dynamically
determine a port for JaSSI every time a JaSSI server or JaSSIRB
server starts up.
|
0 |
|
nameSpace
|
Specifies
when the standard Web server should use the WebZ Extension to route
instructions down to the JaSSI server. The value of nameSpace is
used as a URL indicator to denote the tasks JaSSI performs and manage.
| Notes: |
(1)
In version 4.0.x, the nameSpace variable MUST equal
/WebZ/.
(2)
Beginning with version 4.1.0, it is possible to specify an
alternate namespace.
|
|
/WebZ/ |
|
DocumentRoot
|
States the
location of the directory that contains the HTML documents and image
files associated with the WebZ interface and the Web server (JaSSIServer.ini)
or the HTML documents and image files associated with the Record
Builder interface and the Web server (JaSSIServer_rb.ini).
Beginning with
version 4.1.0, SiteSearch supports versioning
of the WebZ interface. This allows you to place a customized
interface in its own directory under <Document_root>/htdocs/.
If you wish to do this, specify the interface's location in this
variable.
|
JaSSIServer.ini
- version 4.0.x
<Document_root>/htdocs/
JaSSIServer.ini
- version 4.1.0
<Document_root>/htdocs/obiv1
JaSSIServer_rb.ini
<Document_root>/htdocs/rbv0
| Note: |
OCLC
recommends that <Document_root> be equal to <WebZ_root>. |
|
|
ClassRoot
|
Defines
the location of the directory that contains all of the Java classes
(.java and .class) associated with the WebZ software.
|
<WebZ_root>/classes |
|
IniFileRoot
|
Specifies
the location of the configuration files in the WebZ system. This
location is added to any configuration file referenced in the JaSSIServer.ini
file or JaSSIServer_rb.file that does not have a fully qualified
pathname.
|
<WebZ_root>/ini |
|
TimeoutPage
|
Links to
the HTML page that displays when a user session times out because
the session remains idle for a specified period of time. The UserSessionIdleTimeout
variable in the [Timers] section of this .ini file defines the timeout
value.
|
version 4.0.x:
<WebZ_root>/htdocs/error/
nosessionpage.html
version 4.1.0:
/WebZ/error/nosessionpage.html |
|
FailurePage
|
Links to
the HTML page that contains system information and error responses
for display to the user when a "bad" HTML page has not been specified.
|
version 4.0.x:
<WebZ_root>/htdocs/error/
failurepage.html
version 4.1.0:
/WebZ/error/failurepage.html |
|
TempSessionDir
|
Specifies
a directory for storing temporary subdirectories for active user
sessions. These subdirectories are "work areas" for users to store
information written to disk, such as bookmarked records, while their
sessions remain active. Each individual subdirectory is removed
after a user logs off or a session times out.
|
<WebZ_root>/tmp |
|
CGIRoot
|
Defines
the location of the directory for storing Web server Common Gateway
Interface (CGI) scripts for system use. The WebZ CGI scripts, such
as the tif to gif image display scripts, are also stored in a subdirectory,
sscgi, of this directory.
|
<WebServer_root>/cgi-bin/sscgi |
|
AdminEmail
JaSSIServer_rb.ini
only
|
Administrative
e-mail to send diagnostic messages resulting from errors with Record
Builder Newton database updates. |
sample@university.edu |
Return
to Sections list
[Timers]
Section
|
Variable
|
Description
|
Default |
|
HouseKeepingInterval
|
Defines
how often, in seconds, JaSSI or JaSSIRB performs housekeeping tasks.
JaSSI and JaSSIRB ensure that the rolling intervals for servers,
users, and statistics logs function correctly and flushes the logs
if necessary. The server also reports its current system load statistics
to the OpServe.
This variable
does not set how often garbage collection occurs; the Java Virtual
Machine (JVM) performs garbage collection dynamically.
|
300
(5 min.)
|
|
ThreadTimeout
|
Specifies
how long, in seconds, an active Java thread is allowed to run in
system memory before the thread is terminated. This variable value
increases performance by maintaining control over runaway threads.
|
300
(5 min.) |
|
UserSessionIdleTimeout
|
Specifies
how long, in seconds, a user session can remain idle before JaSSI
or JaSSIRB automatically logs the user off the server.
|
900
(15 min.) |
|
idleGCTimer
JaSSIServer_ini.only
(beginning
with version 4.1.2a)
|
(Optional)
Specifies how long, in seconds, remains idle before the OpServe
submits a system garbage collection call (system.gc()) for it. 900
seconds (15 minutes) is a recommended value for this variable.
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 JaSSI'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 JaSSI'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.
|
NULL |
Return
to Sections list
[Performance]
Section
| Note: |
The Java
Virtual Machine automatically grows the size of the two hash tables
described below, if necessary.
|
|
Variable
|
Description
|
Default |
|
UserHashSize
|
Configures
the size of the user hash table that JaSSI or JaSSIRB allocates
at startup. The recommended value for this variable is 2 times the
number of simultaneous users allowed for your license. The default
value of 300 allows JaSSI or JaSSIRB to store session information
for up to 150 users.
|
300 |
|
EntityTableSize
|
Configures
the size of the individual user session hash tables that JaSSI or
JaSSIRB allocates at startup. The value for this variable reflects
the number of items in the userstate.
|
100 |
Return
to Sections list
[ServerTrace]
Section
|
Variable
|
Description
|
Default |
|
traceLevel
|
Specifies
the level of detail in the trace
messages written to the JaSSI or JaSSIRB server log file.
You can
also set JaSSI or JaSSIRB logging manually with the settrace
command in the ssadmin interface.
|
TRACE_NONE |
|
traceDirectory
|
Provides
the location of the directory JaSSI or JaSSIRB uses to store its
server logs.
|
<WebZ_root>/logs |
|
traceFilename
|
Provides
the base name that JaSSI or JaSSIRB uses to write out server log
files. JaSSI or JaSSIRB adds the host, port, time, and date stamps
to this base name before saving the server log.
|
JaSSIServer.ini:
jassi.serverLog
JaSSIServer_rb.ini:
jassi_rb.serverLog |
|
rollInterval
|
Defines
how frequently, in seconds, JaSSI or JaSSIRB saves and closes the
current log and creates a new log file in its place.
You can
also perform this task manually with the flushlog
command in the ssadmin interface.
|
0 |
Return
to Sections list
[SessionTrace]
Section
|
Variable
|
Description
|
Default
|
|
traceLevel
|
Specifies
the level of detail in the trace
messages written to the JaSSI or JaSSIRB user log file.
You can
set JaSSI or JaSSIRB logging manually set with the settrace
command in the ssadmin interface.
|
TRACE_NONE |
|
traceDirectory
|
Provides
the location of the directory where JaSSI or JaSSIRB stores user
log files.
|
<WebZ_root>/logs |
|
traceFilename
|
Provides
the base name that JaSSI or JaSSIRB uses to write out user log files.
JaSSI or JaSSIRB adds the sessionid, time, and date stamps to this
base name before saving the user log.
|
JaSSIServer.ini:
jassi.userLog
JaSSIServer_rb.ini:
jassi_rb.userLog |
Return
to Sections list
[Stats]
Section
|
Variable
|
Description
|
Default |
|
statsDirectory
|
Provides
the location of the directory JaSSI or JaSSIRB uses to write statistics
files.
|
<WebZ_root>/stats |
|
statsFilename
|
Provides
the base name that JaSSI or JaSSIRB uses to write out statistics.
JaSSI or JaSSIRB also adds host, port, time, and date stamps on
the end of this base name for the statistics log files.
|
JaSSIServer.ini:
jassi.stats
JaSSIServer_rb.ini:
jassi_rb.stats |
|
statsClass
|
Specifies
the Java class used to write out the user statistics.
|
ORG.oclc.stats.JaSSIUserStats |
|
rollInterval
|
Defines
how frequently, in seconds, JaSSI or JaSSIRB saves and closes the
current statistics file and creates a new file in its place.
You can
also perform this task manually with the flushstats
command in ssadmin.
|
21600
(6 hours) |
Return
to Sections list
[PackageOrder]
Section
|
Variable
|
Description
|
Default |
|
packagen
OR, beginning
with version 4.0.2:
package*
|
Defines
the order in which JaSSI or JaSSIRB searches the WebZ Java packages,
or sets of classes, to find the class it needs to execute.
Specify
the package that JaSSI or JaSSIRB uses most frequently in the first
package. Specify the package that JaSSI or JaSSIRB uses second most
commonly in the second package, and so on.
This "order
of precedence" is important because when a class is called JaSSI
or JaSSIRB starts with the first package defined in this list and
looks through all of the packages in order until it finds the necessary
class. By including the most frequently used packages first, JaSSI
or JaSSIRB can locate classes much faster, thus increasing response
time.
| Note: |
Beginning
with version 4.0.2, you can use either numerals or asterisks
to list the packages, but do not mix the two; use either all
numerals or all asterisks. For versions prior to 4.0.2, use
numerals only.
|
|
JaSSIServer.ini:
package1 =
ORG.oclc.obi
package2
= ORG.oclc.obi.extverb
package3
= ORG.oclc.webz
package4
= ORG.oclc.jassi
JaSSIServer_rb.ini:
package*
= ORG.oclc.obi
package*
= ORG.oclc.obi.extverb
package*
= ORG.oclc.webz
package*
= ORG.oclc.jassi
package* = ORG.oclc.mantis.verbs
package* = ORG.oclc.mantis.obi
package* = ORG.oclc.mantis |
Return
to Sections list
[InitClasses]
Section
Return
to Sections list
[ServerMngr]
Section
|
Variable
|
Description
|
Default |
|
servern
OR, beginning
with version 4.0.2:
server*
|
Lists the
names of all of the WebZ servers that JaSSI or JaSSIRB communicates
with to perform its functions.
| Notes: |
(1)
Important: Each server name in this section MUST have
an individual section in this file that contains information
that JaSSI requires to communicate with the server. See the
[server] section.
|
|
| (2)
Beginning with version 4.0.2, you can use either numerals or
asterisks to list the servers, but do not mix the two; use either
all numerals or all asterisks. For versions prior to 4.0.2,
use all numerals. |
| (3)
Beginning with version 4.1.2, the last three entries represent
the generic interlibrary loan (ILL) servers (OCLC ILL Direct
Request, e-mail ILL, and MIME e-mail ILL, respectively) shipped
with SiteSearch. Comment out or remove the ILL servers you are
not using. If you are using another ILL server supported by
SiteSearch 4.1.2, the server's name must also match the bracketed
name at the top of its ILL server configuration file. |
|
|
JaSSIServer.ini
- beginning with version 4.1.2:
server1 = ZBase
server2 =
AccessServer
server3 = OclcISOILL
server4 = EmailILL
server5 = MimeEmailILL
JaSSIServer.ini
- versions 4.0.x, 4.1.0, 4.1.1
server1 = ZBase
server2 =
AccessServer
server3 = ILLServer
JaSSIServer_rb.ini:
server1 = ZBaseRB
server2 =
AccessServer
|
Return
to Sections list
[server]
Section
Include an individual
server section with the information described in the table below for each
of the servers defined in the [ServerMngr] section.
By default, five [server] sections are included in JaSSIServer.ini
beginning with SiteSearch 4.1.2: [ZBase], [AccessServer], [OclcISOILL],
[EmailILL], and [MimeEmailILL]; three sections are included in JaSSIServer.ini
for SiteSearch versions 4.1.1 and earlier: [ZBase], [AccessServer], and
[ILLServer]; and two sections are included in JaSSIServer_rb.ini: [ZBaseRB]
and [AccessServer].
|
Variable
|
Description
|
|
inifile
|
Defines
the name of the server's configuration file in the WebZ (or Record
Builder) environment. For example, in JaSSIServer.ini, servers/ZBase.ini
is the location of the ZBase server configuration file and resides
in the directory specified by the IniFileRoot
variable in the [JaSSI] section above.
|
|
InitClass
|
Defines
the full name of the server's initialization class. For example,
ORG.oclc.webz.Zserver is the initialization class for the Z39.50
servers.
|
|
sectionName
|
Specifies
a single section in the server configuration file defined in the
inifile variable above that JaSSI needs to access. See the following
example from JaSSIServer.ini:
[AccessServer]
inifile = servers/Access.ini
InitClass = ORG.oclc.access.AccessConnectInfo
sectionName = JaSSI
|
In the Access.ini
configuration file for the Access server for WebZ, JaSSI only needs
to retrieve information from the JaSSI section included in the file.
Thus, JaSSI is the value of sectionName in the example above. This
also applies to the Access_rb.ini configuration file for the Access
server for Record Builder.
| Important
Note: |
The
sectionName variable is only required in the [AccessServer]
section and is not included in other WebZ or Record Builder
server sections.
|
|
Return
to Sections list
[Topics]
Section
|
Variable
|
Description
|
Default |
|
inifile
|
Specifies
the location of the configuration file that defines which databases
comprise the various WebZ Out-of-the-Box Interface (OBI) topic areas.
The relative root, or location, for the system-level .ini directory
is defined in the IniFileRoot variable
in the [JaSSI] section of the configuration file.
|
JaSSIServer.ini
- version 4.0.x
interface/ObiTopics.ini
JaSSIServer.ini
- version 4.1.0
interface/obiv1/ObiTopics.ini
JaSSIServer_rb.ini
interface/rbv0/ObiTopics.ini |
Return
to Sections list
[Locations]
Section
|
Variable
|
Description
|
Default |
|
inifile
|
Specifies
the name and location of the configuration file that contains a
list of individual configuration files
for Interlibrary Loan (ILL) lenders. These configuration files
relate strings in a catalog database's Locations field (such as
MAIN STACKS) to their OCLC institution symbols. This allows WebZ
to specify an item's location by the appropriate OCLC institution
symbol in ILL requests. The relative root, or location, for the
system-level ini directory is defined in the IniFileRoot
variable in the [JaSSI] section of the configuration file.
|
locations.ini |
Return
to Sections list
[InterfaceStyles]
Section
This section lists
all of the possible types of interface styles that will be used by the
JaSSI to create a WebZ interface for the user. The default values include
all the styles included in the WebZ OBI. If you plan to use the Access
component, leave these style references until after you test
your Access component configuration. On the other hand, loading unused
styles increases memory usage unnecessarily, so comment out any styles
you are not currently using.
|
Variable
|
Description
|
Default |
|
stylename
|
Defines
the location of the interface style configuration file based on
the directory specified by the IniFileRoot
variable in the [JaSSI] section above.
| Notes: |
(1) In
version 4.0.x, do NOT remove the doct style included
above if you want to search the online Open SiteSearch Suite
documentation provided with your installation. |
|
(2)
Do not modify the [InterfaceStyles] section of JaSSIServer_rb.ini.
|
|
JaSSIServer.ini
- version 4.0.x
default
= interface/defaultStyle.ini
red
= interface/redStyle.ini
rss
= interface/rssStyle.ini
doct = interface/doctStyle.ini
JaSSIServer.ini
- version 4.1.0
default
= interface/obiv1/frameGreenStyle.ini
noframe
= interface/obiv1/noframeBlueStyle.ini
rss
= interface/obiv1/frameRssStyle.ini
JaSSIServer_rb.ini
default
= interface/rbv0/noframeBlueStyle.ini
rb
= interface/rbv0/RBStyle.ini
|
Return
to Sections list
[InterfaceDisplayGadgets]
Section
This section lists
the interface display gadgets files associated with every interface style
used by the JaSSI to create a WebZ interface for the user.The default
values include all the styles included in the WebZ OBI. If you plan to
use the Access component, leave these
references intact until after you test your
Access component configuration. On the other hand, loading unused
styles increases memory usage unnecessarily, so comment out any styles
you are not currently using.
|
Variable
|
Description
|
Default |
|
stylename
|
Specifies
the location of the configuration file used to create interface
elements called gadgets. stylename is equal to an interface
style defined in the [InterfaceStyles]
section of the configuration file.
The configuration
files defined in this section use the root directory specified by
the IniFileRoot variable in the [JaSSI]
section as a base location.
| Notes: |
(1) In
version 4.0.x, do NOT remove the doct style included
above if you want to search the online Open SiteSearch Suite
documentation provided with your installation. |
|
(2)
Do not modify the [InterfaceDisplayGadgets] section of JaSSIServer_rb.ini.
|
|
JaSSIServer.ini
- version 4.0.x
default
= interface/DisplayGadgets.ini
red
= interface/DisplayGadgets.ini
rss
= interface/rssStyle.ini
doct
= interface/DisplayGadgets.ini
JaSSIServer.ini
- version 4.1.0
default
= interface/obiv1/frameDisplayGadgets.ini
noframe = interface/obiv1/noframeDisplayGadgets.ini
rss = interface/obiv1/noframeDisplayGadgets.ini
JaSSIServer_rb.ini
default
= interface/rbv0/noframeDisplayGadgets.ini
rb
= interface/rbv0/noframeDisplayGadgets.ini
|
Return
to Sections list
[MimeTypes]
Section
|
Variable
|
Description
|
Default |
|
inifile
|
Defines
the location of the JaSSI MIME types configuration file. JaSSI and
JaSSIRB use this configuration file to identify the unique identifiers
used for different file types when conveyed across a MIME-based
protocol, such as MIME e-mail or HTTP.
The configuration
file defined by this variable uses the root directory specified
by the IniFileRoot variable in the [JaSSI]
section as a base location.
|
JaSSIMimeTypes.ini |
Return
to Sections list
[Operations]
Section
|
Variable
|
Description
|
Default
|
|
OpsConfigDir
|
Specifies
the location of the Operations directory where JaSSI or JaSSIRB
reads server load balancing values. The other WebZ servers have
access to JaSSI's or JaSSIRB's load balancing values in this directory.
|
<WebZ_root>/ops |
|
ServerType
|
Identifies
the type of server defined in this configuration file. The OpServe
and its administrative client, ssadmin,
use this information to execute administrative tasks for the JaSSI
or JaSSIRB server.
| Note: |
Do
not change the default value for ServerType.
|
|
JaSSIServer.ini:
JaSSI
JaSSIServer_rb.ini:
JaSSIRB
|
|
HostMapIni
|
Defines
the location of the host environment configuration file used by
the WebZ software and the Web server's
WebZ Extension. This file contains information such as the ID, name,
and load distribution percentage of the servers hosting the WebZ
system.
The configuration
file defined by this variable uses the root directory specified
by the IniFileRoot variable in the [JaSSI]
section as a base location.
|
HostMap.ini |
Return
to Sections list
[servername]
Section
This section contains
threshold information used to determine the load factor of a JaSSI or
JaSSIRB server. A JaSSI or JaSSIRB server has a load factor of 1, 2, 3,
or 4, based on its various threshold levels. Threshold levels are tracked
for used system memory, active user sessions, active Java threads, and
open file descriptors. JaSSI or JaSSIRB uses the variables and values
in the table below to set threshold levels. When a server starts, each
threshold level has its own corresponding load factor, separate from the
server load factor, of 1. If a threshold level reaches the low load value
defined in this section, the load factor adjusts to 2. If a threshold
level reaches the medium load value defined in this section, the load
factor adjusts to 3, and so on.
The server determines
its own overall load factor level after it processes a request. The load
factor for the server always equals the highest threshold level load factor.
For example, if all of the threshold variables have a load factor of 1
except for the user sessions, which has a load factor of 2, the system
estimates that the server has an overall load of 2.
As threshold levels
change, the load factor for the JaSSI or JaSSIRB server adjusts to the
corresponding value. OpServe manages the system load balance by starting
and stopping JaSSI servers (or JaSSIRB servers, as applicable).
In a SiteSearch
environment without Record Builder, OpServe starts a new JaSSI when an
existing server reaches the start threshold load factor level defined
in the [JaSSI] server section of
the OpServe.ini file, unless the system is running the maximum number
of JaSSI servers allowed (also defined in OpServe.ini). OpServe stops
an existing JaSSI server when the server reaches the stop threshold load
factor level defined in the JaSSI server section of the OpServe.ini file,
unless the system is running the minimum number of JaSSI servers allowed
(also defined in the OpServe.ini). The OpServe starts and stops servers
in the same manner in an environment that includes WebZ and Record Builder,
except that it reads threshold load factors for both JaSSI and JaSSIRB
from the OpServe_rb.ini file.
You can temporarily
adjust the maximum and minimum number of JaSSI servers or JaSSIRB servers
allowed by executing the setmax
and setmin commands in the ssadmin
interface. To permanently change the maximum and minimum values, edit
the [JaSSI] section of the OpServe.ini file (or the [JaSSI] and [JaSSIRB]
sections of the OpServe_rb.ini file) during a low usage period and restart
the WebZ system.
The JaSSIServer.ini
file should contain a [servername] section for every host system
that the WebZ software runs on. The JaSSIServer_rb.ini file should contain
a [servername] section for every host system that the WebZ and
Record Builder software runs on.
|
Variable
|
Description
|
Default |
|
LowUsedMemory
MedUsedMemory
HighUsedMemory
|
Sets threshold
levels based on the amount of host server memory used.
|
JaSSIServer.ini
- version 4.0.x
LowUsedMemory
= 6000
MedUsedMemory
= 10000
HighUsedMemory
= 14000
JaSSIServer.ini
- version 4.1.0:
LowUsedMemory = 15000
MedUsedMemory
= 20000
HighUsedMemory
= 25000
JaSSIServer_rb.ini
(UNIX)
LowUsedMemory = 20000
MedUsedMemory
= 30000
HighUsedMemory
= 40000
JaSSIServer_rb.ini
(Windows NT)
LowUsedMemory = 45000
MedUsedMemory
= 50000
HighUsedMemory
= 55000
|
|
LowSessions
MedSessions
HighSessions
|
Sets the
threshold levels based on the number of sessions running on the
JaSSI or JaSSIRB server.
|
LowSessions
= 10
MedSessions
= 15
HighSessions
= 25
|
|
LowThreads
MedThreads
HighThreads
|
Sets the
threshold levels based on the number of active Java threads running
on the JaSSI or JaSSIRB server.
|
LowThreads
= 100
MedThreads
= 500
HighThreads
= 1000
|
|
LowFiles
MedFiles
HighFiles
|
Sets the
threshold levels based on the number of active files running on
the JaSSI or JaSSIRB server.
|
LowFiles
= 100
MedFiles
= 500
HighFiles
= 1000
|
JaSSIServer.ini
Example
| Note: |
This example
is the JaSSIServer.ini file delivered with SiteSearch 4.1.0. |
# JaSSIServer.ini
[JaSSI]
port = 0
nameSpace = /WebZ/
DocumentRoot = <WebZ_root>/htdocs/obiv1
ClassRoot = <WebZ_root>/classes
IniFileRoot = <WebZ_root>/ini
TimeoutPage = /WebZ/error/nosessionpage.html
FailurePage = /WebZ/error/failurepage.html
TempSessionDir = <WebZ_root>/tmp
CGIRoot = <WebZ_root>/cgi-bin/sscgi
#AdminEmail = sample@university.edu
# Given in seconds
[Timers]
HouseKeepingInterval = 300
ThreadTimeout = 300
UserSessionIdleTimeout = 900
[Performance]
UserHashSize = 300
EntityTableSize = 100
[ServerTrace]
traceLevel = TRACE_NONE
traceDirectory = <WebZ_root>/logs
traceFilename = jassi.serverLog
rollInterval = 0
[SessionTrace]
traceLevel = TRACE_NONE
traceDirectory = <WebZ_root>/logs
traceFilename = jassi.userLog
[Stats]
statsDirectory = <WebZ_root>/stats
statsFilename = jassi.stats
statsClass = ORG.oclc.stats.JaSSIUserStats
rollInterval = 21600
[PackageOrder]
package1 = ORG.oclc.obi
package2 = ORG.oclc.obi.extverb
package3 = ORG.oclc.webz
package4 = ORG.oclc.jassi
[InitClasses]
class1 = ORG.oclc.jassi.ServerMngr
class2 = ORG.oclc.gadgets.GadgetAndStyleLoader
class3 = ORG.oclc.obi.util.TopicLoader
class4 = ORG.oclc.isoill.LocationsLoader
[ServerMngr]
server1 = ZBase
server2 = AccessServer
server3 = ILLServer
[ZBase]
inifile = servers/ZBase.ini
InitClass = ORG.oclc.webz.ZServer
[AccessServer]
inifile = servers/Access.ini
InitClass = ORG.oclc.access.AccessConnectInfo
sectionName = JaSSI
[ILLServer]
inifile = servers/ILLService.ini
InitClass = ORG.oclc.webz.ILLServer
[Topics]
inifile = interface/obiv1/ObiTopics.ini
[Locations]
inifile = locations.ini
[InterfaceStyles]
default = interface/obiv1/frameGreenStyle.ini
noframe = interface/obiv1/noframeBlueStyle.ini
rss = interface/obiv1/frameRssStyle.ini
[InterfaceDisplayGadgets]
default = interface/obiv1/frameDisplayGadgets.ini
noframe = interface/obiv1/noframeDisplayGadgets.ini
rss = interface/obiv1/noframeDisplayGadgets.ini
[MimeTypes]
inifile = JaSSIMimeTypes.ini
[Operations]
OpsConfigDir = <WebZ_root>/ops
ServerType = JaSSI
HostMapIni = HostMap.ini
[servername]
LowUsedMemory = 15000
MedUsedMemory = 20000
HighUsedMemory = 25000
LowSessions = 10
MedSessions = 15
HighSessions = 25
LowThreads = 100
MedThreads = 500
HighThreads = 1000
LowFiles = 100
MedFiles = 500
HighFiles = 1000
[HOST2]
LowUsedMemory = 15000
MedUsedMemory = 20000
HighUsedMemory = 25000
LowSessions = 10
MedSessions = 15
HighSessions = 25
LowThreads = 100
MedThreads = 500
HighThreads = 1000
LowFiles = 100
MedFiles = 500
HighFiles = 1000
See Also
OpServe
Configuration Files
WebZ Configuration Files
WebZ System Administration
Description of the WebZ System
About Interface Style Configuration Files
Record Builder Process Model and System
Overview
Record Builder Configuration Files
|