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.
Source plug-ins are used to import component artifacts. Each source plug-in provides the properties that are used to import a specify artifact type, such as a build tool, or file system.
Automation plug-ins provide discreet steps that are used to create component or generic processes. When you use an automation plug-in to create a component process, you can use steps from several plug-ins and configure the steps as you go.
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 numerous plug-ins. The plug-in system is open and extensible; plug-ins can be written in any language.