IT Administrators‎ > ‎Installation‎ > ‎

Migrating from the Test Server to the Live Server

 This article is suitable for an IT Adminstrator

Ref: 201101121531
Last Edited: 14th August 2013


This document is intended to describe how to migrate from the use of a test Triaster server to a live server.
It's assumed that the Triaster Server software has been installed and configured on the live server as described in the configuration documentation referenced below. Migrating to its use should then be primarily copying or moving content, and perhaps replacing some configuration files. The source of the various content may depend on whether the test server was used to host production content, and whether there's an existing live server that's being replaced.



Process Maps and Menu Pages

Ensure the live server will use a current copy of the process maps and menu pages (Visio files). Current maps and menu pages may presently be hosted on:
  • a test server
  • a current live server
  • a separate file server

Process Maps and Menu Pages to be Hosted on the Live Server

If the process maps and menu pages are to be hosted on the live server, then they should be copied to the map store, typically:
Triaster\Map Store\ProcessLibrary\
1 Draft Maps\
Sandpit maps\
Prelive Maps
Live Maps\
Menu Pages\
There may be libraries other than 'ProcessLibrary' in 'Map Store'; all such libraries will probably need to be included.

Process Maps and Menu Pages to be Hosted on a Separate File Server

If the process maps and menu pages are to be stored on a separate file server, perhaps continuing to use the existing maps repository, then the live server needs to be configured to use them. If this hasn't been done already, when configuring the Publication Server on the live server, then do so as follows:
  1. On the live server, run the Triaster Publication Server Configuration Utility, typically:

    "C:\Program Files\Triaster\PublicationServer\PublicationWrapper\PubServerConfig.exe"
  2. Click on the '3. Publication Tasks Configuration' tab.
  3. For each site in the 'Site settings for update' list:
    1. Set 'Process Maps Path' to the appropriate maps repository.
    2. Set 'Menu Page Maps Path' to the appropriate menu pages repository.
    3. Click 'Apply' after each configuration.
  4. Click OK.


Dynamic Home and Menu Pages

If sites use dynamic home and menu pages (Flash-based), then ensure changes that may have been made on the test server, and which should be applied to the live server, are implemented.
Menu configurations are made through 'flash-menu.xml' files, typically found in:
 Live\static html\
 Prelive\static html\
 Sandpit\static html\
If there are libraries other than 'ProcessLibrary', then these need to be considered too.
If the dynamic menu system on the test server is to be replicated on the live server, then copy the 'flash-menu.xml' files from the test server to the corresponding locations on the live server.

Search Filter Lists

There are lists of items that are used to filter the Ownership, Roles and Systems search reports. These lists are in 'config.xml' files commonly found in these locations:
These lists can be customised. If the lists on the test server have been amended, and correspond to the lists which should be implemented on the live server, then copy the 'config.xml' files from the test server to their corresponding locations on the live server.

Site URLs

There may be URLs that target the current live server or test server that should now target the new live server. For example, '', where 'processlibraries' is an alias that needs to be redefined to point to the new live server.

Process Navigator Users' Configurations

Map Store

If the map store has changed, which it will have done if it's hosted on the new live server, then Process Navigator users, i.e. those who create and edit the Visio process maps, will need to be informed. Drive mappings that are associated with the old map store should be redefined.

Template, Stencil and Properties File Store

The Visio template and stencil, and the properties XML file, are often located in a shared location, particularly if these files have been customised. They may reside on a separate file server, in which case, they can remain there. However, if this shared location is on a server which will no longer be used with the Triaster process mapping system, then it ought to be moved.
This shared location is commonly a 'Config Files\Desktops' folder.

Need further help? Contact the Triaster Support team by e-mailing 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