The newly introduced Configurator component aims to tackle the cumbersome task of product and instance configuration with complex requirements. In the case of a Cartridge instance, there are numerous run-time factors that you need to take into account for the correct configuration to take place. Some of these factors include clustering and database information, the role of the Cartridge type in the clustering context and even the role of the Cartridge on the product specific distributed setup (such as that of WSO2 API Manager). The Configurator simplifies these factors into a simple module.ini
file, which includes all the parameters that are configurable in that specific Cartridge. Thereby, you can use the configurator to seamlessly automate the configuration process that needs to be carried out when configuring Private PaaS and its cartridges.
Table of Contents | ||||
---|---|---|---|---|
|
Template Module
The Configurator operates on a set of configuration templates, which are referred to as a Template Module
. A Template Module should be of the following folder structure and should contain the files and templates, which are needed to configure the specific Cartridge.
...
The Configurator is hosted on the Private PaaS Cartridge Repository. When running the configurator you have to point to the location of the template module. It will look for the module.ini
file, read the configuration values, process the templates inside templates
folder, and copy the processed templates and the files inside files
folder to the CARBON_HOME
. For details steps on running the configurator, see Running the Configurator with the Template Module.