Plugin steps for component processes

Deployment Automation provides a variety of plugin steps for designing component processes.

To use the steps, open the component process and drag the steps from the Tools pane onto the design space.

For more component process steps, see Utility steps for component processes.

Plugin steps overview

Plugins provide functionality in discrete steps that you can use in component and global processes to configure, or deploy into, target environments.

The selection of plugin steps includes basic Deployment Automation and file operation functions as well as a variety integrations with third-party tools. Deployment Automation releases with plugins for many common deployment process needs.

Plugins break down a tool's functions into steps, for example:

detect if a server is stopped — stop a server — start a server.

When you design a component process, you typically use steps from several plugins. For example, you might create a process with a plugin for a source control tool, which deploys a component to a middleware server, and another plugin to configure a step that removes the component from the server.

Deployment Automation provides plugins for:

  • Running standard utility processes, such as inventory management and workflow control and native Deployment Automation operations.
  • Running common processes, such as downloading and uploading artifacts, and retrieving environment information.
  • Interacting with a variety of tools, such as middleware tools, databases, and servers.

To use plugin steps, first download and install the necessary plugins. For details about available plugins, see Plugins list.

For plugins created by others, check the Community website.

Back to top

Plugin post-processing

When a plugin step finishes processing, the system runs its default post-processing script, which is defined in the plugin XML file. For details, see The plugin.xml file.

You can override the default behavior by using your own script. Enter the script in the step's Post Processing Script field.

For details on creating post-processing scripts, see Post-processing scripts.

Back to top

See also: