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 Option Description
--repoVersion Name:1.0.0
You can also export multiple types of objects with the same export command.
export-package --exportFilePath pkgname.zip --fromGroup Dev
--applicationVersion aname:1.0.0 --serviceVersion sname:1.0.0 --
scriptTaskVersion stname:1.0.0
The ALL keyword exports all versions of the object type in the specified business
group.
export-package --exportFilePath pkgname.zip --fromGroup Dev
--applicationVersion ALL --serviceVersion ALL --
scriptTaskVersion ALL
--uncompressed
Export the package in uncompressed format. Required for export packages with
a .xml file extension.
Exporting dependencies
When you export an object, you also export its dependencies. For a high-level object like an application,
dependencies can include services, VM templates, script tasks, and more. The export command validates
the owning business group of the top-level object, but not of the dependent objects which might belong to
different business groups. The command simply exports the dependent objects as part of the top-level
object. For example, suppose an application belongs to the Development business group but a service in
the application belongs to the Production business group. A member of the Development group can
export the application which includes the service. However, a member of the Production business group
can export only the service but not the application. Of course, a member of both business groups can
export both objects together or independently.
Export requirements
The following table shows when you must belong to the owning business group to export or import an
object.
Exported Object Business Group Requirements
Application
Service
External Service
VmTemplate
The following tasks require membership in the owning business group.
n
Export the object.
n
Export the private object as a dependency.
The following tasks allow membership in any business group in the tenant.
n
View a shared application or service.
n
Export the shared object as a dependency.
Script Task
(always shared)
The following tasks require membership in the owning business group.
n
Export the object.
The following task allows membership in any business group in the tenant.
n
View the object.
Using Application Services
VMware, Inc. 255