DOCS

Rochade Architecture

The Rochade client/server architecture is based on the use of a central Rochade Server that supplies the clients that are connected to it via a communication interface with data from the Rochade databases. The following illustration displays a simple diagram of this architecture.

Rochade Client/Server Architecture

The Rochade Server has these characteristics:

  • It can operate on several databases. All databases that can be accessed by it form a Rochade data space. The server has exclusive access to this data space.
  • Several clients can use the services of the server at the same time.
  • The server supports the execution of several requests running simultaneously.
  • All Rochade write operations are executed as transactions in the server to maintain consistency in the database even if a write operation is aborted.
  • Server aborts will not lead to a loss of data or to data corruption. When the server is started up again after an abort, connected databases are checked for consistency, and where necessary, are automatically reconstructed. In this way, interrupted write actions are either completed or reset.
  • The server is able to recognize and react immediately to inconsistencies in the data supplied to it.
  • You can control the operating mode of the server using special settings in the initialization file.
  • The server maintains a server event log that contains an entry for each significant event that occurs during the server’s operation. The log provides valuable information for isolating the cause of errors and unexpected behavior by the server. ASG, therefore, recommends that you check it on a regular basis.
  • For details about the messages and error codes that may occur in the server event log, see Messages and Return Codes.

    You can use Metability to check the server event log, create backups, and to start new logs.

  • The server can maintain LOG files for all databases connected to it so that, if necessary, a restore can be carried out on the databases.
  • The server functions correctly in a virtual environment (also called a virtual server). You must make sure, however, to shut down the server before stopping the virtual server; otherwise, it cannot close the databases, which can lead to inconsistencies.