Customize the plug-in registry files

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.

Registry files identify plug-ins to iSeries™ Navigator, describe their functions, and specify any prerequisites for using the plug-in.

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.

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:

• 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 <vendor>.<component>, i.e. IBM^®.Sample.
• Registry keys that identify the object types in the iSeries Navigator hierarchy for which a plug-in intends to supply additional function.
• 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.

Descriptions of the required sections of the registry files, and the recommended changes:

• C++ registry files
• VB registry files
• Java™ registry files

Special considerations for the registry files

• Property sheet handling in C++
• Property sheet handling in VB
• SSL support in plug-ins

• Customize the C++ registry values
  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.
• Customize the VB plug-in registry values
  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.
• Sample Java registry file
  Each of the sample plug-ins written in Java provides its own registry file.
• Property pages for a property sheet handler
  The Microsoft^® Foundation Class Library classes cannot be used to construct property pages for a property sheet handler. However, IBM provides CExtPropertyPage, which may be used in place of the MFC class CPropertyPage.
• Example: Constructing Visual Basic property pages for a property sheet handler
  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.
• Property sheet handling in Java
  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.
• Secure Sockets Layer (SSL) registry entry
  iSeries Navigator users can request a secure connection to an iSeries server by selecting the Use Secure Sockets Layer checkbox on the Connection 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.