To view and configure products that were selected during environment creation, use VMware Aria Suite Lifecycle.

You can configure product details as part of installation or as part of subsequent configuration tasks. Under the Product Details, select products for a new installation.
Product Function
VMware Aria Automation
  1. To monitor health of VMware Aria Automation, select the Monitor with VMware Aria Operations 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.

    This is only available for a new installation where in VMware Aria Operations monitors health of VMware Aria Automation. Inter-product configuration is not supported for an existing environment.

    Cross-product integration for VMware Aria Automation with VMware Aria Operations is not applicable for an import of VMware Aria Automation. This option is only applicable if there is a new installation of VMware Aria Automation.

    If VMware Aria Operations is not present, then you can integrate the products outside of VMware Aria Suite Lifecycle.

    You can also perform cross-product configuration when VMware Aria Automation is the only product and VMware Aria Operations is a part of an environment or when VMware Aria Automation is deployed with import or as new install of VMware Aria Operations.
  3. For a newly installed VMware Aria Automation, select the Configure internal pods and service subsets checkbox, and then enter a K8 Cluster IP Range and K8 Service IP Range.
  4. Select the product certificate from the drop-down menu.
  5. (Optional) Select ON or OFF to activate or deactivate the FIPS compliance mode.
  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.
  9. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for each deployed VM.

For more information about database creation, see Create a new private cloud environment using the installation wizard in VMware Aria Suite Lifecycle.
VMware Aria Automation Config
  1. For VMware Aria Automation Config, select the Tenant ID from the drop-down menu under Product Properties.
  2. For vVMware Aria Automation Config, enter the VM name, FQDN and Virtual IP Address under Components.
  • For VMware Aria Automation Config, you can only perform a single node VMware Aria Automation Config installation at a time. For VMware Aria Automation deployment along with VMware Aria Automation Config, the tenant ID is selected by default. Any additional VMware Aria Automation Config deployment can be performed based on the tenant as organic growth.
  • Federal Information Processing Standard 140-2 Support (FIPS) is supported for VMware Aria Automation Config.
VMware Aria Operations for Logs

Federal Information Processing Standard 140-2 Support (FIPS) is supported for VMware Aria Operations for Logs.

  1. Select the node size from the drop-down menu.
  2. (Optional) Select ON or OFF to enable or deactivate the FIPS compliance mode.
  3. Under Integrated Load Balance Configuration, if you select the Configure Cluster Virtual IPs, enter the FQDN and Virtual IP Address.
  4. To add more node, click ADD NODE.
  5. Select the Applicable Time Sync Mode.
  6. Under components, enter the vRLI primary node details.
  7. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for each deployed VM.
  8. (Optional) Click Add Components to configure additional settings.
  9. Enter the required fields.
VMware Aria Operations

Federal Information Processing Standard 140-2 Support (FIPS) is supported for VMware Aria Operations for Logs.

  1. Under Product Properties, select the Disable TLS version from the drop-down menu.
  2. (Optional) Select ON or OFF to enable or deactivate the FIPS compliance mode.
  3. Select the Certificate from the drop-down menu.
  4. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for each deployed VM.
  5. Add the Product Password.
  6. (Optional) Click Integrate with Identity Manager check box.
  7. Select the Time Sync Mode.
  8. For continuous availability-based deployment, under Components, enter the Infrastructure and Network details for the Witness Domain.
  9. For Continous Availability (CA) based deployment, enter the Infrastructure and Network details for Fault Domain 1 and Fault Domain 2.
  10. If you want to add additional data nodes for a cluster, click the Add Components tab.

    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.

  11. If you want to add remote collectors, click Add Collector Group, and then add the details for the new collector nodes.
VMware Aria Operations for Networks
  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 platform and collector details for VMware Aria Operations for Networks.
  4. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for each deployed VM.
VMware Aria Automation Orchestrator
VMware Aria Automation Orchestrator offers two setup options:
  • VMware Aria Automation Orchestrator-Integrated

    This is the traditional VMware Aria Automation Orchestrator setup option, where VMware Aria Automation Orchestrator is integrated with VMware Aria Automation and you can install VMware Aria Automation Orchestrator after installing VMware Aria Automation

  • VMware Aria Automation Orchestrator Standalone: This setup option has no dependency on VMware Aria Automation and it allows you to integrate with vSphere.
    In addition to the configuration steps described below, the standalone setup requires the following input:
    • vCenter Host: vCenter FQDN.
    • Admin Group: Group name.
    • Admin Group Domain: Domain that the user belongs to.
    Note: To deploy VMware Aria Automation Orchestrator with vSphere authentication using VMware Aria Suite Lifecycle, the Admin Group in vSphere must have full administrator permissions.
  1. Under the Product Properties, select ON or OFF to enable or deactivate the FIPS compliance mode.
  2. Select the Certificate from the drop-down menu.
  3. Add the Product Password.
  4. Select the applicable Time Sync Mode.
  5. For a standard deployment, enter the host name and IP address under Components.
  6. Under Cluster Virtual IP, enter the load balancer host FQDN for the cluster deployment.
  7. Under Components, enter the host name and IP address for the primary and secondary nodes.
VMware Workspace ONE Access
  1. Under the Product Properties, select the certificate from drop-down menu.
  2. Select the admin password from the locker.
  3. Specify the default configuration admin user name and password. This configuration is created as local user in VMware Workspace ONE Access and is used for VMware Aria Suite product integration.
  4. Check Sync Group Members. When enabled, members of the groups are synced from the active directory. When this is deactivated, group names are synced to the directory, but members of the group are not synced.
  5. For a cluster deployment, under Cluster Virtual IP, enter Cluster VIP FQDN. This setting is used to load balance the application.
  6. For a cluster deployment, enter the database IP address that is used internally for proxy access to the primary postgres database.

    This is not same as the address used to load-balance the application and the IP address should be free and available.

  7. Under Components, enter the VMware Workspace ONE Access single or cluster node details.