Overview
TCP v2.10 is the first version that includes native web provided functionality. The intention is that a separate Web Server is provided to run alongside the TCP application server.
The document gives an initial specification we expect that web server to require. This will be continually reviewed as the system is used in 'real world' environments.
The web server to be used is Microsoft Internet Information Services (IIS)
Accessing the Web System
Supported Devices
Microsoft Windows Based PC
Android device with a minimum screen size of 7"
Apple device with a minimum screen size of 7"
Supported Browser
Initially we will only be supporting the Chrome Web Browser.
Web Server Minimum Specifications
This specification is based on a Total Control Premier setup of:-
- A single SQL Database up to 3GB
- Up to 10,000 Products per site
- Up to 5 Sites
- Up to 10 concurrent users
- 3 years of historical sales transactions.
- 3 year of historical stock transactions.
The specification may be increased based upon the setup of the database, and typical usage. This will be discussed with you at the point of upgrade.
Operating System:
Microsoft Windows 10
Microsoft Servers (2012+)
Memory
32BIT - 4GB
64BIT - 8GB
CPU
2GHz with 4 Cores (more speed and cores will
be better)
Disk
SSD will be better, but a normal hard disk
will work.
Install Size - 180MB (1GB Free)
Other Requirements
.NET Framework 4.7.2
Application Pool 32 Bit as .NET 4.0
Windows Auth is not currently supported for connection to the SQL Database. An SQL user with DBO access is required as TCP Cloud auto-updates the database with missing tables required for cloud use.
Windows Optional Feature Roles Required (IIS)
IIS Features are enabled utilising a PowerShell Script Fidelity provide to enable the necessary features required to be able to run the Web Site successfully - this is optional, and should you chose to manually configure it then that is OK.
The list of features enabled are:
IIS-WebServerRole
IIS-WebServer
IIS-CommonHttpFeatures
IIS-HttpErrors
IIS-HttpRedirect
IIS-ApplicationDevelopment
NetFx4Extended-ASPNET45
IIS-NetFxExtensibility45
IIS-HealthAndDiagnostics
IIS-HttpLogging
IIS-LoggingLibraries
IIS-RequestMonitor
IIS-HttpTracing
IIS-Security
IIS-RequestFiltering
IIS-Performance
IIS-WebServerManagementTools
IIS-IIS6ManagementCompatibility
IIS-Metabase
IIS-ManagementConsole
IIS-BasicAuthentication
IIS-WindowsAuthentication
IIS-StaticContent
IIS-DefaultDocument
IIS-WebSockets
IIS-ApplicationInit
IIS-ISAPIExtensions
IIS-ISAPIFilter
IIS-HttpCompressionStatic
IIS-ASPNET45
IIS Notes
IISROOT is c:\ on first run because iis does not exist, otherwise it will be in IISROOT (Inetpub\wwroot)
Will not work as a VIRTUAL DIRECTORY (SUBFOLDER) MUST BE IN ROOT.
If you find your web system running rather sluggish there are 2 settings which we have found make a positive impact on the system when set
1. Setting the Start Mode of the DefaultAppPool in IIS to Always running
2. Enabling Preload on your website
The Start mode setting is found by heading into IIS Manager, clicking on application pools, right clicking the DefaultAppPool and selecting Advanced settings
The Preload setting is found by heading into IIS Manager, clicking your site (Fidelity TCPCE) in the left hand pane under Sites then selecting Advanced Settings in the right hand pane where the Actions are listed