Administering web applications
Subtopics
Modifying the default web container configuration
A web container handles requests for servlets, JavaServer Pages (JSP) files, and other types of files that include server-side code. The web container creates servlet instances, loads and unloads servlets, creates and manages request and response objects, and performs other servlet management tasks. The web server plug-ins, provided by the product, help supported web servers to pass servlet requests to web containers.Configuring JSP engine parameters
Learn about how to add, change or delete JSP engine configuration parameters.Backing up and recovering servlets
Servlet source and class files, user profile data, Hypertext Transfer Protocol (HTTP) configuration, and administrative configuration should be considered for backup when using servlets. You should consider saving your HTTP configuration because changes to the HTTP configuration are often made to enable WebSphere® Application Server to serve servlets and JSP requests, and to enable WebSphere Application Server security. You should consider backing up the user profile data if you use the User Profile function of WebSphere Application Server.Backing up and recovering JavaServer Pages files
JavaServer Pages source and generated servlet classes, Hypertext Transfer Protocol (HTTP) configuration, and administrative configuration should be considered for backup when using JavaServer Pages files.Administering RRD applications
Asynchronous request dispatching settings
Expression Language 3.0 feature functions
The Expression Language (EL) 3.0 feature provides full support for the EL 3.0 specification.JavaServer Pages 2.3 feature functions
The JavaServer Pages (JSP) 2.3 feature provides full support for the JSP 2.3 specification.JavaServer Faces 2.2 feature functions
Learn about JavaServer Faces (JSF) 2.2, which supports the JSF 2.2 specification. You can configure WebSphere Application Server traditional Version 9.0 to use JSF 2.2 for improved developer efficiency and compatibility with modern paradigms.Servlet behavior changes
The Servlet 3.1 implementation contains behavior changes that might cause an application that was written for Servlet 3.0 to behave differently or fail when you use the Servlet 3.1 feature.Servlet 3.1 feature functions
WebSphere Application Server traditional supports the Servlet 3.1 specification. View the clarifications and descriptions of highlighted functions.


File name: container_webapp_administer.html