57 lines
3.5 KiB
HTML
57 lines
3.5 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-10-17" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
|
<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))' />
|
|
<title>Configure OptiConnect</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
|
|
<a name="configure"></a>
|
|
<h1 id="configure">Configure OptiConnect</h1>
|
|
<p>Any iSeries™ server application that was written to use Distributed Data Management
|
|
(DDM) can use OptiConnect. This is true for existing applications as well
|
|
as new applications. Many applications that use an iSeries server database
|
|
can transparently use DDM without changes to the application. OptiConnect
|
|
uses the same mechanism as traditional DDM, where the DDM file controls access
|
|
to a database. Applications that access a database by using OptiConnect DDM
|
|
can also use traditional APPC DDM to access another database at the same time.</p>
|
|
<p>There are two ways to route data requests through OptiConnect. The first
|
|
is the <span class="bold">Fastpath OptiConnect</span> method and involves specifying
|
|
a special keyword in the DDM file. The second method involves setting up <span class="bold">Extended Function Path OptiConnect</span>. If you are using the
|
|
Fastpath method, OptiConnect agent jobs start in the OptiConnect Connection
|
|
Manager and run in the QSOC subsystem. These jobs follow the OptiConnect
|
|
job naming convention. Fastpath OptiConnect is the faster means of communication
|
|
due to shorter code path, but two-phase commit protocols are not supported.</p>
|
|
<p>If the Extended Function Path method is used, OptiConnect agent jobs are
|
|
started by the advanced program-to-program communications (APPC) attach manager
|
|
and run in QCMN subsystem. The agent job names follow the standard DDM naming
|
|
conventions for communication jobs. Two-phase commit protocols are supported.</p>
|
|
<p>The following information discusses the various ways you can configure
|
|
OptiConnect:</p>
|
|
<ul>
|
|
<li><a href="rzau3route1.htm#route1">Configure fastpath OptiConnect routing</a></li>
|
|
<li><a href="rzau3ctld.htm#ctld">Configure extended function path routing</a></li>
|
|
<li><a href="rzau3custom.htm#custom">Customize OptiConnect</a></li>
|
|
<li><a href="rzau3advcfg.htm#advcfg">Advanced OptiConnect customization</a></li>
|
|
<li><a href="rzau3tcpip.htm#tcpip">TCP/IP over OptiConnect</a></li></ul>
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|