-Dproperty=value)
or in the application properties file named on the command line. Any changes to
configuration properties from previous releases will be noted in the
release documentation.
By default, the RedDwarf Server consists of a single node, as described in Configuring a Single Node System. Alternatively, multiple nodes can be configured to work together, as described in Configuring a Multi-Node System.
The type of node being configured is specified by the following property:
singleNode
coreServerNode
appNode
For example configuration files of the different node types, see the single-node.properties, core-server.properties, and app-node.properties files.
The core server node must be running before starting the application nodes.
Properties in this section specify which node is the core server node, which are the application nodes, and how the application nodes discover the core node. Note that some Required Properties will also need to be specified.
The node.type property must be set to
coreServerNode to start the core server.
The node.type property must be set to
appNode to start an application node.
AppListener for
the application, specified as a fully qualified class name. See the
class javadoc for requirements of
valid class implementations.
com.sun.sgs.transport.Transport
and supports
Delivery.RELIABLE.
See the
SimpleSgsProtocolAcceptor class for more details.
DataService.
See the
DataServiceImpl class for a complete
description and further configuration options.
DataService that control the implementation of the
underlying
DataStore.
See the
DataStoreImpl class
for a complete description and further configuration options.
Setting these properties has no effect on application nodes.
com.sun.sgs.impl.service.data.store.db.je.JeEnvironment
selects a database implementation based on
Berkeley DB Java Edition. Other values should specify the fully
qualified name of a non-abstract class that implements
com.sun.sgs.service.store.db.DbEnvironment
, and that has a
public constructor with four parameters: a java.util.String,
which specifies the directory containing database files, a
java.util.Properties, which specifies configuration options,
a
com.sun.sgs.kernel.ComponentRegistry which provides a
registry of available system components, and
a
com.sun.sgs.service.TransactionProxy for access to
the current transaction and its owner. Note that persistent data created using Berkeley DB is incompatible with data created using Berkeley DB Java edition
DataService that control the behavior of the Berkeley
DB database, when it has been specified as the implementation of the
underlying database using the
com.sun.sgs.impl.service.data.store.db.environment.class
property. Setting these properties has no effect on application nodes.
20000. Using a cache that is too small
can introduce a significant reduction in performance.
WatchdogService.
See the
WatchdogServiceImpl class
for a complete description and further configuration options.
Setting these properties has no effect on application nodes.
100 milliseconds.
Using a renew interval that is too small may cause some application nodes to
be considered failed by the WatchdogService when they are very
busy. Using an interval that is too large will increase the amount of time the
system takes to respond to failed nodes.
ClientSessionService.
See the
ClientSessionServiceImpl class
for a complete description and further configuration options.
false, a new
user with the same identity as an existing user is not permitted
to log in. If the property is true, the user's existing
session is disconnected, and the new login is allowed to proceed.
200 milliseconds.
ProtocolAcceptor used by the
ClientSessionService.
See the
SimpleSgsProtocolAcceptor class
for a complete description and further configuration options.
SimpleSgsProtocol version used by clients
connecting to the server. The default value for the protocol
version is an earlier version of the protocol, 0x04.
The default protocol supports older clients that have not yet
been upgraded to support the newer version of the protocol which
supports client session relocation (introduced in protocol version
0x05). The server will reject a connection from a
client that uses a protocol version other than the value
specified by the property.
IdentityAuthenticators to use for the application. The
order defines the precedence when authenticating an identity. The default
authenticator simply accepts any name-password pair.
min - minimal profiling data is collected.
medium - more data is collected, but is still appropriate
for monitoring a production system.
max - all available profiling data is collected. This
level may only be appropriate for debugging systems in
development.
TaskManager.
Services to start
after all of the core Services have started. Each
Service should be specified as a fully qualified class name.
Services will be started in the order that they are specified
in this list.
Managers to use. Each
Manager should be specified as a fully qualified class name.
This list must contain the same number of classes as the
com.sun.sgs.services list described above. Each Manager in the
list is paired with the corresponding Service in the
Services list at the same index. To specify a
Service with no Manager, leave the appropriate
element in the list empty.
Service/Manager pair in the
lists described above should be started on. This list must contain the same
number of items as the Service and Managers lists.
Valid values for a node type are:
SINGLECOREAPPSINGLE_OR_CORESINGLE_OR_APPCORE_OR_APPALLIn order to enable monitoring on a remote machine, the following properties must be used. By default, only local monitoring is enabled.
com.sun.management.jmxremote.authenticate=false com.sun.management.jmxremote.ssl=falseFor more information, please refer to the Java SE Monitoring and Management Guide, especially Chapter 2, Monitoring and Management Using JMX Technology.
com.sun.sgs.impl.kernel.Kernel
com.sun.sgs.impl.kernel.LockingAccessCoordinator
com.sun.sgs.impl.kernel.LoggerPropertiesInit
com.sun.sgs.impl.kernel.TaskSchedulerImpl
com.sun.sgs.impl.kernel.TrackingAccessCoordinator
com.sun.sgs.impl.kernel.TaskSchedulerImpl
com.sun.sgs.impl.kernel.logging.TransactionAwareLogManager
com.sun.sgs.impl.kernel.schedule.ImmediateRetryPolicy
com.sun.sgs.impl.kernel.schedule.NowOrLaterRetryPolicy
com.sun.sgs.impl.profile.ProfileCollectorImpl
com.sun.sgs.impl.profile.listener
(package)
ProfileCollectorImpl
. Each listener also may have its own set of configuration
properties.
com.sun.sgs.impl.protocol.simple.SimpleSgsProtocolAcceptor
com.sun.sgs.impl.service.channel.ChannelServiceImpl
com.sun.sgs.impl.service.data.DataServiceImpl
com.sun.sgs.impl.service.data.store.DataStoreImpl
com.sun.sgs.impl.service.data.store.db.bdb.BdbEnvironment
com.sun.sgs.impl.service.data.store.db.je.JeEnvironment
com.sun.sgs.impl.service.data.store.net.DataStoreServerImpl
com.sun.sgs.impl.service.nodemap.NodeMappingServerImpl
com.sun.sgs.impl.service.nodemap.NodeMappingServiceImpl
com.sun.sgs.impl.service.nodemap.RoundRobinPolicy
com.sun.sgs.impl.service.session.ClientSessionServiceImpl
com.sun.sgs.impl.service.task.FixedTimeContinuePolicy
com.sun.sgs.impl.service.task.TaskServiceImpl
com.sun.sgs.impl.service.transaction.TransactionCoordinatorImpl
com.sun.sgs.impl.service.watchdog.WatchdogServerImpl
com.sun.sgs.impl.service.watchdog.WatchdogServiceImpl
com.sun.sgs.impl.transport.tcp.TcpTransport