Update BI Configuration by Fabric Command
Updating the BI configuration in production can be performed manually, in the same way that it is updated in any other environment. However, to keep sensitive information safe, Fabric provides a command that automates this process.
Before starting this process make sure that PHP is installed on your BI server, as described in the Installation guide.
Do the following:
Go to the Configuration folder on the Production BI server: /opt/apps/exago/Config.
Backup the current WebReports.xml and WebReports.xml.enc files.
Copy the WebReports.xml from your source BI server (e.g. QA) here: /opt/apps/exago/Config.
Run the following commands:
> sudo chown apache:apache WebReports.xml
> sudo chmod 600 WebReports.xml
To start the configuration update process, run the command as follows:
> MOVE_TO_PROD_BI ENV = [ENV NAME]
This command carries out the following actions:
- Matches the BI's data sources to the Fabric interfaces on the given Environment by its name.
- Note that each data source defined in the Admin module must have a corresponding interface in Fabric with the same name, including a Fabric.
- Example: if BI includes two data sources named Fabric-Local and Postgres-Local, you must have Fabric interfaces with the same names.
- Data sources and interfaces that are not matched are skipped.
- For each match, take the connection details from the Fabric interface per the input Environment and populate them into the BI's configuration file WebReports.xml.
- If the Environment name is not provided in the command input, the connection details are taken from the active Environment.
- Once the connection details of all matched data sources are updated, create the updated encrypted WebReports.xml.enc file.
- Delete the unencrypted WebReports.xml file.
After the command execution is completed:
- Run the following commands:
> sudo chown apache:apache WebReports.xml.enc
> sudo chmod 777 WebReports.xml.enc
- Restart the BI server.
Update BI Configuration by Fabric Command
Updating the BI configuration in production can be performed manually, in the same way that it is updated in any other environment. However, to keep sensitive information safe, Fabric provides a command that automates this process.
Before starting this process make sure that PHP is installed on your BI server, as described in the Installation guide.
Do the following:
Go to the Configuration folder on the Production BI server: /opt/apps/exago/Config.
Backup the current WebReports.xml and WebReports.xml.enc files.
Copy the WebReports.xml from your source BI server (e.g. QA) here: /opt/apps/exago/Config.
Run the following commands:
> sudo chown apache:apache WebReports.xml
> sudo chmod 600 WebReports.xml
To start the configuration update process, run the command as follows:
> MOVE_TO_PROD_BI ENV = [ENV NAME]
This command carries out the following actions:
- Matches the BI's data sources to the Fabric interfaces on the given Environment by its name.
- Note that each data source defined in the Admin module must have a corresponding interface in Fabric with the same name, including a Fabric.
- Example: if BI includes two data sources named Fabric-Local and Postgres-Local, you must have Fabric interfaces with the same names.
- Data sources and interfaces that are not matched are skipped.
- For each match, take the connection details from the Fabric interface per the input Environment and populate them into the BI's configuration file WebReports.xml.
- If the Environment name is not provided in the command input, the connection details are taken from the active Environment.
- Once the connection details of all matched data sources are updated, create the updated encrypted WebReports.xml.enc file.
- Delete the unencrypted WebReports.xml file.
After the command execution is completed:
- Run the following commands:
> sudo chown apache:apache WebReports.xml.enc
> sudo chmod 777 WebReports.xml.enc
- Restart the BI server.
