Java Server Page

The Internet was once full of Web sites hosting static pages ("brochure-ware") or simple forms at best. Now it's an interactive environment for transacting daily business, from shopping to trading stocks to interacting with suppliers, in a personalized and dynamic setting. Today, the tools and products to build dynamic, Web-based applications are still maturing. Traditionally, companies used CGI applications to generate dynamic content for Web pages. But that solution hasn't scaled well to support complex functionality and growing numbers of concurrent users. JavaServer Pages ^TM (JSP^TM) technology provides a highly scalable method for creating dynamic content for the Web. As part of the Java^TM family of APIs, JSP technology shares the Write Once, Run Anywhere^TM benefits of the Java platform, with easy access to a broad range of Java APIs. JSP technology enables a tiered development methodology that lets organizations leverage internal programming expertise to create applications that are fast to deploy and easy to maintain.

The growth and acceptance of the Internet in both businesses and homes is changing the face of many industries - and the information systems that support them. From new .com companies to brick-and-mortar establishments, businesses everywhere are finding new ways to leverage the power of the Internet. Software developers have been quick to realize the possibilities of Web-based clients in application architectures. With a browser on virtually every desktop, companies can deploy a multitier architecture in which Web servers act as a middle tier, managing interactions with Web-based clients.

A Web-based client architecture may have three or more layers. This multitier architecture provides many benefits over a traditional (two-tiered) client/server architecture.

Installing and deploying the user interface is virtually instantaneous - only the Web interface in the middle tier needs to be updated.
Because the application itself is server-based, users always access the most up-to-date version.
Without a "thick" client interface, it is easier to deploy, maintain, and modify applications - no matter where the client is located.

These benefits explain the growing popularity of the multitier architecture, and why almost every client/server application provider has retooled or is retooling to support Web-based clients.

Development Tools and Methodologies Are Maturing

Companies building and deploying applications on this model are faced with an application environment that is still maturing. A number of different technologies - ranging from traditional CGI scripts to JSP technology - are available today to build the interactive, "customer-facing" component of these applications. The challenge is selecting an application architecture and component design that meets the evolving user needs (whether they be customers, partners, or internal staff) as well as the enterprise's own IT requirements.

Users Have Heightened Requirements

Internet users have heightened expectations for application availability and reliability. They want to be able to access applications at any time of day or night to perform a wide variety of tasks online. They expect up-to-date information and fast response times.

To support these requirements, application providers need high-performance, highly reliable applications that can be updated easily. They need applications that can scale to support large numbers of users, and that can interact with vital business systems.

Solutions Must Meet Demanding Enterprise Software Requirements

The organizations that are building and maintaining these applications also have stringent requirements when selecting the architectures, products, and tools for creating Web-based applications.

The development platform must support fast application deployment and rapid updates.
The application must be easy to maintain using minimal developer resources. Many organizations face a shortage of qualified Web developers and need to protect the developers they already have.
Finally, the organization needs to retain the ability to adopt new tools or technologies as needed, so the development environment should not close out options. With new tools, systems, and information sources appearing nearly everyday, there is a risk to selecting a solution that leaves the organization entirely at the mercy of a single vendor - even if that vendor is the market leader.