server.xml elements beginning with P
The following elements are discussed below:
pkcs11
The pkcs11 element configures the PKCS #11 subsystem. This element may appear zero or one time within the server element. For more information, see server.
Subelements
The pkcs11 element can contain the following subelements:
Table 3-35 List of pkcs11 Subelements
| Element | Occurrences | Description |
|---|---|---|
| enabled | 0 or 1 | Determines whether the server initializes PKCS#11 tokens, prompting for Personal Identification Numbers (PINs) as necessary. The default value is true if SSL is enabled and false if SSL is not enabled. |
| crl-path | 0 or 1 | The directory that contains dynamically updated CRL files. The value is the name of the directory. If a relative path is used, it is relative to the server's config directory. |
| token | 0 or more | Configures a PKCS#11 token. For more details, see token. |
See Also
pkcs11 bypass
The pkcs11 bypass element instructs the NSS to bypass the PKCS#11 layer during SSL/TLS processing, thereby improving performance.
During startup, the server automatically verifies each token, holding a server key, to assess if they support PKCS#11 bypass. If the tokens support bypass in the current configuration the PKCS#11 layer will be bypassed, else the bypass will be disabled. Thus, the server automatically takes advantage of the performance benefits of pkcs11 bypass whenever possible.
In certain unique circumstances, you can disable PKCS#11 bypass manually by using the server.xml element <allow-bypass>.
<pkcs11>
<enabled>1</enabled>
<allow-bypass>0</allow-bypass>
</pkcs11>
See Also
profiler
The profiler element configures a JVM profiler. This element may appear zero or one time within the jvm element. For more information, see jvm.
Subelements
The profiler element can contain the following subelements:
Table 3-36 List of profiler Subelements
| Element | Occurrences | Description |
|---|---|---|
| enabled | 0 or 1 | Determines whether the profiler is enabled at runtime. The default value is true. |
| class-path | 0 or 1 | The classpath for the profiler. |
| native-library-path | 0 or 1 | The native library path for the profiler. The value is the operating system library path. |
| jvm-options | 0 or more | The JVM options for the profiler. For more details, see http://java.sun.com/docs/hotspot/VMOptions.html. |
property
The property element defines a name-value pair. The effect of defining a property name-value pair depends on the context in which the property element appears as described below:
- Properties defined at the auth-db level configure ACL authentication databases. For more information, see auth-db.
- Properties defined at the soap-auth-provider level configure SOAP message-level authentication providers. For more information, see soap-auth-provider.
- Properties defined at the auth-realm level configure Servlet container authentication realms. For more information, see auth-realm.
- Properties defined at the jdbc-resource level configure JDBC drivers. For more information, see jdbc-resource.
- Properties defined at the custom-resource and external-jndi-resource levels configure JNDI resources. For more information, see custom-resource and external-jndi-resource.
- Properties defined at the mail-resource level configure standard Java mail properties. For more information, see mail-resource.
Subelements
The property element can contain the following subelements:
Table 3-37 List of property Subelements
| Element | Occurrences | Description |
|---|---|---|
| name | 1 | The name of the property. |
| value | 1 | The value of the property. |
| encoded | 0 or 1 | Determines whether the property value has been encoded using the uunencode algorithm. The default value is false. |
| description | 0 or 1 | The description of the property. |
See Also
property-db
The property-db element configures the WebDAV property database. This element may appear zero or one time within the dav element and zero or one time within the dav-collection element. For more information, see dav, and dav-collection.
Subelements
The property-db element can contain the following subelements:
Table 3-38 List of property-db Subelements
| Element | Occurrences | Description |
|---|---|---|
| max-size | 0 or 1 | The maximum size (in bytes) of WebDAV property database files. The value can be from 0 to 2147483647, or -1 for no limit. |
| update-interval | 0 or 1 | The interval (in seconds) at which the WebDAV property databases are synchronized to disk. The value can be from 0.001 to 3600, or 0 to disable caching of WebDAV properties. |
Sign up or Log in to add a comment or watch this page.