VCP6-CMA Objective 1.4

VCP6-CMA Objective 1.4

Objective 1.4: Configuring vRealize Automation Settings

Configure vRealize system settings to handle system notifications and appearance

Branding

vRealize automation allows the user interface to be customized to provide a customer/tenant specific appearance. A default appearance/branding is configured by the system administrator role that applies to all tenants by default but can be overridden by a tenant administrator.

Configure default branding
Configuration of the default system branding is managed by a system administrator.

Step #1 - Log in to the vRealize Automation console as a system administrator.

Step #2 - Select Branding under the Administration tab.

Step #3 - Clear the Use Default check box and configure the desired settings. Click Next to configure the footer.

Step #4 - Configure the footer settings and click Update to commit the changes.

Configure tenant branding
Configuration of the tenant branding is managed by a tenant administrator.

Step #1 - Log in to the vRealize Automation console as a tenant administrator.

Step #2 - Select Branding under the Administration tab.

Step #3 - Clear the Use Default check box and configure the desired settings. Click Next to configure the footer.

Step #4 - Configure the footer settings and click Update to commit the changes.

Email Servers
vRA utilizes email for system notifications for things such as request status messages and approval responses. The system administrator role is used to configure inbound and outbound email servers at the global level. The global email servers are inerited by each tenant but the tenant administrator can override the email server configuration at the tenant level.

Global Outbound Email Server

Step #1 - Log in to the vRealize Automation console as a system administrator.

Step #2 - Select Email Servers from the Notifications section under the Administration tab.

Step #3 - Click Add to select whether to add an inbound or outbound email server.

Step #4 - Select the Email - Outbound radio button and click OK.

Step #5 - Configure all the appropriate settings and click Test Connection to verify that the settings work. Click Update to commit the changes.

Global Inbound Email Server

Step #1 - Log in to the vRealize Automation console as a system administrator.

Step #2 - Select Email Servers from the Notifications section under the Administration tab.

Step #3 - Configure all the appropriate settings and click Test Connection to verify that the settings work. Click Update to commit the changes.

The configured email servers are now shown in the Email Servers section.


Enable connections and set concurrency limits on IaaS server

Enable connections

Set concurrency limits on IaaS server Machine provisioning limits and data collection frequency can be adjusted to improve performance of vRealize Automation based upon the specific needs of an environment.

Machine Provisioning
vRealize Automation limits concurrent provisioning to avoid overloading the underlying infrastructure. By default vRealize Automation limits concurrent virtual provisioning activities for hypervisors that use proxy agents to two per proxy agent.

Step #1 - Log in to the IaaS server hosting the manager service.

Step #2 - Open the C:\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config configuration file.

Step #3 - Update the desired variables in the workflowTimeoutConfigurationSection section and restart the manager (VMware vCloud Automation Center Service) service. If running in HA mode changes need to be made on the primary and failover servers

  • MaxOutstandingResourceIntensiveWorkItems: Concurrent provisioning limit (default of two)
  • CloneExecutionTimeout: Virtual provisioning execution timeout interval
  • SetupOSExecutionTimeout: Virtual provisioning execution timeout interval
  • CloneTimeout: Virtual provisioning clone delivery timeout interval
  • SetupOSTimeout: Virtual provisioning setup OS delivery timeout interval
  • CloudInitializeProvisioning: Cloud provisioning initialization timeout interval
  • MaxOutstandingDataCollectionWorkitems: Concurrent data collection limit
  • InventoryTimeout: Inventory data collection execution timeout interval
  • PerformanceTimeout: Performance data collection execution timeout interval
  • StateTimeout: State data collection execution timeout interval

Adjust Execution Frequency of Machine Callbacks
vRealize Automation supports changing the frequency at which several callbacks such as checks for new machines, machine request, and more happen.

Step #1 - Log in to the IaaS server hosting the manager service.

Step #2 - Open the C:\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config configuration file.

Step #3 - Update the desired variables in the appSettings section and restart the manager (VMware vCloud Automation Center Service) service. If running in HA mode changes need to be made on the primary and failover servers

  • RepositoryWorkflowTimerCallbackMilliSeconds: Checks the repository service, or Model Manager Web Service for activity.
  • ProcessLeaseWOrkflowTimerCallbackIntervalMiliSeconds: Checks for expired machine leases
  • BulkRequestWorkflowTimerCallbackMiliSeconds: Checks for bulk requests
  • MachineRequestTimerCallbackMiliSeconds: Checks for machine requests
  • MachineWorkflowCreationTimerCallbackMiliSeconds: Checks for new machines

Configuring DataCenter Locations

Adding a datacenter location

  • Log onto the IaaS website host and open C:\Program Files (x86)\VMware\vCAC\Server\Website\XmlData\DataCenterLocations.xml
  • In the CustomDataType section add a Data Name entry for each datacenter location desired and close file when finished.
<CustomDataType>  
  <Data Name="Chicago" Description="Chicago Datacenter" />
</CustomDataType>  
  • Restart the manager (VMware vCloud Automation Center Service) service

Removing a datacenter location

  • Log onto the IaaS website host and open C:\Program Files (x86)\VMware\vCAC\Server\Website\XmlData\DataCenterLocations.xml
  • In the CustomDataType section remove the Data Name entry for each datacenter location desired and close file when finished.
  • Restart the manager (VMware vCloud Automation Center Service) service

Reference

Configuring vRealize Automation

Subscribe to