Deploy the vRealize Automation Appliance

Before you can take any of the installation paths, vRealize Automation requires that you deploy at least one vRealize Automation appliance.

About this task

To create the appliance, you use the vSphere client to download and deploy a partially configured virtual machine from a template. You might need to perform the procedure more than once, if you expect to create an enterprise deployment for high availability and failover, with multiple vRealize Automation appliances behind a load balancer.

1. Select the vSphere Deploy OVF Template option.
2. Enter the path to the vRealize Automation appliance .ovf or .ova file.
3. Review the template details.
4. Read and accept the end user license agreement.
5. Enter an appliance name and inventory location.

   When you deploy appliances, use a different name for each one, and do not include non-alphanumeric characters such as underscores (_) in names.

6. Select the host and cluster in which the appliance will reside.
7. Select the resource pool in which the appliance will reside.
8. Select the storage that will host the appliance.
9. Select a disk format.

   Thick formats improve performance, and thin formats save storage space.

   Format does not affect appliance disk size. If an appliance needs more space for data, add disk by using vSphere after deploying.

10. From the drop-down menu, select a Destination Network.
11. Complete the appliance properties.
    1. Enter and confirm a root password.

       The root account credentials log you in to the browser-based administration interface hosted by the appliance, or the appliance operating system command line console.

    2. Select whether or not to allow remote SSH connections to the command line console.

       Disabling SSH is more secure but requires that you access the console directly in vSphere instead of through a separate terminal client.

    3. For Hostname, enter the appliance FQDN.

       For best results, enter the FQDN even if using DHCP.

       Note:

       vRealize Automation supports DHCP, but static IP addresses are recommended for production deployments.

    4. In Network Properties, when using static IP addresses, enter the values for gateway, netmask, and DNS servers. You must also enter the IP address, FQDN, and domain for the appliance itself, as shown in the following example.

       

12. Depending on your deployment, vCenter Server, and DNS configuration, select one of the following ways of finishing deployment and powering up the appliance.

    • If you deployed to vSphere, and Power on after deployment is available on the Ready to Complete page, take the following steps.

      1. Select Power on after deployment and click Finish.

      2. After the file finishes deploying into vCenter Server, click Close.

      3. Wait for the machine to start, which might take up to 5 minutes.

    • If you deployed to vSphere, and Power on after deployment is not available on the Ready to Complete page, take the following steps.

      1. After the file finishes deploying into vCenter Server, click Close.

      2. Power on the vRealize Automation appliance.

      3. Wait for the machine to start, which might take up to 5 minutes.

      4. Verify that the vRealize Automation appliance is deployed by pinging its FQDN. If you cannot ping the appliance, restart the virtual machine.

      5. Wait for the machine to start, which might take up to 5 minutes.

    • If you deployed the vRealize Automation appliance to vCloud using vCloud Director, vCloud might override the password that you entered during OVA deployment. To prevent the override, take the following steps.

      1. After deploying in vCloud Director, click your vApp to view the vRealize Automation appliance.

      2. Right-click the vRealize Automation appliance, and select Properties.

      3. Click the Guest OS Customization tab.

      4. Under Password Reset, clear the Allow local administrator password option, and click OK.

      5. Power on the vRealize Automation appliance.

      6. Wait for the machine to start, which might take up to 5 minutes.

13. Verify that the vRealize Automation appliance is deployed by pinging its FQDN.

What to do next

Log in to a console session to activate FQDN for RabbitMQ. See Activate FQDN for RabbitMQ Before Installation.