System landscape and installation
Components of the system landscape
The system at the site consists of site components and CloudEngine:
-
Location Programmes
-
Location Databases
-
Location Portal Connector
-
Location 3rd Party APIs
-
Optional MCP workstations
The MyHypersoft Portal consists of these cloud components:
-
MyHypersoft Portal Programmes
-
Portal Databases
-
Portal Location Connector
-
Portal 3rd Party APIs
We call your optional extension for eCommerce CloudBOX and it consists of:
-
Your server (Windows 10 virtualised, static access)
-
Your eCommerce designs and data
-
Basis for:
If you connect the locations to a central office, you have central components:
The central components correspond to the site components in terms of installation. The CloudEngine also acts here. Through special settings, a central system is configured as such and acts as "client 1" without a local POS area by default. The especially webclearing licence synchronises the data between locations and the head office.
The CloudEngine refers to the programmes and database of the site system that connects to the MyHypersoft portal. The local data storage is designed in such a way that the basic functionality (definition depending on individual requirements) of the POS system can be used "indefinitely" even without an internet connection and can otherwise benefit from all the advantages of a cloud.
All this is independent of whether you use a single site or have one or more sites connected to a central office. The sites usually also exchange data with the head office via the internet and both sites are also connected to the MyHypersoft portal for your convenience. This data exchange only takes place once a day as standard and can also be suspended for "any duration" for technical reasons, for example. The extension to the CloudBOX provides you with all eCommerce options. It is then your web space and a Windows-based web server, individually provided for you.
Further documentation: CloudBOX for eCommerce.
Installation as standard
All standard Hypersoft programmes are installed as part of the setup. The possibility of calling up individual programmes depends on the licences purchased. To install the Hypersoft Suite, start by running the Hypersoft Setup on the device that is to be the data server for the POS system. In the case of a single-user system, this is usually the device itself.
Installations on an RDP system (Remote Desktop from Microsoft) and VPN are basically no problem, but please note the restrictions of peripheral devices if they are to be connected.
Hypersoft manages the purchased licences for you in a licence database. This shows which programmes you can use and access. The licence is linked to your company data, so you do not have to manage licence holders and would not have to worry about losing licences.
When starting the initial installation, the desired language is selected. An update uses the language under which Hypersoft Suite was installed.
Set currency symbol...
Depending on whether you are using the German or English version, the settings from the Windows system are also used. Here, the corresponding setting in Hypersoft does not have to match the active setting of the operating system.
Please note, however, that programmes such as the Report Manager use the currency symbol from the settings of the respective Windows operating system. This must then match the settings in Hypersoft.
Planned restarts...
Please also note the chapter Automated program restart.
Known limitations...
Note the topics in the section Limitations and methods.
Best practice for installations
| Best Practice Type | Best Practice Theme |
|---|---|
|
General |
|
| Orientation | Find best practice topics in the documentation |
| Operational safety | Best Practice Use IP Printer |
| Operational safety | Best Practice Printer Reliability |
| Operational safety | Best practice for emergency operation of the card units |
| Facilitating work | Best Practice Use Hypersoft Sidepanel |
| Technology | Best practice replacement for missing LAN connections |
| Technology | Best Practice with own layouts |
| SQL Fraud | Best practice against fraud via SQL accesses |
| TSE Problems (D) | Best Practice: TSE Error Report (D) |
|
Live Report |
|
| Evaluations | Best Practice: Customize Live Report |
| Control & Communication | Best Practice: Location communication |
Standard or project?
Hypersoft is a standard programme with extensive possibilities through logical functions and comprehensive documentation. Some things are described as project work requiring planning. This means that you cannot use them as standard, but the use should be coordinated and planned with us. However, it does not follow from this that everything else does not have to or should not be voted on. Thus, at this point we would like to indicate a project status at least conditionally if one of the following things is true:
-
Your cash register system should work 24 hours a day.
-
You have in a network:
-
more than 10 outlets, or...
-
more than 10 cash register stations or mobile devices in total, or...
-
use point-of-sale clearing, or...
-
work with more than 5000 articles.
-
-
You have ordered software development from us.
-
You are using a 3rd party interface that has been installed less than three times so far.
-
They have other requirements that we are not aware of than those described here.
Restart after configuration changes
If you add Hypersoft licences or set up new programmes, the POS system must be restarted for activation. This always affects the main cash register or the server acting as such. If there is no restart, the settings will be applied at the latest at /TTA
The theoretical end of day (TTA) applies the calendar day change at a time specified by you (default setting 6:00 a.m.). The programme can automatically perform closures, updates and maintenance at this time. A new sales day then begins with the first POS booking of the day., if there is a restart before the TTA, the settings will be applied with it. This concerns, for example, the set-up of interfaces, the first activation of a web voucher system or new payment terminals. However, things like new forms may require a restart or waiting for a TTA. For this reason, we recommend a targeted restart to activate these things.
Some things don't require a restart, such as new items with new commodity groups, new staff with new operator permissions. These master data, which are not confrontations, are updated during operation.
Further documentation:
English and international version
Licences for the Hypersoft // system
1. The optimal operating system
5. Programme Specific Requirements
Installing the Actian ZEN SQL database
Getting Started After Installation
Back to the parent page: Service and Support