General tab

Table 3-1 describes the general properties that you can configure for individual servers.

Table 3-1: Server general properties

Property

Description

Statistics URL

Select to display a spreadsheet that contains server statistics.

Host Name

The name of the machine on which the server is running. The repository property name is host.name.

Process ID

A unique ID for the server instance, in the form of a dotted-decimal TCP/IP address, a colon, and a port number; for example, 10.11.12.13:2000.

The processID is used to construct session IDs, so it must be unique across the network of connected servers that share the same databases.The ID need not contain an actual TCP/IP address; the default value is derived from either the iiopListeners or the httpListeners property, but you can redefine it.

Java Class Path

Classes in this path are loaded before classes in the server class path at server start-up.

NoteSybase recommends that you define this path carefully; incorrect use may interfere with server operation.

Alternately, you can add extension JAR files, which are loaded after classes in the server class path, to the EAServer lib/ext directory.

If classes are required by user-spawned threads, add them either to the Java class path or to the lib/ext directory.

For loading classes used by EJB modules and Web applications, you can configure named class loaders at the server, application, or package level—see Chapter 10, “Configuring Java Class Loaders.”

The javaClassPath property has no default value.

Java Start-up Options

java command line options used to start the server. If you are using a Sun JVM, use the -server option to activate the HotSpot Server VM.

The javaStartupOptions property has no default value.

License Configuration

Select the server license configuration from the list. Initially, featureManagerConfig is set to “default.” See “Configuring the server license”.

Default Code Set

Select the character encoding to use; the default value of defaultCodeSet is utf8 (8-bit Unicode Transformation Format).

Allow Runtime Compile

Select to allow runtime compilation of Java source code. If the code has changed since the last time it was compiled, the server recompiles the code for IIOP interface stubs, SQL persistence classes, and JavaServer Pages (JSPs). The default value of allowRuntimeCompile is true.

IIOP interface stubs and SQL persistence classes are precompiled automatically when you deploy EJB modules.

If your server is running under a Java Runtime Environment (JRE) without a Java compiler, unselect this property.

If you change the configuration of a data source that is used by EJB entity beans, and this property is unselected, you must redeploy the EJB-JAR files and restart the server.

If you are using JSPs and this property is unselected, your JSPs must be precompiled. If you define all JSPs that need to be precompiled with their own “servlet” elements in your web.xml files, you can precompile them using the deploy tool. See deploy.

The deploy tool requires the Java compiler, so if the target machine does not have a Java compiler, you can run deploy on one machine and transfer the deployed configuration to the target machine. To transfer deployed configurations between machines, you can use an export configuration—see Chapter 7, “Exporting Server Modules.”

Disable Statistics

Select to disable all server statistics.

The default value of disableStatistics is false. Selecting this option improves performance, but provides much less information about server actions.

You may want to compare the difference in performance to determine whether the lack of statistics is worth the performance gain.

Disable 60-Second Statistics

Select to disable 60-second summaries for all available statistics; disableStatistics must be true.

In addition to the statistical information described in Chapter 11, “Runtime Monitoring,” 60-second summary information includes:

  • For count statistics, the change in the last 60 seconds.

  • For range statistics, the minimum and maximum values for the last 60 seconds.

  • For time statistics, the changes in total time, and minimum and maximum time values for the last 60 seconds.

The default value of disable60SecondStatistics is false.

60-second summary information is updated once per minute, for the previous full minute.

Disable 60-Minute Statistics

Select to disable 60-minute averages for all available statistics; disableStatistics must be true.

In addition to the statistical information described in Chapter 11, “Runtime Monitoring,” 60-minute summary information includes:

  • For count statistics, the change in the last 60 minutes.

  • For range statistics, the minimum and maximum values for the last 60 minutes.

  • For time statistics, the changes in total time, and minimum and maximum time values for the last 60 minutes.

The default value of disable60MinuteStatistics is false.

60-minute summary information is updated once per hour, for the previous full hour.

Enable Reverse Host Lookup

If enabled, the server makes network calls to request the host names of client machines, to use for statistics. Some customers do not support these queries on their network. If disabled, performance improves because EAServer does not attempt to get client host names.

The default value of reverseHostLookupEnabled is true.

Enable XML Entity Cache

Select to cache XML entities used by the deploy tool. XML entities (such as external DTDs) are cached in the XmlEntityCache.properties file, in the Repository/Component/com/sybase/djc/xml directory. You can delete this file to clear the cache.

The default value of enableXmlEntityCache is true.

Enable XML Grammar Cache

Select to cache XML grammars used by the Xerces parser.

The default value of enableXmlGrammarCache is true.

Work Offline

Select to disable JMS store and forward operations at server start-up time.

You can activate JMS store and forward operations dynamically (once the server is running) in Java code by setting the Java system property jms.workOffline to true.

The ability to disable JMS store and forward operations is most useful on mobile devices, where running applications may need to control whether background JMS operations use the network.

By default, the workOffline property is false.