Feature | Description | |
|---|---|---|
| Java EE 6 Web Profile support | Application Server (AS) 5.3.0 supports Javaee 6, which uses Apache TomEE. To use this feature in AS 5.3.0, you have to configure a new runtime called "Javaee". With this new runtime, you will be allowed to deploy javaee web apps in AS.
| |
| WebSocket support for web applications | Starting from version 5.3.0, WSO2 AS provides support for Websocket 1.1 API as defined by the JSR-356 specification. This is provided by Apache Tomcat, which is embedded in AS. See the following sample demonstration on how web sockets work in AS 5.3.0. | |
| Apache Aries SPI Fly | The WSO2 Carbon platform integrates ‘Apache Aries SPI Fly’, which provides OSGi support for JRE SPI mechanisms.
| |
| Publishing web application statistics from AS to BAM | The Application Server (AS) previously had the capability of only monitoring statistics through WSO2's Business Activity Monitor (BAM). However, now the Application Server has the capability of monitoring web application statistics as well using BAM 2.3.0.
| |
| Support for multiple AS modes/profiles | Multi-profile support allows the user to run the product pack in a preferred profile. The available profiles are:
| |
| Distributed Caching implementation based on Hazelcast | Cluster wide distributed caching is supported by using Hazelcast implementation. Thereby, the caching API, response caching etc. can be used in a distributed manner. | |
| Clustering support for High Availability and High Scalability | You can install multiple instances of WSO2 products in a cluster to ensure that if one instance becomes unavailable or is experiencing high traffic, another instance will seamlessly handle the requests. Starting from AS 5.2.1, we provide Clustering clustering support through Hazelcast. For more information see, Clustered Deployment. | |
| Secondary user store support | Secondary user stores can be dynamically configured via the Application Server UI. In addition, users are allowed to configure their own user stores, out-of-the-box. | |
| CarbonContext API | This is an API for developers to access certain core services (such as registry, caching and more) from the Carbon runtime. | |
Support for Servlet 3, JSP 2.2, EL 2.2, JSTL 1.2 specifications | ||
Full JAX-WS 2.2 and JAX-RS 2.0 Specification specification support | WSO2 AS provides out-of-the-box support for JAX-WS 2.2 and JAX-RS 2.0 specifications via CXF. | |
Integration of Jaggery | Developing Jaggery Applications is a server side scripting framework. It allows you to write webapps web apps and HTTP-focused web services for all aspects of the application: front-end, communication, server-side logic and persistence in pure Javascript.Mashup services support | |
| Mashups allow you to expose simple Javascript functions as full-fledged SOAP Web services. | Multi-tenant support for standalone deployment | In addition , to the ability to create of creating tenants in cloud deployments, the user can create and use tenants in standalone mode as well. |
100% Apache Tomcat compliance | WSO2 Application Server is based on Apache Tomcat and is compliant with Tomcat. | |
| Lazy loading for tenants | Lazy loading support for tenants allows you to load the tenants only when it is requestedon request. For example, the tenant is loaded when a tenant user is logged in, and a web application/service request is sent to a tenant's artifact. This makes starts the server start-up much faster, due to efficient memory usage, since not all the tenants and its artifacts are not loaded at a given time. | |
Lazy loading for web applications and services | This allows the user to load the web applications and web services only when it's being requested. This makes starts the server start-up faster, due to efficient memory usage, since not all the artifacts are not loaded at a given time. | |
Tooling support | Application Server related artifacts can be easily generated using WSO2 Developer Studio, which is an Eclipse plugin. | |
| By default, JMX is enabled in WSO2 Carbon. Therefore, the WSO2 Application Server facilitates JMX-based monitoring. Some of the monitoring and management capabilities available in the Application Server's Management Console are also exposed via JMX. | ||
WS-* and REST support | The WSO2 Application Server (AS) supports most of the WS specifications including WS-Security, WS-Trust, WS-Policy, WS-Secure Conversation, WS-Reliable Messaging, WS-Discovery etc. AS also includes support for REST Web services via JAX-RS and WSDL 2.0 | |
UI, command line, and IDE-based tools for Web service and Web application development | You can develop Web services (such as, Axis2 , Data services etc.) and Web applications (such as, JAX-WS, JAX-RS and generic webappwebapps) via Developer Studio, which is an Eclipse plugin. Data Services can be developed via Management Console UI as well. | |
Equinox P2 based provisioning support | The user can install/update/uninstall features to/from a WSO2 Carbon-based products with WSO2 Carbon. | |
WSDL2Java/Java2WSDL/WSDL 1.1, and UI-based try it (invoke any remote Web service), TCPMon | The WSO2 Application Server ships these tools since these are very useful for web service developers. |
Page Comparison
Manage space
Manage content
Integrations