Before you start
To distribute a user-defined
extension, you must include the runtime component - LIL or JAR file. For user-defined
nodes only, but not for parsers, you must also include the workbench component
that allows users to add your nodes to their flows. This topic covers the
workbench components only; to see which runtime components are needed, see Installing a user-defined extension on a broker domain.
The node project is an Eclipse plug-in. It sits in the workbench while it is being developed. Each user of the workbench needs to have the node project in their install_dir\evtoolkit\eclipse\plugins directory to be able to add the node to their message flows. When the project is tested to your satisfaction, you can prepare it for distribution.
The zip file is saved to the location you specified. If you developed your Java source code within the project, this is included in the zip file. You can add your C source code or compiled files to the zip file using any zip utility. You then have a self-contained package that you can distribute to all internal users.
Unzip the file into the install_dir\evtoolkit\eclipse\plugins directory
If running the Toolkit as a non-root user, you must set the file permissions as follows:
cd <install_dir>/evtoolkit/eclipse/plugins/<name of project being installed> chmod 666 * chmod 755 icons
If you want to distribute your node commercially, please see the PDE Guide for information about issues such as versioning and updating your user-defined node.