These instructions apply only to ICA available from Patriot Version 6.6.26 onwards.
ICA can be customised to use your company's own branding as well as that of your dealers.
Which set of branding to use can be configured based on the URL used to access the site.
This document will describe what can be configured and how to do so.
Before beginning ICA customisation, please ensure that the following step from the ICA Installation procedure was followed when ICA was installed:
Run IIS Manager. Select the server, then select Configuration Editor. Select the Webserver/proxy section. Find the key labed "preserveHostHeader" and set it to True.
This document will refer to your Patriot storage directory. For most systems this will be the Patriot Data Service install directory (i.e. "C:\Program Files (x86)\Patriot Systems\Patriot Data Service") however if you are using High Availability then storage directory refers to your configured LocalStorageDirectory.
Create a folder named ICA_Customisations and a file named ICA_Customisations.xml in your storage directory. Any files placed in the ICA_Customisations folder will be publicly available via www.{yoururl}.com/customisations/{filepath} this is where any files used for customisation should be placed.
The ICA_Customisations.xml file defines what customisations to apply based on what URL is used to access ICA. Example contents of ICA_Customisations.xml is as follows:
<?xml version="1.0"?>
<BrandingDefinitions>
<BrandingDefinition HostName="ica.abcdealer.com">
<FavIconUrl>abc/favicon.ico</FavIconUrl>
<NavbarIconUrl>abc/brand.png</NavbarIconUrl>
<LoginHeaderHtmlUrl>abc/login_header.html</LoginHeaderHtmlUrl>
<HeaderHtmlUrl>abc/header.html</HeaderHtmlUrl>
</BrandingDefinition>
<BrandingDefinition>
<SiteName>Alarm
Portal</SiteName>
<FavIconUrl>favicon.ico</FavIconUrl>
<NavbarIconUrl>brand.png</NavbarIconUrl>
<LoginHeaderHtmlUrl>login_header.html</LoginHeaderHtmlUrl>
<HeaderHtmlUrl>header.html</HeaderHtmlUrl>
</BrandingDefinition>
</BrandingDefinitions>
The urls in the above definition (i.e "favicon.ico", "abc/favicon.ico", "header.html" etc.) should refer to files placed in the ICA_Customisations folder.
In the example above 2 sets of branding details are configured:
As many BrandingDefinition blocks can be added as necessary.
Note that in the above example SiteName is not specified in the top block. This will result in the sitename from the default block to be used (i.e. "Alarm Portal").
For the above example the file structure would be as follows:
Sets the name displayed in the browser's title bar:
Sets the icon displayed in the browser's title bar.
Sets the image which will be displayed in the top left of each page (once logged in):
Sets a piece of partial html which will be displayed above the login form.
Setting this to refer to an html file with the following content:
would result in the following login page:
This can refer to a piece of partial html which will be displayed above the navigation bar once a user is logged in.
Setting this to a url pointing to an html file with the following content:
Would result in the following page header:
All text on the Patriot ICA website can be translated in the same manner as the Patriot Windows Client. Please refer to the guide here for instructions on translating Patriot. Once your translation is complete, copy the langauge folder (e.g. German Language "de") into the Data Service installation folder, and then, in the same folder, edit the file locale-data\languages.json and add your new translation language abbreviation to the supported languages list:
Now when an end-user refreshes or connects to the ICA website with their browser language set to one of your supported languages, the ICA web site will display your translated phrases in place of the default English.