We are preparing a new source of documentation for you. Work in progress!

Difference between revisions of "Client and server communication"

From Resco's Wiki
Jump to: navigation, search
(Created page with "== Resco Cloud == The Resco Mobile application (client) communicates directly with the Resco Cloud server (public or private). To synchronize the Resco Mobile CRM application...")
 
(Resco Cloud: remove reference to TLS 1.0)
Line 1: Line 1:
 
== Resco Cloud ==
 
== Resco Cloud ==
  
The Resco Mobile application (client) communicates directly with the Resco Cloud server (public or private). To synchronize the Resco Mobile CRM application with Resco Cloud, only the connectivity to the standard Resco Web Services is required. All the communication between the app and Resco Cloud uses standard web services via HTTPS protocol secured by the TLS 1.2, TLS.1.1 and TLS 1.0 certificates.
+
The Resco Mobile application (client) communicates directly with the Resco Cloud server (public or private). To synchronize the Resco Mobile CRM application with Resco Cloud, only the connectivity to the standard Resco Web Services is required. All the communication between the app and Resco Cloud uses standard web services via HTTPS protocol secured by the TLS 1.2 and TLS 1.1 certificates.
  
 
If you are deploying an on-premise instance of Resco CRM server, you can also take advantage of [https://en.wikipedia.org/wiki/Virtual_private_network VPN] and [https://en.wikipedia.org/wiki/DirectAccess DirectAccess] connection for additional security of the data transfer.
 
If you are deploying an on-premise instance of Resco CRM server, you can also take advantage of [https://en.wikipedia.org/wiki/Virtual_private_network VPN] and [https://en.wikipedia.org/wiki/DirectAccess DirectAccess] connection for additional security of the data transfer.

Revision as of 07:34, 10 December 2019

Resco Cloud

The Resco Mobile application (client) communicates directly with the Resco Cloud server (public or private). To synchronize the Resco Mobile CRM application with Resco Cloud, only the connectivity to the standard Resco Web Services is required. All the communication between the app and Resco Cloud uses standard web services via HTTPS protocol secured by the TLS 1.2 and TLS 1.1 certificates.

If you are deploying an on-premise instance of Resco CRM server, you can also take advantage of VPN and DirectAccess connection for additional security of the data transfer.

Microsoft Dynamics CRM and Dynamics 365 synchronization

The Resco Mobile application (client) communicates directly with the Dynamics CRM server.

Connection to Microsoft Dynamics CRM.png

When synchronizing the Resco Mobile app with Microsoft Dynamics CRM, the communication uses standard Dynamic CRM web services provided by Microsoft. There is no middleware or transient data storage. The CRM data is not stored (or cached) anywhere except for the local storage on the client. The local storage (SQL database and files) contains only the configured subset of the CRM data. Selected CRM data (entities) can be configured to be "online only", in which case it is not stored on the client at all.

For Mobile CRM Client Access License validation, the system uses only a minimal dataset needed for validation of the license for the particular Dynamics CRM users. See Resco licensing service for additional details about the licensing.

Salesforce synchronization

When connected to Salesforce, the Resco Mobile app communicates with Resco Cloud to download metadata (object schema, mobile customizations) and with Salesforce’s SOAP and REST APIs to manipulate the business data (objects and fields).

Connection to Salesforce CRM.png

To download metadata from Resco Cloud, connectivity to standard Resco Web Services is required. All the communication between the app and Resco Cloud uses standard Web Services via HTTPS protocol secured by the TLS 1.2, TLS.1.1 and TLS 1.0 certificates.

Data synchronization with Salesforce, the target organization, must support access to its data via standard Salesforce API.

See also

For more information about overall architecture security, read also: