This article applies to Total Control Premier version 2.11 and higher - screenshots are taken from Total Control Premier version 2.11.
Before You Begin
Total Control Premier Cloud Edition is a web application running on Internet Information Services, as a front end to the Total Control Premier database. The server will need access to the Total Control Premier SQL Server database, and it will also need to be accessible from any desktop, laptop or tablet on the network that requires access to the application. Typically this means opening firewall access to port 8080, or whichever port is bound as per the Web Site Bindings detailed below. An SMTP server is required for sending activation emails as new users are created, and this can be internal such as an on-premises Exchange server, or external such as Office 365 or Gmail.
If Internet Information Services is not enabled, the Total Control Premier InstallShieldWizard will attempt to enable the feature as detailed in the IIS Setup section below.
Total Control Premier Installation
Total Control Premier Cloud Edition is installed as a Custom Feature of Total Control Premier version 2.11 and higher. When prompted with the choice to use the Server, Client, or Custom install options, select
Custom, and then click
Next. Click the
Cloud Edition feature dropdown and set the option to
This feature, and all subfeatures, will be installed on local hard drive. Follow the
Total Control Premier Server Setup article as needed to complete the rest of the installation.
IIS Setup
If the intended host machine does not have Internet Information Services enabled, the InstallShield Wizard will attempt to enable it through a series of Windows PowerShell commands. You will be prompted to allow an Execution Policy Change which allows the InstallShield Wizard to enable Internet Information Services. Press A to answer Yes To All, then press Enter. After a few moments, the PowerShell commands will execute, displaying a number of Feature Enable routines with progress bars. Once this is complete, the InstallShield Wizard will continue with the remainder of the Total Control Premier installation as per the notes in the Total Control Premier Server Setup article.
The InstallShield Wizard will only attempt to enable IIS during a new installation - running the InstallShield Wizard after the initial Total Control Premier installation and using the Modify option to add the IIS feature will not work. You will need to uninstall and then reinstall Total Control Premier if you need IIS enabling as part of the installation.
Web Site Folder Location
Once the installation is complete, you'll find the web site installed in C:\inetpub\wwwroot\Fidelity-TCPCE\X00, where X00 is a folder named for the current version number. Inside this folder will be the contents of the web site.
Web Site Configuration
Open Internet Information Services, expand the Sites and then click Fidelity TCPCE.
Connection Strings
Two Connection Strings need to be configured, one of which points the application at the Total Control Premier database, and the other points the ELMAH error logging tool at the database. A SQL Server account with DBO permissions is required, as the application adds and updates tables in the Total Control Premier database if they are missing or out of date, as well as inserting and updating rows in the SQL database as per the other regular Total Control Premier functions.
TCP_Entities
1. Double-click Connection Strings
|
|
2. Double-click TCP_Entities
|
|
3. Select Custom, and then add the following string...
- Data Source=SERVER; Initial Catalog=DATABASENAME; user=SQLUSER; password=SQLPASSWORD; MultipleActiveResultSets=True; application name=EntityFramework
...replacing the values in bold italic with those relevant to your setup, eg:
- Data Source=MSSQLSERVER; Initial Catalog=TotalControl; user=Fidelity; password=Password123; MultipleActiveResultSets=True; application name=EntityFramework
|
|
5. Click OK
|
|
elmah-sqlserver
1. Double-click Connection Strings
|
|
2. Double-click elmah-sqlserver
|
|
3. Select Custom, and then add the following string:
- Data Source=SERVER; Initial Catalog=DATABASENAME; user=SQLUSER; password=SQLPASSWORD; application name=EntityFramework
...replacing the values in bold italic with those relevant to your setup, eg:
- Data Source=MSSQLSERVER; Initial Catalog=TotalControl; user=Fidelity; password=Password123; application name=EntityFramework
|
|
5. Click OK
|
|
Web Site Bindings
1. Click Bindings under the Edit Site category of the Actions menu
|
|
2. Double-click the first entry in the list
|
|
3. Change Port to the required port number
|
|
4. Click OK
|
|
5. Click Close
|
|
You will need to ensure that firewall access is open to and from the server over the required port.
Additional settings can be configured here, such as binding the Web Site to a particular host name or IP address, but this is beyond the scope of the Fidelity setup, and is something that your IT/network support provider can advise on and/or configure.
Application Settings
There are 2 Application settings you really need to check before you try to use the system. the first goes in hand with the Website Binding which is named the SystemTenantURL and the second being DefaultSupervisorFullname.
SystemTenantUrl
This option should really match the binding you have setup, the default option for this will be localhost. For access across the network I would set this to the Hostname of the server
1. Double-click Application Settings
|
|
2. Double-click SystemTenantUrl | |
3. Update the Value and Press OK | |
DefaultSupervisorFullname
This option must match the Full name of an admin user in the TCP Database not their username. the default for this will be System Administrator, you will need to update this where necessary
1. Load up User Maintenance in TCP Desktop and locate your Admin/Supervisor account
|
|
2. Back in IIS Application Settings Double-click DefaultSupervisorFullname | |
3. Update the Value with the Full Name of the TCP User and Press OK | |
SMTP Settings
1. Double-click SMTP Settings
2. Enter the E-mail address that the activation emails are to come from
3. Enter the SMTP Server and Port
4. Tick Use localhost if you are using a mail server on the same host as the web application
5. Set the Authentication Settings:
- Tick Not required if no authentication is required
- Tick Windows if you want to use the credentials of the current user
6. Tick Specify credentials if you want to use specific credentials, then click Set:
- Enter the User name of the email account you want to use
- Enter the Password of the email account
- Enter the password again in the Confirm password box
|
|
7. Click OK
|
|
8. Click Apply
|
|
If you get an error sending and ELMAH shows a STARTTLS error you need to manually add this onto the line that holds the SMTP setup - enableSsl="True"
<network defaultCredentials="false" host="smtp.office365.com" password="REDACTED" port="587" userName="reports@emailaddress.com" enableSsl="True" />
Restart the Web Server
Click the server name at the top of the Connections list to open the home page for the web server, then click Restart, to restart the server with the new settings.
Total Control Premier Service and Role Setup
Total Control Premier needs to be configured to push reporting data to the web application, allowing it to be viewed in the web interface on dashboards are reports. The Update Service maintains the cached tables, but during the initial configuration, any existing reporting data can be cached so that the Update Service doesn't have to cache it on its first run.
Computer Roles
The Cache Data role will need to be enabled against the Update Service.
Supervisor User
Total Control Premier Cloud Edition uses the Supervisor user (User ID 1) as the master user with full access to the web application. Until other users are added and enabled, the Supervisor user is the only user that can log in. Allow Web Access, which marks a user as active in the web application, needs to be set to True on the Supervisor user's record in the desktop edition.