Last Edited: December 16th, 2014
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.
http://processlibraries.triaster.co.uk/processlibraries 2011/triaster sample library
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 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" />
A hyperlink from a map or a Flash Menu XML file to a document could be of the form:
but would be better expressed as:
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.
A server’s identity may be changed where:
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.
MTop INI Files
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.txt’ 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.