Previous Contents Index Next
Sun ONE Web Server 6.1 Administrator's Guide

> ## The Java Tab

> The Java tab allows you to configure Java features in Sun ONE Web Server. The Java tab contains the following pages:

> - The Enable/Disable Servlets/JSP Page
> - The JVM General Page
> - The JVM Path Settings Page
> - The JVM Options Page
> - The JVM Profiler Page
> - The JDBC Connection Pools Page
> - The JDBC Resources Page
> - The JNDI Custom Resources Page
> - The JNDI External Resources Page
> - The Java Security Page
> - The Edit Realms Page

> ##

> The Enable/Disable Servlets/JSP Page

> The Enable/Disable Servlets/JSP page allows you to enable and disable Java features such as web applications, servlets, and JavaServer Pages (JSP).

> For information about how to configure web applications in Sun ONE Web Server 6.1, see Deploying Web Applications.

> The following elements are displayed:

> Enable Java Globally. Enables or disables support for Java features for the entire server instance.

> Virtual Server Class. Lists the virtual server classes. Clicking on a virtual server name opens a new browser window displaying the Manage Virtual Servers page for the virtual server.

> Enable/Disable Java. Enables or disables support for Java features for a particular virtual server class.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JVM General Page

> The Configure JVM Attributes page allows you to set parameters for the Java virtual machine (JVM).

> For more information, see Configuring JVM Settings.

> The following elements are displayed:

> Java Home. Specifies the path to the directory where the Java Developer's Kit (JDK) is installed. Sun ONE Web Server supports the Sun JDK 1.4.1.

> Debug Enabled. If true, the server starts up in debug mode ready for attachment with a JPDA-based (Java Platform Debugger Architecture-based) debugger.

> Debug Options. By default, this is set to: -Xdebug-Xrunjdwp:transport=dt_socket,server=y,suspend=n

> A list of debug options is available at: http://java.sun.com/products/jpda/doc/conninv.html#Invocation

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JVM Options Page

> The JVM Options page allows you to set JVM command line options.

> For more information, see Configuring JVM Options.

> The following elements are displayed:

> Operation. Allows you to add, edit or delete a JVM option.

> JVM Option. Specifies the JVM command line option.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JVM Profiler Page

> The JVM Profiler Page allows you to configures a profiler for use with the server.

> For more information, see Configuring the JVM Profiler.

> The following elements are displayed:

> Profiler. Allows you to enable, disable or delete the profiler. By default, the profiler is enabled.

> Classpath. Specifies the classpath for the profiler.

> Native Lib Path. Specifies the native library path for the profiler.

> Operation. Allows you to add, edit, or delete a JVM option.

> JVM Option. Specifies the JVM command line option.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JVM Path Settings Page

> The JVM Path Settings page allows you to configure the path to the Java Virtual Machine (JVM) in the Administration interface.

> For more information, see Configuring Path Settings.

> The following elements are displayed:

> Classpath Suffix. Specifies a suffix for the system's classpath. You might want to do this to override system classes, such as the XML Parser classes.

> Ignore Env Classpath. Specifies whether to ignore the environment classpath.

> If you do not ignore the classpath, the CLASSPATH environment variable is read and appended to the Sun ONE Web Server classpath. The CLASSPATH environment variable is added after the classpathsuffix, at the very end. For a development environment, the classpath should be used.

> For a production environment, this classpath should be ignored to prevent environment variable side effects.

> Native Lib Path Prefix. Specifies the native library path prefix.

> Native Lib Path Suffix. Specifies the native library path suffix.

> Note | The native library path is the automatically constructed concatenation of the Web Server installation relative path for its native shared libraries, the standard JRE native library path, the shell environment setting (LD_LIBRARY_PATH on UNIX), and any path specified in the profiler element. Since this is synthesized, it does not appear explicitly in the server configuration.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JDBC Connection Pools Page

> The JDBC Connection Pools Page allows you to create or configure a JDBC connection pool. A JDBC connection pool is a named group of JDBC connections to a database. Each connection pool uses a JDBC driver to establish a connection to a physical database at server start-up.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> New. Allows you to create a new connection pool. Click to proceed to the New JDBC Connection Pool page.

> Delete. Specifies the classpath for the profiler.

> Name. Specifies the native library path for the profiler.

> Data Source Class Name. Allows you to add, edit or delete a JVM option.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Add New JDBC Connection Pool Page

> The Add New JDBC Connection Pool Page allows you to add a new JDBC connection pool.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> General

> - Pool Name. Enter a name for the new connection pool.
> - DataSource Classname. The vendor-specific classname that implements the data source. If you selected Other from the Database Vendor list in the New JDBC Connection Pool page, you must enter the vendor-specific classname of the data source you plan to use.

> Properties

> Specify standard and proprietary JDBC connection pool properties; many of these properties are optional. By default the names of all of the standard properties are provided. You will need to consult your database vendor's documentation to determine which standard and vendor specific properties are required.

> Pool Settings

> - Steady Pool Size. Specifies the minimum number of connections that must be maintained in the pool. When a connection is given to a requesting thread, it is removed from the pool, reducing the current pool size. The steady pool size also refers to the number of entries that will be added to the pool on server startup.
> - Max Pool Size. Specifies the maximum number of connections that can be allowed in the pool at any given point in time.
> - Pool Resize Quantity. When the pool shrinks toward the steady pool size it is resized in batches. This value determines the size of the batch. Making this value too large will delay connection recycling, making it too small will be less efficient. Note, the pool capacity is only ever increased one connection at a time so this field does not effect increases in pool capacity.
> - Idle Timeout (secs). Specifies the maximum time in seconds that a connection can remain idle in the pool. After this time, the pool implementation can close this connection.
> - Max Wait Time (milli secs). Specifies the amount of time the caller will wait before getting a connection timeout. The default wait time is long, which means that a caller can wait for a long time.

> Connection Validation

> - Connection Validation Required. If this field is checked then connections will be validated before they are passed to the application. This allows the web server to automatically re-establish database connections in the case of the database becoming unavailable due to network failure or database server crash. Validation of connections will incur additional overhead and slightly reduce performance.
> - Validation Method. Specifies the methods the Web server can employ to validate database connections. Choose from the following values:
> - auto-commit. In this mode, query statements are executed and committed as individual transactions.
> - meta-data. In this mode, a connection's database is able to provide meta-information describing its tables, its stored procedures, and so on.
> - table. This method requires the Web server to perform a query on a user-specified table.
> - Table Name. If you selected table as the validation method, specify the table name here.
> - Fail All Connections. Specifies whether to fail all connections in the pool and re-establish them if a single connection is determined to have failed. If left unchecked, connections will be individually re-established only when they are used.

> Transaction Isolation

> The isolation level that a transaction uses determines how sensitive the application is to changes other users' transactions make, and consequently, how long the transaction must hold locks to protect against these changes.

> - Transaction Isolation. Allows you to select the transaction isolation level for this connection. Choose from the following values:
> - read-uncommitted. Lets a transaction read any data currently on a data page, whether or not that data has been committed.
> - read-committed. Places shared locks on data in such a way that data another transaction has changed but not yet committed will never be read. Because uncommitted data is not read, if a transaction running with read-committed isolation queries the data again, that data might have changed, or additional data might appear that meet the criteria of the original query.
> - repeatable-read. Ensures that locks will be placed on all data that is used in a query. No other user can modify the data that your transaction visits as long as you have not yet committed or rolled back your transaction.
> - serializable. Locks ranges of data so that if a query is reissued, no data will have changed and no additional rows of data will appear during the time interval between the first and second query.
> - Guarantee Isolation Level. Ensures that any connection taken from the pool will have the same isolation level. For example, if the isolation level for the connection was changed programmatically (for example, con.setTransactionIsolation) when last used, this mechanism will change it back to the specified isolation level.

> OK. Saves your entries. Click Apply after saving your changes for the changes to take effect.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit JDBC Connection Pool Page

> The Edit JDBC Connection Pool Page allows you to edit a JDBC connection pool.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> General

> - Pool Name. Displays the connection pool name.
> - DataSource Classname. The vendor-specific classname that implements the data source.

> Properties

> Specify standard and proprietary JDBC connection pool properties. You will need to consult your database vendor's documentation to determine which standard and vendor specific properties are required.

> - Add. Click to add a property name and value.
> - Delete.To delete a property, check the corresponding checkbox and click the Delete button.

> Pool Settings

> - Steady Pool Size. Specifies the minimum number of connections that must be maintained in the pool. When a connection is given to a requesting thread, it is removed from the pool, reducing the current pool size. The steady pool size also refers to the number of entries that will be added to the pool on server startup.
> - Max Pool Size. Specifies the maximum number of connections that can be allowed in the pool at any given point in time.
> - Pool Resize Quantity. When the pool shrinks toward the steady pool size it is resized in batches. This value determines the size of the batch. Making this value too large will delay connection recycling, making it too small will be less efficient. Note, the pool capacity is only ever increased one connection at a time so this field does not effect increases in pool capacity.
> - Idle Timeout (secs). Specifies the maximum time in seconds that a connection can remain idle in the pool. After this time, the pool implementation can close this connection.
> - Max Wait Time (milli secs). Specifies the amount of time the caller will wait before getting a connection timeout. The default wait time is long, which means that a caller can wait for a long time.

> Connection Validation

> - Connection Validation Required. If this field is checked then connections will be validated before they are passed to the application. This allows the web server to automatically re-establish database connections in the case of the database becoming unavailable due to network failure or database server crash. Validation of connections will incur additional overhead and slightly reduce performance.
> - Validation Method. Specify the methods the Web server can employ to validate database connections. Choose from the following values:
> - auto-commit. In this mode, query statements are executed and committed as individual transactions.
> - meta-data. In this mode, a connection's database is able to provide meta-information describing its tables, its stored procedures, and so on.
> - table. This method requires the Web server to perform a query on a user-specified table.
> - Table Name. If you selected table as the validation method, specify the table name here.
> - Fail All Connections. Specifies whether to fail all connections in the pool and re-establish them if a single connection is determined to have failed. If left unchecked, connections will be individually re-established only when they are used.

> Transaction Isolation

> The isolation level that a transaction uses determines how sensitive the application is to changes other users' transactions make, and consequently, how long the transaction must hold locks to protect against these changes.

> - Transaction Isolation. Allows you to select the transaction isolation level for this connection. Choose from the following values:
> - read-uncommitted. Lets a transaction read any data currently on a data page, whether or not that data has been committed.
> - read-committed. Places shared locks on data in such a way that data another transaction has changed but not yet committed will never be read. Because uncommitted data is not read, if a transaction running with read-committed isolation queries the data again, that data might have changed, or additional data might appear that meet the criteria of the original query.
> - repeatable-read. Ensures that locks will be placed on all data that is used in a query. No other user can modify the data that your transaction visits as long as you have not yet committed or rolled back your transaction.
> - serializable. Locks ranges of data so that if a query is reissued, no data will have changed and no additional rows of data will appear during the time interval between the first and second query.
> - Guarantee Isolation Level. Ensures that any connection taken from the pool will have the same isolation level. For example, if the isolation level for the connection was changed programmatically (for example, con.setTransactionIsolation) when last used, this mechanism will change it back to the specified isolation level.

> OK. Saves your entries. Click Apply after saving your changes for the changes to take effect.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JDBC Resources Page

> The JDBC Resources Page allows you to use JNDI naming to create or configure a JDBC (javax.sql.DataSource) resource.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> New. Allows you to create a new JDBC resource.

> Delete. Allows you to delete existing JDBC resources.

> JNDI Name. Displays the JNDI name of the JDBC resource.

> Status. Displays the runtime status - enabled or disabled - of the resource.

> Pool Name. Displays the name of the connection pool used by this JDBC resource.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JDBC New Resource Page

> The JDBC New Resource Page allows you to create a new JDBC resource.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Enter the JNDI name that application components must use to access the JDBC resource.

> Status. Specifies whether the resource is enabled at runtime.

> Pool Name. Select from the list the name (or ID) of the connection pool used by this JDBC resource.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit JDBC Resource Page

> The Edit JDBC Resource Page allows you to edit a JDBC resource.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Displays the JNDI name of the JDBC resource.

> Pool Name. Select from the list the name (or ID) of the connection pool used by this JDBC resource.

> Data Resource Enabled. Specify whether the resource is enabled at runtime.

> Properties. You can add properties to the resource or delete them:

> - Add. Click to add a property name and value.
> - Delete.To delete a property, check the corresponding checkbox and click the Delete button.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JNDI Custom Resources Page

> The JNDI Custom Resources Page allows you to create or configure a new JNDI custom resource. A custom resource accesses a local JNDI repository.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> New. Allows you to create a new custom resource.

> Delete. Allows you to delete existing custom resources.

> JNDI Name. Displays the JNDI name of the custom resource.

> Status. Displays the runtime status - enabled or disabled - of the resource.

> Resource Type. Displays the fully qualified type of the custom resource.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The New Custom Resource Page

> The Custom Resources Page allows you to create a new JNDI custom resource. A custom resource accesses a local JNDI repository.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Enter the JNDI name that application components must use to access the custom resource.

> Resource Type. Enter the fully qualified type of the custom resource.

> Factory Class. Enter the fully qualified name of the user-written factory class, which implements javax.naming.spi.ObjectFactory.

> Custom Resource Enabled. Select On to enable the custom resource at runtime.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit Custom Resource Page

> The Edit Custom Resource Page allows you to edit a JNDI custom resource. A custom resource accesses a local JNDI repository.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Displays the JNDI name of the custom resource.

> Resource Type. Enter the fully qualified type of the custom resource.

> Factory Class. Enter the fully qualified name of the user-written factory class, which implements javax.naming.spi.ObjectFactory.

> Custom Resource Enabled. Select On to enable the custom resource at runtime.

> Properties. You can add properties to the resource or delete them:

> - Add. Click to add a property name and value.
> - Delete.To delete a property, check the corresponding checkbox and click the Delete button.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The JNDI External Resources Page

> The External JNDI Resources Page allows you to create or configure an external JNDI resource. External JNDI resources access objects in an external JNDI repository, for example, a generic Java object stored in an LDAP server.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> New. Allows you to create a new external JNDI resource.

> Delete. Allows you to delete existing external JNDI resources.

> JNDI Name. Displays the JNDI name of the resource.

> Status. Displays the runtime status - enabled or disabled - of the resource.

> Resource Type. Displays the fully qualified type of the custom resource.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The New External JNDI Resource Page

> The New External JNDI Resource Page allows you to create a new external JNDI resource. External JNDI resources access objects in an external JNDI repository, for example, a generic Java object stored in an LDAP server.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Enter the JNDI name that application components must use to access the external resource.

> Description. Enter a short description of the external JNDI resource.

> Resource Type. Enter the fully qualified type of the external resource.

> Factory Class. Enter the fully qualified name of the user-written factory class, which implements javax.naming.spi.ObjectFactory.

> JNDI Lookup. Enter the JNDI value to look up in the external repository. For example, if you are creating an external resource to connect to an external repository, to test a mail class, your JNDI Lookup could read cn=testmail.

> External Resource Enabled. Select On to enable the external resource at runtime.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit External JNDI Resource Page

> The Edit External JNDI Resource Page allows you to edit an external JNDI resource. External JNDI resources access objects in an external JNDI repository, for example, a generic Java object stored in an LDAP server.

> For more information, see Configuring Naming and Resources.

> The following elements are displayed:

> JNDI Name. Displays the JNDI name of the external resource.

> Description. Enter a short description of the external JNDI resource.

> Resource Type. Enter the fully qualified type of the external resource.

> Factory Class. Enter the fully qualified name of the user-written factory class, which implements javax.naming.spi.ObjectFactory.

> JNDI Lookup. Enter the JNDI value to look up in the external repository. For example, if you are creating an external resource to connect to an external repository, to test a mail class, your JNDI Lookup could read cn=testmail.

> External Resource Enabled. Select On to enable the external resource at runtime.

> Properties. You can add properties to the resource or delete them:

> - Add. Click to add a property name and value.
> - Delete.To delete a property, check the corresponding checkbox and click the Delete button.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Java Security Page

> Sun ONE Web Server 6.1 leverages the security model defined in the J2EE 1.3 Specification to provide several features that help you develop and deploy secure Java-based Web applications.

> The Java Security Page allows you to specify Java security settings for the server.

> For more information, see About Sun ONE Web Server Security.

> The following elements are displayed:

> Default Realm. Specifies the active authentication realm for this server instance.

> Anonymous Role. Used as the name for default or anonymous role.

> Audit Enabled. If true, additional access logging is performed to provide audit information. Audit information consists of:

> - Authentication success and failure events
> - Servlet access grants and denials

> Log Level. Controls the type of messages logged to the errors log.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit Realms Page

> The J2EE-based security model provides for security realms that identify and authenticate users. The user information is obtained from an underlying security realm. The Security Page allows you to configure a security realm for your server instance.

> For more information, see Realm-based Security.

> The following elements are displayed:

> New. Allows you to add a new security realm. By default, the following realms are provided:

> - The ldap realm -- Allows you to use an LDAP database for user security information.
> - The file realm -- The file realm is the default realm when you first install the Sun ONE Web Server.
> - The native realm -- Provides a bridge between core ACL-based authentication and the J2EE/Servlet authentication model.

> Delete. Allows you to delete one or more selected realms.

> Realm Name. Displays the names of existing realms. Click to edit the realm in the The Edit Security Realm Page.

> Class Name. Specifies the Java class that implements this realm.

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> ##

> The Edit Security Realm Page

> Realm Name. Displays the names of existing realms.

> Class Name. Specifies the Java class that implements this realm.

> Property Name. Specifies the name of a property. Restricted to a maximum of six name- value pairs for a realm.

> Property Value. Specifies the value of the property

> OK. Saves your entries.

> Reset. Erases your changes and resets the elements in the page to the values they contained before your changes.

> Help. Displays online help.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.