Working with vRealize Suite Lifecycle
Manager
When mode is
enabled in , the
behavior of is
aligned with the
architecture.
introduces
the following features:
- Automatic load balancer configuration. Load balancer preparation and configuration are no longer a prerequisite when you use to deploy or perform a cluster expansion on , , or . Load balancer preparation and configuration take place as part of the deploy or expand operation.
- Automatic infrastructure selection in ’s deployment wizards. When you deploy a vRealize Suite product through , infrastructure objects such as clusters and networks are pre-populated. They are fixed and cannot be changed to ensure alignment with the architecture.
- Cluster deployment for a new environment. You can deploy , , or in clusters. You can deploy either as a cluster or a single node. If you deploy as a single node, you can expand it to a cluster later.
- Consistent Bill Of Materials (BOM). only displays product versions that are compatible with to ensure product interoperability.
- Inventory synchronization between and . can detect changes made to vRealize Suite products and update its inventory through inventory synchronization. When mode is enabled in , inventory synchronization in also updates ’s inventory to get in sync with the current state of the system.
- Product versions. You can only access the versions for the selected vRealize products that are specifically supported by itself.
- Resource pool and advanced properties. The resources in the Resource Pools under the Infrastructure Details are blocked by the UI, so that the topology does not change. Similarly, the Advanced Properties are also blocked for all products except for Remote Collectors. also auto-populates infrastructure and network properties by calling deployment API.
- Federal Information Processing Standard (FIPS) compliance.
- Watermark.