We are going to describe this setup assuming the scenario described below. Note that you will need to adjust the rest of the commands in this document to suit your environment (mostly host names and IPs).
|Machine||Host name||IP Address|
|Abiquo Monolithic & Apache2 SSL front-end|
|Datacenter2 Remote Services||dc2rs.example.com||192.168.1.150|
# tree /var/www/html/ui/ /var/www/html/ui/ ???|-- config ?| ???|-- client-config.json ?| ???|-- tutorials ... ???|-- theme ?| ???|-- abicloudDefault ...
We need to create a configuration file and theme folder per subdomain. In the sample scenario the structure will look like:
# tree /var/www/html/ui/ /var/www/html/ui ???|-- config ?| ???|-- theme1.json ?| ???|-- theme2.json ... ???|-- theme1 ... ???|-- theme2 ...
You can have different property configuration in each config json file, but it is very important that the config.endpoint property points to its related API subdomain URL:
# tree /etc/httpd/conf.d/ /etc/httpd/conf.d ???|-- api.conf ???|-- theme1.conf ???|-- theme2.conf
First of all you need to change api.conf. This VirtualHost configuration file will group SSL access for all Abiquo Appliance Manager webapps and the API endpoint: (api.conf)