7.3

d Select the expected type for the value of your property.
e Define the value for your property.
Option Description
Use the value you supply now
n
Enter a value.
n
Deselect Overridable.
n
Select Required.
Require architects to supply a value
n
To provide a default, enter a value.
n
Select Overridable.
n
Select Required.
Allow architects to supply a value if
they choose
n
To provide a default, enter a value.
n
Select Overridable.
n
Deselect Required.
Architects can configure your Software properties to show to users in the request form. Architects
can use the Show in Request option to require or request that users fill in values for properties
that you mark as overridable.
7 Follow the prompts to provide a script for at least one of the software life cycle actions.
Table 3‑48. Life Cycle Actions
Life Cycle Actions Description
Install Install your software. For example, you might download Tomcat server installation bits and install a
Tomcat service. Scripts you write for the Install life cycle action run when software is first
provisioned, either during an initial deployment request or as part of a scale out.
Configure Configure your software. For the Tomcat example, you might set the JAVA_OPTS and
CATALINA_OPTS. Configuration scripts run after the install action completes.
Start Start your software. For example, you might start the Tomcat service using the start command in
the Tomcat server. Start scripts run after the configure action completes.
Update If you are designing your software component to support scalable blueprints, handle any updates
that are required after a scale in or scale out operation. For example, you might change the cluster
size for a scaled deployment and manage the clustered nodes using a load balancer. Design your
update scripts to run multiple times (idempotent) and to handle both the scale in and the scale out
cases. When a scale operation is performed, update scripts run on all dependent software
components.
Uninstall Uninstall your software. For example, you might perform specific actions in the application before a
deployment is destroyed. Uninstall scripts run whenever software components are destroyed.
Include exit and status codes in your action scripts. Each supported script type has unique exit and
status code requirements.
Script Type Success Status Error Status Unsupported Commands
Bash
n
return 0
n
exit 0
n
return non-zero
n
exit non-zero
None
Windows CMD
exit /b 0 exit /b non-zero
Do not use exit 0 or exit non-zero codes.
PowerShell
exit 0 exit non-zero;
Do not use warning, verbose, debug, or host calls.
Configuring vRealize Automation
VMware, Inc. 439