WAS v8.5 > WebSphere applications > Web applications > Learn about web applications

Web applications

A web application is comprised of one or more related servlets, JSP technology (JSP files), and Hyper Text Markup Language (HTML) files managed as a unit.

The files in a web application are related in they work together to perform a business logic function. The web application is a concept supported by the Java Servlet Specification. Web applications are typically packaged as .war files.

Subtopics

• Web modules
  A web module represents a web application. A web module is created by assembling servlets, JSP files, and static content such as HTML pages into a single deployable unit. Web modules are stored in WAR files, which are standard Java archive files.
• Web container request attributes
  A web container provides three custom HttpServletRequest attributes that can be used to provide a servlet or a trust association interceptor (TAI) with the certificate information for a request.
• web.xml file
  The web.xml file provides configuration and deployment information for the web components that comprise a web application.
• Default Application
  WAS provides a default configuration that administrators can use to easily verify the Application Server is running. When the product is installed, it includes an application server called server1 and an enterprise application called Default Application.
• JSP
  JSP are application components coded to the JSP Specification. JSP enable the separation of the HTML code from the business logic in web pages so that HTML programmers and Java programmers can more easily collaborate in creating and maintaining pages.
• Servlets
  Servlets are Java programs that use the Java Servlet Application Programming Interface (API). You must package servlets in a WAR file or web module for deployment to the application server. Servlets run on a Java-enabled web server and extend the capabilities of a web server, similar to the way applets run on a browser and extend the capabilities of a browser.
• Web fragments
  When developing web applications, if multiple web modules use the same components, consider including the components in a Web fragment JAR file. The web fragment JAR file contains both the configuration metadata and component class files. This practice enables easier copying from application to application.
• Asynchronous servlet best practices
  The asynchronous servlet feature enables you to process incoming requests and responses without being bound to the original thread that initiated the request.
• Web container properties
  Learn about system properties, custom properties, and application properties for the web container.
• Java EE application resource declarations
  We can configure your Java EE applications to declare dependencies on external resources and configuration parameters. These resources might be injected into the application code, or might be accessed by the application through the JNDI.
• Web applications: Resources for learning
  

Related concepts:

Servlets
JSP
Web modules

Reference:

Default Application

+

Search Tips   |   Advanced Search