Default path for component processes when relative path is specified for a field
(SPE2101)
The default path for any UrbanCode Deploy/HCL Launch component process is relative to the working directory folder. The following table defines the default path for a component process depending on where the component process is created and the type of system:
Location of component process creation | Type of execution environment configuration | Default path | ||||||
|---|---|---|---|---|---|---|---|---|
Directly on the UrbanCode Deploy/HCL Launch web user interface | Agent | UCDagentHome/var/work/componentName For example:
|
In these paths:
- The UCDagentHome variable represents the directory on the system on which the agent execution environment is configured.
- The componentName variable represents the name of the component.
Examples of specifying the relative path for a field
The working directory folder can contain the files that BMC AMI DevOps might use. Some fields in the component process configuration define the paths of the required files. For these fields, you can also enter the relative path of the file.
The following fields support relative paths:
Process step | Field |
|---|---|
BMC AMI DevOps Common - Authentication | Plug-in Variables File Path |
BMC AMI DevOps Common - File Transmission | Source PDS or Directory Name |
Destination PDS or Directory Name | |
BMC AMI DevOps Schema Migration - Output Transmission | Destination Directory Name |
BMC AMI DevOps Common - JCL Execution | Execution JCL PDS or Directory Name |
The following example illustrates the default path that BMC AMI DevOps considers when you specify the relative path of a file.
Related topics