Server User Manual
Table Of Contents
- Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide
- Preface
- Overview of Enterprise Server Performance Tuning
- Tuning Your Application
- Java Programming Guidelines
- Java Server Page and Servlet Tuning
- EJB Performance Tuning
- Goals
- Monitoring EJB Components
- General Guidelines
- Using Local and Remote Interfaces
- Improving Performance of EJB Transactions
- Use Container-Managed Transactions
- Don’t Encompass User Input Time
- Identify Non-Transactional Methods
- Use TX_REQUIRED for Long Transaction Chains
- Use Lowest Cost Database Locking
- Use XA-Capable Data Sources Only When Needed
- Configure JDBC Resources as One-Phase Commit Resources
- Use the Least Expensive Transaction Attribute
- Using Special Techniques
- Tuning Tips for Specific Types of EJB Components
- JDBC and Database Access
- Tuning Message-Driven Beans
- Tuning the Enterprise Server
- Deployment Settings
- Logger Settings
- Web Container Settings
- EJB Container Settings
- Java Message Service Settings
- Transaction Service Settings
- HTTP Service Settings
- ORB Settings
- Thread Pool Settings
- Resources
- Tuning the Java Runtime System
- Tuning the Operating System and Platform
- Tuning for High-Availability
- Index

Administration
A single Application Server installation on a server can encompass multiple instances. A group
of one or more instances that are administered by a single Administration Server is called a
domain. Grouping server instances into domains permits dierent people to independently
administer the groups.
You can use a single-instance domain to create a “sandbox” for a particular developer and
environment. In this scenario, each developer administers his or her own application server,
without interfering with other application server domains. A small development group may
choose to create multiple instances in a shared administrative domain for collaborative
development.
In a deployment environment, an administrator can create domains based on application and
business function. For example, internal Human Resources applications may be hosted on one
or more servers in one Administrative domain, while external customer applications are hosted
on several administrative domains in a server farm.
The Application Server supports virtual server capability for web applications. For example, a
web application hosting service provider can host dierent URL domains on a single
Application Server process for ecient administration.
For detailed information on administration, see
Sun GlassFish Enterprise Server 2.1
Administration Guide
.
GeneralTuning Concepts
Some key concepts that aect performance tuning are:
■
User load
■
Application scalability
■
Margins of safety
The following table describes these concepts, and how they are measured in practice. The left
most column describes the general concept, the second column gives the practical ramications
of the concept, the third column describes the measurements, and the right most column
describes the value sources.
General Tuning Concepts
Chapter 1 • Overview of Enterprise Server PerformanceTuning 23










