IT Administrators‎ > ‎Installation‎ > ‎

Branding a Process Library

 This article is suitable for an IT Adminstrator
 
Ref: 201009241009
Last Edited: 14th August, 2013

Branding the Process Library on a Triaster Server 10.1

Assessment of content

If performing an upgrade, then required folders from Previous Triaster Version archive (if an archive has been taken) or from the old system, are:

  1. \Publication Server\Config Files
  2. \Web Server\ProcessLibrary\Live\Tools
  3. \Web Server\ProcessLibrary\Prelive\Tools
  4. \Web Server\ProcessLibrary\Sandpit\Tools
  5. \Web Server\ProcessLibrary\Live\static html
  6. \Web Server\ProcessLibrary\Prelive\static html
  7. \Web Server\ProcessLibrary\Sandpit\static html
  8. \File Store\Menu Pages

    If performing an install or a rebrand then the required files are on your custom files page:

    1. static html.zip
      The key files contained in this file are as follows:
      • Header.html
      • Header.css
      • Toolset.css
      • All of the required image and flash files required for the customers branding.
    2. publish.css (may be contained in static html.zip)
    3. <company name> Template.vtx
    4. <company name> Stencil.vss
    5. <company name> Properties.xml
    6. Homepage.vdx
    7. Any custom Visio sub-menu pages

    Static HTML

    Navigation bar content only

    If you do not have Flash content and you are upgrading then:
    1. Copy in all content, including sub-folders, originating in "<Library>\Live\static html" on the server apart from:
         
      all mismatched deliverables.html
      how to.html
      list of libraries.html
      performance summary 2.html
      performance summary.html
      priority mismatched deliverables.html
      publish checklist.html
      revision history.html
      table of contents.html
        
      to all instances of \<ProcessLibraries>\<Library>\<Site>\static html where <ProcessLibraries>=the name of the ProcessLibraries folder, <Library>=Library name, <Site>=site name.

    Flash homepage and Navigation bar content

    If you have Flash content and you are upgrading:

    1. Copy in all content, including sub-folders, originating in "<Library>\Live\static html" on the server apart from:
      all mismatched deliverables.html
      how to.html
      list of libraries.html
      performance summary 2.html
      performance summary.html
      priority mismatched deliverables.html
      publish checklist.html
      revision history.html
      table of contents.html
       
      to all instances of "\<ProcessLibraries>\<Library>\<Site>\static html", where <ProcessLibraries>=the name of the ProcessLibraries folder (e.g. 'ProcessLibraries'), <Library>=Library name (e.g. 'ProcessLibrary'), <Site>=site name (e.g. 'Live', 'Prelive' or 'Sandpit').
         
    2. TRIASTER SERVER 10.1 AND PREVIOUS ONLY - Modify index.htm in each of the "\<ProcessLibraries>\<Library>\<Site>\" folders to forward to "static html/homepage.html" rather than "html/homepage.html".
        
      <meta http-equiv="refresh" content="0; URL=static html/homepage.html">
        
    Note:
     
    The home page may be named something other than 'homepage.html', e.g. 'sitehome.html', depending on the implementation.
     

    Moving Process Map content into location

    Copy customer process maps in to:

    \Map Store\ProcessLibrary\1 Draft Maps
    \Map Store\ProcessLibrary\Sandpit Maps
    \Map Store\ProcessLibrary\Prelive Maps
    \Map Store\ProcessLibrary\live Maps

     

    Moving Menu pages content into location

    Copy in content originating in "\Menu Pages\" to the corresponding locations in "\Map Store\ProcessLibrary\Menu Pages".
     

    Configuring the publication style sheets

    The publication style sheets are CSS files that determine some of the formatting of the published HTML.
     
    Copy publish.css originating in "<Config Files>\Live" on the old server to the following locations on the new server:
    <PublicationServer>\Config Files\ProcessLibrary\Live
    <PublicationServer>\Config Files\ProcessLibrary\Prelive
    <PublicationServer>\Config Files\ProcessLibrary\Sandpit
    (where '<PublicationServer>\Config Files' is typically "C:\Program Files\Triaster\PublicationServer\Config Files".)
     

    Configuring the publication framesets

    The publication framesets are HTML frameset files within which the published HTML is hosted. The top-most frame hosts the navigation bar, and may need to be resized to fit properly.
    1. Note the frame height necessary to host the navigation bar correctly.
        
      1. Locate the original frameset file from the Live site of the old installation - '<Config Files>\Live\frameset.html'.
         
      2. Open that frameset file in Notepad.
           
      3. Note the height of the first frame, given in a line such as this:
      <frameset rows="44,*" border="0" framespacing="0" frameborder="0">
        
      (In this example, the height of the first frame is 44.)
       
      Please note that in Prelive and Sandpit there will be 3 rows like this:
       
      <frameset rows="20, 44,*" border="0" framespacing="0" frameborder="0">
       
      These 3 rows need to be maintained in order to maintain the disclaimer bar appearance, in this case it is the middle number you need to change.
       
    2. Check, and amend if necessary, the frameset.html file in each of these locations on the new server:
      <PublicationServer>\Config Files\ProcessLibrary\Live
      <PublicationServer>\Config Files\ProcessLibrary\Prelive
      <PublicationServer>\Config Files\ProcessLibrary\Sandpit
      1. Open frameset.html in Notepad.
          
      2. Check, and amend if necessary, the height of the first frame.
         
    3. Delete all HTML content on all affected sites.
    4.  
    5. Run a new publication on all affected sites.

     

    Please click here to go back to the top of the page 

    Configuring the tools framesets

    The various tools, such as the Search features, are also hosted within a frameset. To configure this:
    1. Open '<WebServer>\ProcessLibraries\frames config.xml' in Notepad.
        
    2. There are several lines of the form:
       
      <frame name="top" rowheight="44" path="../../processlibraries/processlibrary/live/static html/nav.html" />
       
      Check, and amend if necessary, the rowheight value. It should be the same as that set for the publication framesets.
     

    Configuring lists for the search filters

    There are lists of roles, owners and systems that are used to filter search reports. These lists are often customised, so would usually need to be implemented in the new system.
    1. Update the roles lists.
        
      1. Locate the old roles list file, which is expected to be '<ProcessLibrary>\Live\Tools\Roles\config.xml'.
          
      2. Open that config.xml file in Notepad.
          
      3. Locate the corresponding roles list file in the new system, which would be something like '<ProcessLibraries>\ProcessLibrary\Live\Tools\Roles\config.xml'.
          
      4. Open that config.xml file in Notepad.
          
      5. Ensure the SearchPhrase items in the new config.xml file match those of the old one.
        See this article for more detail: How to Edit the Roles, Ownership and Systems Lists.
          
      6. Similarly, check the list files for the Prelive and Sandpit sites. If the lists for those sites are the same as that for Live, then the config.xml file in the Live site could be copied to the Prelive and Sandpit sites.
          
      7. Set the width of the filter frame, as described in this article:
    2. Update the ownership lists.
        
      The procedure is the same as that for roles, but using the config.xml files in the 'Ownership' folders.
        
    3. Update the systems lists.
        
      Again, the procedure is the same as that for roles, but using the config.xml files in the 'Systems' folders.
        

    Note:

    These config.xml files in Triaster Server 10.1 allow the width of the left-hand filter frame pane of the Search windows to be configured, whereas those in earlier versions will not. Therefore, the newer versions of these config.xml files shouldn't be overwritten with earlier ones. It is better that the content is updated.
     

    Branding the Process Library on a Triaster Server 11.2

    Assessment of content

    If performing an upgrade, then required folders from Previous Triaster Version archive (if an archive has been taken) or from the old system, are:

    1. \Publication Server\Config Files
    2. \Web Server\ProcessLibrary\Live\Tools
    3. \Web Server\ProcessLibrary\Prelive\Tools
    4. \Web Server\ProcessLibrary\Sandpit\Tools
    5. \Web Server\ProcessLibrary\Live\static html
    6. \Web Server\ProcessLibrary\Prelive\static html
    7. \Web Server\ProcessLibrary\Sandpit\static html
    8. \File Store\Menu Pages
      If performing an install or a rebrand then the required files are on your custom files page:
      1. static html.zip 
        The key files contained in this file are as follows:
        • Header.html
        • Header.css
        • Toolset.css
        • All of the required image and flash files required for the customers branding.
      2. publish.css (may be contained in static html.zip)
      3. <company name> Template.vtx
      4. <company name> Stencil.vss
      5. <company name> Properties.xml
      6. Homepage.vdx
      7. Any custom Visio sub-menu pages.

      Static HTML

      Navigation bar content only

      If you do not have Flash content and you are upgrading then:
      1. Copy in all content, including sub-folders, originating in "ProcessLibrary\Live\static html" on the server apart from:
        all mismatched deliverables.html
        how to.html
        list of libraries.html
        performance summary 2.html
        performance summary.html
        priority mismatched deliverables.html
        publish checklist.html
        revision history.html
        table of contents.html
        to all instances of \<ProcessLibraries>\<Library>\<Site>\static html where <ProcessLibraries>=the name of the ProcessLibraries folder, <Library>=Library name, <Site>=site name.

      Flash homepage and Navigation bar content

      If you have Flash content and you are upgrading:

      1. Copy in all content, including sub-folders, originating in "ProcessLibrary\Live\static html" on the server apart from:
        all mismatched deliverables.html
        how to.html
        list of libraries.html
        performance summary 2.html
        performance summary.html
        priority mismatched deliverables.html
        publish checklist.html
        revision history.html
        table of contents.html
        to all instances of "\<ProcessLibraries>\<Library>\<Site>\static html", where <ProcessLibraries>=the name of the ProcessLibraries folder (e.g. 'ProcessLibraries'), <Library>=Library name (e.g. 'ProcessLibrary'), <Site>=site name (e.g. 'Live', 'Prelive' or 'Sandpit').
      2. Modify index.htm in each of the "\<ProcessLibraries>\<Library>\<Site>\" folders to forward to "static html/homepage.html" rather than "html/homepage.html".
        <meta http-equiv="refresh" content="0; URL=static html/homepage.html">
      Note:
      The home page may be named something other than 'homepage.html', e.g. 'sitehome.html', depending on the implementation.

      Moving Process Map content into location

      Copy customer process maps in to:

      \MapStore\ProcessLibrary\1 Draft Maps
      \MapStore\ProcessLibrary\Sandpit maps
      \MapStore\ProcessLibrary\Prelive maps
      \MapStore\ProcessLibrary\live maps

      Moving Menu pages content into location

      Copy in content originating in "\Menu Pages\" to the corresponding locations in "\Map Store\ProcessLibrary\Menu Pages".

      Configuring the publication style sheets

      The publication style sheets are CSS files that determine some of the formatting of the published HTML.
      Copy publish.css originating in "<Config Files>\Live" on the old server to the following locations on the new server:
      <PublicationServer>\Config Files\ProcessLibrary\Live
      <PublicationServer>\Config Files\ProcessLibrary\Prelive
      <PublicationServer>\Config Files\ProcessLibrary\Sandpit
      (where '<PublicationServer>\Config Files' is typically "C:\Program Files\Triaster\PublicationServer\Config Files".)

      Configuring the publication framesets

      The publication framesets are HTML frameset files within which the published HTML is hosted. The top-most frame hosts the navigation bar, and may need to be resized to fit properly.
      1. Note the frame height necessary to host the navigation bar correctly.
         
        1. Locate the original frameset file from the Live site of the old installation - '<Config Files>\Live\frameset.html'.
        2. Open that frameset file in Notepad.
           
        3. Note the height of the first frame, given in a line such as this:
        <frameset rows="44,*" border="0" framespacing="0" frameborder="0">
        (In this example, the height of the first frame is 44.)
        Please note that in Prelive and Sandpit there will be 3 rows like this:
        <frameset rows="20, 44,*" border="0" framespacing="0" frameborder="0">
        These 3 rows need to be maintained in order to maintain the disclaimer bar appearance, in this case it is the middle number you need to change.
      2. Check, and amend if necessary, the frameset.html file in each of these locations on the new server:
        <PublicationServer>\Config Files\ProcessLibrary\Live
        <PublicationServer>\Config Files\ProcessLibrary\Prelive
        <PublicationServer>\Config Files\ProcessLibrary\Sandpit
        1. Open frameset.html in Notepad.
           
        2. Check, and amend if necessary, the height of the first frame.
           
      3. Delete all HTML content on all affected sites.
      4. Run a new publication on all affected sites.

      Please click here to go back to the top of the page

      Configuring the tools framesets

      The various tools, such as the Search features, are also hosted within a frameset. To configure this:
      1. Open '<WebServer>\ProcessLibraries\frames config.xml' in Notepad.
         
      2. There are several lines of the form:
         
        <frame name="top" rowheight="44" path="../../processlibraries/processlibrary/live/static html/nav.html" />
         
        Check, and amend if necessary, the rowheight value. It should be the same as that set for the publication framesets.

      Configuring lists for the search filters

      There are lists of roles, owners and systems that are used to filter search reports. These lists are often customised, so would usually need to be implemented in the new system.
      1. Update the roles lists.
         
        1. Locate the old roles list file, which is expected to be '<ProcessLibrary>\Live\Tools\Roles\config.xml'.
           
        2. Open that config.xml file in Notepad.
           
        3. Locate the corresponding roles list file in the new system, which would be something like '<ProcessLibraries>\ProcessLibrary\Live\Tools\Roles\config.xml'.
           
        4. Open that config.xml file in Notepad.
           
        5. Ensure the SearchPhrase items in the new config.xml file match those of the old one.
          See this article for more detail: How to Edit the Roles, Ownership and Systems Lists.
           
        6. Similarly, check the list files for the Prelive and Sandpit sites. If the lists for those sites are the same as that for Live, then the config.xml file in the Live site could be copied to the Prelive and Sandpit sites.
           
        7. Set the width of the filter frame, as described in this article:
      2. Update the ownership lists.
         
        The procedure is the same as that for roles, but using the config.xml files in the 'Ownership' folders.
         
      3. Update the systems lists.
         
        Again, the procedure is the same as that for roles, but using the config.xml files in the 'Systems' folders.
         

      Note:

      These config.xml files in Triaster Server 10.1 allow the width of the left-hand filter frame pane of the Search windows to be configured, whereas those in earlier versions will not. Therefore, the newer versions of these config.xml files shouldn't be overwritten with earlier ones. It is better that the content is updated.
        
      Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on + 44 (0)870 402 1234.
       
      Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk 
      Comments