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

106 lines
7.6 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="Customize the plug-in registry files" />
<meta name="abstract" content="After modifying the sample plug-ins, you'll need to make some modifications to the registry files. This topic provides a walk-through of the registry files for each type of plug-in, and recommends some modifications." />
<meta name="description" content="After modifying the sample plug-ins, you'll need to make some modifications to the registry files. This topic provides a walk-through of the registry files for each type of plug-in, and recommends some modifications." />
<meta name="DC.Relation" scheme="URI" content="rzakxpluginreference.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxsmpcplusreg.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxsmpvbreg.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxsmpjvreg.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxproperty.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxconstructvbproppgs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxjavaproperty.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakxsslregistryentry.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakxcreateplugin" />
<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>Customize the plug-in registry files</title>
</head>
<body id="rzakxcreateplugin"><a name="rzakxcreateplugin"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Customize the plug-in registry files</h1>
<div><p>After modifying the sample plug-ins, you'll need to make some modifications
to the registry files. This topic provides a walk-through of the registry
files for each type of plug-in, and recommends some modifications.</p>
<p>Registry files identify plug-ins to iSeries™ Navigator, describe their functions,
and specify any prerequisites for using the plug-in.</p>
<p>The sample plug-ins include two registry files: a windows-readable copy
for use during development, and a copy for distribution on the iSeries server.
You'll need to make some modifications to these registry files after developing
your plug-in. To help you make those changes, this topic provides an overview
of the registry files, and detailed descriptions of the required sections
of each registry file.</p>
<p>iSeries navigator
uses the registry files to learn about the plug-ins existence, requirements
and functions. In order to provide that information every plug-in must specify
at least the following information:</p>
<ul><li>A "primary" registry key that that provides global information about the
plug-in. This section includes the Programmatic Identifier (ProgID) which
specifies the vendor and component name for your plug-in, and will also name
the folder in which your plug-in resides on the iSeries server. The ProgID must follow
the form &lt;vendor&gt;.&lt;component&gt;, i.e. IBM<sup>®</sup>.Sample.</li>
<li>Registry keys that identify the object types in the iSeries Navigator
hierarchy for which a plug-in intends to supply additional function.</li>
<li>A separate registry key for the root of each sub tree of objects that
a plug-in adds to the object hierarchy. This key contains information about
the root folder of the sub tree.</li>
</ul>
<p><strong>Descriptions of the required sections of the registry files, and the
recommended changes:</strong></p>
<ul><li>C++ registry files</li>
<li>VB registry files</li>
<li>Java™ registry
files</li>
</ul>
<p><strong>Special considerations for the registry files</strong></p>
<ul><li>Property sheet handling in C++</li>
<li>Property sheet handling in VB</li>
<li>SSL support in plug-ins</li>
</ul>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzakxsmpcplusreg.htm">Customize the C++ registry values</a></strong><br />
The sample plug-includes two registry files: SAMDBG.REG, a windows-readable
registry file for use during development and SAMPRLS.REG, a registry file
for distribution on the iSeries server.</li>
<li class="ulchildlink"><strong><a href="rzakxsmpvbreg.htm">Customize the VB plug-in registry values</a></strong><br />
The sample plug-includes two registry files: VBSMPDBG.REG, a windows-readbale registry file for use during development and VBSMPRLS.REG, a registry file for distribution on the iSeries server.</li>
<li class="ulchildlink"><strong><a href="rzakxsmpjvreg.htm">Sample Java registry file</a></strong><br />
Each of the sample plug-ins written in Java provides its own registry file.</li>
<li class="ulchildlink"><strong><a href="rzakxproperty.htm">Property pages for a property sheet handler</a></strong><br />
The Microsoft<sup>®</sup> Foundation Class Library classes cannot be used to construct property pages for a property
sheet handler. However, IBM provides <span class="uicontrol">CExtPropertyPage</span>, which may be used in place of the MFC class CPropertyPage.</li>
<li class="ulchildlink"><strong><a href="rzakxconstructvbproppgs.htm">Example: Constructing Visual Basic property pages for a property sheet handler</a></strong><br />
Property pages that are implemented by iSeries Navigator Visual Basic plug-ins can not use a registry key to specify
property pages. You must add a specific property page context menu item in your ListManager class to implement a property page. You can not add a property page to any existing property sheet objects.</li>
<li class="ulchildlink"><strong><a href="rzakxjavaproperty.htm">Property sheet handling in Java</a></strong><br />
Add property pages to property sheets of Java plug-ins. This allows you to build object names,
display properties, share objects with third parties, and mix C++ and Java code in the same plug-in.</li>
<li class="ulchildlink"><strong><a href="rzakxsslregistryentry.htm">Secure Sockets Layer (SSL) registry entry</a></strong><br />
iSeries Navigator users can request a secure connection to an iSeries server by selecting the <span class="uicontrol">Use Secure Sockets Layer</span> checkbox on the <span class="uicontrol">Connection</span> tab of the property sheet for iSeries objects. When this is done, only iSeries Navigator components
that are capable of supporting SSL communications are enabled for activation by the user.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxpluginreference.htm" title="iSeries Navigator handles plug-ins in each programming language in a different way.">Plug-in programming reference</a></div>
</div>
</div>
</body>
</html>