You can configure the infrastructure details when you create an environment.


If the selected data center does not have a vCenter Server associated with it, then you must add a vCenter Server.


  1. Select a vCenter Server from the drop-down menu.
    Note: There should be at least one vCenter Server associated with a data center.
  2. Select a Cluster.
  3. When you click Select a Folder, all the folders that are associated in the vCenter Server are listed.
    If the folders are not displayed, then refresh the vCenter data collection from the vRealize Suite Lifecycle Manager settings page.
  4. To deploy your VM, click Select a Resource Pool.
    All the resource pools that are associated with the selected cluster are listed.
    Note: You can select a resource pool to deploy your VM. Both folder and resource pool selection are optional. If you do not specify any resource pool, the VM is deployed in the root default resource pool of the selected cluster. If you do not specify the folder details for both vCenter Server and resource pool, the deployment of the VM is saved in the root default VM folder of the data center inside the vCenter .
  5. Select the required Network, DataStore, and Disk Disk Mode.
    Note: vRealize Operations Manager deployment fails when you provide incorrect infrastructure details such as wrong DNS or gateway details without running a pre-check while you create an environment flow. If the deployment fails, you might not see the correct cause of deployment failure using the error or code message that appears in vRealize Suite Lifecycle Manager UI, and you cannot proceed further with that deployment. As a result, you might have to delete the Environment card from vRealize Suite Lifecycle Manager with all the products or nodes that were deployed as part of that environment. You can run Pre-check so that the Infrastructure-related issues are detected and can be corrected before triggering the deployment.
  6. With Lifecycle Manager 8.0, to integrate with VMware Identity Manager, select Integrate with Identity Manager toggle button.
    Note: The default configuration admin given while installing VMware Identity Manager (global environment) will be made the admin for the product as well while integrating with VMware Identity Manager.

    VMware Identity Manager acts as an identity provider and manages SSO for the vRealize Suite products and vRealize Suite Lifecycle Manager when integrated with vRealize Suite Lifecycle Manager. SSO provides a single set of credentials to access all vRealize Suite applications and vRealize Suite Lifecycle Manager. With SSO, you are only required to log in once, and then you can seamlessly access all vRealize Suite applications.

  7. Select the Use Content Library to use OVFs hosted on vCenter's Content Library, if there is a network latency from vRealize Suite Lifecycle Manager to vCenter server
    Copying OVF and VMDK files for deployment from vRealize Suite Lifecycle Manager to vCenter Server might take more time and lead to a deployment failure if there is a Network latency from vRealize Suite Lifecycle Manager to target vCenter Server. Content Libraries in vCenter can be used to host OVFs and the same can be used from vRealize Suite Lifecycle Manager to deploy products. You can perform the steps before you trigger a vCenter Inventory Sync in vRealize Suite Lifecycle Manager:

    vRealize Suite Lifecycle Manager supports deployment only from Publisher or Local Content Libraries.

  8. To configure the Binary Mapping, click Next.