Plugins Glossary

Actions: Actions are defined in execution plugin configurations and are executed in integrating products through deployment and failure tasks.
Artifacts: Files or other software elements. In Deployment Automation, these are represented by component versions.
Base Configurations: A base plugin configuration must be created for each set of configurations. It stores connection information and other shared properties and enables you to quickly create configurations of different types using that information. Some fields can be overridden at the derivative configuration level so that you can create configurations for different organizations or for slightly different purposes.
Baselines: In Dimensions CM, containers for release-ready components or artifacts. For more details, refer to the Dimensions CM documentation.
Change Packages: In ChangeMan ZMF, containers for release-ready components. For more details, see the ChangeMan ZMF documentation.
Collections: Collections are the lists of objects that you work with as part of Release Control, such as requests, deployment units, and deployment tasks. These are populated by collection widgets.
Component Versions: Instances of a Deployment Automation component, which contain the artifacts to be deployed or otherwise configured.
Configuration Overrides: You can override field values when creating or updating a configuration. You can also override the configuration settings at the SBM item level using auxiliary table override values. See Auxiliary Table Level Configuration Overrides.
Configurations: Provide connection information, product-specific details, and filters telling the plugin what data to obtain from the integrating product.
Plugin Instances: Variations of a plugin that may represent different versions of the plugin or instances owned by different business units who want to maintain an independent maintenance schedule.
Plugins: Plugins are used to implement the integrations between Release Control and other products.
Projects: In SBM, containers for release items, such as application releases, release trains, and environments; SBM projects.
Providers: Providers implement the plugin functionality. Plugins may have more than one provider implemented, such as an object provider and an execution provider.
Release Items: A general term used to refer to Release Control items that are submitted as SBM items, such as release packages and deployable release trains.
Single Sign-on (SSO): Serena-installed software that enables a user to log in to a Web-based component of SBM and be recognized on subsequent accesses to that component or other Web-based components of SBM. This software also provides the ability for security tokens to be used in an orchestration, allowing Web services to be called without requiring the user to provide credentials at inconvenient times.
Snapshots: A Deployment Automation snapshot captures an application's current state, and as the application moves through different environments, the snapshot ensures that proper component versions are used.
Tags: Tags are unique names you can assign to plugin configurations in addition to the system-assigned Type Name. These are referenced in collection widgets to categorize the objects, such as requests, deployment units, and deployment tasks.
Tasks: Release Control tasks include deployment tasks, failure tasks, and tasks defined in task templates. In some cases, the term deployment tasks may be used in general to refer to all of these types of tasks.
Type Name: Type indicates the type of configuration based whether the configuration is a base configuration or one of the provider types, object (item) or execution (action). Type Name gives the specific instance name of the base configuration or provider type.