You can view and configure the products that were selected environment creation.

Procedure

  • Under the Product Details, select the products for a new installation.
    Product Function
    vRealize Automation
    1. To monitor health of vRealize Automation, select the Monitor with vROps check box.
    2. To manage the workload using load balancer and reclaim unused resources from the resource pool, select the Workload Placement and Reclamation check box.
      Note: This is only available for a new installation where in vRealize Operations Manager monitors health of vRealize Automation. Inter-product configuration is not supported for an existing environment.

      If vRealize Operations Manager is not present, then you can integrate the products outside of LCM.

      Cross-product integration for vRealize Automation with vRealize Operations Manager is not applicable for an import of vRealize Automation. And is only applicable if there is a new installation of vRealize Automation.

      You can also perform a cross product configuration where vRealize Automation is the only case where vRealize Operations Manager is already part of an environment or vRealize Automation is getting deployed along with Import or New Install of vRealize Operations Manager. For subsequent fabric group additions, fabric group admin roles should be assigned to configuration@vspherelocal user for vRealize Operations Manager to retrieve fabric group related information.

      Note: You can perform a cross product integration only when vRealize Operations Manager is already deployed in an environment where you can newly install vRealize Automation. You can also select vRealize Operations Manager Import or New install along with a new installation of vRealize Automation.
      Note: Starting with 8.2, when you newly install vRealize Automation, you can select the Configure internal pods and service subsets checkbox, and then enter the values for K8 Cluster IP Range and K8 Service IP Range.
    3. Enter the Windows Username, and Password.
    4. Select the Product Certificate from the drop-down menu.
    5. You can select the component level certificate by toggling the Component Level Certificate. Select the required IaaS Manager Certificate, IaaS Web Certificate, and Cafe Certificate as required from the drop-down menus.
    6. Select the Applicable Time Sync mode.
    7. Select the Time Server (NTP). For more information, see Configure NTP Servers.
    8. If you want to configure cluster virtual IPs, then select the Yes or No options. If you select yes, the load balancer is connected to the individual product and then configure the vRA Appliance, IaaS Web, and IaaS Manager manually.
    9. As a cloud admin, you can configure a template, click Yes, and from the Configure Windows box, select the required windows template and its associated spec. When you select Yes, the Window box section appears. If no is selected, then vRealize Suite Lifecycle Manager will not deploy new Windows VMs for IaaS components.
    10. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.
    Note: For more information on configuring IaaS components, see Deploy Windows VMs for vRealize Automation Installation. For more information on database creation, see Create a New Private Cloud Environment Using the Installation Wizard.
    vRealize Business for Cloud
    1. Under Product Properties section, enter the VM Name, Hostname, and IP Address.
    vRealize Log Insight
    1. Select the node size from the drop-down menu.
    2. Under Integrated Load Balance Configuration, if you select the Configure Cluster Virtual IPs, enter the FQDN and Virtual IP Address.
    3. To add more node, click ADD NODE.
    4. Select the Applicable Time Sync Mode.
    5. Under components, enter the vRLI primary node details.
    6. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.
    7. (Optional) Click Add Components to configure additional settings.
    8. Enter the required fields.
    vRealize Operations Manager
    1. Under Product Properties, select the Disable TLS version from the drop-down menu.
    2. Select the Certificate from the drop-down menu.
    3. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VMs.
    4. Add the Product Password.
    5. (Optional) Click Integrate with Identity Manager check box.
    6. Select the Applicable Time Sync Mode.
    7. For Continuous Availability (CA) based deployment, under Components, enter the Infrastructure and Network details for Witness Domain.
    8. For Continous Availability (CA) based deployment, enter the Infrastructure and Network details for Fault Domain 1 and Fault Domain 2.
    9. If you want to add additional data nodes for a cluster, click the Add Components tab.
      Note: If you select Use Global Configuration, the field data is populated based on the information provided in the Infrastructure tab. You can select this option for Witness Domain, Fault Domain 1, or Fault Domain 2. Ensure that each domain is in different physical location so that if one fault domain fails, nodes from the other fault domain remains active.
    vRealize Network Insight
    1. Under the Product Properties, select the node size from the drop-down menu.
    2. Select the Applicable Time Sync Mode.
    3. Under components, enter the vrni platform and vrni collector details.
    4. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.
    VMware Identity Manager
    1. Under the Product Properties, select the certificate from drop-down menu.
    2. Select the Admin Password from the locker.
    3. Set Default Configuration Admin Username. This will be created as local user in VMware Identity Manager and is used for vRealize Suite Product Integration.
    4. Select the password for Default Configuration Admin user.
    5. Check Sync Group Members. When enabled, members of the groups are synced from the Active Directory. When this is disabled, group names are synced to the directory, but members of the group are not synced.
    6. For a cluster deployment, under Cluster Virtual IP enter Cluster VIP FQDN, this is used to load balance the application.
    7. For a cluster deployment, enter Database IP used internally for proxying to the postgres master (primary).
      Note: This is not same as the one used to load-balance the application and the IP address should be free, and available.
    8. Under Components, enter the VMware Identity Manager single or Cluster Node details.