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
You cannot export objects with names that contain a tab, underscore, new line, or carriage return
character.
When you export an application, service, external service, script task, or policy version, all of the secure
properties are removed by default to avoid exporting sensitive information such as passwords to another
Application Services instance.
When you run the import command, the entire package is imported to the designated server. You cannot
selectively import elements from the export package.
The export-package command
The CLI export-package command has the following format.
export-package --exportFilePath pathname --fromGroup obgname --CommandOption [[--CommandOption] ...]
[--uncompressed]
The following table describes the required components of the export-package command.
CLI Command Component Description
export-package
The export-package command name.
--exportFilePath pathname
Specifies the path name of the export package to be created. For example, --
exportFilePath /home/dev/joomla.zip specifies the location and name of the
joomla.zip export package. You must use the --uncompressed option when the
export package has a .xml file extension.
--fromGroup busgroupname
Specifies the owning business group of the object to export. Policies are excluded.
Anyone in the tenant can access a policy, so the owning business group is ignored.
--CommandOption
Specifies the type, name, and version of the object to export. For example, the
command option --applicationVersion distmaps:1.0.0 specifies an
application with the name distmaps and the version 1.0.0. An export-package
command can have multiple command options, but must have at least one
command option.
The following table describes the command options you can use when exporting one or more objects.
CLI Command Option Description
--applicationVersion Name:VersionID
Specifies the object and version to export.
n
Name is the name of the application, service, script task, external service,
policy, or artifact repository to export. A name is case-insensitive. If a name
contains a space, enclose it in double quotes.
n
VersionID is the version identifier for the object in the form major . minor . micro
{-qualifier}, for example 1.0.0-beta.
You can export multiple objects of the same type with a single export command by
separating the version names with commas. If a version name in a list of version
names contains a space, enclose the entire list in double quotes.
export-package --exportFilePath pkgname.zip --fromGroup Dev
--applicationVersion "aname1:1.0.0,aname two:1.0.0,aname3:1.0.0"
--serviceVersion Name:VersionID
--scriptTaskVersion Name:VersionID
--externalServiceVersion
Name:VersionID
--policyVersion Name:VersionID
Using Application Services
VMware, Inc. 254