6.2
Table Of Contents
- Using Application Services
- Contents
- Using Application Services
- Updated Information
- Introducing Application Services
- Install and Configure Application Services
- Installing Application Services
- Preparing to Install Application Services
- Start the Application Services Appliance
- Troubleshooting Problems Connecting to the Application Services Web Interface
- Unlock Your darwin_user Account
- Restart Application Services
- Configure Application Services to Use a Proxy for External URLs
- Register Application Services to vRealize Automation
- Upgrading Application Services
- Setting Up Users and Groups
- Using Tenants and Business Groups in Application Services
- Import Predefined Content to a Tenant
- Using the Application Services Web Interface
- Setting Up Application Provisioning for the Application Services Environment
- Virtual Machine Requirements for Creating vRealize Automation Custom Templates
- Creating Virtual Machine Templates in vRealize Automation
- Updating Existing Virtual Machine Templates in vRealize Automation
- Register the vRealize Automation Cloud Provider and Template
- Create a vRealize Automation Deployment Environment
- Setting Up Application Provisioning for the vCloud Director Environment
- Virtual Machine Requirements for Creating vCloud Director Custom Templates
- Creating Windows Virtual Machine Templates in vCloud Director
- Create Linux Virtual Machine Templates in vCloud Director
- Verify Cloud Template Configuration from the vCloud Director Catalog
- Updating Existing Virtual Machine Templates in vCloud Director
- Exporting Virtual Machine Templates with OVF Format
- Register the vCloud Director Cloud Provider and Template
- Create a vCloud Director Deployment Environment
- Setting Up Application Provisioning for the Amazon EC2 Environment
- Developing Application Services Components
- Managing the Application Services Library
- Creating Applications
- Working with Artifacts
- Deploying Applications
- Setting Up and Configuring a Deployment Profile
- Deploying with Deployment Profiles
- Publishing Deployment Profiles to the vCloud Automation Center Service Catalog
- Request a vRealize Automation Service Catalog Item
- Using the Deployment Summary Page
- Using the Composite Deployment Summary Page
- Understanding the Deployment and Update Process
- Understanding Deployment Failures
- Updating Application Deployments
- Initiate an Update Process to Scale Out Deployments
- Initiate an Update Process to Scale In Deployments
- Initiate an Update Process to Modify Configurations
- Use an Existing Update Profile
- Promote an Update Profile
- Rollback an Update Process
- Understanding Run Custom Task Update
- Troubleshoot Failed Update Process to Scale Deployments
- Troubleshoot Failed Update Process to Modify Configuration
- Deploying Predefined Library Components
- Managing Deployments
- View Deployment Task and Blueprint Details for an Application
- View Deployed VM Details and Execution Plan of an Application
- Start a Policy Scan
- Tear Down an Application from the Cloud
- Scale In Deployments from vCloud Automation Center
- Scale Out Deployments from vCloud Automation Center
- Tear Down an Application from vCloud Automation Center
- Delete an Application Deployment from Application Services
- Cancel a Deployment or an Update Process
- View Policy Compliance Summary
- Using the Application Services CLI
- Using the CLI Import and Export Functions
For a computed property, you can modify the value of a property and pass the value to the next life cycle
stage of the action script. For example, if component A has the progress_status value defined as staged,
in the INSTALL and CONFIGURE life cycle stage you change the value to progress_status=installed in
the respective action scripts. If component B is bound to component A, the property values of
progress_status in the life cycle stages of the action script are the same as component A.
Define in the blueprint that component B depends on A. This dependency defines the passing of correct
property values between components whether they are in the same node or across different nodes.
For example, you can update a property value in an action script by using the supported scripts.
n
Bash progress_status="completed"
n
Windows CMD set progress_status=completed
n
Windows PowerShell $progress_status="completed"
n
BeanShell progress_status="completed"
Note Array and content property do not support passing modified property values between action scripts
of life cycle stages and components.
Application Services Predefined Properties
Application Services provides some commonly used properties as predefined properties. These
properties are available for clustered nodes.
Usually, most services need the IP address of the virtual machines they are running in. For clustered
nodes, a service might need the IP addresses of all the virtual machines in the cluster. Therefore, the
virtual machine IP address is designated as a predefined property.
Predefined IP Address Property
A node can have multiple NICs, with each NIC assigned one IP address in the deployed virtual machine.
The following IP addresses are available in the NodeName:NICx_ip properties, where -x- is the NIC
number.
In the sample Clustered Dukes Bank application, the Load Balancer node properties are shown as
load_balancer:NIC0_ip and load_balancer:NIC1_ip because the Load Balancer node has two NICs
defined. It is not guaranteed that NIC0 and NIC1 will be assigned to eth0 and eth1, respectively, in the
virtual machine. The NICs are logical names in the blueprint for the network interfaces. These NICs are
mapped to logical networks, which are mapped to specific cloud networks. The property NIC0_ip returns
the IP address assigned to the virtual machine as defined in the blueprint, not the eth0 IP address in the
virtual machine.
Using Application Services
VMware, Inc. 112