Jump to content



Serena Release Manager

Components

Components represent deployable items along with user-defined processes that operate on them, usually by deploying them. Deployable items – also called artifacts – can be files, images, databases, configuration materials, or anything else associated with a software project. Components have versions which ensures that the proper component instances get deployed.

 

Process Design screenshot

[Click to enlarge] Component Process Design

Artifacts can come from a number of sources: Serena PVCS, Serena Dimensions CM, file systems, build servers such as AnthillPro, source version control systems, Maven repositories, as well as many others. When you create a component, you identify the source and define how the artifacts will be brought into the release automation option. If the source is Subversion, for example, you specify the Subversion repository containing the artifacts. Each component represents artifacts from a single source.

Component Processes

A component process is a series of user-defined steps that operate on a component's artifacts. Each component has at least one process defined for it and can have several. A component process can be as simple as a single step or contain numerous steps and relationships; the switch step enables you to create conditional processes. For example, you might take artifacts from a source – such as Dimensions CM – and map the ones that get deployed to an HTTP server into one component; those that get deployed to a J2EE container to another; and those that get deployed to a database to yet another. Another example, a single-component deployment might consist of two processes: the first moves component files to a server on Friday night, while the second deploys the files Saturday morning.

Component processes are created with the release automation's process editor. The process editor is a visual drag-and-drop editor that enables you to drag process steps onto the design space and configure them immediately. As you place additional steps, you visually define their relationships with one another. Process steps are selected from a menu of standard steps that replace typical deployment scripts and manual processes.

Serena Release Manager's release automation option provides steps for several utility processes, such as inventory management, and workflow control. Additional process steps are provided by plug-ins which provide integration with common deployment tools and application servers, such as IBM WebSphere, Microsoft IIS, and many others.

Out-of-the-box, Serena Release Manager's release automation option provides plug-ins for many common processes, such as downloading and uploading artifacts, and retrieving environment information. A component process can have steps from more than one plug-in. A component process is defined for a specific component. A component can have more than one process defined for it, but each component requires at least one process.

Frequently used component processes can be saved as templates and applied later to new components. Component processes are executed by release automation agents running on hosts. One instance of a component process is invoked for each resource mapped to a component in the target environment.

Learn More: