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
To automate application deployments to a supported cloud environment, users must configure the
components in the cloud abstraction layer (CAL). The cloud template contains a predefined reusable
machine image that includes an operating system and data that is applied to a virtual machine when it is
created. A cloud template is mapped to a logical template in the Application Services library. The cloud
provider offers a cloud instance for deployment. The deployment environment provides a particular
environment for the deployment in the cloud provider instance. Both the cloud provider and deployment
environment map components from the cloud environment to Application Services.
Application architects can use the drag-and-drop interface to create visual application blueprints.
Application architects can use the prepopulated and extensible library of standard logical templates,
application infrastructure service, components, and scripts to model an application blueprint. These
blueprints standardize the structure of the application, including software components, dependencies, and
configurations, for repeated deployments.
Application blueprints are portable across deployment environments. For example, after a blueprint is
available, application development, QA, and release teams can work in the standards set by IT. Teams
can repeatedly deploy a standard blueprint, customize configurations as allowed, and deploy within IT-
approved deployment environments.
From an application blueprint, you can create different deployments using deployment profiles to test
prototypes or deploy mission-critical multitier applications in production environments. From these saved
blueprints, the application deployer can generate execution plans for deploying the application to a private
or public cloud. You can also initiate an update process to scale clustered nodes of deployed applications
and change the configuration or code of deployed applications when a new version is available.
Using Application Services
VMware, Inc. 12