| Table of Contents |
|---|
Implementation Overview
WSO2 API Manager (AM) 1.9.0 and 1.9.1 are provided as a service on WSO2 Private PaaS 4.1.0. This is implemented by creating the following:
Template module
Panel borderColor #71CFF5 borderWidth 2 The template module configures the product in runtime, with a set of key value pairs known as the configuration parameters.
The template module provides a set of templates that is used to configure the specific product with the Configurator.
Cartridge agent plugin
Panel borderColor #71CFF5 borderWidth 2 The cartridge agent plugin, sets the runtime configuration parameters such as hostnames, IP addresses of dependent clusters, dynamic proxy ports and many more.
The plugin configures the following and many more:
server hostname- cluster discovery parameters
- proxy ports
Docker image
Panel borderColor #71CFF5 borderWidth 2 The Docker image is built by packaging the following components:
Cartridge agent
Product distribution
Template module
Configurator
Java runtime
Puppet module
Panel borderColor #71CFF5 borderWidth 2 The puppet module includes the same set of component as in the Docker image. In the puppet image the template module is used to configure automation.
...
Deploying WSO2 API Manager as a Service
Deploy WSO2 API Manager as a service using one of the following methods.
- Deploy the application on Private PaaS when running on a Virtual Machine.
- Deploy the application on Private PaaS when running on
...
Deployment Architecture
The deployment architecture is designed to support different deployment patterns of API manager, within the the API manager application. It consists of two cartridge groups as shown below:
...