The communication from the clients' browser to the zapliance application server is via HTTP.
The communication from zapliance to SAP is via the SAP Java Connector (see paragraph below)
Extracted data is stored locally in the zapliance installation folder (default) or the selected zapliance workspace folder.
zapliance does not need an internet connection, but a connection to the SAP server for the duration of the data extraction.
If the client browser PC has an internet connection, zapliance accesses zapliance.com to show you the current blog article on the login screen. Apart from this exception, the application does not communicate outside your local network. Technically, the Internet connection is not necessary for the program to function correctly.
Note: Make sure that the firewall does not block the connection between the zapliance application server to your SAP server.
The SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound (Java calls ABAP) and outbound calls (ABAP calls Java). SAP JCo can be implemented with Desktop applications and with Web server applications. -- SAP Help
Note: zapliance is not shipped as a Java application! You do not need Java to run zapliance!
JCo uses the SAP program RFC (Remote Function Call) to extract data from the SAP system to your local zapliance instance. For this, you need an SAP User with sufficient privileges. These are only READ permissions. You can monitor all activities of SAP Users via the SAP transaction 'STAD'.
Use transaction 'SM19' to configure SAP user traces. For this consult your SAP admin or the SAP Help Portal.