Last Edited: September 28th, 2011
This article sets out the configuration details that Triaster require for a successful process library installation. Triaster's default installation path is the C:\ drive of any machine, although it is common for us to change this to a drive letter of your choosing.
To view our minimum installation requirements click here
The Triaster solution requires up to 3 server roles. These can be either 3 physical/virtual servers or one server performing 3 roles. How many servers are going to be in use?
The three roles that are required are:
This server hold the maps created by the mapping team using Process Navigator. Maps are stored in a directory structure specific to your organisation. If the file store is to be on a different server, we require access to be mapped to it. Whilst not mandatory it is helpful that the letter used by the users is recorded. The file store requires Read/Write/Modify access.
This server performs the conversion of the Visio maps into HTML content. As already mentioned this can be a separate machine to the file store and Web server
The Triaster solution does not need its own dedicated IIS server, although it does need IIS version 6 or above and .NET version 2.0 or over. If Triaster are going to share the server with other applications, we will create a new virtual directory for the library. If SharePoint is installed on this server, then SharePoint's website content must be stored on a different IIS website to the Browser Toolkit.
The publication wrapper is the tool used by Triaster to start the conversion (or publication) to the website of the Visio files to HTML. Upon finishing a publication an email is sent to an address to notify the user of successful completion or if there were any failures. In the event of a failure occurring during publication it is an option to send Triaster Support the log. The email includes a log file stating exactly what has happened. Triaster support with then respond if it is not a simple error easily rectified by reading the log file. A copy of the logs are also saved on the server. Triaster require a service account to be set up on the publication server with a password that does not expire. This password will need to be given to Triaster for use during the installation or a user will need to be present to enter it on Triaster's behalf. Triaster do not store customer passwords.
Triaster as standard gives technical support remotely which method of entry can Triaster use?