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
Working with Artifacts 15
Artifact management lets your organization deploy an application with build files and other types of
software artifacts without regard to their physical location.
An artifact is a script or the output of a build process. With artifact management, an application blueprint
specifies an artifact by type and name, but not by location or unique identifier. Artifact management
monitors the physical location and identity of artifacts and supplies the required artifact during
deployment.
In artifact management, an application catalog administrator creates artifact repository specifications and
maps them to artifact repository instances. An artifact repository specification identifies a store that can
contain an unlimited number of artifacts. It has properties that identify an artifact repository instance and
the artifacts it contains. Application Services provides out-of-the-box artifact repository specifications for
Jenkins and YUM, and the capacity to define additional artifact repository specifications.
An artifact repository specification has agent- and server-side scripts that can fetch artifacts from an
artifact repository instance. A script can produce metadata and store it with an artifact. It can also track
and search for an artifact. The script lifecycles are resolve artifact, download artifact, and find tracking
IDs. You can write your own Bash, Windows Cmd, Windows Powershell, BeanShell, and JavaScript
scripts.
An application architect and other application administrators create artifact specifications, map them to
artifact repository instances such as actual Jenkins build projects, and then bind the artifact specifications
to the properties of services, external service, or application components such as WAR or JAR files in the
application blueprints. An artifact specification identifies an artifact only by name, description, and
business group. The deployment environment you select determines the actual artifact repository
instance, and the deployment profile you use specifies the actual artifact. You can map an artifact to one
repository instance per deployment environment.
This chapter includes the following topics:
n
Create an Artifact Repository Specification
n
Create an Artifact Repository Instance
n
Create an Artifact Specification
n
Map an Artifact Specification to an Artifact Repository Instance
n
Bind an Artifact to an Application Blueprint
VMware, Inc.
163