Configuring Runtime Environments

WSO2 AS leverages a concept called runtime environments to separately maintain different runtimes for loading the relevant classes for your web applications. The WSO2 web application management feature provides the capability to load classes from different locations to your applications.

Most web applications that are deployed in production environments depend on external, third-party libraries for different functionality. Through the WSO2 Application Server's runtime environment, you can control class loading per server or application. The following runtimes that are available with WSO2 AS are sufficient for most users, but you can also define your own runtimes. There are four default runtime environments available in AS 5.3.0, which are as follows:

• Tomcat Environment: This is the minimal runtime, which is identical to a pure Tomcat runtime. It only has Tomcat, Servlet, JSP, EL and JSTL available in the server-level classpath. If you want additional JARs, you should package them with the web application or place them in the Tomcat environment's extension directory.
• Carbon Environment: This consists of both the Tomcat environment and the WSO2 Carbon runtime. It does not provide CXF or Spring dependencies. If you want additional JARs, you should package them with the web application or place them in the WSO2 Carbon environment's extension directory.
• CXF Environment: This consists of the Tomcat environment, CXF and Spring. It does not provide the WSO2 Carbon runtime. If you want additional JARs, you should package them with the web application or place them in the CXF environment's lib directory.

• Javaee Environment: This consists of the Javaee runtime and the WSO2 Carbon runtime. If you want additional JARs, you should package them with the web application or place them in the Javaee environment's lib directory.

See the following topics for more information:

Setting up the runtime environment

To configure class loading, you should add the class loading configuration in a file named webapp-classloading.xml and place it in the META-INF folder of a web application. This folder should be created inside the src/main/webapp folder of you web application. All the artifacts related to a web application are saved in the following directory: <PRODUCT_HOME>/repository/deployment/server/<Web_Application_Type>/<Web_Application_Name>. For example: <PRODUCT_HOME>/repository/deployment/server/webapps/SampleApp.

The webapp-classloading.xml file takes the following format:

<Classloading xmlns="http://wso2.org/projects/as/classloading"> 
   <Environments>{Runtime Environment Names} </Environments> 
</Classloading> 

• Shown below is the webapp-classloading.xml file configuration to specify CXF as the runtime environment:

  <Classloading xmlns="http://wso2.org/projects/as/classloading">
     <Environments>CXF</Environments>
  </Classloading>

• You might want to access some Carbon features in a CXF application. To achieve this, specify a comma-separated list of environments in the webapp-classloading.xml file. The following example specifies both CXF and Carbon as the runtime environments:

  <Classloading xmlns="http://wso2.org/projects/as/classloading">
     <Environments>Spring,Carbon</Environments>
  </Classloading>

• From AS 5.3.0 onwards, Java EE 6 Web Profile support is available as a feature, which allows you to enable the Javaee runtime environment, in addition to Tomcat, Carbon and CXF runtime environments. See the topic on enabling Java EE 6 Web Profile for step-by-step instructions on configuring the Java EE runtime.

Extending the runtime environments

This section explains how to place your external dependencies in a running server. This allows you to share dependencies with a number of applications without packaging them with each and every application. To do this, place the common dependencies in the relevant directories given below.

• In Tomcat Environment - <PRODUCT_HOME>/lib/runtimes/ext
• In Carbon Environment - <PRODUCT_HOME>/repository/components/lib
• In CXF, Javaee or any Custom Environment – Use the environment's lib directory. For example: <PRODUCT_HOME>/lib/runtimes/cxf

Adding Custom Runtime Environments

To define custom runtime environments, add a new element as <ExclusiveEnvironments> in the <PRODUCT_HOME>/repository/conf/tomcat/webapp-classloading-environments.xml file.  

To define a custom runtime environment for Spring:

1. Modify the webapp-classloading-environments.xmlfile with the following entries.

   <ExclusiveEnvironments> 
      <ExclusiveEnvironment> 
         <Name>Spring</Name> 
         <Classpath>${carbon.home}/lib/runtimes/spring/*.jar;${carbon.home}/lib/runtimes/spring/</Classpath> 
      </ExclusiveEnvironment> 
   </ExclusiveEnvironments>

2. Next, create and copy of the related Spring dependencies in the <PRODUCT_HOME>/lib/runtimes/spring directory.

3. Add the following entries to the webapp-classloading.xml file of each web application so that they can be used in the Spring runtime environment defined above.

   <Classloading xmlns="http://wso2.org/projects/as/classloading">
      <Environments>Spring,Carbon</Environments>
   </Classloading>

Upgrading Existing Runtime Environments

The CXF runtime environment comes by default with core CXF 2.7.5 and core Spring 3.0.7 dependencies. If you want to upgrade to a different CXF version, there are two recommendations:

• Upgrade the CXF runtime environment : You can replace the existing CXF/Spring dependent JARs in the <PRODUCT_HOME>/lib/runtimes/cxf directory with new CXF/Spring JARs.

• Instead of upgrading server-level CXF dependencies, you can package all the required JARs in the Web-INF/lib directory of the web application and deploy that in the Tomcat runtime environment.

If you want to add optional CXF/Spring JARs, copy them to the <PRODUCT_HOME>/lib/runtimes/cxf directory after ensuring that they are compatible with the existing JARs.