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
Exported Object Business Group Requirements
Policy
(always shared)
The following tasks allow membership in any business group in the tenant.
n
Export the object.
Artifact repository
(always shared)
The following tasks require membership in the owning business group.
n
Export the object.
Using the CLI Import Command
The CLI import command imports a package that includes applications and their associated blueprints
and deployment profiles, external services, policies, artifact repositories, services, logical templates, and
available custom tasks between different Application Services instances.
You can import packages created with the export command only. You cannot import a package that has
been altered or created by any means other than the export command.
You must belong to the owning business group of every object in the import package to import the
objects.
When you run the import-package command, you import the entire package to the targeted server. You
cannot selectively import objects from the package.
You cannot import external services with the same name into different business groups, and you cannot
import an external service as a dependency if it is owned by another business group.
n
Make sure the application that contained the deployment profile in the source appliance, is either a
shared application or privately owned by the target group in the target appliance. Importing a
deployment profile into a private application owned by any business group other than the target group
is not supported.
n
Make sure the blueprint that was used when creating the deployment profile is not changed when
importing, any slight change in the blueprint will not allow nodes and components to map and this use
case is not supported.
You can import a deployment profile as a dependency of a shared application, or as a dependency of a
private application owned by the target business group. Also ensure that the blueprint used when creating
the deployment profile does not change during the import because the slightest change prevents nodes
and components from mapping. Before you import a deployment profile, save the custom task you added
to the execution deployment plan. See Review the Execution Plan and Add Custom Tasks.
For the import process to finish successfully, the objects in the package cannot include non-ASCII
characters.
The import-package command
The CLI import-package command has the following format.
import-package --importFilePath pathname --targetGroup obgname --ConflictResolutionAction action
The following table describes the required components of the import-package command.
Using Application Services
VMware, Inc. 256