Technical data
8 Configuring WebLogic Server Web Components
8-6 Administration Guide
files. In addition, a Web Application can access external resources such as EJBs and 
JSP tag libraries. Each server can host any number of Web Applications. You normally 
use the name of the Web Application as part of the URI you use to request resources 
from the Web Application.
For more information, see Assembling and Configuring Web Applications at 
http://e-docs.bea.com/wls/docs61/webapp/index.html.
Web Applications and Clustering
Web Applications can be deployed in a cluster of WebLogic Servers. When a user 
requests a resource from a Web Application, the request is routed to one of the servers 
of the cluster that host the Web Application. If an application uses a session object, 
then sessions must be replicated across the nodes of the cluster. Several methods of 
replicating sessions are provided. 
For more information, see Using WebLogic Server Clusters at 
http://e-docs.bea.com/wls/docs61/cluster/index.html.
Designating a Default Web Application
Every server and virtual host in your domain can declare a default Web Application. 
The default Web Application responds to any HTTP request that cannot be resolved to 
another deployed Web Application. In contrast to all other Web Applications, the 
default Web Application does not use the Web Application name as part of the URI. 
Any Web Application targeted to a server or virtual host can be declared as the default 
Web Application. (Targeting a Web Application is discussed later in this section. For 
more information about virtual hosts, see “Configuring Virtual Hosting” on page 8-8).
The default domain and the examples domain that are shipped with Weblogic Server 
each have a default Web Application already configured. The default Web Application 
in these domains is named 
DefaultWebApp and is located in the applications 
directory of each domain.
If you declare a default Web Application that fails to deploy correctly, an error is 
logged and users attempting to access the failed default Web Application receive an 
HTTP 
400 error message.










