A global environment is created after an installation or a migration of vRealize Suite Lifecycle Manager. A global environment displays the VMware Identity Manager instance and also shows the version. When you click the View Details on a created environment, you can view the lists of primary, secondary, and connector information of the VMware Identity Manager that is used in the vRealize Suite Lifecycle Manager. You can view the product properties for each the VMware Identity Manager cluster. To view the list of inter-product configurations, click the Product References.

After an upgrade, all products currently integrated with global environment VMware Identity Manager are shown in the list. The global environment VMware Identity Manager View Details page contains the day-2 operations:
  • Topology - The Topology Viewer is introduced to help you view the group and node structure, vCenter, and product integration details between VMware Identity Manager and vRealize Suite products.
  • Trigger Cluster Health - Triggers instant health check on the VMware Identity Manager cluster nodes and provides a notification on vRealize Suite Lifecycle Manager UI.

    Based on the health status of the cluster nodes, 'vIDM vPostgres Cluster Health' notification is either marked CRITICAL or OK. For the notification to be precise, verify that VMware Identity Manager can communicate to all the VMware Identity Manager nodes in the cluster and the global environment VMware Identity Manager inventory is up-to-date in vRealize Suite Lifecycle Manager.

    The health check includes postgres service status check, pgpool service (responsible for automatic failover) status check and Delegate IP (database load balancer IP) availability check apart from basic the VMware Identity Manager service availability checks.

    If status is marked CRITICAL, to troubleshoot, a link to the KB article 75080 is provided. This health check also runs every hour as a scheduled job at the backend and latest health statuses are updated in the 'vIDM vPostgres Cluster Health' notification.

    If VMware Identity Manager is clustered through vRealize Suite Lifecycle Manager, then the Power ON option can also be used to remediate the critical cluster heath.

  • Power ON - Turns up the VMware Identity Manager nodes and ensures all the required services are bootstrapped. For a clustered instance (vRealize Suite Lifecycle Manager clustered VMware Identity Manager), this operation fixes any inconsistency in the cluster. For example, fixing the Delegate IP (database load balancer IP), correcting any replication delays in the secondary nodes. If VMware Identity Manager is clustered through vRealize Suite Lifecycle Manager, then use this option for any use case which involves powering on the cluster like snapshot revert, reboot, power on.
    Note: When performing the Power ON operation, if you select the Reboot vIDM nodes checkbox, the reboot will be performed as a part of the remediation, if required. If you choose to disable the checkbox, the request fails if reboot is required to remediate the cluster, which is performed by providing consent in the retry parameters.
  • Power OFF - Brings down all the VMware Identity Manager services by shutting them down and also brings down the services that are responsible for an automatic failover, and its related components in a clustered deployment. This option is provided for both single node and clustered node VMware Identity Manager.

    If VMware Identity Manager is clustered through vRealize Suite Lifecycle Manager, then it is always recommended to use this option for a scenario which involves bringing down the cluster, such as reboot and shut down. Creating VMware Identity Manager snapshot through vRealize Suite Lifecycle Manager stores the snapshot after bringing down the VMware Identity Manager services gracefully.

    Note: A change in VMware Identity Manager certificate requires retrust of VMware Identity Managercertificate on all products or services currently integrated with it. While updating certificate, you can select all currently referenced products to opt in for retrust. For more information on product references, see Product References. To know more about the hardware requirements depending on the number of users in the directory, see System and Network Configurations Requirements.