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:

  1. The Client calls DBServer to retrieve information for a DMSII database.
  2. DBServer calls DBEngine to clone the database, and DBEngine accesses the DMSII database via DMSII access routines.
  3. DBServer receives the records from DBEngine, calls the filter and format in the Support library, and then sends the records to the Client.
  4. DBServer then calls DBEngine to retrieve updates that occurred during and following the extraction.
  5. The Engine reads the audit trail and sends the information to DBServer, which calls the filter and format in the Support library.
  6. DBServer sends the changed information from the audit file to the Client.

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.