Before you set up the secondary data center, configure the primary data center for Elasticsearch replication across clusters.

Elasticsearch, a search and analytics engine embedded in the VMware Identity Manager virtual appliance, is used for auditing, reports, and directory sync logs.

Make these changes in all the nodes in the primary data center cluster.

Prerequisites

You have set up a VMware Identity Manager cluster in the primary data center.

Procedure

  1. Add the load balancer FQDN of the secondary data center cluster to the /usr/local/horizon/conf/runtime-config.properties file of each node in the primary data center cluster.
    1. Edit the /usr/local/horizon/conf/runtime-config.properties file.

      vi /usr/local/horizon/conf/runtime-config.properties

    2. Add this line to the file:

      analytics.replication.peers=https://LB_FQDN_of_second_cluster

  2. Restart the VMware Identity Manager service on all the nodes.

    service horizon-workspace restart

  3. Verify that the cluster is set up correctly by running the following command on all the nodes in the cluster.

    curl 'http://localhost:9200/_cluster/health?pretty'

    The command, which verifies Elasticsearch health, should return a result similar to the following.

    {
      "cluster_name" : "horizon",
      "status" : "green",
      "timed_out" : false,
      "number_of_nodes" : 3,
      "number_of_data_nodes" : 3,
      "active_primary_shards" : 20,
      "active_shards" : 40,
      "relocating_shards" : 0,
      "initializing_shards" : 0,
      "unassigned_shards" : 0,
      "delayed_unassigned_shards" : 0,
      "number_of_pending_tasks" : 0,
      "number_of_in_flight_fetch" : 0
    }

What to do next

Verify that the cluster in the primary data center is set up correctly by viewing the Systems Diagnostics dashboard.