4.2 Procedure to Configure Vertica on a Single Server

A summary of the steps to be followed to configure Vertica on a single server is provided in this section. For more information on each of the steps, click the links specified within each step. To test the feature, it is recommended that you follow this procedure first before adding more servers to the Vertica clusters.

As Kafka requires client authentication to be enabled in the certificate, if you are using an external CA certificate, ensure that client authentication is enabled.

NOTE:ZooKeeper should by default be enabled on your first Primary Server. If you want to add more servers to the ZooKeeper cluster, then see Adding Servers to the Vertica, Kafka and ZooKeeper Cluster. To verify whether the ZooKeeper service is up and running, navigate to ZCC and monitor the status in the Diagnostics page.

If you are enabling Kafka for the first time in the zone, then you can either use the ZMAN utility or ZCC. For more information on enabling Kafka, see Kafka Reference Guide.
Enable Vertica in the zone by executing the following command and specify the GUID, DNS, or path of the Appliance server, and the K factor.
```
zman server-role-vertica-create-cluster (zman srvcc)
```
For more information, see Enabling Vertica.

If Vertica cluster configuration fails, then check the logs on the server on which Vertica is to be enabled as detailed in the section Vertica.

NOTE:If you are planning to create a multi-node cluster, then ensure that you update the K factor to 1 or more.

When the replication factor is 0 for a multi-cluster node, the data recovery cannot be performed. Hence, ensure that you update the K factor to 1 or more while creating the multi-cluster node.

For more information on updating the K factor, see Updating the K Factor.
Restart the ZENserver and ZENloader services on all the Primary Servers.
View the status of Vertica configuration in ZCC, by navigating to Configuration > Performance Upgrade. To continuously monitor the status of Vertica and its nodes, navigate to the Diagnostics page in ZCC. For more information, see Monitoring the Status of Vertica, Kafka and ZooKeeper.
Run the Configure action to calibrate memory requirements for the Vertica and Kafka components. To run the action:
1. In the command line utility of the Appliance server on which Vertica and Kafka are enabled, execute the following command:
```
microfocus-zenworks-configure -c CalibrateMemoryConfigureAction
```
2. A message is displayed informing the user that the ZENworks services will automatically restart on the server after the Configure action is run. If you want to proceed with the memory calibration, then press enter to specify the default value as 1 or else enter the value 2.
3. Login as a dbadmin user by running the following command: su dbadmin
4. Run the following commands to restart the Vertica database:
  1. $ /opt/vertica/bin/admintools -t stop_db -d zenworks -p <password> -F
  2. $ /opt/vertica/bin/admintools -t start_db -d zenworks -p <password>
    
    You can obtain the password by running the command zman server-role-vertica-get-credentials (zman srvgc)and you need to use the database superuser password to stop and start the Vertica database.
For more information, see Managing Vertica Memory Requirements.
Export data in bulk to the configured tables in Vertica from the existing RDBMS, by running the following Configure action on one of the servers in which Vertica is enabled:
```
microfocus-zenworks-configure -c VerticaDBMigrate -Doption=start
```
For more information, see Migrating Data to Vertica.

After bulk data migration, the Change Data Capture process automatically syncs modified or newly added data from the RDBMS to Vertica at an interval of every 10 to 15 minutes.

You can now proceed to add more servers to the ZooKeeper, Kafka, or Vertica clusters. For more information, see Adding Servers to the Vertica, Kafka and ZooKeeper Cluster.