This documentation is for WSO2 Application Server version 5.0.0. View documentation for the latest release.

Skip to end of metadata
Go to start of metadata

This section provides the following information:


The screenshots may vary depending on the product and configuration options you are using.

Introduction to Web Applications

Web components are packaged in Web Application Archives (WAR), which are then deployed in the Application Server. Before creating the .war file, you need the class files and the web.xml file in the archive directory. The hierarchical directory structure of the web archive is as follows:



For more information on WAR files, please refer to

Deploying Web Applications 

Web application deployment and management capability is provided by the following feature:

Name: WSO2 Carbon - Webapp Management Feature

This feature is bundled in WSO2 Application Server by default. If the product you are using does have this feature by default, you can install it using the instructions provided in section Feature Management. Once installed, the necessary menus will appear in the Management Console.

Follow the instructions below to upload a Web archive file to a Carbon Server.

1. Log on to the product's management console and select "Web Applications” under “Applications” -> “Add” in the left pane.

2. The "Upload Web Applications" window appears. Browse and select your Web archive file. Then click "Upload."

For example,

Use the plus ‘+’ sign button to upload multiple Webapps at the same time. Click the minus sign to cancel an additional upload.

3. If the file is uploaded successfully, a message appears prompting you to refresh the page. Click "OK."

4. The .war file will be listed in the "Running Applications" page.

If the Web application is faulty, a "Faulty Web Application Groups" link will appear. You can click the link to view the errors.

You can also manually place the .war containing all the required files into <CARBON_HOME>/repository/deployment/server/webapps. These archive files can be deployed as Web applications.

  • No labels