Coherence Server: Configuration: General
Configuration Options Related Tasks Related Topics
Use this page to configure Coherence servers when using ActiveCache. Coherence servers are stand-alone cache servers, dedicated JVM instances responsible for maintaining and managing cached data.
Note: This page provides backward compatibility for existing Coherence ActiveCache implementations. For new implementations, Coherence is integrated within WebLogic Server as a container subsystem; therefore, Coherence is typically set up in tiers within a WebLogic Server domain, either as a single, managed server instance or using WebLogic Server clusters.
These settings are used for starting managed Coherence cache servers only. The specified settings will not be used by an Administration Server instance that is started by Node Manager.
Name Description Name
An alphanumeric name for this server instance.
This field will not accept spaces.
The name must be unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.
The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
In order to define a unicode server name, the underlying operating system must support unicode characters.
After you have created a server, you cannot change its name. Instead, clone the server and provide a new name for the clone.
The WebLogic Server host computer (machine) on which this server is meant to run.
If you want to use a Node Manager to start this server, you must assign the server to a machine and you must configure the machine for the Node Manager.
You cannot change this value if a server instance is already running.
The system-level Coherence cluster resource associated with this server.
Unicast Listen Address
The IP address for the cluster unicast listener.
This attribute may be used to override the value of the referenced Coherence cluster.
Unicast Listen Port
The port for the cluster unicast listener.
Unicast Port Auto Adjust Enabled
Specifies whether the unicast port will be automatically incremented if the port cannot be bound because it is already in use.
Auto Restart Enabled
Specifies whether the Node Manager can automatically restart this server if it crashes or otherwise goes down unexpectedly.
The number of seconds during which this server can be restarted, up to the number of times specified in RestartMax.
Restart Maximum Tries
The number of times that the Node Manager can restart this server within the interval specified in RestartIntervalSeconds.
The number of seconds the Node Manager should wait before restarting this server.
After killing a server process, the system might need several seconds to release the TCP port(s) the server was using. If Node Manager attempts to restart the Managed Server while its ports are still active, the startup attempt fails.
If AutoMigration is enabled and RestartDelaySeconds is 0, the RestartDelaySeconds is automatically set to the lease time. This prevents the server from failing to restart after migration when the previous lease is still valid.
Node Manager Connect Timeout
Returns the timeout value to be used by NodeManagerRuntime when creating a socket connection to the agent. Default set high as SSH agent may require a high connection establishment time.
- Create Coherence servers
- Configure startup arguments for Coherence servers
- Start Coherence servers from the Administration Console
- Configure Node Manager