Executes commands/scripts on an EBS Instance. Use this operation when you need to execute commands like compile all forms, download AOL from EBS instance, etc. In addition, the plugin provides the ability for the user to define any number of outputs from the execution of the script that could be utilized in subsequent steps in the workflow.
Target Properties
Property Name | Property Source | Required | Description |
|---|---|---|---|
EBS Source Script |
| Yes | Source Script with full path. If you would like to apply changes directly to run edition for EBS R 12.2+, specify the run param after the script. By default, it connects to patch edition when performing the deploy operation. All other operations are sourced from run by default. e.g. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Command |
| Yes | The commands and/or scripts that are to be executed on the EBS instance. |
...
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to Any, which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to All to will result in execution on all selected endpoints.
Special Considerations
User defined outputs – an output must be defined in the workflow editor to be accessible. Within your script, use the following built-in function to set the output with the appropriate value and have it returned to the workflow process. Any number of outputs can be used.
Outputs Syntax
| Code Block | ||
|---|---|---|
| ||
setOutput {output name} {output value}
#Example
setOutput STATUS ${STATUS_VARIABLE}
To load a file into an output, consider syntax like this:
setOutput OUTPUT_NAME "`cat /path/to/file.txt `" |