Use this document to learn how to develop and deploy Web
applications
About this task
A developer creates the files comprising a web application,
and then assembles the web application components into a web module.
Next, the deployer (typically the developer in a unit-testing environment
or the administrator in a production environment) installs the Web
application on the server.
Procedure
- Optional: Migrate existing web applications to run in the
new version of WebSphere® Application Server.
- Design the web application and develop its code artifacts:
Servlets, JavaServer Pages (JSP) files,
and static files, as for example, images and Hyper Text Markup Language
(HTML) files. See the Web applications: Resources for learning topic for links to design
documentation.
JavaServer Pages programming tips:
- Disable session state of JavaServer Pages files using <%@
page language="java" contentType="text/html" session="false" %> instead
of <%@ page language="java" contentType="text/html" %>
- Replace setProperties calls in your JavaServer Pages files with
direct calls to the appropriate setxxx methods.
- Develop the Web
application, using WebSphere Application Server
extensions to enhance its functionality.
- Assemble the web application into a web module using an assembly tool.
Web module assembly properties might include the ability to:
- Configure servlet page lists.
- Configure servlet filters.
- Serve servlets by class name.
Serving servlets by name or class
name is triggered by setting the serveServletsbyclassnameEnabled property
within IBM® extensions. Use the invoker.patterns attribute
to specify the patterns that trigger invocation of the server component
and allows the serving of servlets by name or by class name. This
value is a list separated by either a space, colon, or semicolon.
- Enable file serving.
In file serving, web applications can serve
static file types, such as HTML. File-serving attributes are used
by the servlet that implements file-serving behavior.
- Deploy the
web module or application module that contains the web application.
Following deployment, you might find it handy to use the tool that enables batch
compiling of the JSP files for quicker initial response times.
- Optional: Troubleshoot your web application.
- Optional: Modify
the default web container configuration in the application
server in which you deployed the web module or application module
containing the web application.
- Optional: Manage
the deployed web application.