The Identity of a Triaster Server

 This article is suitable for a Library Administrator

Ref: 201412161141
Last Edited: August 7th, 2017

In the context of this article, a Triaster Server’s identity could be its computer name or an alias. Perhaps the most obvious manifestation is in the addresses of the process library websites, e.g. 2011/triaster sample library


Minimise the dependency on identity

Wherever possible, it’s best to avoid the explicit use of a Triaster Server’s name or alias when configuring Triaster Server or forming links between maps or documents within a process library. Doing so will mean maps and associated data can easily be copied to another Triaster Server, and links will remain valid. This is important when copying data to Disconnected Servers, which host read-only copies of process library data. It also simplifies the changing of a Triaster Server’s identity, whether its computer name or the changing or adoption of an alias.

Some explicit references to a host are necessary. For example, an alert e-mail that contains a link to library content would need that link to be fully-qualified. Any item that is outside of a Triaster Server but needs to link in would require it; items that reside within a Triaster Server shouldn’t.

Hyperlinks to maps

Hyperlinks between maps, such as drill-down links, should automatically be changed to relative links by the export engine, if necessary, when maps are published. Hence, if a set of maps is transferred from one server to another, the links between them should remain valid.

Links to maps in a Flash Menu XML file should be relative, typically prefixed ‘../html/’.

<item name="Sample Map" url="../html/sample%20maps.html" />

Hyperlinks to documents

A hyperlink from a map or a Flash Menu XML file to a document could be of the form: Document.doc

but would be better expressed as:

/Documents/My Document.doc

Note the preceding forward-slash, which denotes the path is relative to the root of the website. Not only is this URL independent of the host identity, it would remain valid if the protocol were to change from HTTP to HTTPS. A slight disadvantage is that such a link is unlikely to work from a Visio file, but that’s only relevant when developing maps, not when they are published.

Changing a server’s identity

A server’s identity may be changed where:
  • An alias is to be used in website URLs.
  • The server’s computer name is to be changed.
  • One Triaster Server is created as a copy of another (creating a production server from a test server, or vice versa), and the copy’s identity needs to change.

When changing a server’s identity, these are the configuration changes that would need to be made.



This is the main configuration file, and any changes should be preceded by taking a copy that could be restored.

  • This is the server’s identity as a Publication Server as seen by Triaster Server’s Token Server service, and should correspond to an entry in the Token Server’s Server List.
  • It doesn’t have to correspond to a server’s computer name, but for consistency and clarity, it should.
  • This needn’t change if just adopting the use of an alias for website URLs.

  • This should correspond to the ‘ServerName’ above.

  • The fully-qualified URLs are pertinent to the construction of links from e-mails to a process library.
  • These should change whether changing the computer name or using an alias.



  • URLs need to change.


MTop INI Files

  • Only necessary in earlier versions of Triaster Server where MTop is the active search mechanism. In later versions, MTop has been superseded by Keyoti.
  • There are unlikely to be any host-specific references, particularly in later implementations, but that should be checked.




  • URLs need to change.



Triaster\TriasterServer2011\ProcessLibraries\<Library>\<Site>\static html\flash-menu.xml
  • These may contain explicit references, but needn’t.


So in the simplest case of adopting the use of an alias, all that should need changing are the site-scoped URL settings in ‘Settings.xml’ and host references in ‘Libraries.xml’ and 'indexableSourceRecord.xml'.

By restricting the use of a Triaster Server’s identity to things that work from outside a Triaster Server, content within is made more portable, and the identity itself is easier to manage.

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