Table of Contents |
---|
Implementation Overview
WSO2 Identity Server (IS) 5.0.0 is 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.
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.
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 IS as a Service
Deploy WSO2 IS 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 Kubernetes.
Note |
---|
Make sure that you note the points given below when running WSO2 Identity Server as a Key Manager:
|
Deployment Architecture
The diagram illustrates the deployment architecture of WSO2 IS on Private PaaS. In the deployment, a Private PaaS cluster will be created for the IS manager.