Plug-in steps are run by an agent that is installed in the target environment. This means that plug-ins can be written in any scripting language as long as the agent can access the required scripting tools on the host.
In this section, we examine the mechanics of plug-ins by examining a plug-in step in detail. The example plug-in that we use is FileUtils, which contains several steps that are related to file manipulation. The FileUtils plug-in is shipped with IBM UrbanCode Deploy.
Each plug-in step is an individually configurable object in the editor. In the following illustration, you can see some of FileUtils' individual steps in the process editor.
We examine the Create File step in this example. Create File is straightforward and (as the name implies) creates a file.
Each step (step-type element) has the same structure:
The following figure illustrates the structure of the Create File step.