Location for a large 32x32 pixel. Currently, this element is not used by WebLogic Server. The optional display-name element specifies the Web application display name, a short name that can be displayed by GUI tools. The optional description element provides descriptive text about the Web application. The distributable element is not used by WebLogic Server.
The optional context-param element contains the declaration of a Web application's servlet context initialization parameters. The following table describes the reserved context parameters used by the Web application container, which have been deprecated and have replacements in weblogic. Deprecated Parameter. See input-charset. Define how often WebLogic Server checks whether a servlet has been modified, and if so, reloads it. A value of -1 is never reload, 0 is always reload. The default is set to 1 second.
See container-descriptor. When this values has been set, the container appends this path to the Web application classpath. This is not a recommended method and is supported only for backward compatibility. No replacement. Sets the default servlet for the Web application. Instead use the servlet and servlet-mapping elements in web.
See servlet-mapping. For additional examples of servlet mapping, see Servlet Mapping. The following context-param parameter is still valid. This attribute specifies that certifications from clients of the Web application are provided in the special WL-Proxy-Client-Cert header sent by a proxy plug-in or HttpClusterServlet.
This setting is useful if user authentication is performed on a proxy server—setting clientCertProxy causes the proxy server to pass on the certs to the cluster in a special header, WL-Proxy-Client-Cer t. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source the plug-in and uses that information to authenticate the user.
For this reason, if you set clientCertProxy , use a connection filter to ensure that WebLogic Server accepts connections only from the machine on which the plug-in is running.
In addition to setting this attribute for an individual Web application, you can define this attribute:. The filter element defines a filter class and its initialization attributes. For more information on filters, see Configuring Filters. The following table describes the elements you can define within a filter element.
Specifies the location within the Web application for a small and large image used to represent the filter in a GUI tool. Contains a small-icon and large-icon element. Defines the name of the filter, used to reference the filter definition elsewhere in the deployment descriptor. The following table describes the elements you can define within a filter-mapping element.
The name of the filter to which you are mapping a URL pattern or servlet. Describes a pattern used to resolve URLs. If the patterns match, the filter mapped in this element is called. The URL must follow the rules specified in the Servlet 2. The name of a servlet which, if called, causes this filter to execute. Define an application listener using the listener element. For more information, see Configuring an Event Listener Class. The servlet element contains the declarative data of a servlet.
The following table describes the elements you can define within a servlet element. Location within the Web application for a small and large image used to represent the servlet in a GUI tool. Defines the canonical name of the servlet, used to reference the servlet definition elsewhere in the deployment descriptor. The full path to a JSP file within the Web application, relative to the Web application root directory. The optional content of this element must be a positive integer indicating the order in which the servlet should be loaded.
Lower integers are loaded before higher integers. If no value is specified, or if the value specified is not a positive integer, WebLogic Server can load the servlet in any order during application startup.
Specifies the run-as identity to be used for the execution of the Web application. I assume it has something to do with the leading slash.
This user asked the same question but had it work without the initial slash: can-i-set-tomcat-with-a-welcome-file-in-a-subfolder. Another discussion on the same topic:. There are some configurations available in weblogic. I think it's a security feature or something else not sure exactly what. In my case dispatcher servlet was capturing the empty request and showing no mapping found. May be you can create a controller mapping for the same and be done with it. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 7 years, 6 months ago. Default is 40 seconds; valid range is 10 to seconds. Common log format is the default, and follows a standard convention. Extended log format allows you to customize the information that is recorded. As of WebLogic Server 5. When either these two criteria are met, the current access log file will be closed and a new access log file will be started.
To enable logging, set the following property in your weblogic. This defaults to access. You may set the log format to either extended log format or common log format. Both formats are described below.
Note: If you are testing the log format, you should set the logFileFlushSecs property to 1 second, so it is updated frequently. Otherwise, the server may not flush the log file before you shut down the server. The default value is 60 seconds, to improve performance.
For a production system, you should use the default or a higher value. All regular WebLogic Server logs shall continue to be written to the weblogic. Note that the HTTP log is always appended to, even between server down-time, and so will grow indefinitely.
You should maintain it manually. Access log rotation allows you to rotate your HTTP access log when it reaches a certain size or after a specified amount of time has passed. When the access log rotates, a new log file with a new file name is started. The access log's file name includes a numeric portion that is incremented upon each rotation. To set up access log rotation , set the following properties in addition to those properties you set to enable access logs in your weblogic.
If you choose this option, you must also set two additional properties: weblogic. Set to size to rotate your access log when it exceeds a certain size. If you choose this option, you must also set the weblogic. The default value is size.
The default value is If you do not set this property, the access log rotates after the amount of time specified with the weblogic. Enter the date using the java. SimpleDateFormat , MM-dd-yyyy-k:mm:ss. See the javadocs for the java. SimpleDateFormat class for more details. For example: If, when you start WebLogic Server, this date has already passed, the first access log rotation will occur on the day you start WebLogic Server, at the hour, minute, and second specified by weblogic.
When the access log reaches this size, it is rotated. If set to 0 the default value access log files do not rotate based on size. This property is ignored when weblogic. This is an emerging standard, and WebLogic follows the draft specification outlined at www. This URL may be subject to change, but the current definitive reference may be found from the W3C page at www.
The extended log format allows you to specify the type and order of information recorded about each HTTP communication. To enable the extended log format, set the following property in your weblogic. A directive begins on a new line and starts with a sign.
If the log file does not exist, a new log file will be created with default directives. However, if the log file does already exist when the server starts, it must contain legal directives at the head of the file. The first line of your log file must contain a directive stating the version number of the log file format.
You must also include a Fields directive near the beginning of the file: Version: 1. Where each xxxx describes the data fields to be recorded.
Field types are specified as either simple identifiers, or may take a prefix-identifier format, as defined in the W3C specification. Here is an example: Fields: date time cs-method cs-uri This would instruct the server to record the date and time of the transaction, the request method that the client used, and the URI of the request for each HTTP access.
Each field is separated by whitespace, and each record is written to a new line, appended to the log file. Note: The Fields directive must be followed by a new line in the log file, so that the first log message is not appended to the same line. Supported Field identifiers The following identifiers are supported, and do not require a prefix. The following identifiers require prefixes, and cannot be used alone. The supported prefix combinations are explained individually.
IP address related fields: These fields give the IP address and port of either the requesting client, or the responding server. The supported prefixes are: c-ip The IP address of the client. DNS related fields These fields give the domain names of the client or the server.
The supported prefixes are: c-dns The domain name of the requesting client s-dns The domain name of the requested server sc-status Status code of the response, for example indicating a "File not found" status. For more information on events, see Using WebLogic Events. The WebLogic Server is set up to handle session tracking by default. You need not set any of these properties to use session tracking, but configuring how WebLogic manages sessions is a key part of tuning your servlet application for best performance.
This will depend upon factors such as: How many users you expect to hit the servlet How many concurrent users hit the servlet How long each session will last How much data you expect to store for each user HTTP session properties You configure WebLogic's session tracking with properties in the weblogic. The relevant properties are described here in more detail: weblogic. You can disable session tracking by setting this property to false.
Sessions occupy RAM, and on busy sites you can tune your application by adjusting the time-out of sessions appropriately. 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. Defaults to ; minimum is 1, maximum is Integer. Again, this is a parameter you use to tune the server for best performance on high traffic sites.
If unset, the property defaults to 60 seconds; the minimum is every second 1 , and the maximum is once a week , seconds. The optional ejb-ref element defines a reference to an EJB resource. This reference is mapped to the actual location of the EJB at deployment time by defining the mapping in the WebLogic-specific deployment descriptor file, weblogic.
The following table describes the elements you can define within an ejb-ref element. Table A ejb-ref Elements. The name of the EJB used in the Web application. For more information, see ejb-reference-description. A security role whose security context is applied to the referenced EJB. The ejb-local-ref element is used for the declaration of a reference to an enterprise bean's local home. The declaration consists of:.
The EJB reference name used in the code of the Web application that references the enterprise bean. The expected type of the referenced enterprise bean. The following table describes the elements you can define within an ejb-local-ref element. Table A ejb-local-ref Elements. Contains the name of an EJB reference. The name must be unique within the Web application.
The ejb-ref-type element contains the expected type of the referenced enterprise bean. The ejb-ref-type element must be one of the following:.
The ejb-link element is used in the ejb-ref or ejb-local-ref e lements to specify that an EJB reference is linked to an EJB.
The name in the ejb-link element is composed of a path name. This path name specifies the ejb-jar containing the referenced EJB with the ejb-name of the target bean appended and separated from the path name by. This allows multiple EJBs with the same ejb-name to be uniquely identified.
However, the version attributed must be set to 2. The following table describes the elements you can define within an web-app element. Table A web-app Elements. All Servlet deployment descriptors must indicate the 2. The following table describes the elements you can define within an icon element.
The following table describes the elements you can define within a filter element. The following table describes the elements you can define within a servlet element. Default value: 60 Maximum value: Integer.
For more information, see session-descriptor. For more information, see Configuring Welcome Files. The following table describes the elements you can define within a taglib element.
Valid values: Shareable Unshareable. See also user-data-constraint. This is an element within the security-constraint. This is the default value. Can be set to one of the following Java types: java. Boolean java. String java. Integer java. Double java. The declaration consists of: An optional description The EJB reference name used in the code of the Web application that references the enterprise bean.
The expected type of the referenced enterprise bean The expected local home and local interfaces of the referenced enterprise bean Optional ejb-link information, used to specify the referenced enterprise bean The following table describes the elements you can define within an ejb-local-ref element. Used in: ejb-local-ref and ejb-ref elements. Defines code set behavior for non-unicode operations. Sets the default servlet for the Web application. A short name intended to be displayed by GUI tools.
The fully-qualified class name of the filter. The name of a servlet which, if called, causes this filter to execute. Name of the class that responds to a Web application event. A text description of the servlet. The fully-qualified class name of the servlet. Defines the name of this attribute. Defines a String value for this attribute.
Text description of the initialization attribute. Defines the name of the security role or principal that is used in the servlet code. A string describing an extension, for example: txt.
File name to use as a default welcome file, such as index. A valid HTTP error code, for example, Provides information on a tag library that is used by a JSP page within the Web application.
Provides a description of the resource environment reference. Used to control the resource sign on for security.
0コメント