Packaging the plug-in components

You extend the Plugin class to identify the components that are used for a custom plug-in. You then create a JAR file to package the components deploy to IBM® Content Navigator.

To package the plug-in:

1. Create a JAR file that contains the files that are used for the plug-in.
   The JAR file must use the following structure:

   packageName 
      // Include all the Java classes that extend the Plugin class and
      // any other Java classes that are required by the plug-in
      Java class 1
      Java class 2
      ...
      WebContent
      // Include all the image, JavaScript, and HTML files 
      // that are required by the plug-in
    META-INF 
      manifest.mf

   In the packageName folder, include the Java™ class files that are defined for the plug-in. Create the subfolders based on the package names of the Java classes. Follow the standard JAR file structure by using nested folders for nested packages.

   Important: All the Java classes must be included in a named package. You cannot use the default package.
2. Modify the manifest.mf file for your plug-in to include the following property:

   Plugin-Class: pluginClassName

   pluginClassName is the name of your Plugin.java subclass.

   You can also include any of the standard properties for a JAR file in the manifest.mf file.