Configure Product Details

Product	Function
vRealize Automation	To monitor health of vRealize Automation, select the Monitor with vROps check box. 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 cross-product configuration when vRealize Automation is the only product and vRealize Operations Manager is a part of an environment or when vRealize Automation is deployed with Import or New Install of vRealize Operations Manager. Note: Starting with 8.2 release, when you newly install vRealize Automation, select the Configure internal pods and service subsets checkbox, and then enter the values for K8 Cluster IP Range and K8 Service IP Range. Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Automation. Select the Product Certificate from the drop-down menu. (Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode. Select the Applicable Time Sync mode. Select the Time Server (NTP). For more information, see Configure NTP Servers. If you want to configure cluster virtual IPs, then select the Yes or No options. (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 database creation, see Create a New Private Cloud Environment Using the Installation Wizard.
vRealize Automation Salt Stack Config vRA Integrated Standalone	For vRA Integrated vRealize Automation Salt Stack Config, select the Tenant ID from the drop-down menu under Product Properties. For vRA Integrated and Standalone vRealize Automation Salt Stack Config, enter the VM name, FQDN and Virtual IP Address under Components. Note: For vRealize Automation SaltStack Config vRA-Integrated setup, you can only perform a single node SaltStack Config installation at a time. For vRealize Automation deployment along with SaltStack Config vRA-Integrated, the tenant ID is selected by default. Any additional SaltStack Config deployment can be performed based on the tenant as organic growth. In the 8.4 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Automation SaltStack Config.
vRealize Business for Cloud	Under Product Properties section, enter the VM Name, Hostname, and IP Address.
vRealize Log Insight	Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Log Insight. It is also supported as a Day-2 operation. Select the node size from the drop-down menu. (Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode. Under Integrated Load Balance Configuration, if you select the Configure Cluster Virtual IPs, enter the FQDN and Virtual IP Address. To add more node, click ADD NODE. Select the Applicable Time Sync Mode. Under components, enter the vRLI primary node details. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's. (Optional) Click Add Components to configure additional settings. Enter the required fields.
vRealize Operations Manager	Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Log Insight.It is also supported as a Day-2 operation. Under Product Properties, select the Disable TLS version from the drop-down menu. (Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode. Select the Certificate from the drop-down menu. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VMs. Add the Product Password. (Optional) Click Integrate with Identity Manager check box. Select the Applicable Time Sync Mode. For Continuous Availability (CA) based deployment, under Components, enter the Infrastructure and Network details for Witness Domain. For Continous Availability (CA) based deployment, enter the Infrastructure and Network details for Fault Domain 1 and Fault Domain 2. 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. If you want to add remote collectors, click Add Collector Group, and then add the details for the new collector nodes.
vRealize Network Insight	Under the Product Properties, select the node size from the drop-down menu. Select the Applicable Time Sync Mode. Under components, enter the vrni platform and vrni collector details. (Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.
VMware Identity Manager	Under the Product Properties, select the certificate from drop-down menu. Select the Admin Password from the locker. Set Default Configuration Admin Username. This will be created as local user in VMware Identity Manager and is used for vRealize Suite Product Integration. Select the password for Default Configuration Admin user. 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. For a cluster deployment, under Cluster Virtual IP enter Cluster VIP FQDN, this is used to load balance the application. 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. Under Components, enter the VMware Identity Manager single or Cluster Node details.

vRealize Automation

To monitor health of vRealize Automation, select the Monitor with vROps check box.
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 cross-product configuration when vRealize Automation is the only product and vRealize Operations Manager is a part of an environment or when vRealize Automation is deployed with Import or New Install of vRealize Operations Manager.

Note: Starting with 8.2 release, when you newly install vRealize Automation, select the Configure internal pods and service subsets checkbox, and then enter the values for K8 Cluster IP Range and K8 Service IP Range.

Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Automation.
Select the Product Certificate from the drop-down menu.
(Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode.
Select the Applicable Time Sync mode.
Select the Time Server (NTP). For more information, see Configure NTP Servers.
If you want to configure cluster virtual IPs, then select the Yes or No options.
(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 database creation, see Create a New Private Cloud Environment Using the Installation Wizard.

vRealize Automation Salt Stack Config

vRA Integrated
Standalone

For vRA Integrated vRealize Automation Salt Stack Config, select the Tenant ID from the drop-down menu under Product Properties.
For vRA Integrated and Standalone vRealize Automation Salt Stack Config, enter the VM name, FQDN and Virtual IP Address under Components.

Note:

For vRealize Automation SaltStack Config vRA-Integrated setup, you can only perform a single node SaltStack Config installation at a time. For vRealize Automation deployment along with SaltStack Config vRA-Integrated, the tenant ID is selected by default. Any additional SaltStack Config deployment can be performed based on the tenant as organic growth.
In the 8.4 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Automation SaltStack Config.

vRealize Business for Cloud

Under Product Properties section, enter the VM Name, Hostname, and IP Address.

vRealize Log Insight

Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Log Insight. It is also supported as a Day-2 operation.

Select the node size from the drop-down menu.
(Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode.
Under Integrated Load Balance Configuration, if you select the Configure Cluster Virtual IPs, enter the FQDN and Virtual IP Address.
To add more node, click ADD NODE.
Select the Applicable Time Sync Mode.
Under components, enter the vRLI primary node details.
(Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.
(Optional) Click Add Components to configure additional settings.
Enter the required fields.

vRealize Operations Manager

Note: In the 8.3 release, Federal Information Processing Standard 140-2 Support (FIPS) is supported for vRealize Log Insight.It is also supported as a Day-2 operation.

Under Product Properties, select the Disable TLS version from the drop-down menu.
(Optional) Select ON or OFF to enable or disable the FIPS Compliance Mode.
Select the Certificate from the drop-down menu.
(Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VMs.
Add the Product Password.
(Optional) Click Integrate with Identity Manager check box.
Select the Applicable Time Sync Mode.
For Continuous Availability (CA) based deployment, under Components, enter the Infrastructure and Network details for Witness Domain.
For Continous Availability (CA) based deployment, enter the Infrastructure and Network details for Fault Domain 1 and Fault Domain 2.
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.
If you want to add remote collectors, click Add Collector Group, and then add the details for the new collector nodes.

vRealize Network Insight

Under the Product Properties, select the node size from the drop-down menu.
Select the Applicable Time Sync Mode.
Under components, enter the vrni platform and vrni collector details.
(Optional) Click Anti-Affinity / Affinity Rule check box to create host rules in the vCenter for the deployed VM's.

VMware Identity Manager

Under the Product Properties, select the certificate from drop-down menu.
Select the Admin Password from the locker.
Set Default Configuration Admin Username. This will be created as local user in VMware Identity Manager and is used for vRealize Suite Product Integration.
Select the password for Default Configuration Admin user.
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.
For a cluster deployment, under Cluster Virtual IP enter Cluster VIP FQDN, this is used to load balance the application.
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.
Under Components, enter the VMware Identity Manager single or Cluster Node details.

Procedure