102 lines
6.1 KiB
HTML
102 lines
6.1 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="Use iSeries Access for Windows in a three-tier environment" />
|
||
|
|
<meta name="abstract" content="By installing iSeries Access for Windows on the middle tier of a three-tier environment, a wide variety of client workstations can access iSeries services." />
|
||
|
|
<meta name="description" content="By installing iSeries Access for Windows on the middle tier of a three-tier environment, a wide variety of client workstations can access iSeries services." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiimultiuser.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiimts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaii3tiertechs.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="rzaiithreetier" />
|
||
|
|
<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>Use iSeries Access
|
||
|
|
for Windows in
|
||
|
|
a three-tier environment</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiithreetier"><a name="rzaiithreetier"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use iSeries Access
|
||
|
|
for Windows in
|
||
|
|
a three-tier environment</h1>
|
||
|
|
<div><p>By installing iSeries™ Access for Windows<sup>®</sup> on the middle tier of a three-tier
|
||
|
|
environment, a wide variety of client workstations can access iSeries services.</p>
|
||
|
|
<p>Additionally, three-tier environments present several other advantages:</p>
|
||
|
|
<ul><li><strong>Improved integration between diverse clients and server applications:</strong> Multiple
|
||
|
|
end-user applications running on various clients can communicate with multiple
|
||
|
|
applications on a Windows server simultaneously. Each of the applications
|
||
|
|
on the Windows server can also, simultaneously, communicate
|
||
|
|
with multiple databases.</li>
|
||
|
|
<li><strong>Enhanced transaction management using Microsoft<sup>®</sup> Transaction Server (MTS):</strong> Three-tier
|
||
|
|
environments allow for more complex transactions, some of which may depend
|
||
|
|
upon each other for their own successful completion. (All transactions must
|
||
|
|
complete successfully in order for any of them to complete.)</li>
|
||
|
|
<li><strong>Importing data from an iSeries server into Web pages, using Microsoft Internet
|
||
|
|
Information Server (IIS):</strong> IIS can use Active Server Pages to dynamically
|
||
|
|
update Web pages with data from a DB2 Universal Database™ for iSeries.</li>
|
||
|
|
</ul>
|
||
|
|
<p>All three-tier environments separate components and applications into three
|
||
|
|
layers. The three layers may reside on separate PCs, or terminals, and communicate
|
||
|
|
over a network. Generally the tiers will have the following characteristics:</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Client tier</h4><p>This layer contains the interface and
|
||
|
|
applications that allow end users to manipulate data. For example, this may
|
||
|
|
involve a Web browser running on a network station, or a custom-built application
|
||
|
|
using a remote component. This layer does not use the iSeries Access for Windows client.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Middle tier</h4><p>This layer contains the business or
|
||
|
|
application logic. In environments using iSeries Access for Windows,
|
||
|
|
this layer should consist of a Windows server running a Microsoft Active
|
||
|
|
Server Pages script or a remote component. </p>
|
||
|
|
<p>This layer uses Microsoft's
|
||
|
|
Internet Information Server (IIS) and can, optionally, use Component Services
|
||
|
|
or Microsoft Transaction
|
||
|
|
Server for distributed transactions. The script uses the ADO.NET provder,
|
||
|
|
OLE DB provider, or ODBC driver that are included with iSeries Access for Windows.
|
||
|
|
These clients communicate with the database tier to get data from the iSeries server. </p>
|
||
|
|
<p>Refer
|
||
|
|
to the following topics for more information about the middle-tier:</p>
|
||
|
|
<ul><li>Use Microsoft Transaction Server (MTS)</li>
|
||
|
|
<li>Access iSeries services
|
||
|
|
from the middle tier</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Database tier</h4><p>This layer usually consists of a DB2
|
||
|
|
Universal Database™ for iSeries database. Your applications can access this
|
||
|
|
and various iSeries services
|
||
|
|
through host server programs, or through custom-built iSeries programs.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaiimts.htm">Use Distributed transaction support</a></strong><br />
|
||
|
|
The iSeries Access
|
||
|
|
for Windows client
|
||
|
|
supports Microsoft Transaction Server (MTS) and the Component
|
||
|
|
Services model, with the iSeries Access ODBC driver and the IBMDASQL OLE DB
|
||
|
|
provider.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaii3tiertechs.htm">Access iSeries services from the middle tier</a></strong><br />
|
||
|
|
There are several ways to provide your middle-tier components with
|
||
|
|
access to the iSeries server.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiimultiuser.htm" title="Learn how iSeries Access for Windows allows you to make services, that are on your server, available to client PCs, in different network environments. Also learn how to administer a PC that has multiple users.">iSeries Access for Windows network environments</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|