The NetWare RuntimeTM serialized NetWare operating system differs from the other versions of NetWare in that it grants file service access to only one NetWare login client connection. This login is for system administration purposes.
NetWare Runtime does not limit the number of SPX or AppleTalk* connections between client applications and NLM-based services. Consequently, NetWare Runtime does not limit the number of users that can access NetWare Btrieve running on the Runtime server.
Figure 12 illustrates the relationship between a NetWare configuration that is not dedicated to database services and a NetWare Runtime configuration that is dedicated to database services.
Figure 12. NetWare Configurations
Running NetWare Btrieve on a server dedicated to database management ensures that all the server's processing power is directed toward database applications. If you anticipate heavy file service activity, a dedicated database server makes that activity more efficient because it frees the nondedicated server to devote all its resources to file services.
Having a dedicated database server is also particularly effective in preventing slow performance on the network during periods of heavy file service activity. To optimize network performance, you can configure so as to include a dedicated database server in addition to other servers offering full NetWare 4 services.
Figure 13 shows an example installation for NetWare Runtime.
The installation procedure for NetWare Runtime is identical to installing the other versions of NetWare. Refer to the documentation that accompanies your NetWare Runtime software for instructions.
Figure 13. NetWare Runtime Installation 
NetWare Runtime supplies a facility (NLICLEAR.NLM) that clears unused connections.
NetWare Runtime provides only one available client connection. Even after the administrator logs out of the application server, a connection is maintained between the workstation and the server. If a second administrator wants to log on to the application server from a second workstation, the single connection will be unavailable.
The NLICLEAR facility is important for NetWare Runtime because, at intervals, NLICLEAR automatically clears the unused connections left after an administrator logs out of the application server. This allows another administrator to log in to and administer the database server.
When you load the Btrieve DOS or OS/2 Requester using the option /C:1, username, password, Btrieve logs in to the NetWare Runtime server with the specified username and the corresponding password. Btrieve also obtains a temporary connection number, which it uses to distinguish between users.
Btrieve verifies that the user has the acceptable rights to open or create a file. Btrieve then logs out of the server, using the temporary connection number. If the user has the appropriate file access rights, Btrieve continues; otherwise, it returns an error.
NOTE: The administrator must set up file access rights on the NetWare Runtime server.
When you load the Btrieve DOS or OS/2 Requester using the /C:1 default option (without specifying a username and password) and then attempt to read a file on the NetWare Runtime server, the Requester must determine what login username Btrieve can use to maintain NetWare security. Btrieve then uses that username to log in temporarily for the client.
In contrast, if the Requester detects that there is no connection, or if it cannot find a valid login username, the Requester returns an error.
For more information about the NetWare Runtime server support option available with the DOS and OS/2 Requesters, see Chapter 4, "Configuring and Using the Requesters."