ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaig_5.4.0.1/rzaigconceptsresilientapplications.htm

78 lines
5.6 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Resilient applications" />
<meta name="abstract" content="A resilient application is an application that can be restarted on a different cluster node without requiring you to reconfigure the clients." />
<meta name="description" content="A resilient application is an application that can be restarted on a different cluster node without requiring you to reconfigure the clients." />
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsresilientresources.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigapplicationsmakeappsresilient.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsrecoverydomain.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigapplications.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaigapplications.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="rzaigconceptsresilientapplications" />
<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>Resilient applications</title>
</head>
<body id="rzaigconceptsresilientapplications"><a name="rzaigconceptsresilientapplications"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Resilient applications</h1>
<div><p>A <dfn class="term">resilient application</dfn> is an application
that can be restarted on a different cluster node without requiring you to
reconfigure the clients.</p>
<p>See Making application programs resilient to learn about what characteristics
make an application resilient.</p>
<p>A resilient application needs the ability to recognize the temporary loss
of the Internet Protocol (IP) connection between the client and the server.
The client application must be aware that the IP connection will be temporarily
unavailable and must retry access rather than ending or initiating a failover.
Similarly, if you are performing a switchover, server applications need to
be aware that the IP connection is no longer available. Eventually, an error
condition is returned to the server application. Once this error condition
is received, it is best if the server application recognizes the condition
and ends normally.</p>
<p>IP address takeover is a high availability function that is used to protect
clients from application server outages. An <span class="uicontrol">application takeover
IP address</span> is a floating address that is to be associated with
an application. The concept is to use IP address aliasing to define a floating
IP address that is associated with multiple application servers or hosts.
When one application server in a cluster fails, another cluster node assumes
the responsibilities of the application server without requiring you to reconfigure
the clients.</p>
<p>Also introduced in support of IP address takeover is the concept of application
cluster resource groups (CRGs). Application CRGs are cluster resource groups
that contain an application takeover IP address resource and a recovery domain.
The recovery domain contains the list of application servers within the cluster
that support a particular application. If a single resource fails, cluster
resource services initiates a failover on the group to which the failing resource
belongs.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigconceptsresilientresources.htm" title="Resilient resources are system resources, such as data, devices and applications, that are highly available if you have used clustering on your systems.">Resilient resources</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaigapplicationsmakeappsresilient.htm" title="Learn how to make application programs resilient.">Make application programs resilient</a></div>
<div><a href="rzaigconceptsrecoverydomain.htm" title="A recovery domain is a subset of cluster nodes that are grouped together in a cluster resource group (CRG) for a common purpose such as performing a recovery action or synchronizing events.">Recovery domain</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaigapplications.htm" title="Application resilience is one of the key elements in a clustered environment. If you are planning to write and use highly available applications in your cluster you should be aware that these applications have specific availability specifications.">Cluster applications</a></div>
</div>
</div>
</body>
</html>