Optional

Sets the time, in seconds, that WebLogic Server waits before timing out an asynchronous job. The default value is 120 seconds.

Setting the timeout to -1 indicates that the asynchronous job never times out.

Optional

Sets the time, in seconds, that WebLogic Server waits between doing checks for timed-out jobs. The default value is 30 seconds.

Required

Specifies the name of an EJB reference used in your Web application.

Required

Specifies a JNDI name for the reference.

Optional

Set to true to enable FastSwap deployment in your application.

Optional

FastSwap checks for changes in application classes when an incoming HTTP request is received. Subsequent HTTP requests arriving within the refresh-interval seconds will not trigger a check for changes. The first HTTP request arriving after the refresh-interval seconds have passed, will cause FastSwap to perform a class-change check again.

Optional

FastSwap class redefinitions are performed asynchronously by redefinition tasks. They can be controlled and inspected using JMX interfaces.

Specifies the number of redefinition tasks that will be retained by the FastSwap system. If the number of tasks exceeds this limit, older tasks are automatically removed.

Sets the interval, in seconds, at which WebLogic Server checks to see if JSP files have changed and need recompiling. Dependencies are also checked and recursively reloaded if changed.

• The value -1 means never check the pages. This is the default value in a production environment.

• The value 0 means always check the pages.

• The value 1 means check the pages every second. This is the default value in a development environment.

In a production environment where changes to a JSP are rare, consider changing the value of pageCheckSeconds to 60 or greater, according to your tuning requirements.

Applies to exploded WARs only.

Checks for updated JSP files, in other words, whether the timestamp on the file is later (more recent) than the one in the build. Only newer files can replace older ones.

When set to false, just checks whether the timestamp has changed. If so, the file is replaced.

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://
xmlns.oracle.com/weblogic/weblogic-web-app">
  <jsp-descriptor>
    <strict-stale-check>false
    </strict-stale-check>
  </jsp-descriptor>
</weblogic-web-app>

When set to true, WebLogic Server automatically precompiles all JSPs when the Web application is deployed or re-deployed or when starting WebLogic Server.

When set to true, WebLogic Server continues precompiling all JSPs even if some of those JSPs fail during compilation. Only takes effect when precompile is set to true.

Saves the Java files that are generated as an intermediary step in the JSP compilation process. Unless this parameter is set to true, the intermediate Java files are deleted after they are compiled.

When set to true, WebLogic Server enables the debugging feature of the JSP compiler.

The default value is false.

For production mode, the default value is false, but for development mode, the default value is true.

When set to true, debugging information is printed out to the browser, the command prompt, and WebLogic Server log file.

The name of a directory where WebLogic Server saves the generated Java and compiled class files for a JSP.

Note: If weblogic.xml defines a working-dir, WebLogic Server does not delete this directory when the Web application is undeployed.

When set to false, this parameter ensures that expressions with "null" results are printed as " ".

When set to true, backward compatibility is enabled.

See Backward Compatibility Flags.

Specifies the default character set used in the JSP page. Use standard Java character set names (see http://docs.oracle.com/javase/8/docs/technotes/guides/intl/).

If not set, this attribute defaults to the encoding for your platform.

A JSP page directive (included in the JSP code) overrides this setting. For example:

<%@ page contentType="text/html; charset=custom-encoding"%>

Specifies the package prefix into which all JSP pages are compiled.

When true, upon the first request for a JSP the newly created JspStub is mapped to the exact request. If exactMapping is set to false, the Web application container generates non-exact URL mapping for JSPs. exactMapping allows path info for JSP pages.

The default file name in which WebLogic Server saves the generated Java and compiled class files for a JSP.

Allows run-time expression values in the name attribute of the jsp:param tag. It is set to false by default.

When set to true, the JSP compiler optimizes Java expressions to improve run-time performance.

When set to true, compresses the HTML in the JSP template blocks to improve run-time performance.

If the JSP's HTML template block contains the <pre> HTML tag, do not enable this feature.

Required

Provides the library name for the library module reference. The default value is null.

Optional

Provides the specification version for the library module reference. The default value is 0. (This is a float.)

Optional

Provides the implementation version for the library module reference. The default value is null.

Optional

The default value is false.

Required

Specifies the name of the log file. The full address of the filename is required.

Optional

Indicates whether or not the log writer is set for either the ManagedConnectionFactory or ManagedConnection. If this element is set to true, output generated from either the ManagedConnectionFactory or ManagedConnection will be sent to the file specified by the log-filename element.

Failure to specify this value will result in WebLogic Server using its defined default value.

Value Range: true | false

Default Value: false

Optional

Sets the file rotation type.

Values are bySize, byTIme, none

• bySize—When the log file reaches the size that you specify in file-size-limit, the server renames the file as FileName.n.

• byTIme—At each time interval that you specify in file-time-span, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in log-filename.

• none—Messages accumulate in a single file. You must erase the contents of the file when the size is unwieldy.

Default Value: bySize

Optional

Specifies whether the number of files that this server instance creates to store old messages should be limited. (Requires that you specify a rotation-type of bySize). After the server reaches this limit, it overwrites the oldest file. If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.

If you enable number-of-files-limited by setting it to true, the server refers to your rotationType variable to determine how to rotate the log file. Rotate means that you override your existing file instead of creating a new file. If you specify false for number-of-files-limited, the server creates numerous log files rather than overriding the same one.

Value Range: true | false

Default Value: false

Optional

The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable number-of-files-limited.)

Default Value: 7

Optional

The size that triggers the server to move log messages to a separate file. (Requires that you specify a rotation-type of bySize.) After the log file reaches the specified minimum 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.

Default Value: 500

Optional

Specifies whether a server rotates its log file during its startup cycle.

Value Range: true | false

Default Value: true

Optional

Specifies the directory path where the rotated log files will be stored.

Optional

The start time for a time-based rotation sequence of the log file, in the format k:mm, where k is 1-24. (Requires that you specify a rotation-type of byTime.) At the specified time, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in file-time-span.

If the specified time has already past, then the server starts its file rotation immediately.

By default, the rotation cycle begins immediately.

Optional

The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a rotation-type of byTime.)

Default Value: 24

Required

Specifies the name of a resource reference.

Required

Specifies a JNDI name for the resource.

Required

Specifies the name of a resource environment reference.

Required

Specifies a JNDI name for the resource environment reference.

Required

Specifies the name of a security role.

Required

Specifies the name of a principal.

Required

Specifies the name of a security role.

Required if externally-defined is not defined.

Specifies the name of a principal that is defined in the security realm. You can use multiple principal-name elements to map principals to a role. For more information on security realms, see Administering Security for Oracle WebLogic Server.

Required if principal-name is not defined.

Specifies that a particular security role is defined globally in a security realm; WebLogic Server uses this security role as the principal name, rather than looking it up in a global realm. When the security role and its principal-name mapping are defined elsewhere, this is used as an indicative placeholder.

The call-property element has the following sub-elements:

name

value

The port-info element has the following sub-elements:

port-name

stub-property

call-property

Required

Specifies the servlet name as defined in the servlet element of the web.xml deployment descriptor file.

Optional

Contains the name of a principal against the run-as-role-name defined in the web.xml deployment descriptor.

Optional

Equivalent to run-as-principal-name for the init method for servlets. The identity specified here should be a valid user name in the system. If init-as-principal-name is not specified, the container uses the run-as-principal-name element.

Optional

Equivalent to run-as-principal-name for the destroy method for servlets. The identity specified here should be a valid user name in the system. If destroy-as-principal-name is not specified, the container uses the run-as-principal-name element.

Optional

This is a deprecated element. Used to assign a given servlet to a configured Work Manager by identifying the Work Manager name. This setting overrides the Web application-level dispatch policy defined by wl-dispatch-policy.

3600

Sets the time, in seconds, that WebLogic Server waits before timing out a session. The default value is 3600 seconds.

On busy sites, you can tune your application by adjusting the timeout of sessions. While you want to give a browser client every opportunity to finish a session, you do not want to tie up the server needlessly if the user has left the site or otherwise abandoned the session.

This element can be overridden by the session-timeout element (defined in minutes) in web.xml.

Sets the time, in seconds, that WebLogic Server waits between doing house-cleaning checks for timed-out and invalid sessions, and deleting the old sessions and freeing up memory. Use this element to tune WebLogic Server for best performance on high traffic sites.

The default value is 60 seconds.

Sets whether the container must invalidate the current session if the currently logged-in user switches to a different user name (which is valid in the security realm) and attempts to log in again.

If the value of this parameter is set to true, the current session is invalidated if the user attempts to log in again using a different user name.

false

Enables Web applications to share HTTP sessions when the value is set to true at the application level.

This element is ignored if turned on at the Web application level.

false

Enables the debugging feature for HTTP sessions.

The default value is false.

52

Sets the size of the session ID.

The minimum value is 32 bytes and the maximum value is Integer.MAX_VALUE.

Note: If a value lower than 32 bytes is set, WebLogic Server automatically raises the value to 32 and displays the following message:

If you are writing a WAP application, you must use URL rewriting because the WAP protocol does not support cookies. Also, some WAP devices have a 128-character limit on URL length (including attributes), which limits the amount of data that can be transmitted using URL rewriting. To allow more space for attributes, use this attribute to limit the size of the session ID that is randomly generated by WebLogic Server.

You can also limit the length to a fixed 52 characters, and disallow special characters, by setting the WAPEnabled attribute. See URL Rewriting and Wireless Access Protocol (WAP).

true

Enables session tracking between HTTP requests.

1028

Sets the cache size for JDBC and file-persistent sessions.

-1

Sets the maximum limit for memory/replicated sessions.

Without the ability to configure bound in-memory servlet session use, as new sessions are continually created, the server eventually grows out of memory. To protect against this, WebLogic Server provides a configurable bound on the number of sessions created. When this number is exceeded, the weblogic.servlet.SessionCreationException occurs for each attempt to create a new session. This feature applies to both replicated and non-replicated in-memory sessions.

To configure bound in-memory servlet session use, you set the limitation in the max-in-memory-sessions element.

The default is -1 (unlimited); any negative value works as the same as -1.

4096

Sets the maximum size, in bytes, of the POST data that the container saves/buffers during FORM authentication.

The default value is 4096 bytes.

40

Defines the timeout, in seconds, for the session that saved/buffered POST data. For FORM authentication, POST data is saved in a session while the user is redirected to the login form.

The default value is 40 seconds.

If the value of the save-post-timeout-secs element is less than the value of the timeout-secs element, then session invalidation may occur during user operations. In this scenario, increase the value of save-post-timeout-secs to match the timeout-secs value or to an acceptable value, according to your needs.

20

Sets the invalidation trigger interval, in seconds, for saving POST data in a session.

The default value is 20 seconds.

Use of session cookies is enabled by default and is recommended, but you can disable them by setting this property to false. You might turn this option off to test.

Defines the session tracking cookie name. Defaults to JSESSIONID if not set. You may set this to a more specific name for your application.

null

Defines the session tracking cookie path.

If not set, this attribute defaults to / (slash), where the browser sends cookies to all URLs served by WebLogic Server. You may set the path to a narrower mapping, to limit the request URLs to which the browser sends cookies.

null

Specifies the domain for which the cookie is valid. For example, setting cookie-domain to.example.com returns cookies to any server in the *.example.com domain.

The domain name must have at least two components. Setting a name to *.com or *.net is not valid.

If not set, this attribute defaults to the server that issued the cookie.

See Cookie.setDomain() in the Servlet specification.

null

Specifies the comment that identifies the session tracking cookie in the cookie file.

Tells the browser to only send the cookie back over an HTTPS connection. This ensures that the cookie ID is secure and should only be used on Web sites that use HTTPS. Session Cookies over HTTP no longer work if this feature is enabled.

You should disable the url-rewriting-enabled element if you intend to use this feature.

Sets the life span of the session cookie, in seconds, after which it expires on the client.

This value can be set as any integer; the default value is -1 (unlimited).

For more information about cookies, see Using Sessions and Session Persistence.

Sets the persistent store method to one of the following options:

• memory—Disables persistent session storage.

• replicated—Same as memory, but session data is replicated across the clustered servers.

• replicated_if_clustered—If the Web application is deployed on a clustered server, the in-effect persistent-store-type will be replicated. Otherwise, memory is the default.

• async-replicated—Enables asynchronous session replication in an application or Web application. See Asynchronous HTTP Session Replication in Tuning Performance of Oracle WebLogic Server.

• async-replicated-if-clustered—Enables asynchronous session replication in an application or Web application when deployed to a cluster environment. If deployed to a single server environment, then the session persistence/replication defaults to in-memory. This allows testing on a single server without deployment errors.

• file—Uses file-based persistence (See also session-descriptor).

• async-jdbc—Enables asynchronous JDBC persistence for HTTP sessions in an application or Web application. See Configuring Session Persistence.

• jdbc—Uses a database to store persistent sessions. (see also session-descriptor).

• cookie—All session data is stored in a cookie in the user's browser.

Sets the name of the cookie used for cookie-based persistence. The WLCOOKIE cookie carries the session state, which should not be shared between Web applications.

See Using Cookie-Based Session Persistence.

Specifies the storage directory used for file-based persistence

Ensure that you have enough disk space to store the number of valid sessions multiplied by the size of each session. You can find the size of a session by looking at the files created in the persistent-store-dir. Note that the size of each session can vary as the size of serialized session data changes.

Each server instance has a default persistent file store that requires no configuration. Therefore, if no directory is specified, a default store is automatically created in the <server-name>\data\store\default directory. However, the default store is not shareable among clustered servers.

You can make file-persistent sessions clusterable by creating a custom persistent store in a directory that is shared among different servers. However, this requires you to create this directory manually.

Specifies the name of a JDBC connection pool to be used for persistence storage.

Specifies the data source JNDI name of a JDBC connection to be used for jdbc- and async-jdbc-based persistence (see persistent-store-type above).

For async-jdbc-based persistence, you must specify the persistent-data-source-jndi-name parameter to configure persistence storage.

Specifies the database table name used to store JDBC-based persistent sessions. This applies only when persistent-store-type is set to jdbc.

The persistent-store-table element is used when you choose a database table name other than the default.

Serves as an alternative name for the wl_max_inactive_interval column name. This jdbc-column-name-max-inactive-interval element applies only to JDBC-based persistence. It is required for certain databases that do not support long column names.

true

Enables URL rewriting, which encodes the session ID into the URL and provides session tracking if cookies are disabled in the browser.

true

When set to false, WebLogic Server adds the following header with the following response:

"Cache-control: no-cache=set-cookie"

This indicates that the proxy caches do not cache the cookies.

The latest servlet specification requires containers to encode the session ID in path parameters. Certain Web servers do not work well with path parameters. In such cases, the encode-session-id-in-query-params element should be set to true. (The default is false.)

Used in ServletSessionRuntimeMBean. The getMainAttribute() of the ServletSessionRuntimeMBean returns the session attribute value using this string as a key.

Example: user-name

This element is useful for tagging session runtime information for different sessions.

Configures the monitoring ID for a given HTTP session.

HTTP sessions are identified with a monitoring ID. By default, the monitoring ID for a given HTTP session is a random string (not the same as a session ID for security reasons). This monitoring ID can be configured by setting the monitoring-attribute-name element in session-descriptor of the weblogic.xml deployment descriptor and then setting a session attribute the defined monitoring-attribute-name. The toString() of the session attribute value will then be used as a monitoring ID.

This element is useful for tagging session runtime information for different sessions. For example, you can set it to "username", if you have a "username" attribute that is unique.

true

Specifies whether HttpOnly cookies are enabled. When this element is set to true, all session cookies would be unavailable to the browser scripts. The default value is true. Therefore, HttpOnly cookies are enabled by default.

20

Defines the length of the secure cookie, _WL_AUTHCOOKIE_JSESSIONID. The default cookie length is 20, and the minimum cookie length is 8.

Required

Specifies a physical location on the disk.

Required

Contains the URL pattern of the mapping. Must follow the rules specified in Section 11.2 of the Servlet API Specification.

Required

Specifies the name of the Work Manager.

Optional

You can choose between the following four elements:

• response-time-request-class—Defines the response time request class for the application. Response time is defined with attribute goal-ms in milliseconds. The increment is ((goal - T) Cr)/R, where T is the average thread use time, R the arrival rate, and Cr a coefficient to prioritize response time goals over fair shares.

• fair-share-request-class—Defines the fair share request class. Fair share is defined with attribute percentage of default share. Therefore, the default is 100. The increment is Cf/(P R T), where P is the percentage, R the arrival rate, T the average thread use time, and Cf a coefficient for fair shares to prioritize them lower than response time goals.

• context-request-class—Defines the context class. Context is defined with multiple cases mapping contextual information, like current user or its role, cookie, or work area fields to named service classes.

• request-class-name—Defines the request class name.

Optional

You can choose between the following two elements:

• min-threads-constraint—Used to guarantee a number of threads the server allocates to requests of the constrained work set to avoid deadlocks. The default is zero. A min-threads value of one is useful, for example, for a replication update request, which is called synchronously from a peer.

• min-threads-constraint-name—Defines a name for the min-threads-constraint element.

Optional

You can choose between the following two elements:

• max-threads-constraint—Limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined.

• max-threads-constraint-name—Defines a name for the max-threads-constraint element.

Optional

You can choose between the following two elements:

• capacity—Constraints can be defined and applied to sets of entry points, called constrained work sets. The server starts rejecting requests only when the capacity is reached. The default is zero. Note that the capacity includes all requests, queued or executing, from the constrained work set. This constraint is primarily intended for subsystems like JMS, which do their own flow control. This constraint is independent of the global queue threshold.

• capacity-name—Defines a name for the capacity element.