7.1

Table 4‑39. New Software Properties (Continued)
Setting Description
Encrypted Mark properties as encrypted to mask the value and
display as asterisks in vRealize Automation. If you change
a property from encrypted to unencrypted,
vRealize Automation resets the property value. For
security, you must set a new value for the property.
I If secured properties are printed in the script
using the echo command or other similar commands, these
values appear in plain text in the log les. The values in the
log les are not masked.
Overridable Allow architects to edit the value of this property when
they are assembling an application blueprint. If you enter a
value, it displays as a default.
Required Require architects to provide a value for this property, or to
accept the default value you supply.
Computed Values for computed properties are assigned by the
INSTALL, CONFIGURE, START, or UPDATE life cycle
scripts. The assigned value is propagated to the subsequent
available life cycle stages and to components that bind to
these properties in a blueprint. If you select Computed for
a property that is not a string property, the property type is
changed to string.
New Software Actions
You create Bash, Windows CMD, or PowerShell action scripts to specify exactly how components are
installed, congured, uninstalled, or updated during deployment scale operations.
Table 4‑40. 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
rst provisioned, either during an initial deployment request or as part of a scale out.
Congure Congure your software. For the Tomcat example, you might set the JAVA_OPTS and
CATALINA_OPTS. Conguration 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 congure 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 specic actions in the application
before a deployment is destroyed. Uninstall scripts run whenever software components are
destroyed.
Select the Reboot checkbox for any script that requires you to reboot the machine. After the script runs, the
machine reboots before starting the next life cycle script. Verify that no processes are prompting for user
interaction when the action script is running. Interruptions pause the script, causing it to remain in an idle
state indenitely, eventually failing. Additionally, your scripts must include proper exit codes that are
applicable to the application deployment. If the script lacks exit and return codes, the last command that ran
in the script becomes the exit status. Exit and return codes vary between the supported script types, Bash,
Windows CMD, PowerShell.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 305