Branding the Web UI
- Last Updated: April 28, 2025
- 2 minute read
- Hybrid Data Pipeline
- Version 4.6
- Documentation
Hybrid Data Pipeline supports branding or white labeling the Web UI. Branding information is persisted in the CSS and properties files. The CSS file determines branding information such as colors, background, name, and logo. The properties file may be used to specify the browser window title and icon path. By modifying the CSS and properties files, you may brand the Web UI during or after the deployment of the Hybrid Data Pipeline server. Branding updates are persisted across upgrades.
Branding during installation or upgrade
- Download the sample CSS file from the following GitHub location: https://github.com/progress/Hybrid-Data-Pipeline/blob/main/Branding/hdp-branding.css.
- Download the sample properties file from the following GitHub location: https://github.com/progress/Hybrid-Data-Pipeline/blob/main/Branding/hdp-branding.properties.
- Update the sample files according to your specifications.
- Create a user-specified, external key location. See Shared files and the key location for details.
- Copy the
hdp-branding.cssandhdp-branding.propertiesfiles to the user-specified key location. - Run the installation program. When you run the installer, you should select the Custom installation type. This will allow you to specify the external key location you created. See Installing and upgrading the Hybrid Data Pipeline server for more information.
- Run the installation program on each node that will be running the service.
Note: To brand the Web UI, you must select the
Custom installation type and specify an external key location. You
cannot brand the Web UI using the Typical
installation type or the default key location.
Branding after installation or upgrade
- Update the
hdp-branding.cssfile in the user-specified, external key location. The sample CSS file can be found in the install folder.../ddcloud/samples/branding/hdp-branding.css. - Update the
hdp-branding.propertiesfile in the user-specified, external key location. The sample properties file can be found in the install folder.../ddcloud/samples/branding/hdp-branding.properties. - Restart the Hybrid Data Pipeline server. For cluster deployments, restart the server on each
node in the cluster.
- Run the stop service
script.
./install_dir/ddcloud/stop.shNote: Shutting down Hybrid Data Pipeline can take a few minutes. Wait until you see the Shutdown complete message displayed on the console before taking any additional actions. - Run the start service script.
./install_dir/ddcloud/start.sh
- Run the stop service
script.
Branding a Docker deployment
- Download the sample CSS file from the following GitHub location: https://github.com/progress/Hybrid-Data-Pipeline/blob/main/Branding/hdp-branding.css.
- Download the sample properties file from the following GitHub location: https://github.com/progress/Hybrid-Data-Pipeline/blob/main/Branding/hdp-branding.properties.
- Update the sample files according to your specifications.
- Create a shared file location. The shared file location is an external file location where keys and other information is persisted for one or more Docker containers. See Shared files and the key location for details.
- Copy the
hdp-branding.cssandhdp-branding.propertiesfiles to the shared file location. - Execute the Docker
runcommand to deploy Hybrid Data Pipeline. The command must specify the shared location to which you copied the CSS and properties files. See Deploying Hybrid Data Pipeline using Docker for details.