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
Secured Component Properties
Properties are used to configure deployed components. In some cases, they are used to store sensitive
data, such as passwords.
For example, a WAR component might need to store sensitive data such as passwords to access the
database. These properties can be marked as secured. Values of secured properties are masked and
shown as asterisks in Application Services.
If a property is changed from secured to unsecured, for security purposes, Application Services resets the
property value, for security purposes. You must set a new value for the property.
Important If secured properties are printed in the script using the echo command or other similar
commands, these values appear in plain text in the log files. The values in the log files are not masked.
Required Component Properties
You can set properties as they are required. For example, a deployment might fail if properties are not
defined for scripts that rely on them during the deployment.
For example, to run an Apache Tomcat server, Java is required and the JAVA_HOME property value must
be set.
When a property is marked as required, a value must be provided in at least one of the life cycle stages of
the property, such as the library, blueprint, or deployment profile. For example, an application catalog
administrator can define a required property, mark it as overridable, and not set any value for the property
in the library. The application architect must provide a value for this property in the blueprint or mark it as
overridable in the deployment profile. If the application architect has not set a value for this property, the
deployer is required to set a value for this property in the deployment profile before deploying the
application.
Best Practices for Developing Components
Familiarize yourself with the sample components in the library, as they include a number of examples of
how to define properties and action scripts.
Note Use the sample components in the library only in a test environment.
Follow these best practices when developing components in Application Services.
n
Some installers might need access to the tty console. Redirect the input from /dev/console.
For example, the predefined RabbitMQ service uses the ./rabbitmq_rhel.py --setup-rabbitmq
< /dev/console command in its install script.
Using Application Services
VMware, Inc. 114