RetailForce Fiscal Middleware (and other RetailForce services) can be connected to other software products - such as an electronic recording system ("cash register") - in various ways.
This article describes different system- and integration variants as examples. If you have any questions or cannot find the variant you are planning to integrate, please contact us at office (at) retailforce dot cloud.
If the term "POS software" is used in this article, it is representative of all possible types of electronic recording systems.
Installation options
Below are some examples of how RetailForce Fiscal Middleware can be placed within the system architecture.
Local installation
Ideally, the Fiscal Middleware should be installed in the same system as the POS system. In the course of a .dll integration (see below) this is almost inevitable. Examples: PC, tablet PC, smartphone as "cash register", the RetailForce Fiskal Middleware is installed on the same device. This variant also covers the case where the actual POS software is provided centrally on a server and the individual client tills access the central software via a remote desktop connection, for example.
Fig. 1.: local installation of the Fiscal Client
Network installation
Since the Fiskal Client can be accessed via a REST interface, it is also possible to run the middleware on its own physical or virtual machine. In this case, the communication between POS software and Fiskal middleware takes place via a network connection (LAN or WAN).
Fig. 2.: Network installation of the Fiscal Client
Cloud installation
As a RESTful web service or in the course of a native (.dll) integration, the Fiscal Middleware can also be operated as a cloud application.
Fig. 3.: Cloud installation of the Fiscal Clients
Integration variants
The following describes different ways to integrate the fiscal service into the POS system.
Interface integration
This integration variant uses the Fiskal middleware in the form of the RESTful web service. The Fiscal Client is installed as a service and the communication between the POS software and the Fiscal Middleware takes place via the REST interface.
This integration variant is available for Windows, Linux and macOS systems.
Fig. 4. Interface integration
NuGet integration
The Fiscal Client is also provided in the form of .dlls (NuGet packages). This means that the Fiskal middleware can be natively integrated into the respective application programme.
This variant can be used under Windows, Linux, macOS, Android and iOS systems.
Fig. 5. NuGet integration
Service Client integration
In some architectures it may be useful / necessary to combine the features of the two integration variants mentioned above - for example, if the POS software is not able to make REST calls. This is possible through service-client integration.
Here, a service client in the form of .dlls (NuGet packages) is natively integrated into the application software. The service client takes over the function of communicating with the actual fiscal client.
Fig. 6.: Service Client integration
Further planned integration variants
In addition to the three integration variants mentioned above, the following options are planned:
- .com integration via ActiveX
- JavaBean integration (not possible for the time being, as .NET currently does not support JAVA)
Comments
0 comments
Please sign in to leave a comment.