169 lines
10 KiB
HTML
169 lines
10 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="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<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="Example: Identify files section of setup.ini" />
|
||
|
|
<meta name="abstract" content="This part of the setup.ini file contains the informations that identifies the files to be installed on the client workstation." />
|
||
|
|
<meta name="description" content="This part of the setup.ini file contains the informations that identifies the files to be installed on the client workstation." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakxsetup.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakxsetupidfiles" />
|
||
|
|
<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>Example: Identify files section of setup.ini</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakxsetupidfiles"><a name="rzakxsetupidfiles"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Identify files section of setup.ini</h1>
|
||
|
|
<div><p>This part of the setup.ini file contains the informations that
|
||
|
|
identifies the files to be installed on the client workstation. </p>
|
||
|
|
<p>The third portion of the setup file contains sections that
|
||
|
|
identify the files that are to be installed on the client workstation. The
|
||
|
|
section in which a file appears identifies the locations of the source and
|
||
|
|
target for each file. These file sections are used during initial installations
|
||
|
|
or during an upgrade to a new version or release level.</p>
|
||
|
|
<p>The format for file entries in each file section should be <samp class="codeph">n=file.ext</samp>,
|
||
|
|
where <samp class="codeph">n</samp> is the number of the file in that section. The numbering
|
||
|
|
must start with one (1) and increment by one (1) until all of the files are
|
||
|
|
listed in the section. For example:</p>
|
||
|
|
<pre>[Base Files]
|
||
|
|
1=file1.dll
|
||
|
|
2=file2.dll
|
||
|
|
3=file3.dll</pre>
|
||
|
|
<p>In all cases, only the file name and plug-in should be specified. Do not
|
||
|
|
specify directory path names. If a file section contains no entries, the section
|
||
|
|
simply is ignored.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The Programmer's Toolkit provides a sample setup file for three different
|
||
|
|
sample plug-ins: C++, Java™, and Visual Basic.</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="25%" id="d0e34">Section in Setup.ini</th>
|
||
|
|
<th valign="top" width="75%" id="d0e36">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="25%" headers="d0e34 ">[Base Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to \PLUGINS\<VENDOR>.<COMPONENT>
|
||
|
|
under the Client Access install directory. Normally, the ActiveX server DLL
|
||
|
|
(and associated code DLLs) for the plug-in reside here.<p><span class="uicontrol">For C++
|
||
|
|
and Visual Basic</span>, the ActiveX server DLL (and associated code
|
||
|
|
DLLs) for the plug-in reside here.</p>
|
||
|
|
<p><span class="uicontrol">For Java</span>,
|
||
|
|
the Code JAR file name will reside here.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Shared Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the Client Access Shared directory.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[System Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the \WINDOWS\SYSTEM or \WINNT\SYSTEM32 directory.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Core Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the \WINDOWS\SYSTEM or \WINNT\SYSTEM32 directory
|
||
|
|
that are use counted in the registry and are never removed. These are typically
|
||
|
|
re-distributable files.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[MRI Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied from the MRI directories of the plug-in on the iSeries™ server
|
||
|
|
to the CLIENT ACCESS\MRI29XX\<VENDOR>.<COMPONENT> directories
|
||
|
|
on the workstation. This typically is where the locale-dependent resources
|
||
|
|
for a plug-in reside. This will include your Resource MRI DLL name.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Java MRI29xx] (where 29xx is the NLV feature code for the files)</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Java files that are copied from the MRI29xx directory
|
||
|
|
of the plug-in on the iSeries server to the same directory to which the
|
||
|
|
[Base Files] are installed. This typically is where the JAR MRI29xx resources
|
||
|
|
for the plug-in reside. For each MRI29xx directory supported by the Java plug-in,
|
||
|
|
there needs to be a [Java MRI29xx] section listing those files. This only
|
||
|
|
is used by Java plug-ins.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Help files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">The .HLP and .CNT files that are copied from the MRI directories of
|
||
|
|
the plug-in on the iSeries server to the CLIENT ACCESS\MRI29XX\<VENDOR>.<COMPONENT>
|
||
|
|
directories on the workstation. The directory path to these files is written
|
||
|
|
to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\HELP in the Windows<sup>®</sup> registry.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Registry files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">The Windows registry file that is associated with the
|
||
|
|
plug-in.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Dependencies]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Defines the sub components that must be installed before the plug-in
|
||
|
|
can be installed. AS400_Client_Access_Express is needed only if the plug-in
|
||
|
|
requires other sub components, besides the iSeries Navigator base support sub component,
|
||
|
|
to be installed.<p><strong>AS400_Client_Access_Express</strong></p>
|
||
|
|
<ul><li>The sub components are specified in a comma-delimited list. A single subcomponent
|
||
|
|
is specified as a single number (AS400_Client_Access_Express=3). The CWBAD.H
|
||
|
|
header file contains a list of constants that are prefixed with CWBAD_COMP_.
|
||
|
|
These constants provide the numeric values that are used in the comma-delimited
|
||
|
|
list for AS400_Client_Access_Express. There are several CWBAD_COMP_ constants
|
||
|
|
that identify PC5250 font sub components. These constants must not be used
|
||
|
|
in the AS400_Client_Access_Express value and are listed below:</li>
|
||
|
|
</ul>
|
||
|
|
<pre>//5250 Display and Printer Emulator sub components
|
||
|
|
#define CWBAD_COMP_PC5250_BASE_KOREAN (150)
|
||
|
|
#define CWBAD_COMP_PC5250_PDFPDT_KOREAN (151)
|
||
|
|
#define CWBAD_COMP_PC5250_BASE_SIMPCHIN (152)
|
||
|
|
#define CWBAD_COMP_PC5250_PDFPDT_SIMPCHIN (153)
|
||
|
|
#define CWBAD_COMP_PC5250_BASE_TRADCHIN (154)
|
||
|
|
#define CWBAD_COMP_PC5250_PDFPDT_TRADCHIN (155)
|
||
|
|
#define CWBAD_COMP_PC5250_BASE_STANDARD (156)
|
||
|
|
#define CWBAD_COMP_PC5250_PDFPDT_STANDARD (157)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_ARABIC (158)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_BALTIC (159)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_LATIN2 (160)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_CYRILLIC (161)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_GREEK (162)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_HEBREW (163)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_LAO (164)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_THAI (165)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_TURKISH (166)
|
||
|
|
#define CWBAD_COMP_PC5250_FONT_VIET (167)</pre>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The AS400_Client_Access_Express value is used if it exists,
|
||
|
|
otherwise, this section is ignored.</div>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Service Base Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to \PLUGINS\<VENDOR>.<COMPONENT>
|
||
|
|
under the iSeries Access
|
||
|
|
for Windows install
|
||
|
|
directory.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Service Shared Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the iSeries Access for Windows Shared
|
||
|
|
directory.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Service System Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the \WINDOWS\SYSTEM or \WINNT\SYSTEM32 directory.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Service Core Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">Files that are copied to the \WINDOWS\SYSTEM or \WINNT\SYSTEM32 directory.
|
||
|
|
These files are use counted in the registry, are never removed, and are typically
|
||
|
|
re-distributable files.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="25%" headers="d0e34 ">[Service Registry Files]</td>
|
||
|
|
<td valign="top" width="75%" headers="d0e36 ">The Windows registry file that is associated with the
|
||
|
|
plug-in.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxsetup.htm" title="Your plug-in's setup.ini file provides the installation wizard with the information needed to install an iSeries Navigator plug-in on a client workstation. It also provides information that allows the Check Service Level program to determine when the plug-in needs to be upgraded or serviced.">Setup.ini file</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|