This documentation is for WSO2 App Manager 1.0.0. View documentation for the latest release.
Architecture - App Manager 1.0.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

The WSO2 App Manager comprises of the following main components:

App Publisher 

Provides an end-user, collaborative web interface for web application providers to publish Apps, share documentation, and gather feedback on the quality and usage of Apps. The App Publisher is powered by Jaggery, WSO2 Governance Registry and WSO2 Identity Server.

For more information on App Publisher and its functionality, see App Publisher Guide.

App Store 

Provides an end-user, collaborative web interface for end users of web applications to self-register, discover Apps, subscribe to Apps, and evaluate them. The App Store is powered by Jaggery, WSO2 Governance Registry and WSO2 Identity Server products.

For more information on the App Store and its functionality, see App Consumer Guide.  

Web App Gateway

A runtime, back-end component developed using the WSO2 ESB, which is proven for its performance capability. Web App Gateway secures, protects, manages, and scales App calls. The App Gateway is a simple App proxy that intercepts App requests and applies policies such as throttling and security checks. It is also instrumental in gathering App usage statistics. A set of handlers are used for security validation and throttling purposes in the App Gateway. Upon validation, it passes web service calls to the actual back-end.

The App Gateway is accessible through the URL: https://localhost:9443/carbon, once the App Manager server is up and running.

You can integrate a monitoring and statistics component to the App Manager without any additional configuration effort. This monitoring component integrates with the WSO2 Business Activity Monitor, which can be deployed separately to analyze events generated by the App manager. For more information, see Publishing App Manager Runtime Statistics.

Although the App Gateway contains ESB features, it is recommended not to use it for ESB-specific tasks, and to use it only for the Gateway functionality related to App invocations. For example, if you want to call external services like SAP, use a separate ESB cluster.

App Handlers

When an App is published, a file with its synapse configuration is created on the Web App Gateway. The synapse configuration of each App has a set of handlers. Each of these handlers is executed on the Apps in the order in which, they appear in the configuration.

You can find a set of default handlers in any App Synapse definition as shown below:

<handler class="org.wso2.carbon.appmgt.gateway.handlers.proxy.ReverseProxyHandler"/>
<handler class=""/>
<handler class=""/>
<handler class="org.wso2.carbon.appmgt.gateway.handlers.throttling.APIThrottleHandler">
<property name="id" value="A"/>
<property name="policyKey" value="gov:/apimgt/applicationdata/tiers.xml"/>
<handler class="org.wso2.carbon.appmgt.usage.publisher.APPMgtUsageHandler"/>

The functionality of each handler will be as follows:

  • ReverseProxyHandler : This adds the existing cookies of the Apps to the new context, as end users will be accessing a proxy of the Apps through App Manger. 

  • SAML2AuthenticationHandler : Validates the SAML2 token used to invoke the App. To extend the default authentication handler, see Writing Custom Authentication Handlers.
  • EntitlementHandler : 
  • APIThrottleHandler : Throttles requests based on the throttling policy specified by the policyKey property. Throttling is applied at the subscription level.
  • APPMgtUsageHandler : Publishes events to BAM and Google Analytics for collection and analysis of statistics. This handler only comes to effect if App usage tracking and Google analytics tracking are enabled. For more information, see Publishing App Manager Runtime Statistics and Integrating with Google Analytics.

The following diagram depicts the collaboration of these main components with an easily-integrable monitoring component.

  • No labels