The Web server provides access to infrastructure capabilities in vRealize Automation. After the first Web server is installed, you might increase performance by installing additional IaaS Web servers.

Do not install Model Manager Data with an additional Web server component. Only the first Web server component hosts Model Manager Data.



  1. If using a load balancer, disable the other nodes under the load balancer, and verify that traffic is directed to the node that you want.

    In addition, disable load balancer health checks until all vRealize Automation components are installed and configured.

  2. Right-click the setup__vrealize-automation-appliance-FQDN@5480.exe setup file and select Run as administrator.
  3. Click Next.
  4. Accept the license agreement and click Next.
  5. On the Log in page, supply administrator credentials for the vRealize Automation appliance and verify the SSL Certificate.
    1. Type the user name, which is root, and the password.

      The password is the password that you specified when you deployed the vRealize Automation appliance.

    2. Select Accept Certificate.
    3. Click View Certificate.

      Compare the certificate thumbprint with the thumbprint set for the vRealize Automation appliance. You can view the vRealize Automation appliance certificate in the client browser when the management console is accessed on port 5480.

  6. Click Next.
  7. Select Custom Install on the Installation Type page.
  8. Select IaaS Server under Component Selection on the Installation Type page.
  9. Accept the root install location or click Change and select an installation path.

    Even in a distributed deployment, you might sometimes install more than one IaaS component on the same Windows server.

    If you install more than one IaaS component, always install them to the same path.

  10. Click Next.
  11. Select Website on the IaaS Server Custom Install page.
  12. Select a Web site from available Web sites or accept the default Web site on the Administration & Model Manager Web Site tab.
  13. Type an available port number in the Port number text box, or accept the default port 443.
  14. Click Test Binding to confirm that the port number is available for use.
  15. Select the certificate for this component.
    1. If you imported a certificate after you began the installation, click Refresh to update the list.
    2. Select the certificate to use from Available certificates.
    3. If you imported a certificate that does not have a friendly name and it does not appear in the list, deselect Display certificates using friendly names and click Refresh.

    If you are installing in an environment that does not use load balancers, you can select Generate a Self-Signed Certificate instead of selecting a certificate. If you are installing additional Web site components behind a load balancer, do not generate self-signed certificates. Import the certificate from the main IaaS Web server to ensure that you use the same certificate on all servers behind the load balancer.

  16. (Optional) Click View Certificate, view the certificate, and click OK to close the information window.
  17. (Optional) Select Suppress certificate mismatch to suppress certificate errors. The installation ignores certificate name mismatch errors as well as any remote certificate-revocation list match errors.

    This is a less secure option.

  18. In the IaaS Server text box, identify the first IaaS Web server component.



    With a load balancer

    Enter the fully qualified domain name and port number of the load balancer for the IaaS Web server component,

    Do not enter IP addresses.

    Without a load balancer

    Enter the fully qualified domain name and port number of the machine where you installed the IaaS first Web server component,

    Do not enter IP addresses.

    The default port is 443.

  19. Click Test to verify the server connection.
  20. Click Next.
  21. Complete the Prerequisite Check.



    No errors

    Click Next.

    Noncritical errors

    Click Bypass.

    Critical errors

    Bypassing critical errors causes the installation to fail. If warnings appear, select the warning in the left pane and follow the instructions on the right. Address all critical errors and click Check Again to verify.

  22. On the Server and Account Settings page, in the Server Installation Information text boxes, enter the user name and password of the service account user that has administrative privileges on the current installation server.

    The service account user must be one domain account that has privileges on each distributed IaaS server. Do not use local system accounts.

  23. Provide the passphrase used to generate the encryption key that protects the database.



    If you have already installed components in this environment

    Type the passphrase you created previously in the Passphrase and Confirm text boxes.

    If this is the first installation

    Type a passphrase in the Passphrase and Confirm text boxes. You must use this passphrase every time you install a new component.

    Keep this passphrase in a secure place for later use.

  24. Specify the IaaS database server, database name, and authentication method for the database server in the Microsoft SQL Database Installation Information text box.

    This is the IaaS database server, name, and authentication information that you created previously.

  25. Click Next.
  26. Click Install.
  27. When the installation finishes, deselect Guide me through the initial configuration and click Next.

What to do next

Install the Active Manager Service.