WSO2 Application Server is built with many features to facilitate the hosting, deployment and management of various applications. The following diagram depicts the process that you need to follow when working with applications in WSO2 AS:
See the following topics for details of the above:
Developing applications for WSO2 AS
Applications that can be deployed in WSO2 AS include Web Applications (generic web applications, JAX-RS/JAX-WS applications) and Jaggery Applications. The following topics explain the different types of applications deployable in WSO2 AS and some instructions and configurations that should be followed when developing them:
Note that you can conveniently create applications using WSO2 Developer Studio. If you are already done with building your application, you can directly proceed to the next step, which is deploying applications in AS.
Configuring WSO2 AS for applications
WSO2 AS inherits many features from the Carbon platform, which allows you the flexibility of configuring your server to provide the necessary support for your web applications. See the section on working with web applications in the administration guide to find information on the server settings that will directly apply to your applications.
Deploying applications in WSO2 AS
Once you are done with developing your application, you can easily deploy it in WSO2 AS using the management console. See the topic on deploying applications in AS for step-by-step instructions.
Managing applications deployed in WSO2 AS
In the management console of WSO2 AS, you will find a separate dashboard for each of the deployed applications. This dashboard can be used to test, edit and even configure the application. See the topic on managing applications in AS for detailed information.
Connecting to applications deployed in WSO2 AS
WSO2 AS supports a variety of transports. Among these, the HTTP and HTTPS servlet transports are used by the applications hosted on AS to connect with other clients and applications. The receiver implementation for the HTTP and HTTPS transports are built into Carbon products, and the sender implementation comes from the Tomcat http connector, which is configured in the catalina-server.xml file (stored in the <PRODUCT_HOME>/repository/conf/tomcat/ folder).