 | Advanced Operations Guide (v10) |  |
|
There are a few significant differences between a server engine and a Workgroup engine. This section explains the differences.
The Linux engine is a server engine only. The Windows server engine runs on Windows 32-bit and 64-bit platforms. The Workgroup engine requires a Windows 32-bit platform.
The Server Engine for Windows is installed to run as a Windows Service. The Workgroup Engine can be installed to run as an application or as a service. See Getting Started With Pervasive PSQL. If installed to run as an application, the Workgroup Engine uses a tray icon for an interface.
The server engine enforces file permissions set up in the operating system. The Workgroup engine does not authenticate users on its own. With the Workgroup engine, if you can see the computer on the network, you can get to the data. This relaxed security is intended for small offices where security is not an issue and ease of use is.
A behavior difference between the Server and Workgroup engines with regard to this lack of OS authentication on the part of the Workgroup engine is that the Mixed security policy for Btrieve is the same as the Classic security policy.
The Workgroup engine creates locator files everywhere it opens files, allowing the engine to dynamically adjust gateway ownership on a day-to-day basis. By default, the Workgroup engine also runs under a user ID, which can be authenticated on other computers and network devices. The Server engine runs as system services. The services typically do not have access rights to files on other computers or network devices. Therefore, replacing a Workgroup engine with a Server engine as a gateway in a workgroup environment is not supported.
The server engines start at 10 concurrent connections and the Workgroup engine starts at 5.
The server engine for Windows makes use of Asynchronous I/O. This feature can provide a significant performance advantage.
|
Chapter contents
Prev topic: Networking
|