Configuring a Cascading Server

If you have multiple clients that access a single data source, you can reduce network traffic and improve performance by setting up cascading Enterprise Server servers. A cascading server configuration is best suited for data sources that are accessed by multiple clients that are either located in different regions or that have different data requirements.

How it works is that you install multiple copies of Enterprise Server -- one for each region -- and network them to a centrally located copy of Enterprise Server. The centrally located copy of Enterprise Server collects data required by all of the regions from the DATABridge Server (DBServer) on the host. It then distributes this data to the networked copies of Enterprise Server. Each “regional” installation of Enterprise Server then caches (filters) the data to fulfill the specific requirements for that region. DATABridge Clients can connect to whichever regional Enterprise Server contains the data they need.

For example, DBE Corporation is the first server in the host chain. Several intermediate servers (called DBE East, DBE West, DBE North, and DBE South) are directly connected to DBE Corporation. Each of these intermediate servers has its own filter and receives and caches data specific to their region (that is, East, West, North, and South). This concept can be extended to any number of intermediate Enterprise Servers, each with its own local filters.

For more information about caching, see Caching.