Creating an IBM® Workload Plug-in Project
You can use the Plug-in Development Kit to create plug-in projects.
Before you begin
About this task
You can use virtual application patterns to add third-party software to your existing platform in an efficient, reusable way by developing the corresponding plug-in for it. Developing a plug-in for your platform requires an understanding of the conventions, configuration, and details for your platform. You typically must edit your configuration files in your preferred text editor.
The plug-in project includes
the following key artifacts:
- src folder
- You can create your Java™ code in this directory.
- JRE System Library folder
- This folder contains all of the JAR files that are needed to compile the plug-in project.
- i18n folder
- This folder contains the globalization files.
- META-INF folder
- This folder contains metadata files.
- OSGI-INF folder
- This folder contains OSGi configuration files.
- plugin folder
- This folder is the plug-in configuration directory, which includes
the config.json plug-in configuration file, and
the following folders:
- appmodel
- nodeparts
- parts
- templates
- build.plugin.xml
- This Ant build file is needed to build the plug-in project.
You can add content to these artifacts to develop your plug-in.
Procedure
What to do next
Add content to the project artifacts to develop your plug-in:
- The plug-in configuration, in the config.json file.
- Components, links, and policies for the Pattern Builder in the metadata.json component property UI configuration file.
- Operations available on the Instance Console, in the operation.json configuration file.
- Configuration parameters in the tweak.json file that can be changed on the running deployment.
- You can create other typical plug-in artifacts, including OSGi service components, plug-in node parts, plug-in parts, and plug-in roles.