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
8 To create an Amazon EBS-backed AMI, select the stopped Amazon EC2 instance, provide the Image
Name, and initiate the process to convert to an EBS-backed image.
The AMI creation might take several minutes.
After the AMI is available, you can end the Amazon EC2 instance.
What to do next
Map the Amazon EC2 Region to a Application Services cloud provider and provide access to the AMIs or
virtual machine templates. See Register the Amazon EC2 Cloud Provider and Template.
Register the Amazon EC2 Cloud Provider and Template
In Application Services, registering a cloud provider means using access keys established in a valid AWS
account to connect to an Amazon EC2 Region.
The following Amazon Region code values are supported when specifying cloud provider information. For
the most current list of supported Amazon Region code values, see Amazon AWS Regions and
Endpoints documentation. For example, see
http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region.
Table 11‑2. Common Supported Amazon Region Code Values
Amazon Region Code Values Region Names
ap-northeast-1 Asia Pacific (Tokyo) region
ap-southeast-1 Asia Pacific (Singapore) region
ap-southeast-2 Asia Pacific (Sydney) region
eu-west-1 EU (Ireland) region
sa-east-1 South America (Sao Paulo) region
us-east-1 US East (N. Virginia) region
us-west-1 US West (N. California) region
us-west-2 US West (Oregon) region
Prerequisites
n
Log in to Application Services as an application cloud administrator.
n
Verify that an AWS user account is set up with access keys.
n
Create virtual machine templates that meet virtual private cloud (VPC) requirements. See Virtual
Machine Requirements for Creating Amazon EC2 Custom Templates.
Procedure
1 On the Application Services title bar, click the drop-down menu and select Clouds > Cloud
Providers.
2 Click New.
Using Application Services
VMware, Inc. 97