ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakx_5.4.0.1/rzakxhowtodistrub.htm

139 lines
7.7 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="Distribute plug-ins" />
<meta name="abstract" content="Deliver your plug-in code to iSeries Navigator users by including it with your i5/OS applications." />
<meta name="description" content="Deliver your plug-in code to iSeries Navigator users by including it with your i5/OS applications." />
<meta name="DC.Relation" scheme="URI" content="rzakxplugsuport.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxsetup.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxmrisetup.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakxhowtodistrub" />
<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>Distribute plug-ins</title>
</head>
<body id="rzakxhowtodistrub"><a name="rzakxhowtodistrub"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Distribute plug-ins</h1>
<div><p>Deliver your plug-in code to iSeries™ Navigator users by including
it with your i5/OS<sup>®</sup> applications.</p>
<p>The installation program for the application writes the plug-in's code
binaries, registry file, and translatable resources to a folder in the iSeries server
integrated file system. After completing this process, your end users can
obtain the plug-in from the iSeries Access for Windows<sup>®</sup> folder (with the help of an iSeries NetServer
mapped network drive) using the iSeries Access for Windows Selective
Setup program. Selective Setup copies your plug-in code to the user's machine,
downloads the appropriate translatable resources based on the language settings
on the user's PC, and runs the registry file to write your plug-in's registry
information to the Windows registry. If you are not initially installed,
you can also install plug-ins on the initial install using the custom option.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e45">For this type of plug-in...</th>
<th valign="top" id="d0e47">Install in this directory...</th>
<th valign="top" id="d0e49">And include these files...</th>
</tr>
</thead>
<tbody><tr><td valign="top" headers="d0e45 ">C++</td>
<td valign="top" headers="d0e47 "> /QIBM/USERDATA/OpNavPlugin/ &lt;vendor&gt;.&lt;component&gt; (To prevent
installation without iSeries Access for Windows) </td>
<td valign="top" headers="d0e49 "> <ul><li>The registry file for the plug-in.</li>
<li>The iSeries Access
for Windows setup
file for the plug-in.</li>
<li>The ActiveX server DLL for the plug-in, and any associated code DLLs.</li>
</ul>
</td>
</tr>
<tr><td valign="top" headers="d0e45 ">Java™</td>
<td valign="top" headers="d0e47 ">/QIBM/USERDATA/OpNavPlugin/ &lt;vendor&gt;.&lt;component&gt; (Java plug-ins
require iSeries Access) </td>
<td valign="top" headers="d0e49 "> <ul><li>The registry file for the plug-in.</li>
<li>The iSeries Access
for Windows setup
file for the plug-in.</li>
<li>The Java JAR file contains all Java classes, HTML, .gif, PDML, PCML, and
serialization files..</li>
</ul>
</td>
</tr>
<tr><td valign="top" headers="d0e45 ">Visual Basic</td>
<td valign="top" headers="d0e47 ">/QIBM/USERDATA/OpNavPlugin/ &lt;vendor&gt;.&lt;component&gt; (VB plug-ins
require iSeries Access
for Windows)</td>
<td valign="top" headers="d0e49 "> <ul><li>The registry file for the plug-in.</li>
<li>The iSeries Access
for Windows setup
file for the plug-in.</li>
<li>The ActiveX server DLL for the plug-in, and any associated code DLLs.</li>
</ul>
</td>
</tr>
</tbody>
</table>
</div>
<div class="note"><span class="notetitle">Notes:</span> </div>
<ul><li>The &lt;vendor&gt;.&lt;component&gt; subdirectory must match the one specified
in the registry file.</li>
<li>Support for the GUIPlugin location will be removed in a future release
so you should migrate your plug-ins to the OpNavPlugin location.</li>
</ul>
<p>Additionally, all plug-ins must create at least one directory below the &lt;vendor&gt;.&lt;component&gt;
subdirectory called MRI29XX, where XX identifies a supported language. For
example, MRI2924 (English). This directory should contain the correct national
language version of the following items:</p>
<ul><li>The resource DLL for the plug-in</li>
<li>The help files for the plug-in</li>
<li>The MRI setup file for the plug-in.</li>
</ul>
<div class="section"><h4 class="sectiontitle">Upgrading or uninstalling the plug-in</h4><p>After the
users have installed your new plug-in, you may choose either to upgrade it
at a later date or ship bug fixes. When the code is upgraded on the iSeries server,
the iSeries Access
Check Version program will detect that this process has occurred and automatically
download the updates onto the users machines. iSeries Access for Windows also
provides uninstall support, which lets your users completely remove the plug-in
from their machines anytime they wish. Users can learn what plug-ins are installed
on their machines by clicking on the Plug-ins tab on the iSeries Navigator
Properties for an iSeries server.</p>
</div>
<div class="section"><h4 class="sectiontitle">Restricting access to the plug-in with system policies and
Application Administration</h4><p>If you provide a Windows policy
template with your plug-in, you can also take advantage of Windows system
policies to control which network users can install your plug-in. Additionally,
you can use the iSeries server
based Application Administration support in iSeries Navigator to control which users
and user groups can access your plug-in.</p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzakxsetup.htm">Setup.ini file</a></strong><br />
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.</li>
<li class="ulchildlink"><strong><a href="rzakxmrisetup.htm">MRI setup file</a></strong><br />
Provides the iSeries Access for Windows Selective Setup program with the information it needs to install the locale-dependent resources that are associated with an iSeries Navigator plug-in on a client PC.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxplugsuport.htm" title="iSeries Navigator Plug-in support provides a convenient way to integrate your own functions and applications into a single user interface: iSeries Navigator.">Plug-in support in iSeries Navigator</a></div>
</div>
</div>
</body>
</html>