Skip to end of metadata
Go to start of metadata

WSO2 Application Server is a program for hosting, deploying and managing various applications. See Application Development and Deployment for an overview of the process. Once you have developed the required applications, you can deploy them in AS using the management console as explained in the following instructions.

First, start WSO2 Application Server and log in to the management console. You can then deploy your applications using the Manage/Applications menu in the Main tab on the navigator:

Deploying applications on AS 

The following topics explain how different types of applications should be deployed in AS:

Deploying web applications 

This topic explains the steps that you have to follow in order to deploy web applications as web archive files (WAR files). These include various types of web applications, such as generic web applications, JAX-RS/JAX-WS applications as well as Spring applications.

Before you begin, note that the support for web application deployment in AS is provided by the following features, which are installed in AS by default:

  • The capability to deploy and manage generic web applications is provided by the following feature:

    Name: WSO2 Carbon - Webapp Management Feature 
    Identifier: org.wso2.carbon.webapp.mgt.feature.group 
  • The capability to deploy and manage JAX-RS/JAX-WS web applications is provided by the following feature:

    Name: WSO2 Carbon - JAX-WS/JAX-RS Webapp Management Feature
    Identifier: org.wso2.carbon.jaxws.webapp.mgt.feature.group 

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

  1. Log in to the product's management console and click Web Applications under Applications in the navigator. The Upload Web Applications screen appears. 
  2. Browse and select your Web archive file. 
  3. If you are logged in as the super tenant, you can select the host for your web application. In the above example, the host is the default 'localhost'. If you have virtual hosts configured in you AS, other domains will be listed in addition to 'localhost'. This means that you can deploy the same application in multiple domains.
  4. You can use the plus sign ('+') to add multiple web applications.

  5. Click UploadIf the file is uploaded successfully, a message appears prompting you to refresh the page. Click OK.

  6. 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 in the Running Applications page. You can click the link to view the errors. 

Instead of using the management console, you can manually place the .war file containing all the required files in the <PRODUCT_HOME>/repository/deployment/server/webapps/ directory. These archive files will be deployed as web applications when the server starts.

Deploying Jaggery applications

This topic explains the steps that you have to follow in order to deploy Jaggery applications in AS. 

WSO2 supports the deployment of Jaggery applications based on Apache Tomcat through the following feature in the WSO2 feature repository:

Name WSO2 Carbon - Jaggery Server Feature
Identifier: org.wso2.carbon.jaggery.server.feature.group

The Jaggery application management feature is bundled in AS (version 5.0.0 onwards) by default.

Follow the instructions below to deploy the file in a running Carbon instance.

  1. Before deploying a Jaggery application through the management console, bundle it as a '.zip' archive with all the resources and third-party libraries related to Jaggery applications.
  2. Log in to the product's management console. Click Add under the Jaggery Applications menu.
  3. The Upload Jaggery Applications page appears. Select your file and click Upload.
    If you want to add multiple services at the same time, click on the '+' sign next to Browse.
  4. If the Jaggery application was deployed successfully, a message appears confirming the deployment and opens the Running Applications page. For example,
  5. If the Jaggery application is faulty, a "Faulty Jaggery Application Groups" link will appear. You can click the link to view the errors.

Instead of using the Management Console, you can manually place the .zip file in <PRODUCT_HOME>/repository/deployment/server/jaggeryapps and it will be deployed. Instead of creating a zip file, you can also add the resource files such as style sheets, images, java scripts etc. in the said location (preferably within a folder) along with the index.jag file. The files will be auto deployed.

  • No labels