System Administrators install
vRealize Automation into their existing virtualization environments. Before the installation begins, there are a number of preliminary steps that must be completed to prepare the deployment environment.
DNS and Host Name Resolution vRealize Automation requires the system administrator to identify all hosts using a fully qualified domain name (FQDN). In a distributed deployment, all vRealize Automation components must be able to resolve each other by using an FQDN. The Model Manager Web service, Manager Service, and Microsoft SQL Server database must also be able to resolve each other by their Windows Internet Name Service (WINS) name. You must configure the Domain Name System (DNS) to resolve these host names in your environment.
Hardware and Virtual Machine Requirements Installation requires minimum system resources to install virtual appliances and minimum hardware requirements to install IaaS components on the Windows Server.
Browser Considerations Some restrictions exist for browser use with vRealize Automation.
Password Considerations The vRealize Automation administrator password cannot contain a trailing "=" character.
Windows Server Requirements The virtual or physical Windows machine that hosts the IaaS components must meet configuration requirements for the IaaS database, the IaaS server components, the IaaS Manager Service, and Distributed Execution Managers.
Port Requirements vRealize Automation uses designated ports for communication and data access.
User Accounts and Credentials Required for Installation You must verify that you have the roles and credentials to install vRealize Automation components.
Security vRealize Automation uses SSL to ensure secure communication among components. Passphrases are used for secure database storage.
Time Synchronization A system administrator must set up accurate timekeeping as part of the vRealize Automation installation.