01.06.2013 Views

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Underst<strong>and</strong>ing server-level <strong>and</strong> connection-level fault tolerance<br />

Underst<strong>and</strong>ing server-level <strong>and</strong> connection-level fault<br />

tolerance<br />

By default, a Unified Broker instance relies on a single controlling NameServer to<br />

resolve client connection requests <strong>and</strong> a single Unified Broker instance to provide<br />

services to the client. You can configure the controlling NameServer so that multiple<br />

NameServer instances are available to resolve any client connection request, thus<br />

providing connection-level fault tolerance. If your product supports load balancing, you<br />

can also configure a single NameServer to resolve each connection request using<br />

multiple Unified Broker instances that support the same Application Service, thus<br />

providing server-level fault tolerance. Figure 9 shows the relationship between these<br />

configuration options.<br />

Client<br />

Server -level<br />

fault tolerance<br />

Unified<br />

Broker<br />

instances<br />

NameServer<br />

instance<br />

Client<br />

Figure 9: Server-level <strong>and</strong> connection-level fault tolerance<br />

These two levels of fault tolerance operate as follows:<br />

Connection -level<br />

fault tolerance<br />

NameServer<br />

instances<br />

Unified<br />

Broker<br />

instance<br />

• Server-level fault tolerance — Allows multiple Unified Broker instances to<br />

register with a NameServer for the same Application Service. A client requesting<br />

a connection is connected to one of several registered Unified Broker instances<br />

that the NameServer determines are available to provide the specified Application<br />

Service. If appropriate weight factors are specified, the NameServer also<br />

balances connection load among the several broker instances. For more<br />

information on load balancing, see the “Underst<strong>and</strong>ing load balancing” section on<br />

page 491.<br />

• Connection-level fault tolerance — Allows you to configure a collection of<br />

NameServers that work together to resolve a client connection request. You can<br />

use two different techniques, individually or together, to implement a fault-tolerant<br />

NameServer collection. This section describes these techniques <strong>and</strong> assumes<br />

that you are familiar with the documentation on using the NameServer with your<br />

Unified Broker product.<br />

You can apply server-level <strong>and</strong> connection-level fault tolerance individually or together<br />

to achieve the level of fault tolerance that your application requires.<br />

<strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> 493

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!