clearString neatComponents 
Documentation

  

neatComponents is the hybrid-cloud database engine that powers clearString.

Previous pageIntersite Communication Next page
Introduction to Intersite Communication 

This section describes the features provided to facilitate the communication of data between sites.

Communication between sites is key to:

  • Creating Scalable solutions
  • Allowing strategic reuse of modules of functionality

In describing the processes involved we will be referring to two sites:

Site A

This is the site that starts a process by sending data.

Site B

This is the site that receives this data.
This may also send data back to Site A as a response.

In a real-world scenario more than two sites can be communicating with each other, but each individual communication will be between two sites

You may also have communication working in both directions, so the roles of the two sites are reversed depending on the particular process flow.

Communication process

Security is inherent in the communication, so before any communication can occur API keys and secrets need to be set up to ensure connections are only accepted from authorised counterparties.

Diagnostics fields are provided to allow for communication errors or misconfigurations to be understood and corrected.

Once security is set up. the communication process involves:

  1. Site A. Preparing the data to be sent using a query and view
  2. Site A. Sending the data
  3. Site B. Receiving that data
  4. Site B. Importing the received data into tables
  5. Site B. Responding back with data
  6. Site A. Receiving the response data
  7. Site A. Importing the response data into tables

The following pages (listed on the right) detail the configuration required.

Additional Resources

Intersite Communication 
Copyright © 2025 Enstar LLC    All rights reserved Print this pageTranslate: