|
|
|
FairCom RTG is intended as a client/server architecture offering many advantages a single-server process can provide in total file coordination including transaction control, encryption, hot backups, etc.
However, by not going through the FairCom RTG Database Server, database I/O can at times be faster, typically when there is only a single instance performing database I/O. In addition, inter-process communication between client and server is eliminated. This model of access is termed standalone; the FairCom RTG COBOL process physically accesses files in the file system without reliance on a central server process (faircom.exe in V3 or ctreesql.exe in prior releases).
Possible use cases for standalone usage include high-speed data load (when loading a single file at a time – when loading multiple files concurrently, use of the FairCom RTG Database Server is still recommended), storing data locally on the application side for convenience, or for having local data storage that is only available to the client application, and therefore not shareable by other users.
Standalone support is enabled with the <localinstance> element of your local FairCom RTG ctree.conf configuration file. All <file> rules defined within a <localinstance> section cause matching files to be created/opened directly in the local machine (standalone model) rather than on the server environment.
Note: <localinstance> and (although not discussed here) <redirinstance> are only supported for the FairCom RTG BTRV interface and the COBOL ExtFH interface (Micro Focus).
