89 lines
7.3 KiB
HTML
89 lines
7.3 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Network redundancy considerations for a distributed relational database" />
|
|
<meta name="abstract" content="Network redundancy provides different ways for users on the distributed relational database network to access a relational database on the network." />
|
|
<meta name="description" content="Network redundancy provides different ways for users on the distributed relational database network to access a relational database on the network." />
|
|
<meta name="DC.subject" content="network redundancy, redundancy, communications network, command, WRKCFGSTS (Work with Configuration Status), Work with Configuration Status (WRKCFGSTS), command, CL, WRKCFGSTS (Work with Configuration Status), Work with Configuration Status (WRKCFGSTS), configuration status, working with, VRYCFG (Vary Configuration), Vary Configuration (VRYCFG), Vary Configuration (VRYCFG), configuration, varying" />
|
|
<meta name="keywords" content="network redundancy, redundancy, communications network, command, WRKCFGSTS (Work with Configuration Status), Work with Configuration Status (WRKCFGSTS), command, CL, WRKCFGSTS (Work with Configuration Status), Work with Configuration Status (WRKCFGSTS), configuration status, working with, VRYCFG (Vary Configuration), Vary Configuration (VRYCFG), Vary Configuration (VRYCFG), configuration, varying" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1recover.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/vrycfg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrkcfgsts.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbal1netredund" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Network redundancy considerations for a distributed relational database</title>
|
|
</head>
|
|
<body id="rbal1netredund"><a name="rbal1netredund"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Network redundancy considerations for a distributed relational database</h1>
|
|
<div><p>Network redundancy provides different ways for users on the distributed
|
|
relational database network to access a relational database on the network.</p>
|
|
<p> If there is only one communications path from an application requester
|
|
(AR) to an application server (AS), when the communications line is down,
|
|
users on the AR do not have access to the AS relational database. For this
|
|
reason, network redundancy considerations are important to the distributed
|
|
relational database administrator for the Spiffy Corporation. For example,
|
|
consider service booking or customer parts purchasing issues for a dealership.
|
|
When a customer is waiting for service or to purchase a part, the service
|
|
clerk needs access to all authorized tables of enterprise information to schedule
|
|
work or sell parts.</p>
|
|
<p>If the local server is down, no work can be done. If the local server is
|
|
running but a request to a remote server is needed to process work and the
|
|
remote server is down, the request can not be handled. In the Spiffy Corporation
|
|
example, this might mean that a dealership cannot request parts information
|
|
from a regional inventory center. Also, if an AS that handles many AR jobs
|
|
is down, none of the ARs can complete their requests. In the case of the Spiffy
|
|
Corporation network, if a regional center is down, none of the application
|
|
servers it supports can order parts.</p>
|
|
<p>Providing the region's dealerships with access to regional inventory data
|
|
is important to the Spiffy Corporation distributed relational database administrator.
|
|
Providing paths through the network to data can be addressed in several ways.
|
|
The original network configuration for the Spiffy Corporation linked the end
|
|
node dealerships to their respective network node regional centers.</p>
|
|
<div class="fignone" id="rbal1netredund__rbal1netred"><a name="rbal1netredund__rbal1netred"><!-- --></a><span class="figcap">Figure 1. Alternative network paths</span><br /><img src="rv2w739.gif" alt="Alternative Network Paths" /><br /></div>
|
|
<p>An alternative for some dealerships might be a switched-line connection
|
|
to a different regional center. If the local regional center is unavailable
|
|
to the network, access to another AS allows the requesting dealership to obtain
|
|
information needed to do their work. In the first figure, some ARs served
|
|
by the MP000 server establish links to the KC000 server, which can be used
|
|
whenever the MP000 server is unavailable. The <span class="cmdname">Vary Configuration
|
|
(VRYCFG)</span> or <span class="cmdname">Work with Configuration Status (WRKCFGSTS)</span> command
|
|
can be used by a server operator or distributed relational database administrator
|
|
to vary the line on when needed and vary the line off when the primary AS
|
|
is available. </p>
|
|
<p>Another alternative might be if one of the larger area dealerships also
|
|
acted as an AS for other dealerships. As shown in the second figure, an end
|
|
node is only an AS to other end nodes through its network node. In the first
|
|
figure, if the link to Minneapolis is down, none of the dealerships can query
|
|
another (end node) for inventory. The configuration illustrated above can
|
|
be changed so that one of the dealerships is configured as an APPN network
|
|
node, and lines to that dealership from other area dealerships are set up.</p>
|
|
<div class="fignone" id="rbal1netredund__rbal1altas"><a name="rbal1netredund__rbal1altas"><!-- --></a><span class="figcap">Figure 2. Alternate application server</span><br /><div class="imageleft"><img src="rv2w744.gif" alt="Alternate Application Server" /></div><br /></div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1recover.htm" title="In a distributed relational database environment, data availability not only involves protecting data on an individual server in the network, but also ensuring that users have access to the data across the network.">Data availability and protection</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../cl/vrycfg.htm">Vary Configuration (VRYCFG) command</a></div>
|
|
<div><a href="../cl/wrkcfgsts.htm">Work with Configuration Status (WRKCFGSTS) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |