131 lines
7.4 KiB
HTML
131 lines
7.4 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="Access iSeries services from the middle tier" />
|
|
<meta name="abstract" content="There are several ways to provide your middle-tier components with access to the iSeries server." />
|
|
<meta name="description" content="There are several ways to provide your middle-tier components with access to the iSeries server." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiithreetier.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaik/rzaikdotnetprovider.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaik/rzaikoledbprovider.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaik/rzaikodbcinterfaces.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaik/rzaikappodbc.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="rzaii3tiertechs" />
|
|
<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>Access iSeries services
|
|
from the middle tier</title>
|
|
</head>
|
|
<body id="rzaii3tiertechs"><a name="rzaii3tiertechs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Access iSeries services
|
|
from the middle tier</h1>
|
|
<div><p>There are several ways to provide your middle-tier components with
|
|
access to the iSeries™ server.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> Middle-tier components cannot have a user interface; therefore, if iSeries Access
|
|
prompts for sign-on information, your three-tier applications may appear to
|
|
hang. To prevent this, developers must use a new system object to specify
|
|
required connection information (user ID and password) to the iSeries server.
|
|
The prompt mode value for this object must be <span class="uicontrol">prompt never</span>.</div>
|
|
<div class="section"><h4 class="sectiontitle">iSeries Access
|
|
for Windows<sup>®</sup> .NET
|
|
Data Provider</h4><p>The <strong>IBM<sup>®</sup> DB2<sup>®</sup> UDB for iSeries .NET Provider</strong> offers the
|
|
best performance to access the iSeries database for programmers that
|
|
write applications using Microsoft's .NET Data Access Framework. Throughout
|
|
this documentation, <span class="uicontrol">Managed Provider</span> is used interchangeably
|
|
with <strong>IBM DB2 UDB
|
|
for iSeries .NET
|
|
Provider</strong> and <span class="uicontrol">IBM.Data.DB2.iSeries data provider</span>.
|
|
Regardless of the name that is referenced, you can take advantage of the full
|
|
set of .NET data types and SQL functionality to make it easy for applications
|
|
to work with data stored securely in your iSeries server databases.</p>
|
|
<p>See .NET
|
|
programming for more information.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">iSeries Access
|
|
for Windows OLE
|
|
DB provider</h4><p>Most applications and components use the iSeries Access
|
|
for Windows OLE
|
|
DB provider through ActiveX Data Objects (ADO). Here are the four primary
|
|
benefits to implementing this technique:</p>
|
|
<ul><li>It allows your developers to make only minor modifications to a single
|
|
interface and programming technique in order to access iSeries programs, commands, SQL queries,
|
|
stored procedures, and physical and logical files.</li>
|
|
<li>It supports automatic data conversions between iSeries and PC data types.</li>
|
|
<li>It allows you to avoid the overhead associated with SQL by providing support
|
|
for record-level file access.</li>
|
|
<li>It is relatively easy to implement and to develop applications. This method
|
|
is generally the most simple technology for developing three-tier applications.</li>
|
|
</ul>
|
|
<p>See OLE DB programming for more information.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">iSeries Access
|
|
for Windows ODBC
|
|
driver</h4><p>Additionally, you can access the iSeries Access ODBC driver through either
|
|
ADO or Remote Data Services (RDS), by using the Microsoft<sup>®</sup> OLE DB provider for ODBC
|
|
(MSDASQL).</p>
|
|
<p>For more information about accessing ODBC through ADO, see
|
|
Choosing an interface to access the ODBC driver.</p>
|
|
<p>For other iSeries Access
|
|
ODBC driver information, see ODBC programming.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> The iSeries Access
|
|
for Windows OLE
|
|
DB provider, and several functions in the iSeries Access ODBC driver, require MDAC
|
|
version 2.5 or later.</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">ActiveX automation objects</h4><p>The iSeries Access
|
|
for Windows client
|
|
provides a library of ActiveX automation objects that your developers can
|
|
use for middle-tier development. These objects provide access to:</p>
|
|
<ul><li>iSeries data
|
|
queues</li>
|
|
<li>Remote commands and distributed program calls</li>
|
|
<li>Administration objects</li>
|
|
<li>iSeries system
|
|
objects</li>
|
|
<li>Data Transfer access to iSeries database tables</li>
|
|
</ul>
|
|
<p>In some cases, ActiveX objects provide greater versatility and functionality
|
|
than ADO, but require slightly more complex programming.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> The iSeries Access
|
|
for Windows client
|
|
includes the automation library from the Windows 95/NT client (the XD1 product).
|
|
These automation objects, including database, do not support use in a three-tier
|
|
environment.</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Express C/C++ APIs</h4><p>iSeries Access for Windows APIs
|
|
provide fast, low-level access to i5/OS™ host servers. However, using these
|
|
APIs requires developers who are experienced with C/C++. Specifically, developers
|
|
must be familiar with C APIs and data types, and must also account for thread-safety
|
|
considerations when creating their components.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiithreetier.htm" title="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.">Use iSeries Access for Windows in a three-tier environment</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="../rzaik/rzaikodbcinterfaces.htm">Choosing an interface to access the ODBC driver</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../rzaik/rzaikdotnetprovider.htm">.NET programming</a></div>
|
|
<div><a href="../rzaik/rzaikoledbprovider.htm">OLE DB programming</a></div>
|
|
<div><a href="../rzaik/rzaikappodbc.htm">ODBC programming</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |