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
CLI Command Component Description
import-package
The import-package command name.
--importFilePath pathname
Specifies the path name of the import package. For example, --
importFilePath /home/dev/joomla.zip specifies the location and name of the
joomla.zip import package.
--targetGroup busgroupname
Specifies the owning business group of the object to import. Policies are excluded.
Anyone in the tenant can access a policy, so the owning business group is ignored.
--ConflictResolutionAction action
Specifies the CHECK, SKIP, OVERWRITE, or IMPORTASNEW conflict resolution
action. An import-package command must specify one conflict resolution action.
The following table describes the conflict resolution actions to use when importing objects with an import
package.
Conflict Resolution Action Description
CHECK
Lists all objects in the import package and indicates whether an object exists on the
target. Determines a match by comparing the object names and version identifiers.
A version identifier has the form major.minor.micro.qualifier, for example,
2.0.1.beta.
SKIP
Copies the object from the package if the object does not exist on the target. Does
not copy the object If the object exists on the target. A copied object belongs to the
owning business group specified by --TargetGroup.
OVERWRITE
Overwrites the contents of an object with contents from the package if the object
exists on the target. Copies an object that does not exist on the target to the owning
business group specified by --TargetGroup. The logged-in user must belong to
the owning business group of the objects in the package to import them.
IMPORTASNEW
Copies an object from the package to the target with a new name if the object exists
on the target. The new object belongs to the owning business group specified by
--TargetGroup. You must specifiy a suffix for the renamed object with the --
suffix option.
The following table describes the command options available.
CLI Command Option Description
--shared
Shares the new items in the package with the members of all business groups in
the tenant. If omitted, makes the new items in the package private to the members
of the owning business group.
--suffix sfxtext
Adds an underscore and the specified text represented by sfxtext to the end of
every object copied from the package as a match. For example, if you specify
--suffix NEW and copy apache:1.0.0 from the package, the new name of the
object is apache _NEW with version 1.0.0. The owning business group for the new
object is the target group specified by --targetGroup.
Using Application Services
VMware, Inc. 257