Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Web Applications

[Attributes and Console Screen Reference for Web Applications]

# Overview

A Web Application is a J2EE deployment unit that defines a collection of Web resources such as JSPs, servlets, and HTML pages. Web Applications can also define references to external resources such as EJBs.

These procedures describe how to use the Administration Console to deploy Web Applications.

Note: A Web service is a special kind of Web Application. Web services are Web applications that have an additional deployment descriptor called `web-services.xml`. If you package a Web service as a `.war` file or an exploded `.war` directory, you can deploy the Web service in the same manner as you would a Web application.

For more information about configuring Web Applications, see Developing Web Applications for WebLogic Server. For more information about J2EE Enterprise applications in the Administration Console, see Applications.

# Tasks

For more information on application deployment, refer to Deploying Applications and Modules.

## Designating a Default Web Application

The default Web Application is presented to clients who do not specify a URI (or specify "/" as the URI). To deploy a Web Application as a default Web Application, set the value of the `context-root` element to "/" in its deployment descriptor.

You can specify the `context-root` element in the `weblogic.xml` deployment descriptor for Web Applications that are packaged as a `.war` archive or exploded `.war` directory. If you package the Web Application as part of an Enterprise Application (`.ear` archive or exploded `.ear`), specify the `context-root` in `application.xml`. Note that the `application.xml` context-root takes precedent over the `weblogic.xml` value.

Deploy the application using the instructions in Deploying a New Web Application.

To deploy a Web Application as part of an .ear archive or exploded .ear, see Deploying WebLogic Server Applications.

## Deploying a New Web Application

To deploy a new Web application packaged as a WAR archive or exploded WAR directory using the WebLogic Server Administration Console:

1. Start the WebLogic Server Administration Console for the domain in which you will be working.
2. In the left pane of the Console, expand the Deployments folder, right-click Web Application Modules, and select Deploy a New Web Application Module. This initiates the Deployment Assistant.
3. Using the Deployment Assistant, locate the WAR file you would like to configure for use with WebLogic Server. You can also configure an "exploded" Web Application or component directory. Note that WebLogic Server will deploy all components it finds in and below the specified directory.
4. When you have located the archive file to configure, click Target Application.
5. If you have more than one server or cluster in your domain, select the one on which you want to deploy your new Web Application and click Continue. If you have just one server in your domain, go to the next step.
6. Enter a name for the Web Application in the Name field.

If you have more than one server or cluster in your domain, click whether you want to copy the file to each server.

7. Click Deploy. The Console displays the Deploy panel, which lists deployment status and deployment activities for the Web Application.
8. Using the available tabs, enter the following information:

- Configuration—Define the general configuration of this Web Application.
- Targets—Define the servers or clusters on which you would like to deploy all of the modules in this Web Application.
- Deploy—View the deployment status of each module in Web Application, and to undeploy or redeploy individual modules.
- Notes—Include any additional information that describes the configuration of this Web Application.

9. Click Apply.

## Testing the Deployment

To test the deployment of a Web Application in the Administration Console:

1. In the left pane of the Console, expand Deployments. Then expand Web Application Modules and click the name of the application you want to test.
2. On the Testing tab, click the Web Application Module to ensure that it has been properly deployed.

## Viewing Deployed Web Applications

To view deployed Web Applications in the Administration Console:

1. In the left pane of the Console, expand Deployments and click the Web Applications Modules folder name.
2. View a list of deployed Web Applications in the table displayed in the right side of the Console.

## Stopping Deployed Web Applications

Stopping a Web Application makes the application unavailable to WebLogic Server clients. Stopping an application does not remove the deployment files from the server; you can later redeploy a stopped application by clicking its redeploy button in the Administration Console.

To stop a deployed Web Application:

1. In the left pane of the Console, expand Deployments and then Web Applications Modules.
2. Click the name of the Web Application you wish to stop.
3. Select the Deploy tab, and click Stop or Stop All buttons to stop the application.

## Adding or Editing Web Application Deployment Notes

To add or edit Web Application deployment notes:

1. In the left pane of the Console, expand Deployments and then click the Web Application Modules folder name.
2. Click the name of the Web Application.
3. Select the Notes tab.
4. Add or edit the optional information in the Notes scroll box.
5. Click Apply.

## Deleting a Web Application

To delete a Web Application:

1. In the left pane of the Console, expand Deployments and then click the Web Application Modules folder name. A table is displayed in the right pane of the Console showing all the deployed Web Applications.
2. Select the Configuration tab if it is not displayed.
3. Click the Garbage Can icon to the right of the file you want to delete.
4. Click Yes to confirm your decision.
5. Click Continue to return to the previous screen.

## Monitoring Web Applications and Servlets

To monitor active Web Applications and Servlets in the Console, proceed as follows:

1. In the left pane of the Console,expand Deployments, right-click Web Application Modules, and select Monitor All Web Application Modules.
2. To monitor Web Applications, select the Web Applications sub-tab.
3. To monitor Servlets, select the Servlets sub-tab.
4. To enable Session Monitoring, select the Session sub-tab and select the Session Monitoring Enabled checkbox. Then click Apply.
5. On the Web Applications or Servlets sub-tab, you can select Customize This View to customize the available monitoring features. You can choose which items to monitor, determine how to sort these options, and set this view as your default view. Click Apply to save your settings.

## Viewing and Updating Run-Time Descriptor Elements

This release of WebLogic Server has deprecated the Administration Console Deployment Descriptor Editor. A new Descriptor tab in the Administration Console has replaced it. Using the Descriptor tab, you can view, modify, and persist deployment descriptor elements to the descriptor file within an exploded Web application in the same manner that they were persisted using the Deployment Descriptor Editor.

These descriptor elements are engaged dynamically at runtime; you do not have to redeploy the Web Application. The descriptor elements contained in the Descriptor tab are limited to only those descriptor elements that may be dynamically changed at runtime.

To view and edit descriptor information in the Console, proceed as follows:

1. In the left pane of the Console, expand Deployments and then click the Web Application Modules folder name.
2. Click the name of the Web Application whose descriptors you want to change.
3. In the right pane, select Configuration and then select Descriptor
4. Click the link for the deployment descriptor you want to change.
5. Define the configuration of the application deployment descriptor file that is associated with this Web application module by changing the provided attribute values as needed.
6. Click Apply to save your changes.