Appendix B Repository Properties Reference
Server
property names begin with com.sybase.jaguar.server
.
A server represents an application server process.
Chapter 3, "Creating and Configuring Servers"
Specifies the JDMK/SNMP agent to manage this server.
The name of an agent defined in the repository. There is no default.
Specifies whether API checking is enabled for Open Server Server-Library calls.
true
or false
.
The default is true
.
This property affects only code that calls Open Server Server-Library routines. See the EAServer Programmer's Guide for information on running Open Server applications in EAServer.
Specifies the applications that are installed in this server.
A comma-separated list of application names.
com.sybase.jaguar.server.packages, com.sybase.jaguar.server.webapplications,
Application properties
Specifies whether operating-system-based user name/password authentication is in effect.
true
or false
.
The default is false
.
com.sybase.jaguar.server.authservice,
com.sybase.jaguar.server.jaas.config,
com.sybase.jaguar.server.jagadminpassword
Specifies how long the jagadmin user account is locked after five failed login attempts.
An integer specifying the lockout period, in seconds. The default is 600 (10 minutes).
The length of time, in seconds, that the server can cache authorization data for a user's access to a resource.
An integer specifying the number of seconds; the default is 7200, which is 2 hours.
Specifies the name of a custom authorization service component.
A URL to identify the custom authorization service component. There are two accepted forms of the URL:
pseudo://java/JavaClass/package/component
pseudo://cpp/SharedLibraryName/package/component
The EAServer Security Administration and Configuration Guide explains how to create a custom authorization service.
com.sybase.jaguar.server.authentication,
com.sybase.jaguar.server.authservice,
com.sybase.jaguar.server.jaas.config,
com.sybase.jaguar.server.roleservice
Specifies the name of a custom authentication service component.
The authentication service component name, in the form:
package/component
The package must be installed on the server, and the component must implement the interface CtsSecurity::AuthService.
The EAServer Security Administration and Configuration Guide explains how to create a custom authentication service.
com.sybase.jaguar.server.authentication,
com.sybase.jaguar.server.authorization.service,
com.sybase.jaguar.server.jaas.config,
com.sybase.jaguar.server.roleservice
Specifies how long authentication results can be cached.
The cache timeout period in seconds. The default is 3600 (1 hour).
com.sybase.jaguar.server.authentication, com.sybase.jaguar.server.authservice
Specifies when the name service binds component names.
Value | To indicate |
---|---|
run
(the
default)
|
Components are bound in the name service run method. |
start
|
Components are bound in the name service start method. Use this value if you have service components that make intercomponent calls in their start method. |
Specifies other servers that use this server for naming services.
This property is set automatically as servers bind to the name service, and should not be set manually.
com.sybase.jaguar.server.CosNaming.nameserver,
Chapter 5, "Naming Services"
Enables custom class loader tracing.
true
or false
.
The default is false
, which
disables class loader tracing.
This property is useful for determining which custom loader (server, application, package, Web application, or component) is loading a particular class for a particular component or Web application.
In Jaguar Manager, set this property using the All Properties tab in the Server Properties dialog box.
com.sybase.jaguar.server.java.classes,
com.sybase.jaguar.server.jvm.verbose,
com.sybase.jaguar.server.jvm.verboseGC,
com.sybase.jaguar.component.java.classes,
com.sybase.jaguar.application.java.classes,
com.sybase.jaguar.package.java.classes,
com.sybase.jaguar.webapplication.java.classes
Specifies the default for the com.sybase.jaguar.package.code.set package property.
Same as com.sybase.jaguar.component.code.set. The default is iso_1
.
In Jaguar Manager, set this property using the Codeset field on the General tab in the Server Properties dialog box.
com.sybase.jaguar.component.code.set,
com.sybase.jaguar.package.code.set
Specifies the password to bind to the naming service.
The password text.
"Name binding password security".
Enables heart beat detection for the name service.
true
or false
.
The default is false
.
com.sybase.jaguar.server.CosNaming.heartbeatfrequency,
"Heartbeat detection"
When com.sybase.jaguar.server.CosNaming.heartbeat is true
,
specifies the heartbeat frequency.
An integer that specifies the number of seconds between heartbeat tests. The default is 120.
com.sybase.jaguar.server.CosNaming.heartbeat,
"Heartbeat detection"
Specifies the initial naming context.
The initial naming context. The default is a zero-length string.
When com.sybase.jaguar.server.CosNaming.strategy is persistent
, specifies
the URL to connect to the LDAP server.
The URL text.
com.sybase.jaguar.server.CosNaming.strategy,
"Using an LDAP server with EAServer"
When com.sybase.jaguar.server.CosNaming.strategy is persistent
, specifies
the user name to connect to the LDAP server.
The user name.
com.sybase.jaguar.server.CosNaming.strategy,
com.sybase.jaguar.server.CosNaming.mgrpwd,
"Using an LDAP server with EAServer"
When com.sybase.jaguar.server.CosNaming.strategy is persistent
, specifies
the password to connect to the LDAP server.
The password text.
com.sybase.jaguar.server.CosNaming.strategy,
com.sybase.jaguar.server.CosNaming.mgrdn,
"Using an LDAP server with EAServer"
Specifies whether this server acts as its own name server, or connects to another EAServer engine for naming services.
true
or false
.
The default is true
.
com.sybase.jaguar.server.nameservice,
Chapter 5, "Naming Services"
When com.sybase.jaguar.server.CosNaming.nameserver is true
, specifies
whether to store naming services internally in server memory, or externally
in a name server.
Value | To indicate |
---|---|
transient
(the default)
|
Name bindings are stored internally in server memory. |
persistent
|
Name bindings are stored externally in an LDAP name server. |
"Transient versus persistent storage".
Specifies an optional text description of the server.
The descriptive text.
Specifies whether or not the Open Server ATTENTION event handler is called when a client disconnects.
true
or false
.
The default is false
.
com.sybase.jaguar.server.handler.attnevent,
com.sybase.jaguar.server.handler.disconnevent
Specifies the class name for a custom DOM XML parser factory class.
The class name. If the class is in a JAR file, the JAR file name must be listed in the com.sybase.jaguar.server.java.classes property.
com.sybase.jaguar.server.jagmgr.DOMFactoryChoice, com.sybase.jaguar.server.SAXfactory, com.sybase.jaguar.server.XSLTfactory
Enables and disables PowerDynamo Web site execution.
true
or false
.
The default is false
.
Specifies the name of the PowerDynamo NSAPI plug-in.
The library or DLL name.
Enables and disables tracing of PowerDynamo plug-in calls.
true
or false
.
The default is false
.
Specifies the default required role for EJB component methods that do not have a method-level role setting.
Value | To indicate |
---|---|
nobody
(the
default)
|
No user can execute the method. |
everybody
|
All users can execute the method. |
The default value for this property provides compliance with the EJB 2.0 specification.
Behavior in EAServer 4.0 versus 4.1 and later The effect of the com.sybase.jaguar.server.ejb.role.default property on EJB 2.0 components in EAServer 4.0 differs from EAServer version 4.1 and later:
com.sybase.jaguar.method.security-roles
Specifies a string of name/value pairs used to define server-level HTTP custom headers.
A string of the form:
entry1, entry2, ...
Where entry1, entry2, and so forth are of the form:
(description=,value=type:String&val:value,name=name)
Where value is the property value and name is the property name.
Specifies an Open Server ATTENTION event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server BULK event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server CONNECT event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server CURSOR event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server DISCONNECT event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server DYNAMIC event.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server ERROR event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server INITIALIZATION event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server LANGUAGE event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server MESSAGE event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server OPTIONS event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server RPC event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server START event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies an Open Server STOP event handler.
library:function
Where library is the DLL or shared library name, and function is the function name.
Appendix B, "Migrating Open Server Applications to EAServer," in the EAServer Programmer's Guide
Specifies whether this server is in a hot standby pair.
true
or false
.
The default is false
.
"Hot standby",
com.sybase.jaguar.server.hotstandby.backup,
com.sybase.jaguar.server.hotstandby.master
When com.sybase.jaguar.server.hotstandby is true
,
specifies the backup server URL in the hot standby pair.
The IIOP or IIOPS URL of the backup server.
"Hot standby",
com.sybase.jaguar.server.hotstandby,
com.sybase.jaguar.server.hotstandby.master
When com.sybase.jaguar.server.hotstandby is true
,
specifies the master server URL in the hot standby pair.
The IIOP or IIOPS URL of the master server.
"Hot standby",
com.sybase.jaguar.server.hotstandby,
com.sybase.jaguar.server.hotstandby.backup
Enables and disables HTTP accept-language header parsing.
true
or false
.
The default is false
.
Specifies whether to write static page cache debug information to the server's log file.
true
or false
.
The default is false
.
Specifies whether to enable static page caching.
true
or false
.
The default is true
.
When static page caching is enabled, specifies the files to exclude from caching.
A comma-delimited string that indicates the files to exclude from the cache. Enter the string in this form, relative to the document root directory:
(<dir>, [<file type>], [<file type>], ...), (<dir>, <file type>, ...), ...
By default, the document root directory is $JAGUAR/html. To exclude all the files in the $JAGUAR/html/images directory, enter:
(images, *.*)
"Static
Page Caching",
com.sybase.jaguar.server.http.docroot,
com.sybase.jaguar.server.http.cache.webapps.exclude-files
Specifies the size of the static page cache.
An integer followed by "B", "K", or "M", indicating bytes, kilobytes, and megabytes, respectively. The default is 10M.
You can specify the size using either uppercase or lowercase
letters; for example, to set the cache size to 20 megabytes, you
can enter 20M
or 20m
.
"Static
Page Caching",
com.sybase.jaguar.server.http.cache.timeout
Specifies the timeout period for entries in the static page cache. When an entry in the cache times out, it becomes invalid. The page is removed from the cache the next time it is requested or when space is needed for a new cache entry.
The timeout period in seconds. The default is 600 (10 minutes).
When static page caching is enabled, specifies the Web application files to exclude from caching.
A comma-delimited string that specifies the Web application files to exclude from the cache. Enter the string in this form; items in brackets are optional:
(<WebAppName >[/<dir>], [<file type>], [<file type>], ...), (<WebAppName>[/<dir>], [<file type>], ...), ...
For example, to exclude all the GIF and JPG files in the images directory and all the files in the archives directory for the Web application "Vacation", enter:
(Vacation/images, *.gif, *.jpg), (Vacation/archives, *.*)
"Static
Page Caching",
com.sybase.jaguar.server.http.cache.enable,
com.sybase.jaguar.server.http.cache.exclude-files
Specifies the default file to look for when an HTTP request URI ends in a directory.
A file name, with no path separators. The default is index.html.
Specifies the HTTP document root directory.
The path to the directory. You can use %JAGUAR% or $JAGUAR to substitute for the EAServer installation directory. The default is the EAServer html subdirectory.
Specifies the domain name of the HTTP server.
The domain name; for example, sybase.com
.
There is no default.
Specifies whether the extended log file format is used to write information to the request log.
true
or false
.
The default is false
.
com.sybase.jaguar.server.http.elffitems
Specifies the items and the order in which to write them to
the request log. This property is used only when you set com.sybase.jaguar.server.http.elffenable to true
.
A comma-separated list of items. Table 15-7 lists the felds that can be included in the list and the headers that identify each field in the log:
Field name | Log header |
---|---|
hostaddr | s-ip |
date | date |
time | time |
reqline | cs-request |
status | cs-status |
length | cs-bytes |
referer | cs(Referer) |
cookie | cs(Cookie) |
user-agent | cs(User-Agent) |
method | cs-method |
uri-stem | cs-uri-stem |
http_version | c-httpversion |
host | s-host |
post | s-port |
By default, these fields are listed in the request log when
you set the com.sybase.jaguar.server.http.elffenable property
to true
:
hostaddr, date, time, reqline, status, length, cookie, refererWhich generates something like this in the log file:
#Version: 1.0 #Date: 2001-12-31 04:10:00 #Fields: s-ip date time cs-request cs-status cs-bytes cs(Cookie) cs(Referer) 120.0.0.1 2001-12-31 04:10:01 "GET /index.html HTTP/1.0" 304 0 - "http://localhost:8080/index.html" 120.0.0.1 2001-12-31 04:10:02 "GET /images/tiny.jpg HTTP/1.0" 304 0 - "http://localhost:8080/index.html"
com.sybase.jaguar.server.http.elffenable
Specifies the HTTP error log file name.
The path and file name. The path can be a full path, or relative to the EAServer bin directory. The default is:
serverhttperror.log
Where server is the server name.
com.sybase.jaguar.server.http.errorlogsize,
com.sybase.jaguar.server.http.errorlogtruncate
Specifies the maximum size of the HTTP error log.
The size in bytes. No value means there is no size limit. If the maximum size is reached, the existing log is closed and renamed and a new log is created.
com.sybase.jaguar.server.http.errorlogname,
com.sybase.jaguar.server.http.errorlogtruncate
Specifies whether the HTTP error log is truncated when the server is restarted.
true
or false
.
The default is false
.
com.sybase.jaguar.server.http.errorlogname,
com.sybase.jaguar.server.http.errorlogsize
Specifies whether HTTP-tunnelled IIOP connections should be closed after sending each IIOP response.
true
or false
.
The default is false
.
When debugging proxy configurations, you can set this property
to true
if it helps your debugging
efforts. This setting degrades server performance, and we suggest
that you use it only for debugging purposes.
Specifies the maximum number of threads to handle HTTP client requests.
A positive integer. The default is 25.
com.sybase.jaguar.server.http.numthreads,
com.sybase.jaguar.server.maxthreads
Specifies the thread pool size to handle HTTP client requests.
A positive integer. The default is 25.
com.sybase.jaguar.server.http.maxthreads
Specifies the HTTP request log file name.
The path and file name. The path can be a full path, or relative to the EAServer bin directory. The default is:
serverhttprequest.log
Where server is the server name.
com.sybase.jaguar.server.http.requestlogsize,
com.sybase.jaguar.server.http.requestlogtruncate
Specifies the maximum size of the HTTP request log.
The size in bytes. No value means there is no size limit. If the maximum size is reached, the existing log is closed and renamed and a new log is created.
com.sybase.jaguar.server.http.requestlogname,
com.sybase.jaguar.server.http.requestlogtruncate
Specifies whether the HTTP request log is truncated when the server is restarted.
true
or false
.
The default is false
.
com.sybase.jaguar.server.http.requestlogname,
com.sybase.jaguar.server.http.requestlogsize
Specifies the HTTP servlet log file name.
The path and file name. The path can be a full path, or relative to the EAServer bin directory. The default is:
serverhttpservlet.log
Where server is the server name.
com.sybase.jaguar.server.http.servletlogsize,
com.sybase.jaguar.server.http.servletlogtruncate
Specifies the maximum size of the HTTP servlet log.
The size in bytes. No value means there is no size limit. If the maximum size is reached, the existing log is closed and renamed and a new log is created.
com.sybase.jaguar.server.http.servletlogname,
com.sybase.jaguar.server.http.servletlogtruncate
Specifies whether the HTTP servlet log is truncated when the server is restarted.
true
or false
.
The default is false
.
com.sybase.jaguar.server.http.servletlogname,
com.sybase.jaguar.server.http.servletlogsize
Enables and disables HTTP statistics logging.
true
or false
.
The default is false
.
com.sybase.jaguar.server.http.statlogfrequency,
com.sybase.jaguar.server.http.statlogname
When HTTP statistics logging is enabled, specifies the update frequency.
An integer specifying the interval between updates, in seconds. The default is 36000.
com.sybase.jaguar.server.http.statlogenable,
com.sybase.jaguar.server.http.statlogname
Specifies the HTTP statistics log file name.
The path and file name. The path can be a full path, or relative to the EAServer bin directory. The default is:
serverhttpstat.dat
Where server is the server name.
com.sybase.jaguar.server.http.statlogenable,
com.sybase.jaguar.server.http.statlogfrequency
When PowerDynamo execution is enabled, specifies the evaluation order of PowerDynamo and servlet path mappings.
Value | To indicate |
---|---|
dynamo,servlet
(the default)
|
PowerDynamo request path mappings take precedence over servlet path mappings. |
servlet,dynamo
|
The reverse of the above. |
com.sybase.jaguar.server.dynamo.exec
Enables and disables IIOP logging in the server.
true
or false
.
The default is false
.
IIOP logging can be useful for debugging, but generates a tremendous amount of log output.
Enables and disables IIOP logging for events that occur after the server begins accepting messages.
true
or false
.
The default is false
.
This generates less log output than com.sybase.jaguar.server.iiop.log because it does not log messages during server start-up.
Specifies the interfaces file name used by Open Client Client-Library connection caches.
The file name. For UNIX platforms, the default is $JAGUAR/interfaces. For Windows, the default is %JAGUAR%\ini\sql.ini.
This interfaces file is used only by the Client-Library implementation provided with EAServer for use in components that use Client-Library connection caches.
Specifies the JAAS configuration file.
The path to the JAAS configuration file.
For more information on this property, see the "JAAS Support on EAServer" chapter in the EAServer Security Administration and Configuration Guide.
Specifies the password for the built-in jagadmin administrative account.
The password text. Values are encrypted in the repository.
Specifies the DOM parser configuration displayed in Jaguar Manager.
Value | To indicate |
---|---|
0 | No parser |
1 | Platform default |
2 | The parser specified by the com.sybase.jaguar.server.DOMfactory property |
com.sybase.jaguar.server.DOMfactory,
com.sybase.jaguar.server.jagmgr.SAXFactoryChoice,
com.sybase.jaguar.server.jagmgr.XSLTFactoryChoice
Specifies the SAX parser configuration displayed in Jaguar Manager.
Value | To indicate |
---|---|
0 | No parser |
1 | Platform default |
2 | The parser specified by the com.sybase.jaguar.server.SAXfactory property |
com.sybase.jaguar.server.SAXfactory, com.sybase.jaguar.server.jagmgr.DOMFactoryChoice, com.sybase.jaguar.server.jagmgr.XSLTFactoryChoice
Specifies the XSLT parser configuration displayed in Jaguar Manager.
Value | To indicate |
---|---|
0 | No parser |
1 | Platform default |
2 | The parser specified by the com.sybase.jaguar.server.XSLTfactory property |
com.sybase.jaguar.server.XSLTfactory, com.sybase.jaguar.server.jagmgr.DOMFactoryChoice, com.sybase.jaguar.server.jagmgr.SAXFactoryChoice
Specifies Java classes and JAR files to be loaded by the application's custom class loader.
Same as for com.sybase.jaguar.application.java.classes.
EAServer uses custom class loaders to support hot-refresh of server-side code. This property defines classes to be custom loaded for components in the package. Components in a package can share common classes, yet still be refreshed by refreshing the package.
In Jaguar Manager, set this property using the Java Classes tab in the Package Properties dialog box.
com.sybase.jaguar.server.classloader.debug,
com.sybase.jaguar.component.java.classes,
com.sybase.jaguar.application.java.classes,
com.sybase.jaguar.package.java.classes,
com.sybase.jaguar.webapplication.java.classes
Specifies the shared library or DLL used for interaction with the Java virtual machine.
Value | To indicate |
---|---|
libjjdk11 | JDK 1.1 |
libjjdk12
|
JDK 1.2 or later |
The JAGUAR_JAVAVM variable overrides this property The JAGUAR_JAVAVM variable overrides this property, and is set in the serverstart script. The default JDK is JDK 1.3.
Determines the behavior of JNDI get connection calls.
The get connection call state, which can be one of:
State | Description |
---|---|
NOWAIT | The default. If there are no connections in the queue, JNDI calls fail. |
WAIT | JNDI calls wait until a connection is available. |
FORCE | If a connection is not available, JNDI calls force a connection to be created. |
Specifies the port number for JDPA remote debugging connections.
The port number.
com.sybase.jaguar.server.jvm.debugging,
com.sybase.jaguar.server.jvm.debug.options
Enables and disables Java in-server debugging in the nondebug server executable.
true
or false
.
The default is false
. Java
debugging is always enabled in the debug server executable.
com.sybase.jaguar.server.jpda.port,
com.sybase.jaguar.server.jvm.debug.options
Specifies additional JVM options to configure in-server Java debugging.
The options string, as it would be passed on the command line to the java executable. When debugging is enabled, these options are passed in addition to those specified by the com.sybase.jaguar.server.jvm.options property.
com.sybase.jaguar.server.jpda.port,
com.sybase.jaguar.server.jvm.debugging,
com.sybase.jaguar.server.jvm.options
Specifies the maximum heap size for the Java virtual machine.
The size in bytes, kilobytes, or megabytes, as described in the following table:
Heap size value syntax | To indicate |
---|---|
nMor nm |
n megabytes, for
example:
512M |
nKor nk |
n kilobytes, for
example:
1024K |
n |
n bytes, for example:
536870912 |
For JDK 1.3, the value must be a multiple of 1024 greater than 2 megabytes. The default depends on the JDK version:
JDK version | Max heap size default |
---|---|
1.2 (all platforms) | The JDK default |
1.3 on Windows | 500MB |
1.3 on Solaris | 1024MB |
1.3 on HP-UX | 1024MB |
1.3 on AIX | 1500MB |
This property corresponds to the -Xmx
option
for the Java interpreter. If you specify a -Xmx
setting
in the value of the property com.sybase.jaguar.server.jvm.options, it takes precedence
over the value of this property.
com.sybase.jaguar.server.jvm.options, com.sybase.jaguar.server.jvm.minHeapSize
Specifies the minimum heap size for the Java virtual machine.
Same as for com.sybase.jaguar.server.jvm.maxHeapSize.
This property corresponds to the -Xms
option
for the Java interpreter. If you specify a -Xms
setting
in the value of the property com.sybase.jaguar.server.jvm.options, it takes precedence
over the value of this property.
com.sybase.jaguar.server.jvm.options, com.sybase.jaguar.server.jvm.maxHeapSize
When using the Client Hotspot Java Virtual Machine (VM), specifies whether the just-in-time (JIT) Java compiler is disabled.
true
or false
. In
EAServer 4.1 and later, the default for new servers is false
. In
releases prior to 4.1, the default is true
.
This property has no effect if the server is started with the Server Hotspot VM. The server VM is determined by the command-line options used to start the server or to install it as a Windows service.
Specifies options to be passed to the server's Java virtual machine.
The options string, as it would be passed to the java command line. The default is:
-Djava.protocol.handler.pkgs=com.sybase.jaguar.net
The default configures the EAServer HTTPS connection protocol handler as the default for HTTPS protocol javax.net.URLConnection instances.
com.sybase.jaguar.server.jvm.debug.options, com.sybase.jaguar.server.jvm.maxHeapSize, com.sybase.jaguar.server.jvm.minHeapSize
Enables and disables verbose logging of Java system class loader activity.
true
or false
.
The default is false
.
Enables and disables verbose logging of Java garbage collection.
true
or false
.
The default is false
.
Specifies the server's key tab file, which is used for interserver authentication in a cluster.
The file name. The file is generated when you create a cluster, and there is normally no need to set this property manually.
Specifies the language (locale) in which messages are logged.
The language or locale name. The default is us_english
.
Specifies the location from which the server loads DLLs or shared libraries for C++ and C components.
The directory name. The default is the EAServer cpplib subdirectory.
Specifies the server's network listeners as a comma-separated list.
listener1, listener2, ...
Where listener1, listener2, and so forth are listener names defined in the repository.
Specifies the name of the server's log file.
The path and file name. The path can be a full path, or relative to the EAServer bin directory. The default is:
server.log
Where server is the server name.
com.sybase.jaguar.server.logfilesize,
com.sybase.jaguar.server.truncatelog
Specifies the maximum size of the server log file.
The size in bytes. No value means there is no size limit. If the maximum size is reached, the existing log is closed and renamed and a new log is created.
com.sybase.jaguar.server.logfilename,
com.sybase.jaguar.server.truncatelog
Configures the return status for Methods As Stored Procedures (MASP) invocations.
Value | To indicate |
---|---|
false
(the
default)
|
A return value of 1 indicates success; a value of 0 indicates failure. |
true
|
Reverses the meanings of 0 and 1 return values. |
"Executing Methods as Stored Procedures" in the EAServer Programmer's Guide
Specifies the maximum number of simultaneous connections.
A positive integer. The default is 30.
Specifies the maximum number of simultaneous threads.
A positive integer. The default is 50.
Specifies the server name.
The name text.
Specifies the default NameServiceURL parameter
for the C++ and Java ORB when run in the server.
Also, when the com.sybase.jaguar.server.CosNaming.nameserver property is false
, specifies
the server to connect to for naming services.
The IIOP URL for naming services. The default is iiop://0:0
.
The default is appropriate if the server provides naming services
to itself.
com.sybase.jaguar.server.CosNaming.nameserver
Specifies whether native (operating system) thread mutexes are used in the server.
true
or false
.
The default is true
.
Specifies the default size of the network buffer.
The size in bytes. The default is 2048.
Specifies the packages that are installed in this server.
A comma-separated list of package names.
Packages may be installed in a server directly using this property or as part of an application using the com.sybase.jaguar.server.applications property.
com.sybase.jaguar.server.applications,
Package properties
Specifies server-wide access control restrictions.
The name of a valid EAServer role.
If you set this property to a name of a role, only users that are members of that role can access the methods, components, and packages hosted on that server. For example, if you set this property to "MyRole", only users that are members of "MyRole" can access the components hosted on the server.
This property does not affect Web applications, or the resources it contains.
Specifies the name of a custom component that evaluates a user's role membership to control access to components and HTTP URLs.
package/component
Where package/component is the name of an EAServer package/component.
Specifies the class name for a custom SAX XML parser factory class.
The class name. If the class is in a JAR file, the JAR file name must be listed in the com.sybase.jaguar.server.java.classes property.
com.sybase.jaguar.server.jagmgr.SAXFactoryChoice,
com.sybase.jaguar.server.DOMfactory,
com.sybase.jaguar.server.XSLTfactory
Specifies the list of trusted identities used for incoming component invocations when propagating client credentials from another server.
t1,t2,t3,...
Where t1, t2, and so forth are identity names that are defined in the repository.
com.sybase.jaguar.server.security.identity, Security properties
Specifies the identity used for outgoing component invocations when propagating client credentials to another server.
The name of an identity that is defined in the repository.
com.sybase.jaguar.server.security.identities, Security properties
A list of components that run as service components in the server.
A comma-separated list of components; for example:
CtsComponents/MessageService
Chapter 31, "Creating Service Components," in the EAServer Programmer's Guide.
Specifies the aliases (prefixes) for execution of servlets that are installed directly in this server.
A comma-separated list of aliases. If not set, the default alias is "servlet".
Servlets that are installed directly in the server using the com.sybase.jaguar.server.servlets property are executed using request paths of the form:
/alias/servlet-name
Or:
/alias/servlet-class
Where alias is the servlet alias, servlet-name is the servlet name, and servlet-class is the servlet class name in Java dot notation. Class-name requests can be disabled with the com.sybase.jaguar.server.servlet.class-name-req property.
This property does not affect servlets or JSPs that are installed in a Web application.
com.sybase.jaguar.server.servlets, com.sybase.jaguar.server.servlet.class-name-req, com.sybase.jaguar.server.webapplications
Specifies whether servlets that are installed directly in this server can be executed by specifying the class name in the URL.
true
or false
.
The default is true
.
This property affects only servlets that are installed directly in the server (those specified by the com.sybase.jaguar.server.servlets property), not servlets that are installed in a Web application.
com.sybase.jaguar.server.servlet.aliases, com.sybase.jaguar.server.servlets
Specifies the context initialization parameters for the servlets that are installed directly in this server.
A string of the form:
entry1, entry2, ...
Where entry1, entry2, and so forth are of the form:
(description=desc,value=value,name=name)
Where:
This property allows you to specify context initialization parameters for servlets that are installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property.
com.sybase.jaguar.server.servlets, com.sybase.jaguar.webapplication.context-param
The number of seconds that EAServer should wait for servlet service calls to return before calling the servlet destroy method.
The timeout value in seconds. A value of 0 indicates infinity.
This property affects all servlets installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property. It does not affect servlets installed in a Web application.
You can override the server-wide setting for individual servlets by setting the com.sybase.jaguar.servlet.destroy.wait-time property.
com.sybase.jaguar.server.servlets,
com.sybase.jaguar.server.servlet.init-timeout
Enables and disables servlet execution.
true
or false
.
The default is true
, which
enables servlet execution.
Specifies how long the server should wait for each servlet's init method to return.
The timeout period in seconds. The default is 0, which indicates that there is no time limit.
This property affects all servlets installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property. It does not affect servlets installed in a Web application.
You can override the server-wide default timeout for individual servlets by setting the servlet property com.sybase.jaguar.servlet.init.timeout.
If a servlet's init method might run indefinitely, specify a finite timeout period. If the init method does not return in the specified timeout period, the server abandons the servlet and it will be unavailable until the server is restarted or refreshed. Service requests that arrive while init is running are blocked until init returns. If init is allowed to run indefinitely, clients will receive browser timeout errors when attempting to execute the servlet.
com.sybase.jaguar.server.servlet.destroy-wait-time,
com.sybase.jaguar.servlet.init.timeout
Specifies MIME mappings for static files served outside of Web applications.
mapping1, mapping2, ...
Where mapping1, mapping2, and so forth are mappings of the form:
(description=desc,mime-type=mime-def,extension=ext)
Where:
desc | Is an optional description. |
mime-def | Is the MIME type specification, for example, text/plain
or text/sgml
.
|
ext | Is the file extension for files of this type. |
A file's MIME type specifies how a server or browser should interpret the file. For example, whether the file contains plain text, formatted HTML, an image, or a sound recording. In a Web server, MIME mappings specify how a static file should be interpreted by mapping file extensions to MIME types. MIME mappings affect only static files. Servlets and JSPs must be coded to specify a MIME type for their response.
For more information on MIME types, visit:
http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html
EAServer includes preconfigured MIME mappings. These settings override EAServer's preconfigured mappings.
com.sybase.jaguar.webapplication.mime-mapping
Associates request paths with servlets installed directly in this server.
mapping1,mapping2,...
Where mapping1, mapping2, and so forth are mappings of the form:
(description=desc,url-pattern=pattern,servlet-name=servlet)
Where:
desc | Is an optional text description of the mapping. |
pattern | Is a URL pattern that can contain wildcards. |
servlet | Is a servlet that is installed in this application. Servlets in the Web application have names formatted as webapp/servlet. Use only the servlet part of the servlet name. |
This property affects servlets installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property. It does not affect servlets installed in a Web application.
com.sybase.jaguar.server.servlets,
com.sybase.jaguar.webapplication.servlet-mapping
Configures HTTP session properties for servlets installed directly in this server.
Same as the Web application property com.sybase.jaguar.webapplication.session-config.
This property affects servlets installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property. It does not affect servlets installed in a Web application.
com.sybase.jaguar.server.servlets,
com.sybase.jaguar.webapplication.session-config
Enables and disables trace logging in the EAServer servlet execution engine.
true
or false
.
The default is false
, which
disables tracing.
Configures welcome files for Web directories served outside of Web applications. Welcome files are used to satisfy HTTP requests that end in a directory name, rather than specifying the full path to a file or a path that is mapped to a servlet invocation.
A comma-separated list of file names which may not contain path separators.
com.sybase.jaguar.webapplication.welcome-file-list
Specifies the servlets that are installed directly in this server.
A comma-separated list of servlet names that are defined in the repository.
Servlets can also be installed as part of a Web application. Web applications are the preferred deployment mechanism where portability to other J2EE application servers is a concern.
com.sybase.jaguar.server.webapplications,
com.sybase.jaguar.server.applications,
Servlet properties
On UNIX platforms, configures the thread stack size.
The stack size in bytes. If not set, the default is 256K.
"Configuring server stack size"
Specifies the default instance timeout for stateful components running in the server.
The default is 0.
Specifies whether TDS protocol attentions are being traced.
true
or false
.
The default is false
, which
disables tracing.
Specifies whether network driver requests are traced.
true
or false
.
The default is false
, which
disables tracing.
Specifies whether transport control layer requests are being traced. (The transport control layer is an internal EAServer library that acts as an interface to network drivers.)
true
or false
.
The default is false
, which
disables tracing.
Specifies whether TDS packet contents are traced.
true
or false
.
The default is false
, which
disables tracing.
Specifies whether TDS header contents are traced.
true
or false
.
The default is false
, which
disables tracing.
Specifies whether to truncate the server log each time the server is started.
true
or false
.
The default is false
, which
does not truncate the log.
com.sybase.jaguar.server.logfilename
Specifies the default transaction timeout for components running in the server.
The timeout period, in seconds, with 0 indicating no timeout. The default is 0.
In Jaguar Manager, set this property using the All Properties tab in the Server Properties dialog box.
com.sybase.jaguar.component.tx_timeout
Specifies the transaction coordination model for the server.
Value | To indicate |
---|---|
1pc
(the
default)
|
Shared connection model |
dtc
|
Microsoft DTC (Windows platforms only) |
ots
|
OTS/XA |
JTS
|
JTS/JTA |
Specifies whether user membership in operating system groups is checked when determining a user's membership in EAServer roles.
true
or false
.
The default is false
.
Specifies the names of the Web applications that are installed in the server.
A comma-separated list of the Web application names.
Web applications may be installed to a server directly using this property or as part of an application using the property com.sybase.jaguar.server.applications.
com.sybase.jaguar.server.applications
Specifies the class name for a custom XSLT XML parser factory class.
The class name. If the class is in a JAR file, the JAR file name must be listed in the com.sybase.jaguar.server.java.classes property.
com.sybase.jaguar.server.jagmgr.XSLTFactoryChoice,
com.sybase.jaguar.server.DOMfactory,
com.sybase.jaguar.server.SAXfactory
You can set environment variables for the server process by specifying them as server properties. Values specified in environment variables overwrite any values set in the server start-up scripts. You can use this feature to set properties when a server is run as a Windows NT or Windows 2000 service. In this case, the server start-up script settings do not apply.
Specify the environment variable name as the property name, and the value as the property value. For example:
MYPATH=/work/EAServer/deploy
The following variables have default values that can be overwritten by specifying a property with a new value:
Variable | Default value |
---|---|
JAGUAR_HOST_NAME
|
The host name of the machine where the server
is running. You can override the default if the machine supports
multiple addresses (host names), and you want to force the address
that is used when the listener configuration uses the ${JAGUAR_HOST_NAME}
macro.
|
JAGUAR_IP_ADDRESS
|
The IP address of the machine where the server
is running. You can override the default if the machine supports
multiple addresses, and you want to force the address that is used
when the listener configuration uses the ${JAGUAR_IP_ADDRESS}
macro.
|
DLL_SUFFIX
|
The platform-specific suffix used by shared libraries or DLLs. Do not change the default value. |
JAGUAR_PLATFORM
|
The platform-identifier used in generated C++ component make files, and to load platform-specific shared libraries in mixed-architecture clusters. Do not change the default value. |
Copyright © 2002 Sybase, Inc. All rights reserved. |
![]() |