Management → Managing Components → Component Processes → Creating Component Processes
Each component has at least one process defined for it and can have several. These typically define the configuration information you want to do on the target resources for each component. Frequently-used processes can be saved in component templates and applied to other components.
A component process is created in two steps:
To create a component process:
|Name||Identifies the process; appears in many UI elements. Required.|
|Description||The optional description can be used to convey additional information about the process.|
Required. Defines the process type. Available values are:
|Inventory Status||Required. Status applied to component versions after being successfully executed by this process. Active is a built-in status that indicates the component version is deployed to its target resource. An example of a user-defined status is Staged, that could indicate that 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. See Defining Statuses.|
|Default Working Directory||Required. Defines the location used by the agent running the process, for temporary file storage. 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 Deployment Automation security system. The default value is None, meaning anyone can run the process. For information about security roles, see Security Administration.|
Copyright © 2011–2016 Serena Software, Inc. All rights reserved.