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
Table 12‑2. Preconfigured WAR Application Component (Continued)
Application Component Property Auto-Bind Type Auto-Bind Tag
Linux WAR file service_stop Consume Servlet Container, Stop
Linux WAR file webapps_dir Consume Servlet Container, DIR
Some nodes and node arrays have predefined Auto-Bind type and tag parameters for properties. You
cannot edit these parameters. When a service or application component is added to a node or node
Array, the source properties are taken from the service or application component and the target properties
are taken from the node or node array.
Table 12‑3. Predefined Node and Node Array Properties
Node Type Property Auto-Bind Type Auto-Bind Tag
Node, Node Array hostname Expose Hostname
Node, Node Array ip Expose IP Address
Node Array node-array-index Expose Node Array Index
When dependencies exist, the source properties are taken from the component that the link originates.
Target properties are taken from the component from which the link is drawn, and from parent service or
node components.
Property Compatibility
Auto-binding depends on the compatibility between Source and Target property types and Node type.
Table 12‑4. Property Type and Node Type Compatibility
Source Property Type Target Property Type Node Type Compatible
Array String Node Yes
Array Computed Node Yes
Array String Node Array Yes
Array Computed Node Array Yes
String String Node Yes
String Computed Node Yes
String String Node Array No
String Computed Node Array No
Passing Property Values Between Life Cycle Stages and
Components
Properties defined for each component can be used in an action script for each of the life cycle stages.
Using Application Services
VMware, Inc. 111