{"id":31923,"date":"2016-12-16T11:14:04","date_gmt":"2016-12-16T19:14:04","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/system-config-2\/communication\/"},"modified":"2020-05-19T12:23:38","modified_gmt":"2020-05-19T19:23:38","slug":"communication","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/system-configuration\/communication\/","title":{"rendered":"Communication"},"content":{"rendered":"
Ephesoft Transact is a thin-client application so there is no client-side software that needs to be installed. It is designed so that centralized access can be achieved for administrators and operators, regardless of their location. Proper firewall routing, port-forwarding and DNS configurations are necessary if communication with remote administrators or operators is needed.<\/p>\n
Communication from a client workstation is performed using HTTP\/HTTPS through a standard web browser. This includes configuration and maintenance of the system along with operator functions, such as web scanning, batch uploads and exception handling.<\/p>\n
The diagram below shows how communication takes place between different tiers of an Ephesoft Transact infrastructure, including remote admins\/operators. This is not the only way to architect an Ephesoft installation but is a highly secure, recommended approach.<\/p>\n