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
Using Tenants and Business
Groups in Application Services 6
Application Services and vRealize Automation share tenants and business groups. A tenant is an
organizational unit in a vRealize Automation deployment. A business group belongs to a tenant and
associates a set of services and resources with a set of users.
An Application Services appliance is registered to a vRealize Automation deployment, also called an
instance, and to a tenant in that instance. An Application Services system administrator can register the
appliance to different tenants, but only one at a time.
A tenant has multiple business groups. Each business group within a tenant has members and objects
such as applications, services, and external services. Users can be members of multiple business groups
and multiple tenants. Every object is owned by a business group. Only users who belong to the business
group can edit the objects in that group.
Applications, services, and other objects in Application Services are private or shared. Only users who
are members of a particular business group can view or edit private objects in that group. All users in all
business groups within a tenant can view shared objects.
As part of their function, user roles determine which objects users can create. For example, a user
assigned the application architect role can create an application, among other objects. When creating the
application, the user assigns the business group and specifies whether the application is private or
shared. Thereafter, only members of the owning business group can edit the application. If the application
is private, only members of the owning business group can view it. If the application is shared, all
members of all business groups in the tenant can view the application. Regardless of whether the
application is private or shared, only members of the owning business group can edit the application.
The different levels of sharing determine what you can do with the components within the blueprint, and
with the application itself. As the logged-in user who constructs the application blueprint, you must belong
to the owning business group of the application to edit the blueprint. Logical templates, services, external
services, tasks, artifacts, and artifact repositories all belong to business groups and can be private or
shared. If you select shared blueprint components that belong to a different business group, you can view
those components but you cannot alter them. Only when you belong to the owning business group of a
component can you change the component. When you share an application, all of the components in the
application blueprint such as logical templates, services, and external services must be explicitly shared.
VMware, Inc.
42