Configuring Component Processes

A component process is created in two steps: first, you configure basic information, such as name; second, you use the process editor to assemble the process.

To configure a component process:

1. Display the Create New Process dialog Home > Components > Component: component_name > Create New Process).

2. The dialog's fields are described in the following table.

   Create New Process Fields table

   Field	Description
   Name	Identifies the process; appears in many UI elements. Required.
   Description	The optional description can be used to convey additional information about the process.
   Process Type	Required. Defines the process type. Available values are: Deployment: deploys a component version to the target resource and updates the inventory after a successful execution. Configuration Deployment: configuration-only deployment with no component version or artifacts—simply applies the configuration (using properties, or configuration templates) to the target agent and updates the resource configuration inventory afterwards. Uninstall: standard uninstall that removes a component version from a target resource and the resource's inventory. Operational (With Version): operational process which does not add or remove any artifacts or configuration; runs arbitrary steps given a component version. Useful when you want to start or stop some service for a previously deployed component version. Operational (No Version Needed): same as the previous type, but does not require a component version.
   Inventory Status	Required. Status applied to component versions after being successfully executed by this process. Active indicates the component version is deployed to its target resource; Staged means the component version is in a pre-deployment location. The status appears on the Inventory panes for the component itself and environments that ran the process.
   Default Working Directory	Required. Defines the location used by the agent running the process (for temporary files, etc.). The default value resolves to agent_directory\work\component_name_directory. The default properties work for most components; you might need to change it if a component process cannot be run at the agent's location.
   Required Component Role	Restricts who can run the process. The available options are derived from the Serena Release Automation security system. The default value is None, meaning anyone can run the process. For information about security roles, see Serena Release Automation Security.

3. Save your work when you are finished. The process is listed on the Processes pane for the associated component.