Table 52-1 Server attributes
Attribute
|
Description
|
Range of Values and Default
|
AcceptBacklog
|
Allowed backlog of new TCP connection requests for both the plaintext and SSL port. Setting the backlog to 0 may prevent accepting any incoming connection on some of the OS.
|
Admin Console field label: Accept Backlog
Required: no
Default: 50
Minimum: 0
|
AdministrationPort
|
The secure administration port for the server. The setter is used to override the same field in the DomainMBean for this server. If its value is not zero then the same field in the DomainMBean will be used for the server. This port requires SSL to be configured and enabled.
An active administration port only allows connections with administrator credentials. Its existence also prevents any other ports on the server from accepting connections with administrator credentials.
Supports T3S and HTTPS protocols. The managed server will require to use -Dweblogic.management.server=https://admin_server:administration_port to connect to the admin server
|
Admin Console field label: Local Administration Port Override (0: no override)
Required: no
Default: 0
Secure value: (value > 0)
Minimum: 0
Maximum: 65534
|
AutoKillIfFailed
|
Enables/Disables automatic kill of a Failed server by the Node Manager.
|
Admin Console field label: Auto Kill If Failed
Required: no
Default: false
|
AutoRestart
|
Enables/Disables automatic restart of a crashed server by the Node Manager.
|
Admin Console field label: Auto Restart
Required: no
Default: true
|
COMEnabled
|
Whether or not COM support is enabled on the plaintext port. (COM is not supported on the SSL port.)
|
Admin Console field label: Enable COM
Required: no
Default: false
Secure value: false
|
ClasspathServletDisabled
|
The ClasspathServlet will serve any class file in the classpath and is registered by default in every webapp (including management). It does not need to be turned on for many applications though, and represents a security hole if unchecked.
|
Required: no
Default: false
Secure value: true
|
ClientCertProxyEnabled
|
A value of true causes proxy-server plugins to pass identity certifications from clients to all web applications that are deployed on this server instance.
A proxy-server plugin encodes each identify certification in the WL-Proxy-Client-Cert header and passes the header to WebLogic Server instances. A WebLogic Server instance takes the certificate information from the header, trusting that it came from a secure source, and uses that information to authenticate the user.
If you specify true, use a weblogic.security.net.ConnectionFilter to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running. Specifying true without using a connection filter creates a security vulnerability because the WL-Proxy-Client-Cert header can be spoofed.
By default (or if you specify false), the weblogic.xml deployment descriptor for each web application that is deployed on this server determines whether the web application trusts certificates sent from the proxy server plugin. By default (or if the deployment descriptor specifies false), users cannot log in to the web application from a proxy server plugin.
The value that this method sets is overriden if the server is part of a cluster and the cluster's ClusterMBean#setClientCertProxyEnabled(boolean) method specifies true.
|
Admin Console field label: Client Cert Proxy Enabled
Required: no
Default: false
Secure value: false
|
Cluster
|
The cluster to which this server belongs. If set, the server will listen for cluster multicast events.
|
Admin Console field label: Cluster
Required: no
|
ClusterWeight
|
Defines a value used specify the proportion of the load the server will bear relative to other servers in a cluster.
If all servers have the default weight (100) or the same weight, each bears an equal proportion of the load. If one server has weight 50 and all other servers have weight 100, the 50-weight server will bear half as much load as any other server.
|
Admin Console field label: Cluster Weight
Required: no
Default: 100
Minimum: 1
Maximum: 100
|
CompleteCOMMessageTimeout
|
Specify the maximum number of seconds spent waiting for a complete COM message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: COM Message Timeout
Required: no
Units: seconds
Default: 60
Minimum: 0
Maximum: 480
|
CompleteHTTPMessageTimeout
|
Specify the maximum number of seconds spent waiting for a complete HTTP message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: HTTP Message Timeout
Required: no
Units: seconds
Default: 60
Minimum: 0
Maximum: 480
|
CompleteIIOPMessageTimeout
|
Specify the maximum number of seconds spent waiting for a complete IIOP message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending.
|
Admin Console field label: IIOP Message Timeout
Required: no
Units: seconds
Default: 60
Minimum: 0
Maximum: 480
|
CompleteT3MessageTimeout
|
Specify the maximum number of seconds spent waiting for a complete T3 message to be received. This attribute helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: T3 Message Timeout
Required: no
Units: seconds
Default: 60
Minimum: 0
Maximum: 480
|
DefaultIIOPPassword
|
The password for the default IIOP user.
|
Admin Console field label: Default IIOPPassword
Required: no
Encrypted: yes
|
DefaultIIOPUser
|
The default IIOP user.
|
Admin Console field label: Default IIOPUser
Required: no
|
DefaultInternalServletsDisabled
|
This disables all default servlets in the servlet engine. This includes: weblogic.servlet.ClasspathServlet weblogic.servlet.utils.iiop.GetIORServlet weblogic.rjvm.http.TunnelSendServlet weblogic.rjvm.http.TunnelRecvServlet weblogic.rjvm.http.TunnelLoginServlet weblogic.rjvm.http.TunnelCloseServlet If set to true, this property overrides the ClasspathServletDisabled property.
|
Required: no
Default: false
Secure value: true
|
DefaultProtocol
|
Returns the protocol to be used for connections when none is specified.
|
Admin Console field label: Default Protocol
Required: no
Default: t3
|
DefaultSecureProtocol
|
Returns the protocol to be used for secure connections when none is specified.
|
Admin Console field label: Default Secure Protocol
Required: no
Default: t3s
|
DefaultTGIOPPassword
|
The password for the default TGIOP user.
|
Required: no
Encrypted: yes
Default: guest
Secure value: null
|
DefaultTGIOPUser
|
The default TGIOP user.
|
Required: no
Default: guest
Secure value: null
|
DomainLogFilter
|
Determines which messages this server sends to the domain log. If you specify none, the server sends all messages of severity ERROR and higher. This list contains all Domain Log Filters that have been defined for the domain. A server can user only one Domain Log Filter.
This property is relevant only if Log To Domain File is enabled.
|
Admin Console field label: Domain Log Filter
Required: no
Secure value: "none"
|
EnabledForDomainLog
|
Determines whether this server sends messages to the domain log (in addition to keeping its own log).
|
Admin Console field label: Log to Domain Logfile
Required: no
Default: true
Secure value: true
|
ExpectedToRun
|
If this server expected to run if the domain is started.
|
Admin Console field label: Expected To Run
Required: no
Default: true
|
ExternalDNSName
|
The external DNS name for the current server, which will be sent with http session cookies and also with the dynamic server lists to http proxies. This is required for configurations in which a firewall is performing Network Address Translation.
|
Admin Console field label: External DNSName
Required: no
|
ExtraEjbcOptions
|
Returns the extra options passed to ejbc during dynamic ejb compilation.
|
Admin Console field label: Extra ejbc Options
Required: no
|
ExtraRmicOptions
|
Returns the extra options passed to rmic during server-side generation.
|
Admin Console field label: Extra rmic Options
Required: no
|
HealthCheckIntervalSeconds
|
Periodicity (in seconds) of the server's health checks. This controls the frequency of the server's self-health monitoring and the Node Manager's health queries.
|
Admin Console field label: Health Check Interval
Required: no
Units: seconds
Default: 180
Minimum: 1
Maximum: 231-1
|
HealthCheckTimeoutSeconds
|
Time (in seconds) the Node Manager should wait before timing out its health query to the server.
|
Admin Console field label: Health Check Timeout
Required: no
Units: seconds
Default: 60
Minimum: 1
Maximum: 231-1
|
HttpTraceSupportEnabled
|
Attackers may abuse HTTP TRACE functionality to gain access to information in HTTP headers such as cookies and authentication data. In the presence of other cross-domain vulnerabilities in web browsers, sensitive header information could be read from any domains that support the HTTP TRACE method. This attribute is for disabling HTTP TRACE support. It is duplicated both in ClusterMBean and ServerMBean so the attribute HttpTraceSupportEnabled can be used cluster-wide. ClusterMBean overrides ServerMBean
|
Required: no
Default: false
|
HttpdEnabled
|
Whether or not HTTP support is enabled on the plaintext or SSL port.
|
Admin Console field label: Enable HTTPD
Required: no
Default: true
|
IIOPEnabled
|
Whether or not IIOP support is enabled for both the SSL and non-SSL ports.
|
Admin Console field label: Enable IIOP
Required: no
Default: true
|
IdleIIOPConnectionTimeout
|
Specify the maximum number of seconds an IIOP connection is allowed to be idle before it is closed by the server. This attribute helps guard against server deadlock through too many open connections.
|
Required: no
Units: seconds
Default: 60
Minimum: 0
|
InstrumentStackTraceEnabled
|
Determines whether exception messages include the server-side stack trace.
|
Admin Console field label: Instrument Stack Traces
Required: no
Default: true
Secure value: false
|
InterfaceAddress
|
Defines the interface address used to specify the NIC that handles cluster multicast traffic.
|
Admin Console field label: Interface Address
Required: no
|
JDBCLogFileName
|
The name of the JDBC log file. If the pathname is not absolute, the path is assumed to be relative to the root directory of the machine on which the server is running. If the log has no path element and is atomic, ie. jdbc.log to avoid name space conflicts the file will be placed relative to the root directory in ./SERVER_NAME/
|
Admin Console field label: JDBC Logfile Name
Required: no
Default: jdbc.log
|
JDBCLoggingEnabled
|
Determines whether this server maintains a JDBC log file.
|
Admin Console field label: Enable JDBC Logging
Required: no
Default: false
Secure value: true
|
JMSDefaultConnectionFactoriesEnabled
|
Enables JMS default connection factories.
|
Admin Console field label: Enable Default JMS Connection Factories
Required: no
Default: true
|
JNDITransportableObjectFactoryList
|
List of factories that create transportable objects.
|
Required: no
|
JavaCompiler
|
The Java Compiler for all applications that need to compile Java code.
|
Admin Console field label: Java Compiler
Required: no
Default: javac
Secure value: "javac"
|
JavaCompilerPostClassPath
|
Returns the options to append to the Java compiler classpath for when we need to compile Java code.
|
Admin Console field label: Append to classpath
Required: no
Secure value: null
|
JavaCompilerPreClassPath
|
Returns the options to prepend to the Java compiler classpath for when we need to compile Java code.
|
Admin Console field label: Prepend to classpath
Required: no
Secure value: null
|
ListenAddress
|
The IP address or DNS name this server uses to listen for incoming connections. Servers can be reached through the following URL: protocol://listen-address:listen-port
Any network access point (NAP) that you configure for this server can override this listen address.
By default, a server's listen address is undefined, which enables clients to reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that running on the same computer as the server.
If you want to limit the valid addresses for a server instance, specify one of the following:
- Note:
- To resolve a DNS name to an IP address, Weblogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request will fail.
|
Admin Console field label: Listen Address
Required: no
|
ListenDelaySecs
|
Deprecated. Perpetuated for compatibility with 6.1 only.
|
Required: no
Default: 0
|
ListenPort
|
The plain-text (non-SSL) listen port for this server. If this is disabled the SSL port must be enabled. Additional ports can be configured using network channels (see NetworkChannelMBean). The cluster (multicast) port is configured seperately (see getCluster).
|
Admin Console field label: Listen Port
Required: no
Default: 7001
Minimum: 1
Maximum: 65534
|
ListenPortEnabled
|
Get if the plain-text (non-SSL) port is enabled for the server. If this is set to false, the SSL listen port must be configured and enabled.
|
Admin Console field label: Listen Port Enabled
Required: no
Default: true
|
LogRemoteExceptionsEnabled
|
Determines whether the server message log includes exceptions that are raised in remote systems.
|
Admin Console field label: Log Remote Exceptions
Required: no
Default: false
Secure value: true
|
LoginTimeout
|
Not used, use getLoginTimeoutMillis instead.
|
Admin Console field label: Login Timeout
Required: no
Units: milliseconds
Default: 1000
Minimum: 0
|
LoginTimeoutMillis
|
The login timeout for the server's plain-text (non-SSL) port, in milliseconds. This is the maximum amount of time allowed for a new connection to establish. A value of 0 indicates there is no maximum. The value must be equal to or greater than 0.
|
Admin Console field label: Login Timeout
Required: no
Units: milliseconds
Default: 5000
Secure value: 5000
Minimum: 0
Maximum: 100000
|
LowMemoryGCThreshold
|
The threshold level (a percentage value) at which the server logs a low memory warning once the granularity reporting level has been met.
|
Admin Console field label: Low Memory GCThreshold
Required: no
Default: 5
Secure value: 5
Minimum: 0
Maximum: 99
|
LowMemoryGranularityLevel
|
Returns the granularity level used in reporting LowMemory information.
|
Admin Console field label: Low Memory Granularity Level
Required: no
Default: 5
Secure value: 5
Minimum: 1
Maximum: 100
|
LowMemorySampleSize
|
Returns the total sample size used for LowMemoryTimeInterval. By default '10' samples are taken at each LowMemoryTimeInterval.
|
Admin Console field label: Low Memory Sample Size
Required: no
Default: 10
Minimum: 1
Maximum: 231-1
|
LowMemoryTimeInterval
|
Returns the time interval. So every configured 'time', one sample will be taken up to the LowMemorySampleSize and then repeated.
|
Admin Console field label: Low Memory Time Interval
Required: no
Units: seconds
Default: 3600
Minimum: 300
Maximum: 231-1
|
MSIFileReplicationEnabled
|
Indicates whether the replication of configuration files is enabled for a Managed Server. With file replication enabled, the Administration Server copies its configuration file and SerializedSystemIni.dat into the Managed Server's root directory every 5 minutes. This option does not replicate a boot identity file.
You must enable Managed Server Independence to replicate configuration files.
Do not enable file replication for a server that shares an installation or root directory with another server. Unpredictable errors can occur for both servers.
Depending on your backup schemes and the frequency with which you update your domain's configuration, this option might not be worth the performance cost of copying potentially large files across a network.
|
Admin Console field label: MSI File Replication Enabled
Required: no
Default: false
Secure value: false
|
Machine
|
The machine on which this server is meant to run. If the server is already running, this will migrate the server to a different machine. If the machine is the same as the machine is the server is already running on, this is a no-op.
Migration consists of taking down the machine using the stop method on the Server (#stop), and restarting the server on the new machine. If anything fails during migration, the appropriate exception will be thrown.
Setting the machine to null means that the server should not be started. If it is already running, it is shutdown.
|
Admin Console field label: Machine
Required: no
|
ManagedServerIndependenceEnabled
|
Indicates whether Managed Server Independence is enabled for this server. With Managed Server Independence enabled, you can start a Managed Server even if the Administration Server is unavailable. In such a case, the Managed Server retrieves its configuration by reading a configuration file and other files directly.
|
Admin Console field label: Managed Server Independence Enabled
Required: no
Default: true
Secure value: true
|
MaxCOMMessageSize
|
Specify maximum size of an entire COM message. This attribute attempts to prevent a denial of service attack whereby a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. If this attribute is not set, the value of maxMessageSize is used. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: COM Max Message Size
Required: no
Units: bytes
Default: 10000000
Minimum: 4096
Maximum: 2000000000
|
MaxHTTPMessageSize
|
Specify the maximum HTTP message size allowable in a message header. This attribute attempts to prevent a denial of service attack whereby a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. If this attribute is not set, the value of maxMessageSize is used. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: HTTP Max Message Size
Required: no
Units: bytes
Default: 10000000
Minimum: 4096
Maximum: 2000000000
|
MaxIIOPMessageSize
|
Specify the maximum size for an entire IIOP message. This attribute attempts to prevent a denial of service attack whereby a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. If this attribute is not set, the value of maxMessageSize is used.
|
Admin Console field label: IIOP Max Message Size
Required: no
Units: bytes
Default: 10000000
Minimum: 4096
Maximum: 2000000000
|
MaxOpenSockCount
|
Returns the maximum number of open sockets allowed in server at a given point of time. When max threshold is reached, server stops accepting any more new requests until no of sockets drops below threshold.
|
Admin Console field label: Maximum Open Sockets
Required: no
Default: -1
Minimum: -1
Maximum: 231-1
|
MaxT3MessageSize
|
Specify the maximum size for an entire T3 message. This attribute attempts to prevent a denial of service attack whereby a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. If this attribute is not set, the value of maxMessageSize is used. This setting only applies to connections that are initiated using one of the default ports (ServerMBean setListenPort and setAdministrationPort or SSLMBean setListenPort). Connections on additional ports are tuned via the NetworkChannelMBean.
|
Admin Console field label: T3 Max Message Size
Required: no
Units: bytes
Default: 10000000
Minimum: 4096
Maximum: 2000000000
|
Name
|
Set the name of the MBean.
|
Admin Console field label: Name
Required: no
|
NativeIOEnabled
|
Whether or not native I/O is enabled for the server.
|
Admin Console field label: Enable Native IO
Required: no
Default: true
|
NetworkAccessPoints
|
Network access points, or "NAPs", optionally fine-tune the network channels targeted at this server. Network channels and NAPs together to define additional ports and addresses that this server listens on. Additionally, if two servers both support the same channel for a given protocol, then new connections between them will use that channel. If a channel is targeted at a server, but no NAP is configured, the server will still honor the channel using network information configured for the server.
|
Required: no
|
Notes
|
Optional information that you can include to describe this configuration.
|
Admin Console field label: Notes
Required: no
|
PreferredSecondaryGroup
|
Defines secondary clustered instances considered for hosting replicas of the primary HTTP session states created on the server.
|
Admin Console field label: Preferred Secondary Group
Required: no
|
ReplicationGroup
|
Defines preferred clustered instances considered for hosting replicas of the primary HTTP session states created on the server.
|
Admin Console field label: Replication Group
Required: no
|
RestartDelaySeconds
|
Time (in seconds) the Node Manager should wait before restarting the server. This value will be used in cases such as the OS not allowing listen ports to be reused immedietly.
|
Admin Console field label: Restart Delay Seconds
Required: no
Units: seconds
Default: 0
Minimum: 0
Maximum: 231-1
|
RestartIntervalSeconds
|
Interval (in seconds) during which a server can be restarted RestartMax times.
|
Admin Console field label: Restart Interval
Required: no
Units: seconds
Default: 3600
Minimum: 300
Maximum: 231-1
|
RestartMax
|
Number of times a server can be restarted within an interval of RestartIntervalSeconds seconds.
|
Admin Console field label: Max Restarts within Interval
Required: no
Default: 2
Minimum: 0
Maximum: 231-1
|
ReverseDNSAllowed
|
Returns whether or not the kernel is allowed to perform reverse DNS lookups.
|
Admin Console field label: Reverse DNS Allowed
Required: no
Default: false
|
ServerLifeCycleTimeoutVal
|
Number of seconds a ServerLifeCycle operation waits before timing out. It is currently enabled for only shutdown and force shutdown operations. If the operation does not complete within the configured timeout seconds, then the server will shutdown automatically if the state of the server at that time was SHUTTING_DOWN or if the operation was force shutdown. Otherwise, a ServerLifecycleException will be thrown with a message desribing the timeout condition.
The default value is 120 seconds. A value of 0 means that the server will wait indefinitely for life cycle operation to complete.
|
Admin Console field label: Timeout for Server Lifecycle Operations
Required: no
Units: seconds
Default: 120
Secure value: 120
Minimum: 0
|
ServerVersion
|
Returns the release identifier for the server. Since this is a configured attribute it is only as accurate as the configuration. The form of the version is major.minor.servicepack.rollingpatch. Not all parts of the version are required. i.e. "7" is acceptable.
|
Required: no
Default: unknown
|
StagingMode
|
During application preparation, the application's files are copied from the source on the admin server to the managed server's staging area. If this attribute is nostage or external_stage, the copy will not occur. This is useful when the staging area is a shared directory, already containing the application files, or if this is a single server domain. The administrator must ensure that the managed server's staging directory is set appropriately. Deployment errors will result if the application is not available during the preparation or activation of the application. This attribute can be overridden with the ApplicationMBean StagingMode attribute.
|
Admin Console field label: Staging Mode
Required: no
|
StartupMode
|
Startup Mode for the server
|
Admin Console field label: Startup Mode
Required: no
Default: RUNNING
|
StdoutDebugEnabled
|
Determines whether the server sends messages of the DEBUG severity to standard out in addition to the log file. You must enable Log to Standard Out for this property to be relevant.
|
Admin Console field label: Debug to Stdout
Required: no
Default: false
Secure value: false
|
StdoutEnabled
|
Enables the server to send messages to standard out in addition to the log file. Use StdoutDebugEnabled and StdoutSeverityLevel to determine the type of messages that the server sends to standard out.
|
Admin Console field label: Log to Stdout
Required: no
Default: true
|
StdoutFormat
|
The output format to use when logging to the console.
|
Required: no
Default: standard
|
StdoutLogStack
|
Whether to dump stack traces to the console when included in logged message.
|
Required: no
Default: true
|
StdoutSeverityLevel
|
The minimum severity of a message that the server sends to standard out. You must enable Log to Standard Out for this value to be relevant.
The ascending order of severities is as follows:
|
Admin Console field label: Stdout severity threshold
Required: no
Default: 16
Secure value: weblogic.logging.Severities.WARNING
|
StreamPoolSize
|
Returns the size of the pool of MsgAbbrevOutputStreams maintained to optimize serialization and deserialization.
|
Required: no
Default: 5
|
StuckThreadMaxTime
|
Returns the time that is used to determine when a thread might be stuck. If a thread has been working for this time, it might be stuck in some bad state.
|
Admin Console field label: Stuck Thread Max Time
Required: no
Units: seconds
Default: 600
Minimum: 0
Maximum: 231-1
|
StuckThreadTimerInterval
|
Returns the time interval that is used to scan the state of the running threads. This along with StuckThreadMaxTime is used to determine when a thread might be stuck.
|
Admin Console field label: Stuck Thread Timer Interval
Required: no
Units: seconds
Default: 600
Minimum: 0
Maximum: 231-1
|
TGIOPEnabled
|
Whether or not TGIOP support is enabled.
|
Required: no
Default: false
Secure value: false
|
ThreadPoolPercentSocketReaders
|
Returns the percentage (1-99) of execute threads from the default queue hat may be used as socket readers.
|
Admin Console field label: Socket Readers
Required: no
Default: 33
Minimum: 1
Maximum: 99
|
TransactionLogFilePrefix
|
The path prefix for the server's JTA transaction log files. If the pathname is not absolute, the path is assumed to be relative to the root directory of the machine on which the server is running.
|
Admin Console field label: Transaction Log File Prefix
Required: no
Default: ./
|
TransactionLogFileWritePolicy
|
The policy used for writing log records to disk. The "Cache-Flush" policy flushes operating system and on-disk caches after each write. The "Cache-Flush" policy is the default policy. The "Direct-Write" policy tells the operating system to write directly to disk with each write. "Direct-Write" performs better than "Cache-Flush", and is available on Windows, HP-UX and Solaris. If "Direct-Write" is not supported on the host platform, the policy becomes "Cache-Flush" and a log message is printed.
WARNING: On Windows, unlike Solaris and HP, the "Direct-Write" policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe, as a power failure can cause loss of on-disk cache data. For transactionally safe writes using "Direct-Write" on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery backed cache.
The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> "Enable write caching on the disk" check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache.
|
Admin Console field label: Transaction Log File Write Policy
Default: Cache-Flush
|
TunnelingClientPingSecs
|
Interval (in seconds) at which to ping an http-tunneled client to see if its still alive (in seconds).
|
Admin Console field label: Tunneling Client Ping
Required: no
Units: seconds
Default: 45
Minimum: 1
|
TunnelingClientTimeoutSecs
|
Duration (in seconds) after which a missing http-tunneled client is considered dead (in seconds).
|
Admin Console field label: Tunneling Client Timeout
Required: no
Units: seconds
Default: 40
Minimum: 1
|
TunnelingEnabled
|
Enables tunneling via HTTP.
|
Admin Console field label: Enable Tunneling
Required: no
Default: false
|
UploadDirectoryName
|
Identifies the directory path on the AdminServer where all uploaded applications are placed. If an absolute directory name is not specified, the path is relative to rootdirectory/ The default staging directory is "stage", relative to the server root.. On the ManagedServer this returns null, and is not configurable
|
Admin Console field label: Upload Directory Name
Required: no
Secure value: An absolute directory that is outside the root directory of any WebLogic Server instance or application, and that resides on a physical disk that is separate from the WebLogic Server host's system disk.
|
VerboseEJBDeploymentEnabled
|
Whether or not verbose deployment of EJB's is enabled.
|
Required: no
Default: false
|
WeblogicPluginEnabled
|
WLS HttpRequest.getRemoteAddr() used to rely on X-Forwarded-For for its returned value. This is a security hole due to HTTP header can be easily mocked and we end up with returning wrong value. This is improved by introducing a proprietary header WL-Proxy-Client-IP from our plugins and this header will only be used if WLS is configured to use our plugins. This is duplicated both in ClusterMBean and ServerMBean so the attribute WeblogicPluginEnabled can be used cluster-wide. ClusterMBean overrides ServerMBean
|
Admin Console field label: WebLogic Plug-In Enabled
Required: no
Default: false
|
XMLEntityCache
|
|
Required: no
|
XMLRegistry
|
|
Admin Console field label: XMLRegistry
Required: no
|