Introduction: Web apps



Search Tips   |   Advanced Search

Web apps

Servlets, JSPs, and static content stored in deployable *.war files.


Programs that use the Java Servlet API. Packaged in *.war files

Page lists

Eliminate avoid hard-coding of URLs in servlets and JSPs.

Sets locations where requests are to be forwarded using servlet MIME type.

Client type detection support

Uses client_types.xml to determine the markup language type used in a response.

Provided by the PageListServlet.

autoRequestEncoding and autoResponseEncoding

Set encoding values and content type if not already set using Servlet 2.3+ methods.

Servlet filtering

Transform a request or modify a response.

We can chain filters together so that a group of filters can act on the input and output of a specified resource or group of resources.

Application life cycle listeners and events

Notify listeners when...

  • Attributes change
  • Sessions are created or destroyed

JSP engine

Implementation of the JSPs Specification.


Application components coded to the JSPs Specification.

Enable the separation of the HTML code from the business logic in Web pages.

Java Server Faces

User interface framework.

WAS v7.0 supports JSF 1.2 at runtime level, reducing size of the Web app as runtime binaries no longer to be included.

Java Server Faces widget library (JWL)

Widget library.

Eliminates requirement to move *.jar files from the development environment to the runtime environment or package the widget library with each application.

Web component security

Enforce security at the method level.

Security constraints in Web apps

Associate security constraints with Web resource collections.

A constraint consists of...

File serving

Serve static file types, such as HTML.

Remote request dispatcher

Include content from outside of the current executing resource's JVM as part of the response sent to the client.

Application extension registry

WAS has enabled the Eclipse extension framework.

Developers who build WebSphere application modules can use WAS extensions to implement Eclipse tools and to provide plug-in modules to contribute functionality such as actions, tasks, menu items, and links at predefined extension points in the WebSphere application.

Define an extension point and extension processing code in your applications. We can dynamically plug your application into another extensible application.

Application extension registry filtering

Exposes the registry filter extension point, which removes elements within the extension registry.


Series of requests to a servlet, originating from the same user at the same browser.

Session management support

Support for the javax.servlet.http.HttpSession interface.

Distributed sessions

Database session persistence and memory-to-memory session replication in a distributed environment.

Memory-to-memory replication

Session replication to another WAS profile.

Referred to as memory-to-memory session replication.

Sessions can replicate to one or more WAS profiles to address HTTP Session single point of failure (SPOF).

Memory-to-memory session partitioning

Filter or reduce the number of destinations that the session object gets sent to by the replication service.

Specify the number of replicas on the replication domain. The Single replica option is chosen by default. Since the number of replicas is global for the entire replication domain, all the session managers connected to the replication domain use the same setting.

Clustered session support

Supports load balancing, where the workload is distributed among the appservers that compose the cluster.

Scheduled invalidation

Set specific times for the session management facility to scan for invalidated sessions in a distributed environment.

Base in-memory session pool size

Different meanings, depending on session support configuration.

Write operations

Manually control when modified session data is written out to the database or to another WAS instance by using the sync method in...

Related information

Learn about Web apps