Defines access log settings for each http-access-log subelement of each virtual-server.
none
The following table describes attributes for the access-log element.
Table 1–1 access-log Attributes
Attribute |
Default |
Description |
---|---|---|
%client.dns;%auth-user-name;%system.date;%request;%status;%response.length; |
(optional) Specifies the format of the access log. |
|
time |
(optional) Specifies the condition that triggers log rotation. The only legal value is time, which rotates log files at the rotation-interval-in-minutes interval. |
|
1440 |
(optional) Specifies the time interval between log rotations if rotation-policy is set to time. |
|
%YYYY;%MM;%DD;-%hh;h%mm;m%ss;s |
(optional) Specifies the format of the timestamp appended to the access log name when log rotation occurs. |
|
true |
(optional) If true, enables log rotation. |
Defines an administered object for an inbound resource adapter.
The following table describes subelements for the admin-object-resource element.
Table 1–2 admin-object-resource Subelements
Element |
Required |
Description |
---|---|---|
zero or one |
Contains a text description of this element. |
|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the admin-object-resource element.
Table 1–3 admin-object-resource Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the JNDI name for the resource. |
|
none |
Specifies the fully qualified type of the resource. |
|
none |
Specifies the name of the inbound resource adapter, as specified in the name attribute of a connector-module element. |
|
user |
(optional) Defines the type of the resource. Allowed values are:
|
|
enabled |
true |
(optional) Determines whether this resource is enabled at runtime. |
Properties of the admin-object-resource element are the names of setter methods of the adminobject-class specified in the adminobject element of the ra.xml file. Some of the property names can be specified in the adminobject element itself. For example, in jmsra, the resource adapter used to communicate with the Sun Java system Message Queue software, jmsra, Name and Description are valid properties.
For a complete list of the available properties (called administered object attributes in Sun Java System Message Queue), see the Message Queue administration material.
Determines whether the server instance is a regular instance, a domain administration server, or a combination.
The following table describes subelements for the admin-service element.
Table 1–4 admin-service Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Configures a JSR 160 compliant remote JMX connector. |
|
zero or one |
Defines a domain administration server configuration. |
|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the admin-service element.
Table 1–5 admin-service Attributes
Attribute |
Default |
Description |
---|---|---|
server |
Specifies whether the server instance is a regular instance (server), a domain administration server (das), or a combination (das-and-server). |
|
none |
Specifies the name of the internal jmx-connector. |
Configures the alert service, which allows you to register for and receive system status alerts.
The following table describes subelements for the alert-service element.
Table 1–6 alert-service Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Configures a subscription to system status alerts. |
|
zero or more |
Specifies a property or a variable. |
Configures a subscription to system status alerts.
The following table describes subelements for the alert-subscription element.
Table 1–7 alert-subscription Subelements
Element |
Required |
Description |
---|---|---|
only one |
Configures the listener class that listens for alerts from notification emitters. |
|
zero or one |
Configures the filter class that filters alerts from notification emitters. |
The following table describes attributes for the alert-subscription element.
Table 1–8 alert-subscription Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the name of this alert subscription. |
Specifies a deployed application client container (ACC) module.
The following table describes subelements for the appclient-module element.
Table 1–9 appclient-module Subelements
Element |
Required |
Description |
---|---|---|
zero or one |
Contains a text description of this element. |
The following table describes attributes for the appclient-module element.
Table 1–10 appclient-module Attributes
Attribute |
Default |
Description |
---|---|---|
none |
The name of the ACC module. |
|
none |
The location of the ACC module in the Application Server file system. |
|
false |
(optional) Specifies whether the application has been deployed to a directory. |
References an application or module deployed to the server instance.
none
The following table describes attributes for the application-ref element.
Table 1–11 application-ref Attributes
Attribute |
Default |
Description |
---|---|---|
enabled |
true |
(optional) Determines whether the application or module is enabled. |
all virtual servers |
(optional) In a comma-separated list, references id attributes of the virtual-server elements to which the web-module or the web modules within this j2ee-application are deployed. |
|
false |
(optional) If true, all load-balancers consider this application available to them. |
|
30 |
(optional) Specifies the time it takes this application to reach a quiescent state after having been disabled. |
|
none |
References the name attribute of a lifecycle-module, j2ee-application, ejb-module, web-module, connector-module, or appclient-module element. |
Contains deployed J2EE applications, J2EE modules, and Lifecycle modules.
The following table describes subelements for the applications element.
Table 1–12 applications Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a deployed lifecycle module. |
|
zero or more |
Specifies a deployed J2EE application. |
|
zero or more |
Specifies a deployed EJB module. |
|
zero or more |
Specifies a deployed web module. |
|
zero or more |
Specifies a deployed connector module. |
|
zero or more |
Specifies a deployed application client container (ACC) module. |
Subelements of an applications element can occur in any order.
Specifies an optional plug-in module that implements audit capabilities.
The following table describes subelements for the audit-module element.
Table 1–13 audit-module Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the audit-module element.
Table 1–14 audit-module Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the name of this audit module. |
|
none |
Specifies the Java class that implements this audit module. |
Defines a realm for authentication.
Authentication realms require provider-specific properties, which vary depending on what a particular implementation needs.
For more information about how to define realms, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Developer’s Guide.
Here is an example of the default file realm:
<auth-realm name="file" classname="com.iplanet.ias.security.auth.realm.file.FileRealm"> <property name="file" value="domain-dir/config/keyfile"/> <property name="jaas-context" value="fileRealm"/> </auth-realm>
Which properties an auth-realm element uses depends on the value of the auth-realm element’s name attribute. The file realm uses file and jaas-context properties. Other realms use different properties.
The following table describes subelements for the auth-realm element.
Table 1–15 auth-realm Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the auth-realm element.
Table 1–16 auth-realm Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the name of this realm. |
|
none |
Specifies the Java class that implements this realm. |
The standard realms provided with Application Server have required and optional properties. A custom realm might have different properties.
The following table describes properties for the auth-realm element.
Table 1–17 auth-realm Properties
Configures the availability service. Enables high-availability features, such as HTTP session and stateful session bean state persistence to the Sun Java System high-availability database (HADB).
Availability can be enabled or disabled at the following levels:
The server instance (attribute of availability-service). Default is true (enabled).
The EJB or web container (attribute of ejb-container-availability or web-container-availability). Default is true (enabled).
The application (attribute of j2ee-application). Default is false (disabled).
The stand-alone EJB or web module (attribute of ejb-module or web-module). Default is false (disabled).
The stateful session bean. Default is false (disabled). See the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Developer’s Guide.
For availability to be enabled at a given level, it must be enabled at all higher levels, as well. For example, to enable availability at the application level, you must also enable it at the server instance and container levels.
The following table describes subelements for the availability-service element.
Table 1–18 availability-service Subelements
Element |
Required |
Description |
---|---|---|
only one |
Enables availability in the web container. |
|
only one |
Enables availability in the EJB container. |
|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the availability-service element.
Table 1–19 availability-service Attributes
Attribute |
Default |
Description |
---|---|---|
true |
(optional) If set to true, high-availability features apply to all applications deployed to the server instance that do not have availability disabled. All instances in a cluster should have the same availability value to ensure consistent behavior. |
|
jdbc/hastore |
(optional) Specifies the jndi-name of the jdbc-resource used for connections to the HADB for session persistence. For more information about setting up a connection pool and JDBC resource for the HADB, see the description of the configure-ha-cluster command in the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Reference Manual. |