There are two types of plug-in:
Third-party tools exhibit wide and varied functions. Plug-in integration is achieved by breaking down a tool's functions into simple, discrete steps that run a specific behavior. A plug-in step might start a tool, or run different functions in a tool, such as extracting or inserting some type of data.
A component process that contains a plug-in step requires an agent. Unless the agent must interact with the host's file system or system processes, the agent does not need to be on the same host as the target resource. IBM UrbanCode Deploy provides numerous plug-ins. The plug-in system is open and extensible; plug-ins can be written in any language.
The plug-ins that enable basic functionality are included with the product. Some are installed automatically when you install the product.
View plug-ins installed using the user interface:
Plug-ins may be developed and updated more frequently than IBM UrbanCode Deploy release cycles.
Browse, download, and get documentation for plug-ins at the IBM developerWorks site in the UrbanCode Deploy Plug-ins section. The site contains many more plug-ins than are packaged with the IBM UrbanCode Deploy product.
The site includes plug-ins developed by these sources:
Support is provided through the developerWorks community and through IBM technical support.
Support for each partner plug-in is provided exclusively by the partner who provided the plug-in.
Support is provided exclusively through the community.
You can create your own plug-ins for use with IBM UrbanCode Deploy. See Creating plug-ins. See also UrbanCode Deploy Plug-in for Eclipse Development in the DevOps Services community for a tool that can save time in developing plug-ins.