How DBServer Works
DATABridge Server (DBServer) is installed automatically on the host when you install the DATABridge software. On the Unisys MCP server, it interacts with DBEngine. On a remote system, DBServer interacts with the DATABridge Client. It supports communications over TCP/IP, BNA, or HLCN and can support up to 100 simultaneous connections to the DATABridge Client. DBServer is required for all DATABridge Clients (including the DMSII Client and DATABridge Twin). It is not required for DATABridge accessories such as Span or Snapshot.
The following describes how DBServer works with other DATABridge components in the replication and update process:
Using Filtered Audit Files
You can have DBServer read audit files that only contain the DMSII data specific for a DATABridge Client. These audit files are “pre-filtered” by the Tanker accessory. To use the Tanker accessory to pre-filter audit files for DBServer, see Tanker Accessory.
DATABridge Client Access
DBServer must be running for a DATABridge Client to connect to it. If it is not running, the DATABridge Client tries to connect until it eventually times out.