Customizing the Web Interface

z/Scope Anywhere allows you to customize its web interface to match your organization’s branding. The customization mechanism uses a dedicated folder for your modified files and a configuration file that redirects requests from the original resources to your customized versions.

Logo and Image Customization

To modify the application logo:

Create a BrandingFiles folder within the web directory of the z/Scope Anywhere installation (typically at C:/Program Files/zScope Anywhere/web).
Place your custom logo in the BrandingFiles folder.
Create or edit the WebAliases.ini file in the installation’s bin32 directory with alias mappings that redirect default logo paths to your custom files:
```
[Alias]
/images/zawlogo_b.png=BrandingFiles\\MyLogo.png
/favicon.ico=BrandingFiles\\MyFavicon.ico
```
Restart the application to apply the changes.

Any line in the WebAliases.ini file starting with a semicolon is treated as a comment and ignored by the application. You can substitute any interface image or file using the same methodology. If the browser favicon does not update, clear the browser cache and reload.

Structure and Style Customization

For more advanced modifications that involve changes to HTML, CSS, or other web files:

Create a BrandingFiles folder within the web directory of the z/Scope Anywhere installation (typically at C:/Program Files/zScope Anywhere/web).
Copy the original web files that you want to modify into the BrandingFiles folder. Copy only the files to be modified, without their associated folder structure.
Edit the files according to your preferences.

Create or update the WebAliases.ini file in the bin32 installation directory:

[Alias]
/index.html=BrandingFiles\\my_index.html
/css/index.css=BrandingFiles\\my_index.css

Launch the application to verify your customizations.

File paths within HTML, CSS, and other content remain relative to their original locations, so you do not need to update internal path references.

Files Location

It is recommended to keep your customized files in a separate folder rather than mixing them with the original files. This approach lets you revert to the original settings at any time and protects your customizations during version upgrades.

Within the Webroot Directory

Files stored inside the webroot become externally accessible via URL (for example, https://127.0.0.1/BrandingFiles/customizedFile.html). The WebAliases.ini configuration supports relative path references:

[Alias]
/images/zawlogo_b.png=BrandingFiles\\MyLogo.png

This option is simpler to configure but means the customized files are publicly accessible.

Outside the Webroot Directory

Storing the BrandingFiles folder outside the webroot requires absolute file paths in WebAliases.ini:

[Alias]
/index.html=c:/BrandingFiles/my_index.html
/images/zawlogo_b.png=c:/BrandingFiles/MyLogo.png

The files are protected because they cannot be accessed directly from a URL, but the configuration is more complex due to the absolute paths.