Provides the Servlet 2.3 Web Application that maps to the
"default" servlet context (where ContextPath = "/"). This param has
been deprecated 9.0.0.0 starting from 8.1 release. Set
context-root="" instead in weblogic.xml or application.xml.
Alternatively, use getDefaultWebAppDeployment()

You must select a target on which an MBean will be deployed from
this list of the targets in the current domain on which this item
can be deployed. Targets must be either servers or clusters. The
deployment will only occur once if deployments overlap.

Indicates whether this server allows the inclusion of the
context path in the virtual path to context.getRealPath().
(If checked, you cannot use sub directories with the same name as
contextPath). This is a compatibility switch that will be
deprecated 9.0.0.0 in future releases.

Gets the acceptContextPathInGetRealPath attribute of the
WebServerMBean object

Returns the original context-root for the default Web
application for this Web server. Alternatively, you can use the
context-root attributes in application.xml or weblogic.xml to set a
default Web application. The context-root for a default Web
application is /. If "" (empty string) is specified, the Web server
defaults to /.

A priority that the server uses to determine when it deploys an
item. The priority is relative to other deployable items of the
same type.

For example, the server prioritizes and deploys all EJBs before
it prioritizes and deploys startup classes.

Items with the lowest Deployment Order value are deployed first.
There is no guarantee on the order of deployments with equal
Deployment Order values. There is no guarantee of ordering across
clusters.

The name of the host to which all redirected URLs will be sent.
If specified, WebLogic Server will use this value rather than the
one in the HOST header.

Sets the HTTP frontendHost Provides a method to ensure that the
webapp will always have the correct HOST information, even when the
request is coming through a firewall or a proxy. If this parameter
is configured, the HOST header will be ignored and the information
in this parameter will be used in its place.

The name of the HTTP port to which all redirected URLs will be
sent. If specified, WebLogic Server will use this value rather than
the one in the HOST header.

Sets the frontendHTTPPort Provides a method to ensure that the
webapp will always have the correct PORT information, even when the
request is coming through a firewall or a proxy. If this parameter
is configured, the HOST header will be ignored and the information
in this parameter will be used in its place.

The name of the secure HTTP port to which all redirected URLs
will be sent. If specified, WebLogic Server will use this value
rather than the one in the HOST header.

Sets the frontendHTTPSPort Provides a method to ensure that the
webapp will always have the correct PORT information, even when the
request is coming through a firewall or a proxy. If this parameter
is configured, the HOST header will be ignored and the information
in this parameter will be used in its place.

The maximum size (in kilobytes) of the buffer that stores HTTP
requests. When the buffer reaches this size, the server writes the
data to the HTTP log file. Use the LogFileFlushSecs
property to determine the frequency with which the server checks
the size of the buffer.

The interval at which this server checks the size of the buffer
that stores HTTP requests. When the buffer exceeds the size that is
specified in the Log Buffer Size field, the server writes the data
to the HTTP request log file.

The interval (in seconds) at which the server checks the size of
the buffer that stores HTTP requests. When the buffer exceeds the
size that is specified in the LogFileBufferKBytes
property, the server writes the data in the buffer to the HTTP
request log file.

The format of the HTTP log file. Both formats are defined by the
W3C. With the extended log format, you use server
directives in the log file to customize the information that the
server records.

Specifies the format of the HTTP log file. Both formats are
defined by the W3C. With the extended log format, you use server
directives in the log file to customize the information that the
server records.

The name of the file that stores HTTP requests. If the pathname
is not absolute, the path is assumed to be relative to the root
directory of the machine on which this server is running.

The name of the file that stores the HTTP-request log. If the
pathname is not absolute, the path is assumed to be relative to the
server's root directory.

This value is relevant only if HTTP logging is enabled.

The current logfile is always the one whose name equals value of
the this attribute. If you have enabled log file rotation, when the
current file exceeds the size or time limit, it is renamed.

To include a time and date stamp in the file name when the log
file is rotated, add java.text.SimpleDateFormat
variables to the file name. Surround each variable with percentage
(%) characters.

For example, if the file name is defined to be
access_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file
will be named access_yyyy_mm_dd_hh_mm.log.

When the log file is rotated, the rotated file name contains the
date stamp. For example, if the log file is rotated on 2 April,
2003 at 10:05 AM, the log file that contains the old messages will
be named access_2003_04_02_10_05.log.

If you do not include a time and date stamp, the rotated log
files are numbered in order of creation. For example,
access.log00007.

The start time for a time-based rotation sequence of the log
file, in the format MM-dd-yyyy-k:mm:ss. (This field is
only relevant if you set Rotation Type to date.)

Determines the start time for a time-based rotation sequence. At
the time that this value specifies, the server renames the current
log file. Thereafter, the server renames the log file at an
interval that you specify in
LogRotationPeriodMins.

Use the following format: MM-dd-yyyy-k:mm:ss
where

MM

is the month as expressed in the Gregorian calendar

dd

is the day of the month

yyyy

is the year

k

is the hour in a 24-hour format.

mm

is the minute

ss

is the second

If the time that you specify has already past, then the server
starts its file rotation immediately.

By default, rotation starts 24 hours from the time that you
restart the server instance.

The maximum size (in kilobytes) of the HTTP log file. After the
log file reaches this size, the server renames it as
LogFileName.n. A value of 0 indicates that the log file
can grow indefinitely. (This field is relevant only if you set
Rotation Type to size.)

The size that triggers the server to move log messages to a
separate file. After the log file reaches the specified size, the
next time the server checks the file size, it will rename the
current log file as FileName.n and create a new
one to store subsequent messages.

Optional information that you can include to describe this
configuration.

WebLogic Sever saves this note in the domain's configuration
file (config.xml) as XML PCDATA. All left angle
brackets (<) are converted to the XML entity
&lt;. Carriage returns/line feeds are
preserved.

Note:

If you create or edit a note from the Administration Console,
the Administration Console does not preserve carriage returns/line
feeds.

Get the response code to be used when an application is overloaded. An application can get overloaded when the number of pending requests has reached the max capacity specified in the WorkManager or when the server is low on memory. The low memory condition is determined using OverloadProtectionMBean#getFreeMemoryPercentLowThreshold() .

The amount of time this server waits between receiving chunks of
data in an HTTP POST data before it times out. (This is used to
prevent denial-of-service attacks that attempt to overload the
server with POST data.)

Enables use of the highest compatible HTTP protocol
version-string in the response. E.g. HTTP spec suggests that
HTTP/1.1 version-string should be used in response to a request
using HTTP/1.0. This does not necessarily affect the response
format.

Indicates whether the session ID should include JVM information.
(Checking this box may be necessary when using URL rewriting with
WAP devices that limit the size of the URL to 128 characters, and
may also affect the use of replicated sessions in a cluster.) When
this box is selected, the default size of the URL will be set at 52
characters, and it will not contain any special characters.

If the specified attribute has not been set explicitly, and if
the attribute has a default value, this operation forces the MBean
to persist the default value.

Unless you use this operation, the default value is not saved
and is subject to change if you update to a newer release of
WebLogic Server. Invoking this operation isolates this MBean from
the effects of such changes.

Note:

To insure that you are freezing the default value, invoke the
restoreDefaultValue operation before you invoke
this.

This operation has no effect if you invoke it on an attribute
that does not provide a default value or on an attribute for which
some other value has been set.