To prepare the vRealize Appliance for use, a system administrator configures the host settings, generates an SSL certificate, and provides SSO connection information.
- Navigate to the vRealize Appliance management console by using its fully qualified domain name, https://vra-va-hostname.domain.name:5480/.
- Continue past the certificate warning.
- Log in with user name root and the password you specified when you deployed vRealize Appliance.
- Select Resolve Automatically to view the name of the currently specified host. and select
- (Optional) : If you want to change the host name, select Update Host and enter the fully qualified domain name, vra-hostname.domain.name, of the vRealize Appliance in the Host Name text box. If you are using a load balancer, enter the fully qualified domain name for the load balancer server.
- Select the certificate type from the Certificate Action menu.
If you are using a PEM-encoded certificate, for example for a distributed environment, select Import.
Certificates that you import must be trusted and must also be applicable to all instances of vRealize Appliance and any load balancer through the use of Subject Alternative Name (SAN) certificates.Note:
If you use certificate chains, specify the certificates in the following order:
Client/server certificate signed by the intermediate CA certificate
One or more intermediate certificates
A root CA certificate
Copy the certificate values from BEGIN PRIVATE KEY to END PRIVATE KEY, including the header and footer, and paste them in the RSA Private Key text box.
Copy the certificate values from BEGIN CERTIFICATE to END CERTIFICATE, including the header and footer, and paste them in the Certificate Chain text box. For multiple certificate values, include a BEGIN CERTIFICATE header and END CERTIFICATE footer for each certificate.
(Optional) If your certificate uses a pass phrase to encrypt the certificate key, copy the pass phrase and paste it in the Passphrase text box.
Type a common name for the self-signed certificate in the Common Name text box. You can use the fully qualified domain name of the virtual appliance (hostname.domain.name) or a wild card, such as *.mycompany.com. If you use a load balancer, you need to specify the FQDN of the load balancer or a wildcard that matches the name of the load balancer. If the name is the same as the host name for the virtual appliance, you can leave the text box empty. Do not accept a default value if one is shown, unless it matches the host name of the virtual appliance.
Type your organization name, such as your company name, in the Organization text box.
Type your organizational unit, such as your department name or location, in the Organizational Unit text box.
Type a two-letter ISO 3166 country code, such as US, in the Country text box.
Leave the current SSL configuration. Select this option to cancel your changes.
- Click Save Settings to save host information and SSL configuration.
- Configure the SSO settings that the vRealize Appliance uses to interact with the Identity Appliance. These settings must match the settings you entered when configuring the Identity Appliance.
- Click SSO.
- Type the fully qualified domain name of the Identity Appliance, identity-va-hostname.domain.name in the SSO Host text box.
For example, vcac-sso.mycompany.com. Do not use an https:// prefix.
- Edit the default port number, 7444, in the SSO Port text box if you are using a nondefault port.
For example, for vCenter Platform Services Controller SSO, specify 443.
- Do not modify the default tenant name, vsphere.local, in the SSO Default Tenant text box.
- Type the default administrator name email@example.com in the SSO Admin User text box.
- Type the SSO administrator password in the SSO Admin Password text box. The password must match the password you specified in the SSO settings for the Identity Appliance.
- Click Save Settings.
After a few minutes, a success message appears and SSO Status is updated to Connected.
- (Optional) : Select Apply Branding to apply vRealize Automation branding to your installation.
Use this option if you are installing from vCenter and want to use vRealize Automation instead of vCenter branding.
- (Optional) : If the spinner does not stop within a few minutes, exit the appliance, close the browser, and log in again.
- Click Messaging. The configuration settings and status of messaging for your appliance is displayed. Do not change these settings.
- Click the Telemetry tab.
You can choose to participate in the Customer Experience Improvement Program. You can unsubscribe from the program at any time.
Select Enable to activate the Program.
Deselect Enable to unsubscribe from the Program.
When you enable the Program, vRealize Automation attempts to establish a connection to https://vmware.com and to automatically discover any proxy server you might have configured for your vRealize Automation deployment.
- Click Services and verify that services are registered.
Depending on your site configuration, this can take about 10 minutes.Note:
You can log in to the appliance and run tail -f /var/log/vcac/catalina.out to monitor startup of the services.
- Configure the license to enable the Infrastructure tab on the vRealize Automation console.
- Click vRA Settings > Licensing.
- Click Licensing.
- Type a valid vRealize Automation license key that you downloaded when you downloaded the installation files, and click Submit Key.
If you experience a connection error, you might have a problem with the load balancer. Check network connectivity to the load balancer.
- Confirm that you can log in to the vRealize Automation console.
- Open a browser and navigate to https://vcac-hostname.domain.name/vcac.
- Accept the vRealize Automation certificate.
- Accept the SSO certificate.
- Log in with firstname.lastname@example.org and the password you specified when you configured SSO.
The console opens to the Tenants page on the Administration tab. A single tenant named vsphere.local appears in the list.
You have finished the deployment and configuration of your vRealize Appliance. If the appliance does not function correctly after configuration, redeploy and reconfigure the appliance. Do not make changes to the existing appliance.