7.1

n
Windows PowerShell $progress_status="completed"
N Array and content property do not support passing modied property values between action scripts
of life cycle stages.
Best Practices for Developing Components
To familiarize yourself with best practices for dening properties and action scripts, you can download and
import Software components and application blueprints from the VMware Solution Exchange.
Follow these best practices when developing Software components.
n
For a script to run without any interruptions, the return value must be set to zero (0). This seing allows
the agent to capture all of the properties and send them to the Software server.
n
Some installers might need access to the y console. Redirect the input from /dev/console. For example,
a RabbitMQ Software component might use the ./rabbitmq_rhel.py --setup-rabbitmq < /dev/console
command in its install script.
n
When a component uses multiple life cycle stages, the property value can be changed in the INSTALL
life cycle stage. The new value is sent to the next life cycle stage. Action scripts can compute the value of
a property during deployment to supply the value to other dependent scripts. For example, in the
Clustered Dukes Bank sample application, JBossAppServer service computes the JVM_ROUTE
property during the install life cycle stage. This property is used by the JBossAppServer service to
congure the life cycle. Apache load balancer service then binds its JVM_ROUTE property to the all
(appserver:JbossAppServer:JVM_ROUTE) property to get the nal computed value of node0 and
node1. If a component requires a property value from another component to complete an application
deployment successfully, you must state explicit dependencies in the application blueprint.
N You cannot change the content property value for a component that uses multiple life cycle
stages.
Create a Software Component
Congure and publish a Software component that other software architects, IaaS architects, and application
architects can use to assemble application blueprints.
Prerequisites
Log in to the vRealize Automation console as a software architect.
Procedure
1 Select Design > Software Components.
2
Click the Add icon (
).
3 Enter a name and, optionally, a description.
Using the name you specied for your Software component, vRealize Automation creates an ID for the
Software component that is unique within your tenant. You can edit this eld now, but after you save
the blueprint you can never change it. Because IDs are permanent and unique within your tenant, you
can use them to programmatically interact with blueprints and to create property bindings.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 295