Here you can find information about:
|
About this document
 | IMPORTANT: This is the official article regarding the system requirements. No other documents must be considered. |
In this article you can find information about the TCPOS.net Features that have an impact on the integration in an existing infrastructure and the Requirements when a new infrastructure must be created.
Information is grouped by device type, so you can find in one place everything about the related device (client, server, etc.) or about Operating System/Software versions supported.
 | The pdf version of this article is downloadable here:
|
The installation topology
| Example of small installation (single server)
|
Example of big installation (many servers)
|
1. Database, 2. Server Service (SS), 3. Load balancer (LB), 4. Updater Service (UP), Web Service (WS), Import/Esport Service, 5. Business Logic (BI)
|
|
The TCPOS.net Application Tiers
TCPOS.net consists of three physical layers:
- Smart client programs for FrontEnd (till) and for Admin (the software used in the office to maintain the database). A FrontEnd version is also available for mobile Android devices (DroidPos).
- Two services running on a Windows machine that behave as middle tier for database access and software updater. Interfaces to other systems also run as Windows services or as WebServices.
- The database server, which can run either under Windows (on the same machine of the two already mentioned services or on another) or Linux. The database server can be either Oracle, SqlServer or PostgreSQL.
TCPOS and Microsoft .NET
The TCPOS.net runs under the Microsoft .NET.
The .NET must be installed on the smart clients and on the middle tier (database access/updater services).
 | in this document you can find only high level information about the version to install.
Please refer to the specific article TCPOS and Microsoft .NET for deepening information. |
Overview of the technical differences between versions 8.1, 8.0 and 7.x
|
Here below you can find the most important changes related to the technical characteristics of the involved hardware resources between the different versions:
Please click on the title under the related icon to reach the related section.
|
.NET version
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
.NET
|
From TCPOS 8.1 the version currently supported is the:
- .NET 8 + any available service pack
Important: from version 8.0 the mandatory .NET version to be installed changes depending on the TCPOS program to start.
Please refer to the specific chapter below.
|
From TCPOS 8.0 the version currently supported is the:
- .NET 6 + any available service pack
Important: from version 8.0 the mandatory .NET version to be installed changes depending on the TCPOS program to start.
Please refer to the specific chapter below.
|
From TCPOS 7.0 until 7.6 the framework version currently supported is the:
- 4.7.2 + any available service pack
|
clients
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
CLIENT - FrontEnd
|
The following operating system is now supported:
- Windows 10 IoT Enterprise LTSC 2021
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
Starting from this version, the following versions of Windows 11 are supported:
- Windows 11 Enterprise
- Windows 11 Pro
- Windows 11 IoT Enterprise
|
Due to the upgrade of the .NET Framework to version 4.7.2 - that is only supported from Windows 7 (Windows POSReady 7) - the following operating systems are dismissed and no support is given:
- Windows XP (valid until 4.6.x)
- Windows Embedded POSready 2009 (valid until 4.6.x)
- Windows vista
as a consequence tills with these operating systems installed will not be supported anymore.
Note about Windows 10
Windows 10 IoT Enterprise LTSB 2015 does not support .Net Framework 4.7.2. For this reason the OS has to be update at least to version Windows 10 IoT Enterprise LTSB 2016.
- Windows 10 - 1703 or up, 1607 (supported)
- Windows 10 - 1511, 1507 (build 10240) (not supported)
Windows 10 Release information
Note about Windows XP
Although Windows XP is supported by TCPOS until Version 4.6.x, '''its use is discouraged''' also in these versions because it is no longer supported by
Microsoft Windows from 8th April 2014,
Link 2
Note about Terminal Servers
Starting from 7.0 Terminal Servers (are exactly like FrontEnds) are dismissed and no longer supported.
Note about FrontEnd 32 bit or 64 bit
The FrontEnd is compiled to run both on 32 bit and 64 bit systems.
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
CLIENT - Wireless
|
The following operating systems are now supported:
- Android 14
- Android 13
- Android 12
- Android 11
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
The following operating systems are now supported:
|
The following operating systems are now supported:
- Android 9.0 (PIE)
- Android 8.0 (OREO)
and the following are dismissed and no support is given:
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
CLIENT - Admin
|
The following operating system is now supported:
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
Starting from this version, the following versions of Windows 11 are supported:
- Windows 11 Enterprise
- Windows 11 Pro
- Windows 11 IoT Enterprise
|
The following operating system is now supported:
Note about Client 32 bit
Starting from version 7.0 only Clients 64 bit are supported.
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
servers
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
MIDDLE TIER SERVER - Services
|
The following operating system is now supported:
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
No significant changes to report.
|
The following operating system is now supported:
Note about Server 32 bit
Starting from version 7.0 only Server 64 bit are supported.
Server 32 Bit are fully functional, yet they are considered obsolete due to performance limitations and because the new operating systems works on 64 Bit devices.
Furthermore Server 32 bit manages at most 3GB-memory but servers now come with 8GB-memory, therefore Server 32 bit are dismissed and no more supported.
Note about minimum Hardware Requirements recommended for NEW installations
The minimum required values have been revised. Please refer to the related section for detailed information.
|
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
 SERVER - Database
|
The following database engine are now supported:
- Microsoft SQLServer 2022
- PostgreSQL 16
- PostgreSQL 15
- PostgreSQL 14
- PostgreSQL 13
|
No significant changes to report.
|
From version 7.3:
The following database engine is now supported:
- Oracle 19c
- PostgreSQL 12
- SQLServer 2019
From version 7.0:
The following database engine is now supported:
- Oracle 18c
- PostgreSQL 10.8.1 (tcpos installation setup)
Note about Database 64 bit
Starting from Version 7.0 only Database 64 bit are supported.
Note about Oracle
Starting from Version 7.0 The Oracle database engine is no longer included on the TCPOS installation setup.
|
network
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
NETWORK
|
No significant changes to report.
|
No significant changes to report.
|
No significant changes to report.
|
other
|
|
Differences between 8.1 and 8.0
|
Differences between 8.0 and 7.0
|
Differences between 7.0 and 4.6.x
|
|
BROWSERS
|
No significant changes to report.
|
No significant changes to report.
|
No significant changes to report.
|
|
Technical characteristics of the involved Hardware Resources
|
In this chapter you can find information about supported Operating Systems and supported Database Version and about the minimum hardware requirements (without third parties products).
In summary, this is the involved hardware & software.
|
 | Important
This data constitute only an indication. All values described do not consider the hardware and software requirements of third parties products, such as
- Oracle, Microsoft SQLServer, Postgres
- Microsoft .NET (Framework)
- Microsoft Windows Operative Systems (Server and client)
- all additional software applications not developed by TCPOS, eg. applications that manage FTP site
- hardware drivers for devices (device drivers)
- etc
|
Client - FRONTEND
 | The following information refers to Version 8.0 or up
|
|
|
|
Client FrontEnd
| Supported Operating Systems
TCPOS.net supports the following operating systems.
|
Device Type Information
---Note about Windows 11---
TCPOS supports the following versions
* Windows 11 Enterprise
* Windows 11 Pro
* Windows 11 IoT Enterprise
Windows 11 Release information
---Note about Windows 10---
Windows 10 IoT Enterprise LTSB 2015
does not support .Net Framework 4.7.2.
For this reason the OS has to be update at almost to version
Windows 10 IoT Enterprise LTSB 2016.
* Windows 10 - 1703,1607 (supported)
* Windows 10 - 1511, 1507 (build 10240) (not supported)
Windows 10 Release information
|
| Device Type Information
---Virtual machines---
There are no known problems for the use of Virtual machines, but their disadvantages should be taken into consideration during use (e.g. performance issues, available memory and disk space, etc.).
|
| TCPOS FrontEnd SW Information
---FrontEnd 32 or 64 bit---
Starting from Version 7.0.x the FrontEnd is compiled to run both on 64 bit (FrontEnd) and 32 bit (FrontEnd-x86) systems.
When using devices that need external dlls (E.G. OPOS) these may be launched only if the program is executed in 32 bit mode.
---Only for Version before 7.0.x---
In case you are using a 64 bit system connected to a device using a 32 Bit mode, it will be necessary to force the execution of FE at 32 bit, following these procedures:
How to force FrontEnd to run at 32 bit on 64 bit systems.
The suggested operating system is Windows Embedded POSready 7.
|
|
|
Minimum Hardware Requirements recommended
for NEW installations
If you are planning an update in the future, please refer to the following hardware requirements. TCPOS works also with lower requirements than the ones the listed below, but in order to achieve optimal performance (they may also depend on the number of installed plugins),
we recommend to follow our suggestions.
Important: In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in this chapter it is necessary to consider the points about possible critical issues due to the amount of data to handle, described in the chapter
"Method for the evaluation of the hardware required according to the critical points".
PROCESSOR
Intel Celeron 1,5 Ghz dual core or equivalent
The processors installed in new tills give excellent performance
The processors of 3-4 years old tills (like Intel processors with
clock <1Ghz) may not satisfy the end users who expect zero milliseconds response time.
MEMORY
4 GB suggested
DISK SPACE OCCUPIED BY THE APPLICATION
(DATA EXCLUDED)
100 Mbyte
Data excluded means the just installed version.
Operational data and logs or customizations (plugins) are excluded.
|
|
|
Client - WIRELESS
| The following information refers to Version 8.0 or up |
Client Wireless - Android
|
|
Minimum Hardware Requirements recommended
for NEW installations
If you are planning an update in the future, please refer to the following hardware requirements. TCPOS works also with requirements less than the ones listed below, but in order to achieve optimal performance (they may also depend on the number of installed plugins),
we recommend to follow our suggestions.
Important: In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in this chapter it is necessary to consider the points about possible critical issues due to the amount of data to handle, described in the chapter
"Method for the evaluation of the hardware required according to the critical points".
PROCESSOR
Android Dual-core A9 2GHz (minimum)
MEMORY
4GB RAM + 8GB Flash is suggested
WLAN
Wlan 802.11 b/g/n
---TCPOS DroidPos Best Performances---
Since we have carried out extensive tests on the TCPOS DroidPos performances on the handhelds in order to determine which is:
1. the minimum hardware of the recommended devices
2. the configuration and the performances of the network
3. ServerServer hardware used during tests
you can refer to the document TCPOS_DroidPos_Test_Performances_2018_EN_1.0.pdf
to help you decide which are the configuration and the devices
best suited to your needs.
This document is downloadable from this article
TCPOS DroidPos Test Performances 2018.
We remind you that
version 4.6 or up includes the functionalities of version 4.5.18 NF525
to which the document refers.
|
|
|
Client - ADMIN
| The following information refers to Version 8.0 or up |
Client Admin - 64 bit
| Supported Operating Systems
TCPOS.net supports the following operating systems.
|
|
|
Minimum Hardware Requirements recommended
for NEW installations
If you are planning an update in the future, please refer to the following hardware requirements. TCPOS works also with requirements less then the listed below, but in order to achieve optimal performance (they may also depend on the number of installed plugins),
we recommend to follow our suggestions.
Important: In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in this chapter it is necessary to consider the points about possible critical issues due to the amount of data to handle, described in the chapter
"Method for the evaluation of the hardware required according to the critical points".
PROCESSOR
Intel Celeron 1,5 Ghz dual core or equivalent
MEMORY
4 GB suggested
DISK SPACE OCCUPIED BY THE APPLICATION
(DATA EXCLUDED)
500 Mbyte
Disk space is not a problem on even non modern machine: on the clients, 500MB of free disk space is more than enough.
Data excluded means the just installed version.
Operational data and logs or customizations (plugins) are excluded.
---Suggestions---
The same rule is true also for administration office PCs, where the minimum memory requirement is 4GB RAM.
In general, if a user is satisfied of his PC performance with Word or Excel, he will not find TCPOS ‘slow’.
|
|
|
Middle Tier Server - SERVICES
| The following information refers to Version 8.0 or up |
Server 64 bit
| Supported Operating Systems - 64 bit
TCPOS.net supports the following operating systems.
|
|
|
Minimum Hardware Requirements recommended
for NEW installations
If you are planning an update in the future, please refer to the following hardware requirements. TCPOS works also with requirements less then the listed below, but in order to achieve optimal performance (they may also depend on the number of installed plugins),
we recommend to follow our suggestions.
Important: In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in this chapter it is necessary to consider the points about possible critical issues due to the amount of data to handle, described in the chapter
"Method for the evaluation of the hardware required according to the critical points".
The middle tier application has no specific storage requirements and, except for a small storage area used by the application as cache (2GB suggested), used for the management of support data and local Database and temporary files.
Most of the requests made by the clients are usually executed in few milliseconds (including database server response times), so it can work well in a multiprocessor (or multi core) system.
The aspects to take care are the processor speed and the efficiency of the communication between the middle tier and the database server, where a Gigabit Ethernet with is recommended when the system must process more than 200 transactions per second.
PROCESSOR
Intel 2,5 Ghz dual core or equivalent
MEMORY
4 GB as a minimum
Furthermore for the proper calculation of the RAM sizing must be taken into account the Operating System used.
Please refer to the SO version requirements for more information.
DISK SPACE OCCUPIED BY THE APPLICATION (DATA EXCLUDED)
500 Mbyte
Data excluded means the just installed version.
Operational data and logs or customizations (plugins) are excluded.
|
|
|
DATABASE SERVER
| The following information refers to Version 8.0 |
Any third-party product (such as Operating Systems, Datagase Engines) is only supported until the end of life date established by the manufacturer.
Server 64 bit
| Supported Operating Systems - 64 bit
TCPOS.net supports the following operating systems.
---SO and DB Server Combination---
For the possible functioning combinations between Data Base Server and operating system, consult the documentation of the Data Base manufacturer.
|
Supported Database Engines - Oracle
Preferred:
* Oracle 19c - EOL
|
Supported:
* Oracle 18c - EOL
* Oracle 12c 64 bit
* Oracle 11 XE Express edition 32 bit
* Oracle 11g R2
* Oracle 11g
|
|
| Supported Database Engines - PostgreSQL
PostgreSQL is a free open source database, available with no limits of size, memory and processors.
PostgreSQL is supported from TCPOS version 4.4.9.1.
For further information, please refer to this link www.postgresql.org/about
|
---TCPOS Official Setup---
The package includes the following OS:
Microsoft SQLServer 2017 Express
PostgreSQL 10.8.1
|
|
|
Minimum Hardware Requirements recommended
for NEW installations
If you are planning an update in the future, please refer to the following hardware requirements. TCPOS works also with requirements less then the listed below, but in order to achieve optimal performance (they may also depend on the number of installed plugins),
we recommend to follow our suggestions.
Important: In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in this chapter it is necessary to consider the points about possible critical issues due to the amount of data to handle, described in the chapter
"Method for the evaluation of the hardware required according to the critical points".
PROCESSOR - MEMORY -
DISK SPACE OCCUPIED BY THE APPLICATION
The database size is related to the number of tills and the average number of transactions.
Data excluded means the just installed version.
Operational data are excluded.
Furthermore for the proper calculation of the sizing must be taken into account the Database Engine used.
Please refer to the manufacturer requirements for more information.
DATA STORAGE REQUIREMENTS
The TCPOS.net database is made by two distinct parts:
the configuration data (articles, prices, operators, customers and so on)
and the transactions.
In a production environment, the database storage space needed by the first tables is negligible compared to the one used by transactions.
The typical transaction in quick service environments
(where a single till can process over than one thousand transaction per day)
is made by less than 10 records (transaction header, 8 articles and 1 payment).
Each record uses about 50 bytes and about the same space
is used by indexes and other internal data structures.
As result the size of a transaction is around 1Kbyte.
The rule of the thumb to calculate the storage space is
“1 gigabyte for 1 million of transaction”.
This calculation is valid for Oracle databases.
SQL Server and PostgreSQL require approximately the same space.
|
| TCPOS and Domain Controller
Microsoft SQL Server®, Oracle® and PostgreSql®
can NOT be installed successfully on a domain controller and
this configuration is not supported by the software vendors.
For further information, please refer to the technical documentation available on the respective software vendor website.
Furthermore, due to the specific security restrictions applied to the operative system
by Microsoft Active Directory on Domain Controllers and
the resource demands of Domain Controllers, we strongly suggest
to NEVER install TCPOS.Net on a domain controller;
otherwise, performances could be strongly degraded.
|
|
|
NETWORK ENVIRONMENT
| The following information refers to Version 7.0 or up |
Network
Network indication (This data is only an indication)
When working in WAN, it is suggested to decrease the network usage using the local database for article lookup and send the transaction data to the central server in asynchronous mode.
The traffic generated in this situation is about 3KB per sale transaction containing 10 articles. During the peak time, this means about 5KB per minute per till. In other words, if we have 100 tills working at full speed (5Kbytes per minute) the traffic generated is 500K per minute, rounding up, 100Kbit per second (500Kbytes* 10bits / 60seconds).
This means that the upload band requested in a shop per till is about 1Kbit. A shop with 20-30 tills can safely work with a 200Kbit network without any saturation effect.
As comparison, a refresh of the www.google.com web page, one of the simplest pages present in the Internet, generates more than 5Kbytes of network traffic, even without the transmission of the Google logo bitmaps
because they are present in the browser cache.
The WAN bandwidth of the segment where the central server is present must obviously be bigger. An approximate requirement is about 1MBit for 1000 tills.
It is also possible to reduce even more the traffic compressing the transmitted data packets, cutting the bandwidth requirements to one third of the numbers specified above. The side effect is more CPU requirements in the middle tier machine that must compress and decompress the received packets.
Other communications between the tills and the server are negligible, at least 10 times less than the transaction data.
There is also network traffic existing between the server and the till.
This is the download of the local database of the till. This download is initiated by a till present in this shop, which copies data (physically a single file) in its hard disk. Other tills will then refresh their copy from this one, with a file transfer over the LAN that interconnects the tills, with no WAN communication. The data transferred via WAN is about 1MB for a database with about 15’000 articles. The database is typically transferred once a day.
---Deepening Network Information---
You can find specific information about the TCPOS Network Architecture (communication protocols and network security)
at this article TCPOS Application Architecture.
|
|
|
MICROSOFT .NET
| The following information refers to Version 7.0 or up |
Clients and Middle tier
Framework indication
The TCPOS.net runs under the Microsoft .NET.
The platform must be installed on the smart clients and on the middle tier (database access/updater services).
From TCPOS 8.1 the version currently supported is the .NET 8.0 + any available service pack.
From TCPOS 8.0 the version currently supported is the .NET 6.0 + any available service pack.
From TCPOS 7.0 to 7.6.x the version supported is the .NET Framework 4.7.2 + any available service pack.
Download and Installation
Please refer to this article TCPOS and Microsoft .NET supported versions.
|
|
|
BROWSERS
TCPOS applications
Desktop browser
Chrome (current version)
Firefox (current version)
Safari (version 5.1+)
Internet Explorer (version 9+) - OBSOLETE
---Browser Version---
(Current - 1) or Current denotes that we support the current stable version of the browser and the version that preceded it.
For example, if the current version of a browser is 24.x, we support the 24.x and 23.x versions.
---Kiosk and Self Check-out Plugins---
These applications work only with Chrome.
|
Mobile browser
IOS (current version)
Android (current version)
---Browser Version---
(Current - 1) or Current denotes that we support the current stable version of the browser and the version that preceded it.
For example, if the current version of a browser is 24.x, we support the 24.x and 23.x versions.
|
|
|
|
Method for the evaluation of the hardware required according to the critical points
In order to meet the performance requirements of the final production environment and for a proper evaluation of the required hardware, in addition to the data described in the previous chapters it is necessary to consider the following points about possible critical issues due to the amount of data to handle.
This data is only an indication. This is helpful for the project manager which will analyze the data and make an assessement for the possible surplus to be applied to the minimum hardware size required.
|
Critical points to be considered when evaluating the resizing
According to the following points, the values of the minimum hardware required must be increased in percentage.
TCPOS Operational data
| Data type
|
|
| Transactions/Year
|
Estimated value: total number of sale transactions per year
|
Time of maximum load/
%transactions
|
Number of consecutive hours when an intensive use of the system is planned and% of the planned transactions. For example, a canteen will do 95% of transactions during the 2 central hours of the day.
|
| Tills
|
Number of tills linked to the system
|
| Shops
|
Number of tills expected for each single shop (tills on the same local network)
|
| Sale articles
|
Number of sale articles expected
|
| Stock articles
|
Number of stock articles expected (only for TCPOS RealTimeStock)
|
| Multimedia data size (images/videos)
|
Value expected: this is the estimated total size of multimedia data (images and video) that will be used on tills.
|
| Customers
|
Number of customers stored in the system (customer cards)
|
| Visibility Criteria
|
Important: from the values mentioned above, any optimization implemented through the visibility criteria is excluded.
|
|
Software Environment
| Element to take into account
|
|
| Database engine
|
Oracle, Microsoft SQL Server or PostgreSQL
|
| Number of TCPOS versions to maintain online
|
How many TCPOS versions you want to execute simultaneously. The minimum value in order to use the software autoupdate feature is 2.
|
| Average value of tills per shop
|
This value is used to estimate how many tills can update the base data by downloading it from the tills available in the same local network, instead of requesting a new download from the central server.
|
|
Medium/high impact TCPOS features
| Element to take into account
|
|
| Saving log centralized data (Advanced FrontEnd Log)
|
This feature allows loading the tills log files (trace) in the central database for immediate access in case of need.
Warning: the amount of data to be entered in the database is very significant and has high-level impact on the sizing of the available storage of the database.
|
| Saving centralized print data (printjob)
|
This feature enables saving an exact copy of the printouts performed from the TCPOS tills.
|
| Daily/tills database update frequency
|
Evaluate how many times a day you must run the refresh of the tills database for each single till. This value, combined with the size of local database generated by the till, might impact on the performance of the system and, in some cases require one or more servers dedicated to the processing of packets to be sent to the tills.
|
| High availability applications
|
This feature enables to distribute the load of the application servers among the tills, decreasing the risk of overload of the single application servers, and limiting the offline tills in case of technical issues.
|
| Usage of the TCPOS LoadBalancer to generate tills data
|
This features requires the usage of a separate server for the creation of the local dababase to be sent to other devices.
|
|
Other Medium/High Impact Elements
| Element to take into account
|
|
| TCPOS Plug-Ins
|
Stock Control, AdvancedFrontEndLog
|
| Data Exchange Interfaces
|
Do not have significant impact.
|
| TCPOS WEB Services
|
in relation to the estimated number of concurrent accesses.
Example of site for the reservation of meals or card recharges for customer number.
|
| TCPOS Updater Service
|
Evaluate only if the available data base is sufficient to support the deployment time required by the customer.
(tills/admin/devices update)
|
| High availability TCPOS application
|
tills, admin, devices update
|
|
|
|
TCPOS in partnership with AZURE
Information about TCPOS on Microsoft Azure.
|
 | Work in progress
We are working to update the information contained in this section. In the meantime, please contact the IT department directly.
|
|
|
|
| 1.
|
Azure provides two options to host the SQL Server workloads in the cloud
- Database SQL Azure: native SQL database in the cloud, also known as platform database distributed as a service (PaaS) or database distributed as a service (DBaaS) optimized for software app development as a service (SaaS). It offers compatibility with most of the features of SQL Server.
- SQL Server on Azure virtual machines: SQL Server installed and hosted in the cloud on Windows Server virtual machines (VM) running on Azure, a configuration also known as an infrastructure distributed as a service (IaaS).
DB TCPOS hosted in the cloud in virtual machines (VM) Windows Server:
The size of the virtual machine (VM) hosting SQL Server can start from a VM type DS3 Standard/DS3_V2 Standard (4Core-14GB), with growth possibilities to DS12 Standard/DS12_V2 Standard (4Core-28GB) or higher profiles as DS13 Standard/DS13_V2 Standard (8Core-56GB).
|
| 2.
|
TCPOS Service Server hosted on VM Windows Server
The size of the virtual machine (VM) hosting the TCPOS Server Service can start from a VM type DS2 Standard/DS2_V2 Standard (2Core-7GB) with growth possibilities to DS11 Standard/DS11_V2 Standard (2Core-14GB).
On each TCPOS SS server, 4 primary services and 4 secondary services (enable to maintain online the version that will be decommissioned, allowing a phased upgrade over time) can be hosted.
Each service guarantees a 100 connections pool (max recommended), allowing to cover up to 400 active connections with only one server. In specific cases, there is the possibility of granting an upper increased limit, depending on the customer configuration.
|
| 3.
|
TCPOS LB Server hosted on VM Windows Server
These servers defined "Local Database Balanced Servers" are meant to prepare the local database for the clients, which will then be delivered by the Server Service. Each TCPOS LB Server serve all TCPOS SS servers, increasing the performances of the TCPOS.net structure. Their number depends on the requirements and it is not directly proportional to the number of TCPOS SS Server, and must be monitored during the expansion phase.
The size of the virtual machine (VM) hosting the TCPOS LB can start from a VM tipo DS2 Standard/DS2_V2 Standard (2Core-7GB) with growth possibilities to DS3 Standard/DS3_V2 Standard (4Core-14GB).
We recommend a larger number of Server DS2 / DS3, rather than few servers but with a larger profile.
|
| 4.
|
TCPOS services (FTP, WS, Inp/Exp, UP) hosted on VM Windows Server
The size of the virtual machine (VM) hosting the complementary TCPOS services (FTP, WS, Import/Export, UP), can start from a VM type DS2 Standard/DS2_V2 Standard (2Core-7GB) with growth possibilities to DS3 Standard/DS3_V2 Standard (4Core-14GB). They must be resized at the design stage.
|
| 5.
|
TCPOS BI services hosted on Windows Server VM
The size of the virtual machine (VM) hosting the TCPOS BI services, can start from a VM type DS12 Standard/DS12_V2 Standard (4Core-28GB) with growth possibilities to DS13 Standard/DS13_V2 Standard (8Core-56GB). They must be resized at the design stage.
|
The available Azure Server
At the following links you can find a Microsoft tools helping you to evaluate the possible cost of the involved hardware.
How to use the Azure Microsoft pricing tool
| | The pictures of the following chapters are informative only, for the effective value please refer to the tool forms |
General purpose compute: Basic tier
An economical option for development workloads, test servers, and other applications that don't require load balancing, auto-scaling, or memory-intensive virtual machines.
Prices include Windows Server licensing fee but not sales tax. Monthly Pay-As-You-Go estimates based on 744 hours of continuous use.
General purpose compute: Standard tier
Offers the most flexibility. Supports all virtual machine configurations and features.
Prices include Windows Server licensing fee but not sales tax. Monthly Pay-As-You-Go estimates based on 744 hours of continuous use.
Optimized compute: 60% faster than A-series*, more memory, and local SSD
(*) Relative to the A1-A7 VM sizes. A8-A11 sizes are faster than D-series.
D-series virtual machines feature solid state drives (SSDs) and 60% faster processors than the A-series and are also available for web or worker roles in Azure Cloud Services. This series is ideal for applications that demand faster CPUs, better local disk performance, or higher memories.
We have a new variant of the D-series sizes called “DS” that are specifically targeted for Premium Storage. The pricing and billing meters for the DS sizes are the same as D-series. SSD storage included in D-series VMs is local temporary storage. For persistent storage, use DS VMs instead and purchase Premium Storage separately.
Prices include Windows Server licensing fee but not sales tax. Monthly Pay-As-You-Go estimates based on 744 hours of continuous use.
| Notes
- D-Series is currently available in the following regions: East US, West US, North Central US, South Central US, North Europe, West Europe, Southeast Asia, East Asia, Japan East, Japan West, Brazil South, East US 2, Central US, US Gov Virginia, US Gov Iowa, Australia East, Australia Southeast
- D-series is not available in Canada East, Canada Central.
- For Azure Government pricing information, contact your Microsoft representative or reseller.
|
Optimized compute: 35% faster than D-series, latest generation of CPU
Dv2-series instances are the next generation of D-series instances that can be used as Virtual Machines or Cloud Services. Dv2-series instances will carry more powerful CPUs which are on average about 35% faster than D-series instances, and carry the same memory and disk configurations as the D-series. Dv2-series instances are based on the latest generation 2.4 GHz Intel Xeon® E5-2673 v3 (Haswell) processor, and with Intel Turbo Boost Technology 2.0 can go to 3.2 GHz. Dv2-series and D-series are ideal for applications that demand faster CPUs, better local disk performance, or higher memories and offer a powerful combination for many enterprise-grade applications.
We have a new variant of the Dv2-series sizes called “DSv2” that are specifically targeted for Premium Storage. The pricing and billing meters for the DSv2 sizes are the same as Dv2-series. SSD storage included in Dv2-series VMs is local temporary storage. For persistent storage, use DSv2 VMs instead and purchase Premium Storage separately.
Prices include Windows Server licensing fee but not sales tax. Monthly Pay-As-You-Go estimates based on 744 hours of continuous use.
| Notes
- Dv2-series is not available in the Brazil South region.
- For Azure Government pricing information, contact your Microsoft representative or reseller.
|
Performance optimized compute: unparalleled computational performance with latest CPUs, more memory, and more local SSD
| xeon-e5-solutions
G-series virtual machines feature latest Intel® Xeon® processor E5 v3 family, two times more memory and four times more Solid State Drive storage (SSDs) than the D-series. G-series will provide unparalleled computational performance, more memory and more local SSD storage than any current VM size in the public cloud making it very ideal for your most demanding applications. |
We have a new variant of the G-series sizes called “GS” that are specifically targeted for Premium Storage. The pricing and billing meters for the GS sizes are the same as G-series. SSD storage included in G-series VMs is local temporary storage. For persistent storage, use GS VMs instead and purchase Premium Storage separately.
G5 instance is isolated to hardware dedicated to a single customer.
GB is represented using 1024^3 bytes sometimes referred to as Gibibyte, or base 2 definition. When comparing sizes that use different base systems, remember that base 2 sizes may appear smaller than base 10 but for any specific size, a base 2 system provides more capacity than a base 10 system, because 1024^3 is greater than 1000^3.
| Notes
- G-series virtual machines are currently only available in West US, East US 2, West Europe, and Southeast Asia regions.
- G-series is not available in the following regions: in East US, North Central US, South Central US, North Europe, East Asia, Japan East, Japan West, Brazil South, Central US, Australia East, Australia Southeast, Canada East, Canada Central.
|
Network optimized: fast networking with InfiniBand support
| xeon-processor-e5-family
Available in select data centers. A8 and A9 virtual machines feature Intel® Xeon® E5 processors. Adds a 32 Gbit/s InfiniBand network with remote direct memory access (RDMA) technology. Ideal for Message Passing Interface (MPI) applications, high-performance clusters, modeling and simulations, video encoding, and other compute or network intensive scenarios. |
A8-A11 instances are only available in East US, North Central US, South Central US, West US, North Europe, West Europe, and Japan East.
Compute intensive
| xeon-processor-e5-family
Available in select data centers. A10 and A11 virtual machines feature Intel® Xeon® E5 processors. For high-performance clusters, modeling and simulations, video encoding, and other compute or network intensive scenarios. Similar to A8 and A9 instance configuration without the InfiniBand network and RDMA technology. |
A8-A11 instances are only available in East US, North Central US, South Central US, West US, North Europe, West Europe, and Japan East.
|
 |
