7.1

Table Of Contents
4 (Optional) If you want to control how your Software component is included in blueprints, select a
container type from the Container drop-down menu.
Option Description
Machines
Your Software component must be placed directly on a machine.
One of your published Software
components
If you are designing a Software component specically to install on top of
another Software component that you created, select that Software
component from the list. For example, if you are designing an EAR
component to install on top of your previously created JBOSS component,
select your JBOSS component from the list.
Software components
If you are designing a Software component that should not be installed
directly on a machine, but can be installed on several dierent Software
components, then select the software components option. For example, if
you are designing a WAR component and you want it to be installed on
your Tomcat Server Software component, and your Tcserver Software
component, select the software components container type.
5 Click Next.
6 Dene any properties you intend to use in your action scripts.
a
Click the Add icon ( ).
b Enter a name for the property.
c Enter a description for the property.
This description displays to architects who use your Software component in blueprints.
d Select the expected type for the value of your property.
e Dene 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 congure 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 ll 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 437. 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.
Configuring vRealize Automation
296 VMware, Inc.