On the Windows NT server data access shows to be extremely slow as soon as more than one user opens a file. The reason for this is that data cannot be buffered with the client. The EBUS-Server produces relief here and provides a significant speed increase.

The EBUS-Server is a pure client-server application that runs only on the NT server at the moment and communicates with the EBUS client program via Remote Procedure Calls (RPC). All data access runs directly on the NT server, only the data sets found are transported via network. This results in a significant speed increase compared to the decentralized data access of the client.

With the EBUS-Server data can be reorganised from every EBUS client with the same speed that could so far only be reached with the direct reorganisation on the NT server.
Since the index files are solely opened by the EBUS-Server, the crash of one EBUS client does no longer result in reorganisation of the index files.

The EBUS-Server also allows RAS access via ISDN or DSL with satisfactory speed.
It is very easy to integrate the EBUS-Server into an EBUS program. To establish a connection with the EBUS-Server the following order must be inserted into the EBUS client program:

SERVER = <PROTOCOL>,<SERVERNAME>,<ENDPOINT>

With TCP/IP the specification of the server name and the protocol is sufficient. If the server has the name SERVER1 e.g., the following order has the effect that all index files of the program are accessed via RPC:

SERVER = "ncacn_ip_tcp","SERVER1",""

With the order SERVER the name of a single index file can be given as well, e.g.:

SERVER(ARTICLE) = "ncacn_ip_tcp","SERVER2",""

In addition, every single index file can be opened on a different NT server.