This guide describes how to create and run Java™ 2 Platform, Standard Edition (J2SE platform) applications that follow the new open Java standards model for servlets and JavaServer Pages™ (JSP) technology on the Sun Java System Web Server 6.1. In addition to describing programming concepts and tasks, this guide offers implementation tips and reference material.
This preface contains the following topics:
The intended audience for this guide is the person who develops, assembles, and deploys web applications (servlets and JSPs) in a corporate enterprise.
This guide assumes you are familiar with the following topics:
The J2SE specification
HTML
The Java™ programming language
Java APIs as defined in servlet, JSP, and Java™ DataBase Connectivity (JDBC) specifications
Structured database query languages such as SQL
Relational database concepts
Software development processes, including debugging and source code control
The Sun Java System Web Server 6.1 SP10 manuals are available online files PDF and HTML formats at: http://docs.sun.com/app/docs/coll/1308.7
The following table lists the tasks and concepts described in the Sun Java System Web Server manuals.
Table P–1 Sun Java System Web Server Documentation Roadmap
This guide provides a Sun Java System Web Server environment overview for designing web applications, and has the following chapters:
This chapter introduces web applications and describes how they are supported in Sun Java System Web Server.
This chapter describes how to create and use servlets.
Chapter 4, Using JavaServer Pages
This chapter describes how to create and use JSPs.
This chapter describes how to create and manage a session that allows users and transaction information to persist between interactions.
Chapter 6, Securing Web Applications
This chapter describes the basic security features of the Sun Java System Web Server and how to write secure web applications.
Chapter 7, Deploying Web Applications
This chapter describes how web applications are assembled and deployed in the Sun Java System Web Server.
Chapter 8, Debugging Web Applications
This chapter provides guidelines for debugging web applications in Sun Java System Web Server.
Appendix A, Internationalization Issues
This appendix discusses internationalization issues pertaining to servlets and JSPs.
Appendix B, Migrating Legacy Servlets
This appendix discusses migrating legacy servlets.
This section describes the types of conventions used throughout this guide.
File and directory paths
These are given in UNIX® format (with forward slashes separating directory names). For Windows versions, the directory paths are the same, except that backslashes are used to separate directories.
URLs are given in the format:
http://server.domain/path/file.html
In these URLs, server is the server name where applications are run; domain is your Internet domain name; path is the server's directory structure; and file is an individual file name. Italic items in URLs are placeholders.
Font conventions include:
The monospace font is used for sample code and code listings, API and language elements (such as function names and class names), file names, path names, directory names, and HTML tags.
Italic monospace type is used for code variables.
Italic type is also used for book titles, emphasis, variables and placeholders, and words used in the literal sense.
Bold type is used as either a paragraph lead-in or to indicate words used in the literal sense.
Installation root directories are indicated by install_dir in this guide.
By default, the location of install_dir is as follows:
On UNIX-based platforms: /opt/SUNWwbsvr/
On Windows: C:\Sun\WebServer6.1
If you have problems with your system, contact customer support using one of the following mechanisms:
The online support web site at:
The telephone dispatch number associated with your maintenance contract
Please have the following information available prior to contacting support. This helps to ensure that our support staff can best assist you in resolving problems.
Description of the problem, including the situation where the problem occurs and its impact on your operation.
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem.
Detailed steps on the methods you have used to reproduce the problem.
Any error logs or core dumps.