The system administrator installs the Model Manager Website component to provide access to infrastructure capabilities in the vRealize Automation Web console.

Prerequisites

Procedure

  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__vra-va-hostname.domain.name@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 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 Appliance.

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

      Compare the certificate thumbprint with the thumbprint set for the vRealize Appliance. You can view the vRealize 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.
  10. Click Next.
  11. Select Website and ModelManagerData 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.