The vRealize Automation Installation Wizard presents you with easy to use pages where you check for prerequisites, enter settings, validate settings, and install vRealize Automation components.

About this task

Note:

The wizard includes steps where you log in to other systems such as load balancers and the IaaS Windows servers.

Prerequisites

  • In vSphere, deploy the vRealize Automation appliance OVA or OVF to create one or more appliances.

    Minimal deployments use one vRealize Automation appliance. Enterprise deployments may have multiple appliances behind load balancing.

  • Have one or more Windows systems available on which to host IaaS components.

  • Start the wizard by pointing a Web browser to the vRealize Automation appliance URL.

    https://vrealize-automation-appliance-FQDN:5480

Procedure

  1. On Deployment Type, the minimal option expects to deploy to one vRealize Automation appliance and one Windows server that will host the IaaS Web and Manager Service components. Enterprise deployments support multiple, separate appliances and Windows hosts, with load balancing.
  2. On Installation Prerequisites, you pause to log in to your IaaS Windows servers and install the Management Agent. The Management Agent allows the wizard to discover and connect to those IaaS servers.

    Management Agent installation requires communication with a running vRealize Automation appliance.

    On the prerequisites page, you also select whether to synchronize time using your deployment host or an external network time protocol (NTP) server.

  3. (Enterprise Deployments Only) For vRealize Appliances, enter FQDNs and login credentials for each vRealize Automation appliance in the enterprise deployment.
  4. (Enterprise Deployments Only) For Server Roles, select which Windows machines will serve as IaaS primary and additional Web servers, Manager Service hosts, DEM hosts, and Agent hosts.
  5. On Prerequisite Checker, you allow the wizard to check for and fix Windows server configurations to support IaaS installation.

    The wizard cannot fix insufficient memory or CPU. You must correct those issues in vSphere or on your hardware, if they occur.

  6. For vRealize Automation Host, enter the vRealize Automation appliance FQDN. If you are deploying an enterprise configuration that includes multiple vRealize Automation appliances, enter the load balancer FQDN.
  7. For Single Sign-On, enter the password that vRealize Automation users will use to log in to the default tenant.
  8. For IaaS Host, enter the Windows server FQDN of the machine that will host the IaaS Web component, enter domain account credentials with administrator privileges on all IaaS servers, and enter a passphrase to use for IaaS database access.
  9. For Microsoft SQL Server, enter the Windows server FQDN of the SQL database server on which you will host the IaaS database.

    In addition to administrator privileges on all IaaS servers, the domain account that you used in the previous step must have the sys admin role in SQL.

  10. (Enterprise Deployments Only) For Web Role, enter an Internet Information Services (IIS) Web site name and port for the IaaS Web site, and enter login credentials to the Windows machines that will be the IaaS Web servers. Use domain account credentials with administrator privileges on all IaaS servers.
  11. (Enterprise Deployments Only) For Manager Service Role, select which Windows machine will serve as the active IaaS Manager Service host, and enter login credentials. Use domain account credentials with administrator privileges on all IaaS servers.

    Even when there are multiple Manager Service machines, never run the service simultaneously on more than one.

  12. For Distributed Execution Managers, enter FQDNs, a unique instance name, and credentials for each IaaS Windows server that will run a Distributed Execution Manager. Use domain account credentials with administrator privileges on all IaaS servers.
  13. For Agents, enter FQDNs, agent names, endpoint types, and login credentials for each kind of virtualization resource that vRealize Automation will deploy to. vSphere is usually one of the agent types.

    Alternatively, you can add agents post-installation.

  14. For vRealize Appliance Certificate, enter an organization name, organization unit (OU), and country code, and click Save Generated Certificate.

    Alternatively, you can import a certificate.

  15. For Web Certificate, enter an organization name, organization unit (OU), and country code, and click Save Generated Certificate.

    Alternatively, you can import a certificate or paste in the thumb print of a certificate that is already installed on the Web server.

  16. (Enterprise Deployments Only) For Manager Service Certificate, enter an organization name, organization unit (OU), and country code, and click Save Generated Certificate.

    Alternatively, you can import a certificate or paste in the thumb print of a certificate that is already installed on the Manager Service host.

  17. (Enterprise Deployments Only) On Load Balancers, you pause to log in to your load balancer and configure the pool of members based on the nodes shown on the wizard page.
  18. To determine whether the IaaS components can be installed by the Wizard, click Validate.
  19. In vSphere, take a snapshot of each vRealize Automation appliance and IaaS Windows server. Select the option to snapshot the virtual machine memory.
  20. Click Install. If you need to retry the installation, first revert to the snapshots taken in the previous step.

    Depending on how the install failed, you might need to examine errors, apply corrective actions, and take snapshots again before retrying.

  21. For Licensing, enter a vRealize Automation, vRealize Suite, vRealize Business, or vRealize Code Stream key.
  22. For Telemetry, decide whether or not to participate in the VMware Customer Experience Improvement Program (CEIP) by sending vRealize Automation usage statistics to VMware.
  23. On Post-Installation Options, you have the option to start creating vRealize Automation catalog items in the default tenant. To do so, you must have installed at least one agent on the Agents wizard page. Alternatively, you can migrate data from an older deployment.

What to do next

(Optional) The last wizard page displays the path and name to a properties file. You can edit the file and use it to perform a silent vRealize Automation installation with the same or similar settings from your wizard session.