5.3 Using the Scripts in Single-node Deployments

Applies only when your deployment does not need high availability

The installation scripts automatically take care of all the prerequisites, software installations, and post-installation configurations. For deployments with a small workload, the script sets the appropriate configuration settings for Vertica. For medium and large workloads, you must manually adjust the configuration settings after the installation is complete.

IMPORTANT:For Identity Intelligence 1.1.1 and later, the scripts disable plain text communication between Transformation Hub (Kafka) and all the components outside the Kubernetes cluster, such as Identity Governance, Identity Manager Driver for Entity Data Model, Vertica, and so on.

Therefore, ensure to configure SSL between Transformation Hub (Kafka) and the components that are outside the Kubernetes cluster. The scripts automatically configures SSL for Vertica as Vertica is installed as part of the script.

To install Identity Intelligence by using scripts:

  1. Log in to the master node as root.

  2. Change to the directory where you downloaded the Identity Intelligence installer files.

    cd /opt

    For information about downloading the Identity Intelligence installer files, see Downloading Identity Intelligence.

  3. Execute the scripts in the following order:

    1. ./prepare-install-single-node-host.sh

    2. ./install-single-node.sh

    3. ./install-single-node-post.sh

  4. (Conditional) For deployments with medium and large workloads, complete the following steps to modify the Vertica resource pool settings:

    1. Log in to the Vertica node.

    2. Change to the following directory:

      cd /opt/arcsight-vertica/scripts

    3. Execute the following command with the appropriate values:

      tuning_util.sh <parameter_1> <value> <parameter_2> <value>

      For example:

      tuning_util.sh -m 2048 -c 3 -x 4

      To see a list of tuning parameters, use the following command:

      tuning_util.sh -h

      For more information about the tuning values for your deployment, see Hardware Requirements and Tuning Guidelines.

  5. (Conditional) By default, Vertica is installed with community edition. If you want to upgrade to enterprise edition, perform steps in the Installing the License for Vertica.

  6. (Conditional) If you want to use mutual SSL authentication between Transformation Hub and its clients, perform steps in the Enabling Client Authentication section.

  7. Continue with Configuring Data Collection.