Skip to content

Install VMware Identity Manager (vIDM) using vRealize Lifecycle Manager (vRLCM)

This entry is part 3 of 4 in the series Install vRealize Automation 8 using vRLCM

This blog post is part of the Install vRealize Automation 8 using vRLCM series and focuses on the install of VMware Identity Manager (vIDM).

vRA8 simplifies the application stack versus vRA7 by doing away with the Windows IaaS components in place of a self contained appliance. While this is true it does add it's own complexity.

vIDM (VMware Identity Manager) is embedded in vRA 7 appliance, which when vRA is clustered automatically clusters vIDM.

In vRA8 it is a separate appliance. There is no point clustering vRA8 appliances and leaving vIDM as a single appliance so this should also be clustered. To do so is where the extra complication comes in. Multiple vIDM appliances must be configured with a load balancer in front.
I started off installing vRLCM 8.0 but part way through upgraded it to vRLCM 8.1. You may notice some differences in the screenshots but the process remains the same for both versions.

Check out the vRLCM 8.0 release notes, especially the known issues which details the removal of a file otherwise services may not start post reboot.

Check out the vRLCM 8.1 release notes too. One of the benefits of vRLCM 8.1 over 8.0 is the ability to change the vRLCM certificate in the GUI. Despite VMware's vRLCM 8.1 docs detailing the old method.
Documentation for vIDM is lacking and contradictory. Especially around clustering, load balancing and internal vs external database.

I have therefore listed some useful vIDM documentation below:
Firstly a vIDM cluster using embedded postgres can be used. In addition the "vRealize Automation 8.1 Load Balancing" document for NSX is mainly correct (SSL Passthrough etc), however...

  • Service Monitor > Receive value should be "ok" (case sensitive)
  • Pool > (each) Member > Monitor Port value should be "443" not "8008"
  • vIDM Install

    Estimated Time: 30 minutes.

    This post provides the step by step instructions needed to install VMware Identity Manager (vIDM) because this is required for vRA.

    1. Load Balancer

      Firstly setup your load balancer of choice according to the documentation. Initially make sure only the first node is enabled. Most importantly disable service/healthcheck monitoring until installation is complete.

    2. Create Environment

      Navigate to Lifecycle Operations > Create Environment to kick off the vIDM install. Provide an email address, select the Datacenter and setup a Default password.

    3. Select Product

      Select “New Install”, version and “Cluster” as deployment type.

    4. EULA

      After that accept the EULA so you can continue.

    5. Certificate

      Select the certificate generated for vIDM from the available list.

    6. Infrastructure

      Select required values for each option, vCenter for instance. This is so vCenter can deploy the vIDM VMs.

    7. Network

      Provide required values for each option, Default Gateway for instance.

    8. Products

      Provide required values for each option, Sync Group Members for instance. This section details the hostname and IP information for each node along with the cluster configuration.

    9. Run Precheck

      Run a check of all settings and selected values.

    10. Manual Validations

      Manually confirm the below actions because vRLCM doesn’t.

    11. Precheck Success

      Everything should certainly come back successful.

    12. Summary

      Finally check all details are correct and then proceed with install.

    13. Complete

      In conclusion you will see vIDM installed as the “globalenvironment”.

    Series Navigation<< Configure vRealize Lifecycle Manager (vRLCM)Install vRealize Automation (vRA) using vRealize Lifecycle Manager (vRLCM) >>
    Published invRealize Automation

    Be First to Comment

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.