Server property names
begin with com.sybase.jaguar.server.
A server represents an application server process.
Chapter 3, “Creating and Configuring Servers”
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 Appendix B, “Migrating Open Server Applications to EAServer,” in 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 a 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:
For all component types, the URL can be set to the EAServerPackage/EAServerComponent; the component must be installed in the server.
Java CORBA and C++ CORBA components can be accessed using the pseudocomponent object URL. The syntax for a Java pseudocomponent is:
pseudo://java/JavaClass/package/component
Where JavaClass is the Java class name, package is the EAServer package name, and component is the component name. The syntax for a C++ pseudocomponent is:
pseudo://cpp/SharedLibraryName/package/component
Where SharedLibraryName is the DLL or UNIX shared library file name.
Components implemented for pseudocomponent access must be thread-safe, and you must restart EAServer to refresh the component.
For more information on pseudocomponents, see Chapter 34, “Creating and Using EAServer Pseudocomponents,” in the EAServer Programmer’s Guide.
The EAServer Security Administration and Programming 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 Programming 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 |
|---|---|
|
Components are bound in the name service run method. |
|
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 EAServer Manager, set this property using the Advanced 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
Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide
For servers that run in clusters and support Internet Protocol Version 6 (IPV6), specifies a server ID that is unique in the cluster.
A string in the format of an IPV4 address that is unique in the cluster, for example:
10.123.456.789
If you do not specify a value, EAServer generates a server ID, however, the generated ID is not guaranteed to be unique in the cluster if servers use IPV6 addresses.
Specifies a default effective transaction isolation level for EJB CMP entity beans installed in the server.
See “Configuring CMP isolation level” in the EAServer Performance and Tuning Guide.
com.sybase.jaguar.component.cmp_iso_level
Specifies the default for the com.sybase.jaguar.package.code.set package property.
Same as com.sybase.jaguar.component.code.set. The default is utf8.
In EAServer 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 |
|---|---|
|
Name bindings are stored internally in server memory. |
|
Name bindings are stored externally in an LDAP name server. |
“Transient versus persistent storage”
Specifies the interface supported for remote Java debugging.
Value |
To indicate |
|---|---|
|
Java debugging supported by the sun.tools.debug interface. |
|
Java debugging is supported by the JPDA interface, at the port specified by the com.sybase.jaguar.server.jpda.port property. |
com.sybase.jaguar.server.jpda.port
Specifies the default connection cache for EJB CMP entity beans that are imported from an EJB-JAR file.
The name of an existing JDBC connection cache. If not set,
the default is JavaCache.
The connection cache for EJB CMP entity beans is set as cache part
of the com.sybase.jaguar.component.storage component property.
To override the default, you can set this property with the sybase-easerver-config.xml configuration
file in the EJB-JAR file.
com.sybase.jaguar.component.storage, “Using EAServer configuration files in J2EE archives”, Chapter 27, “Creating Entity Components,” in the EAServer Programmer’s Guide
Specifies an optional text description of the server.
The descriptive text.
Whether to destroy pooled component instances when shutting down the server.
A value of true indicates
that pooled instances must be destroyed explicitly before shutting
down. For example, an EJB component’s ejbRemove method will
be called. This allows the pooled instance to clean up resources,
such as closing database connections. A value of false specifies
that instances are not destroyed. The default is true.
If many component instances are pooled, explicit destruction of instances may lengthen the time required to shut down or restart the server.
The server setting can be overridden for individual components by setting the com.sybase.jaguar.component.destroyPooledInstancesOnShutdown component property.
com.sybase.jaguar.server.destroyPooledInstancesOnShutdownTimeout, com.sybase.jaguar.component.destroyPooledInstancesOnShutdown
How long to wait for each instance destruction method to return when destroying pooled instances during server shutdown.
The time to wait, in seconds. If no value is specified, the default is 5.
com.sybase.jaguar.server.destroyPooledInstancesOnShutdown, com.sybase.jaguar.component.destroyPooledInstancesOnShutdownTimeout
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. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.server.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
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 |
|---|---|
|
No user can execute the method. |
|
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:
The com.sybase.jaguar.server.ejb.role.default property is a server-wide property. To assign roles to all methods of an EJB 2.0 component in EAServer 4.0, you can assign individual roles to all methods of the component, or set the com.sybase.jaguar.server.ejb.role.default property to everybody.
Beginning with EAServer 4.1, com.sybase.jaguar.server.ejb.role.default has been removed. To assign a role to any one method of an EJB 2.0 component, assign roles to all methods of the component. Otherwise, the server displays an error message when trying to execute the method that does not have a role assigned to it.
If none of the methods of an EJB 2.0 component have roles assigned to them, authorization checks are not enforced and authorization is not performed. No error message is sent to the server log.
com.sybase.jaguar.method.security-roles
For components that are installed on this server but run externally, specifies how long to wait for a response from the external server before returning an error to the client.
The timeout in seconds. If not set, the default is 60 seconds. A value of 0 specifies infinity.
com.sybase.jaguar.component.external.request.timeout
For components that are installed on this server but run externally, specifies how long to wait for a response from the external server before returning an error to the client.
The timeout in seconds. If not set, the default is 60 seconds. A value of 0 specifies infinity.
com.sybase.jaguar.component.external.serverstart.timeout
Associates a custom response header filter with URL paths. The default mapping is “/*”; this runs the filter on all server resources.
mapping1, mapping2, mapping3, ...
Where mapping1, mapping2, mapping3 are strings of the form:
(description=desc,filter-name=filter, type=pattern)
Where:
desc is an optional description of the mapping.
filter is the filter name.
pattern is the URL pattern.
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.
Enables flow control for HTTP client requests.
true or false.
The default is false, which
disables flow control.
When the server is very busy with many client connections, client request threads may repeatedly conflict with each other for access to low-level system resources. Flow control provides a coarser level of granularity for synchronizing access to system resources by request threads. When enabled, flow control can improve performance by replacing multiple, serial choke points in the request processing sequence with a single choke point.
com.sybase.jaguar.server.flowcontrol.iiop, com.sybase.jaguar.server.flowcontrol.maxexethreads
Enables flow control for IIOP client requests.
true or false. The default is false, which disables flow control.
WARNING! In some scenarios, IIOP client threads may deadlock when IIOP flow control is enabled. Do not enable IIOP flow control in production servers without first stress testing your applications with scenarios that reflect production loads.
com.sybase.jaguar.server.flowcontrol.http, com.sybase.jaguar.server.flowcontrol.maxexethreads
Specifies the maximum number of threads that can concurrently execute code that is governed by flow control.
Specify a positive integer. If not set, the default is the value of the com.sybase.jaguar.server.maxthreads property, which means all threads can proceed. For the best performance, you should tune this number to get the best performance under peak stress conditions. Values between 15 and 30 are a good starting point. To tune the setting, monitor response time at peak load conditions, and raise or lower the value to find the setting that results in the best response time.
com.sybase.jaguar.server.flowcontrol.http, com.sybase.jaguar.server.flowcontrol.iiop, com.sybase.jaguar.server.maxthreads
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.
This property is no longer supported. To exclude files from the cache, use the com.sybase.jaguar.server.http.cache.webapps.exclude-files property.
The value is ignored.
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
Specifies the Web application to invoke when users access the default URL http://host:port/. If not set, the welcome page of the Web application with the context path “/” is invoked; by default, this is the EASDefault Web application, and its welcome page is $JAGUAR/html/index.html.
The name of a Web application.
“The EASDefault Web application” in Chapter 21, “Creating Web Applications,” in the EAServer Programmer’s Guide.
Enables browsing of directories for HTTP clients.
true or false.
The default is false.
Directory browsing allows a client to see a list of files in a directory when the specified URL ends in a directory name and the directory does not include a welcome file. If directory browsing is not enabled for the directory, EAServer returns HTTP 500 errors for these requests.
To enable browsing, you must set this property to true and also list the directory trees that can be browsed by setting the properties com.sybase.jaguar.server.http.dirbrowseinclude and com.sybase.jaguar.server.http.dirbrowsewebappinclude.
Restart the server for the changes to take effect.
com.sybase.jaguar.server.http.dirbrowseinclude, com.sybase.jaguar.server.http.dirbrowsewebappinclude
This property is no longer supported. If directory browsing is enabled, specify the directories under the document root that can be browsed using the com.sybase.jaguar.server.http.dirbrowsewebappinclude property.
The value is ignored.
If directory browsing is enabled, specifies Web application subdirectories that can be browsed.
A list of Web applications and browseable directories within each web application. Each entry in the list must be in the form:
(WebApp, dir-list)
Where:
WebApp is
the Web application name. Use * to
specify all Web applications; in this case, the specified directories
can be browsed in any Web application where they exist.
dir-list is a comma-separated
list of directories which must begin with a /. The
contents of each specified directory and its subdirectories can
be browsed. To allow browsing of all directories, enter /*.
For example, to allow browsing of images in the Retail Web application and docs and images in the Wholesale Web application, specify:
(Retail, /images), (Wholesale, /docs, /images)
To allow browsing of images and help directories in any Web application, specify:
(*, /images, /help)
To allow browsing of any directory in any Web application, specify:
(*, /*)
Browsing must be enabled by setting the com.sybase.jaguar.server.http.dirbrowseenable property. Restart the server for the changes to take effect after changing these properties.
The special Web application directories WEB-INF and META-INF cannot be browsed even if specified because the Java Servlet specification does not allow servlet containers to return content from these directories.
com.sybase.jaguar.server.http.dirbrowseenable, com.sybase.jaguar.webapplication.welcome-file-list
Specifies whether to send HTTP 1.1 client responses as chunked streams or in byte-serving mode. If not set, responses are sent as chunked streams.
true or false.
The default is false.
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 host and/or domain name for the proxy HTTP server.
The host or domain name; for example, sybooks.sybase.com or sybase.com.
There is no default.
Set this only if you are configuring the redirection URL for use with a Web proxy, as described in “Configuring redirection addresses when using a proxy server”.
com.sybase.jaguar.server.http.httpport, com.sybase.jaguar.server.http.httpsport, com.sybase.jaguar.server.http.proxyprotocol, com.sybase.jaguar.webapplication.httpdomain.override
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
If the HTTP request log uses extended log file format (ELFF), specifies the items and the order in which to write them to the request log.
A comma-separated list of items. Table B-20 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 |
clientaddr |
c-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 |
This property is used only when you set com.sybase.jaguar.server.http.elffenable to true.
The default is:
clientaddr, date, time, reqline, status, length, cookie, referer
Which generates something like this in the log file:
#Version: 1.0 #Date: 2001-12-31 04:10:00 #Fields: c-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.
When a domain name is specified by setting com.sybase.jaguar.server.http.domainname, the port for HTTP redirection URLs.
The port number. If not specified, the default is 80.
Set this only if you are configuring the redirection URL for use with a Web proxy, as described in “Configuring redirection addresses when using a proxy server”.
com.sybase.jaguar.server.http.domainname, com.sybase.jaguar.server.http.httpsport, com.sybase.jaguar.server.http.proxyprotocol
When a domain name is specified by setting com.sybase.jaguar.server.http.domainname, the port for HTTP redirection URLs.
The port number. If not specified, the default is 80.
Set this only if you are configuring the redirection URL for use with a Web proxy, as described in “Configuring redirection addresses when using a proxy server”.
com.sybase.jaguar.server.http.domainname, com.sybase.jaguar.server.http.httpport, com.sybase.jaguar.server.http.proxyprotocol
Specifies the maximum number of threads to handle HTTP client requests.
A positive integer. The default is 25.
com.sybase.jaguar.server.maxthreads
When a domain name is specified by setting com.sybase.jaguar.server.http.domainname, the protocol for redirection URLs.
The protocol; for example, HTTP or HTTPS. The default is the protocol of the original request.
Set this only if you are configuring the redirection URL for use with a Web proxy, as described in “Configuring redirection addresses when using a proxy server”.
com.sybase.jaguar.server.http.domainname, com.sybase.jaguar.server.http.httpport, com.sybase.jaguar.server.http.httpsport
Enables and disables HTTP request logging.
true or false.
The default is false.
com.sybase.jaguar.server.http.requestlogname, com.sybase.jaguar.server.http.requestlogsize, com.sybase.jaguar.server.http.requestlogtruncate
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.requestlogenable, 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.requestlogenable, 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 whether to EAServer should add the “Server” response header field to each HTTP response. This optional HTTP response header field contains a description of the server software.
true or false.
The default of false specifies
omission of the “Server” field in the response
header.
Obsolete since version 5.0. Configure the log profile properties to discard messages logged from the servlet engine.
N/A.
Obsolete since version 5.0. Use the log profile properties to specify a file name.
N/A.
Obsolete since version 5.0. Use the log profile properties to specify a maximum file size.
N/A.
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
Specifies whether sign-on occurs externally. Set this property to true if you are using an external single-sign on provider.
true or false.
The default is false.
“Supporting external single sign-on providers” in the EAServer Security Administration and Programming Guide.
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 |
|---|---|
|
PowerDynamo request path mappings take precedence over servlet path mappings. |
|
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 JAAS, see Chapter 11, “Using the JAAS API,” in the EAServer Security Administration and Programming Guide.
com.sybase.jaguar.server.jaas.section
Specifies the section name in the JAAS configuration file to be used for this server.
The section name. If not specified, the default is the name of the server.
Setting this property allows you to use the same JAAS configuration setting in multiple servers. For more information on JAAS, see Chapter 11, “Using the JAAS API,” in the EAServer Security Administration and Programming Guide.
com.sybase.jaguar.server.jaas.config
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 EAServer 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 EAServer 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 EAServer 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 server’s custom class loader.
Same as for com.sybase.jaguar.application.java.classes.
See “Custom class lists for packages, applications, or servers” in Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
In EAServer 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
Enables tracing of Java Connection Manager (JCM) activity.
The get connection call state, which can be one of:
State |
Description |
|---|---|
true |
Tracing enabled. Trace information is written to the server log. Restart the server for the change to take effect. |
false |
The default. Tracing is disabled. |
Specifies the port number for JDPA remote debugging connections.
The port number.
com.sybase.jaguar.server.jvm.debug.options
When using the JPDA remote debugging interface, allows you to pause the server at startup so that breakpoints can be set in Java code that executes at startup time.
true or false.
In the default configuration, the value is ${JPDASUSPEND}, which
evaluates to the JPDASUSPEND environment variable as set in the server
startup scripts. The default configuration allows you to set this
property with the -jpdasuspend command line option.
See “Starting the server” for
more information.
After the server pauses, you must resume execution with your remote debugger.
Specifies the size of the in-memory table that the transaction manager uses to cache information about pending transactions.
An integer value. The default is 1024. For best performance, set the value to at least one-half of the maximum number of simultaneous transactions expected in your application.
Specifies the directories and JAR files in the boot classpath search list for the Java virtual machine. Classes loaded from these locations can override the core Java runtime classes. In most cases, the value should match the com.sybase.jaguar.server.jvm.classpath setting.
The default is ${BOOTCLASSPATH}, which
is replaced by the valur of the BOOTCLASSPATH environment variable
at runtime. If you add entries or use a different value, the resultant
list must consist of directories and the full paths to JAR files.
On Windows platforms, use a semicolon (;) to separate entries. On
UNIX platforms, use a colon (:). For example, this setting uses
the default prefixed with a different JAR file:
d:\devstuff\experimental.jar;${BOOTCLASSPATH}
com.sybase.jaguar.server.jvm.bootclasspath.jars, com.sybase.jaguar.server.jvm.classpath
Specifies additional JAR files to be included in the BOOTCLASSPATH setting for the server’s Java virtual machine.
A comma separated list of JAR file names, which must be located in the EAServer java/classes subdirectory, for example:
jaxrpc-api.jar,commons-logging.jar,log4j.jar
Setting this property avoids the limit on environment variable size. If the BOOTCLASSPATH setting exceeds the size limit, the Windows serverstart batch file may fail. Although this problem occurs on Windows, the setting can be used on all platforms.
JAR files located in the java/lib subdirectory are automatically added to the CLASSPATH and BOOTCLASSPATH environment variable when the server starts.
com.sybase.jaguar.server.jvm.bootclasspath, com.sybase.jaguar.server.jvm.classpath.jars
Specifies the directory search path to load native libraries used by Java classes.
The syntax is the same as for the platform PATH environment
variable setting. The default is ${BOOTLIBRARYPATH},
which is replaced by the value of the BOOTLIBRARYPATH variable at
runtime.
com.sybase.jaguar.server.jvm.bootclasspath, com.sybase.jaguar.server.jvm.classpath
Specifies which version of the EAServer custom class loader to use.
A value of JaguarClassLoaderv2 specifies
version 2.0 of the EAServer custom class loader. Any other value
specifies version 1.0.
EAServer uses customized Java class loaders to allow hot refresh of Web application classes and Java components without restarting the server. EAServer versions earlier than 5.1 use version 1.0 of the custom class loader. Beginning in EAServer 5.1, you can use the version 2.0 class loader by setting this property. The newer class loader provides additional configuration options and improved diagnostics. For backward compatibility with applications developed with EAServer 5.1, the default EAServer configuration uses the version 1.0 class loader.
Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
Specifies the classpath for the Java virtual machine, which is the list of directories and JAR files that are searched to load classes. These locations are searched after the locations specified in com.sybase.jaguar.server.jvm.bootclasspath and cannot override the core Java runtime classes.
The default is ${CLASSPATH}, which
is replaced by the valur of the CLASSPATH environment variable at
runtime. If you add entries or use a different value, the resultant list
must consist of directories and the full paths to JAR files. On
Windows platforms, use a semicolon (;) to separate entries. On UNIX
platforms, use a colon (:). For example, this setting uses the default
prefixed with a different JAR file:
d:\devstuff\experimental.jar;${BOOTCLASSPATH}
com.sybase.jaguar.server.jvm.classpath.jars, com.sybase.jaguar.server.jvm.bootclasspath
Specifies additional JAR files to be included in the CLASSPATH setting for the server’s Java virtual machine.
A comma separated list of JAR file names, which must be located in the EAServer java/classes subdirectory, for example:
jaxrpc-api.jar,commons-logging.jar,log4j.jar
Setting this property avoids the limit on environment variable size. If the CLASSPATH setting exceeds the size limit, the Windows serverstart batch file may fail. Although this problem occurs on Windows, the setting can be used on all platforms.
JAR files located in the java/lib subdirectory are automatically added to the CLASSPATH and BOOTCLASSPATH environment variable when the server starts.
com.sybase.jaguar.server.jvm.bootclasspath
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 you start the server in debug mode, 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.options
When set to true, the server logs the JVM options when starting.
true or false.
The default is false.
com.sybase.jaguar.server.jvm.options, com.sybase.jaguar.server.jvm.debug.options, com.sybase.jaguar.server.jvm.maxHeapSize, com.sybase.jaguar.server.jvm.minHeapSize
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 |
|---|---|
nM or nm |
n megabytes, for example: 512M |
nK or 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.3 on Windows |
500MB |
1.3 on Solaris |
1024MB |
1.3 on HP-UX |
1024MB |
1.3 on AIX |
1500MB |
1.3 on Linux (using the IBM JDK 1.3) |
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, in a format similar to command-line options. To specify multiple options, separate the values with commas, for example:
com.sybase.jaguar.server.jvm.options=-DMyVariable=true,-DMyOtherVariable=no
To specify an option setting that includes commas, wrap the setting in single quotes, for example:
com.sybase.jaguar.server.jvm.options=’comment=value1, with a comment’
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.
This property allows you to configure the Java Virtual Machine options directly. See the JDK documentation for information on setting options.
You can set properties specific to a particular JDK version by setting the properties com.sybase.jaguar.server.jvm13.options or com.sybase.jaguar.server.jvm14.options. These properties allow you to use the same server properties when the server requires different JVM options depending on which JDK version is specified at start-up.
Some other properties, referenced in the See also section, configure specific JVM options; settings from these other properties are added to the JVM options when EAServer creates the JVM. For troubleshooting these settings, you can set the com.sybase.jaguar.server.jvm.displayOptions property so the server logs the complete options string at start-up.
com.sybase.jaguar.server.jvm.debug.options, com.sybase.jaguar.server.jvm.displayOptions, com.sybase.jaguar.server.jvm.maxHeapSize, com.sybase.jaguar.server.jvm.minHeapSize, com.sybase.jaguar.server.jvm13.options, com.sybase.jaguar.server.jvm14.options
Specifies additional Java VM options when the server is started with JDK 1.3.
The syntax is the same as com.sybase.jaguar.server.jvm.options. The JDK 1.3 options are appended to those set by the com.sybase.jaguar.server.jvm.options property.
Specifies additional Java VM options when the server is started with JDK 1.4.
The syntax is the same as com.sybase.jaguar.server.jvm.options. The JDK 1.4 options are appended to those set by the com.sybase.jaguar.server.jvm.options property.
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.
Enables and disables verbose logging of Java Native Interface (JNI) method linking and execution.
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.
Obsolete since version 5.0. Use the log profile properties to specify a file name.
N/A.
Obsolete since version 5.0. Use the log profile properties to specify the maximum file size.
N/A.
The log profile used when the server is started in debug mode.
The log profile name.
Log profile properties, com.sybase.jaguar.server.logging.profile.prod
The log profile used when the server is started in production mode.
The log profile name.
Log profile properties, com.sybase.jaguar.server.logging.profile.debug
Specifies whether the thread identifier is included with log messages.
true or false.
When set to true, the thread
identifier is included in each log message record. The default is false.
To record the thread identifier in the log, you must also
configure a log record formatter that includes a placeholder for
the thread identifier (%TI)
in the output pattern. See “Formatter properties” for more information.
Enables the EAServer lightweight container (LWC) for intercomponent EJB invocations or calls to EJBs from servlets and JSPs hosted in the same server. For more information, see “Lightweight container” in the EAServer Performance and Tuning Guide.
true or false.
A value of true allows you
to enable LWC for indivicual components by setting the component
property com.sybase.jaguar.component.lwc. The default of false disables
LWC for all components regardless of the component setting.
com.sybase.jaguar.server.lwc.enableSkeletons, com.sybase.jaguar.component.lwc
Enables logging of debug (tracing) output from the lightweight container.
true or false.
The default of false disables
debug output.
If com.sybase.jaguar.server.lwc is true, enables LWC calls to EJB components from servlets and JSPs hosted in the same server. Such calls are not supported unless this option is set.
true or false.
A value of true allows LWC
calls to components from servlets and JSPs. The default is false.
com.sybase.jaguar.server.lwc, com.sybase.jaguar.component.lwc.enableSkeletons
Configures the return status for Methods As Stored Procedures (MASP) invocations.
Value |
To indicate |
|---|---|
|
A return value of 1 indicates success; a value of 0 indicates failure. |
|
Reverses the meanings of 0 and 1 return values. |
Appendix A, “Executing Methods As Stored Procedures,” in the EAServer Programmer’s Guide
Specifies the maximum number of simultaneous IIOP connections.
A positive integer. The default is 30.
Specifies the maximum number of simultaneous threads.
A positive integer. The default is 50.
The percentage of system memory that can be used before the server begins blocking external requests.
The percentage as a decimal number. If not set, the default is 70.
com.sybase.jaguar.server.memory.lockLimit
Chapter 9, “Using the Performance Monitor,” in the EAServer Performance and Tuning Guide.
The percentage of system memory that can be used before the server begins blocking external requests and begins cancelling in-process requests to bring usage below the specified critical threshold.
The percentage as a decimal number. If not set, the default is 90.
com.sybase.jaguar.server.memory.alarmLimit
Chapter 9, “Using the Performance Monitor,” in the EAServer Performance and Tuning Guide.
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 the name and path to the EAServer performance monitor 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_performance.log
Where server is the server name.
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. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.server.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
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
By default, one thread runs per service. To specify multiple threads for a service, enter the number of threads in brackets after the component name. For example:
YourPackage/YourService[10]
Chapter 33, “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:
desc is an optional comment describing how the parameter is to be set.
value is the value of the parameter.
name is the parameter’s name.
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
Identifies server-level error pages, which allow you to customize the response that the server sends to clients when an error occurs. You can specify HTML files to send in response to HTTP error codes and to Java exceptions thrown in JSPs or servlets.
A comma-delimited list of complex properties. Each property includes a location, and either an error code or an exception field.
(location=/file.jsp,error-code=(code), (location=/exception.htm,exception=java.lang.Exception)
Where:
The locations of file.jsp and exception.htm are relative to the HTML document root.
code is the error code that triggers the error page.
java.lang.Exception is the fully-qualified Java class name of the exception that triggers the error page.
“Welcome and error page specifications” in Chapter 21, “Creating Web Applications,” in the EAServer Programmer’s Guide.
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.
Same as com.sybase.jaguar.servlet.init.timeout.
This property affects servlets installed directly in the server; that is, those specified by the com.sybase.jaguar.server.servlets property. For servlets installed in a Web application, set the Web application property com.sybase.jaguar.webapplication.init-timeout.
You can override the value for individual servlets by setting the servlet property com.sybase.jaguar.servlet.init.timeout.
com.sybase.jaguar.server.servlet.destroy-wait-time, com.sybase.jaguar.servlet.init.timeout, com.sybase.jaguar.webapplication.init-timeout
Specifies the number of internal 4K servlet response buffers.
A positive integer. The default is 128. You can override the default by setting the value to a positive integer. A value of 0 means buffers are never pooled.
Internally, EAServer uses 4K and 8K temporary buffers when assembling servlet responses. These buffers are pooled and reused to avoid the overhead of repeated buffer allocation and garbage collection.
The required buffers are allocated on an as-needed basis, rather than being preallocated as server startup. Once allocated, buffers are pooled and reused until the specified size is reached. If a peak in client activity requires more buffers than the pool size, additional buffers are allocated, then released for garbage collection after use.
The default configuration suffices for most applications. If the buffer pool size is too small, performance.may decline due to allocation of new buffers. Allocation is costly because the Java VM initializes the allocated byte arrays to 0, which is not required by EAServer. Garbage collection is also costly. On the other hand, if the buffer size is too large, buffers allocated during periods of peak activity may be rarely used while consuming memory that would otherwise be available for other tasks.
For request processing, EAServer uses 8k buffers by default, and uses 4k buffers only when a servlet calls ServletResponse.setBufferSize() to request a buffer size other than 8k. If your application never or seldom changes the buffer size, you can set com.sybase.jaguar.server.servlet.max4kbuffers to 0 so that 4k buffers are not pooled.
To access whether the settings are correct, examine the servlet request patterns to see if the number of concurrent requests often exceeds the buffer pool sizes. If so, consider increasing the value.
com.sybase.jaguar.server.servlet.max8kbuffers
Specifies the number of internal 8K servlet response buffers.
Same as for com.sybase.jaguar.server.servlet.max4kbuffers.
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, |
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
Specifies whether EAServer binds the client IP address to each servlet authenticated session and validates subsequent requests to insure the IP address is the same.
true or false.
The default is false.
A value of true can further
protect against replay attacks against secure Web applications.
Chapter 3, “Using Web Application Security,” in the EAServer Security Administration and Programming Guide.
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:
Variable |
Specifies |
|---|---|
desc |
An optional text description of the mapping. |
pattern |
A URL pattern that can contain wildcards. |
servlet |
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 cannot contain path separators.
com.sybase.jaguar.webapplication.welcome-file-list
Specifies the servlets that are installed directly in this server and therefore part of the default Web application EASDefault.
A comma-separated list of servlet names that are defined in the repository.
Servlets can also be installed as part of a user-defined 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.
Obsolete since version 5.0. Use the log profile properties to specify whether the log should be truncated on start-up.
N/A.
Specifies a server wide default for the component Automatic Transaction Retry property (com.sybase.jaguar.component.tx_retry).
true or false.
If not set, the default is false.
com.sybase.jaguar.component.tx_retry
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 EAServer Manager, set this property using the Advanced tab in the Server Properties dialog box.
com.sybase.jaguar.component.tx_timeout
Specifies the name of the transaction log file, which the recovery manager reads to perform transaction recovery.
The file name. The default is <serverName>Recovery.log.
In EAServer Manager, set this property using the Advanced tab in the Server Properties dialog box.
com.sybase.jaguar.server.TxManager.RecoveryEnabled, Chapter 2, “Understanding Transactions and Component Lifecycles,” in the EAServer Programmer’s Guide.
Specifies the minimum size of the transaction log file.
The file size. The default is 1MB.
In EAServer Manager, set this property using the Advanced tab in the Server Properties dialog box.
com.sybase.jaguar.server.TxManager.logfile
Specifies whether the recovery manager is enabled.
true or false.
The default is false, which
disables the Recovery Manager.
In EAServer Manager, set this property using the Advanced tab in the Server Properties dialog box.
com.sybase.jaguar.server.TxManager.logfile
Specifies the transaction coordination model for the server.
Value |
To indicate |
|---|---|
|
JTS/JTA |
|
Microsoft DTC (Windows platforms only) |
On UNIX platforms, specifies a group name for the effective user ID of the server process.
The operating system group name.
com.sybase.jaguar.server.unix.username, “Changing the effective user ID of the server process”
On UNIX platforms, specifies the effective user ID of the server process.
The operating system user name.
com.sybase.jaguar.server.unix.groupname, “Changing the effective user ID of the server process”
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. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.server.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
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 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 |
|---|---|
|
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 |
|
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 |
|
The platform-specific suffix used by shared libraries or DLLs. Do not change the default value. |
|
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. |
