To begin, access the Vertica Admin Console URL. As suggested during the installation process, access should occur over HTTPS on port 5450 (for example, https://172.17.13.195:5450). Upon successful access, you will be presented with a license agreement, which needs to be accepted.
After accepting the user license and clicking Next, you will be presented with a screen where you will need to specify the following fields:
|
Field |
Description |
|---|---|
|
Username |
A valid operating system user is expected.It is recommended to use Vertica’s standard “dbadmin” user account for Admin Console access. |
|
Password and Confirmation of Password |
A password for accessing the Admin Console. |
|
Unix Group ID |
The operating system level group id for the username specified above.The group id may be obtained using the following command, from a desired node:id -g <username> |
|
Home Directory |
The operating system level home directory for the user mentioned above. |
|
License Directory |
The operating system level directory where the Admin Console’s license will be maintained. |
|
Management Console Port |
The operating system level port on which the Admin Console will be accessible.The default value is 5450, however if this value is changed then you need to ensure that the new port is accessible over the Enterprise’s firewall, for HTTPS access. |
Upon clicking Next, you will be presented with a screen where you will need to specify the following fields:
|
Field |
Description |
|---|---|
|
Catalog Path |
A catalog is a set of files that contains information (metadata) about the objects in a database, such as the nodes, tables, constraints, and projections.This field specifies the file system directory where the catalog will be stored. The home directory of the username specified above is the default value for this field. |
|
Data Path |
This field specifies the file system directory where the data files will be stored.The home directory of the username specified above is the default value for this field. |
Upon clicking Next, you will be presented with a screen where you will need to choose an authentication method for the Admin Console. Choose from: Management Console's internal authentication or Lightweight Directory Access Protocol (LDAP).
After making your selection, you will be presented with a confirmation dialog.
Once the server startup process is complete, you will be presented with the Vertica Admin Console's login screen.
On this screen, enter the username and password that you specified during the initial steps. Then click Log In.
After successful login, click the Import a Vertica Database Cluster option on the presented screen. Upon doing so, you will be presented with a screen where you will need to enter the IP Address of the Sagacity ComputeDB primary Node or the primary Vertica instance's host.
After entering the IP address of the Sagacity ComputeDB Node or the primary Vertica instance's host and clicking Next, you will be presented with a screen where you need to enter the API Key that was generated on the Vertica Admin Console host. The API Key can be obtained by executing the following command on the Vertica Admin Console host instance's terminal:
cat /opt/vertica/config/apikeys.dat | grep "apikey"
Upon entering the API Key successfully and clicking Continue, you will be presented with a screen where you need to enter the username and password that has been setup for accessing Vertica. The values for these fields can be found in Sagacity’s standard install.properties file at the VERTICA_DB_USER and VERTICA_DB_PASSWORD properties, respectively.
After entering the requested credentials, click Import. If the import operation is successful, then you will be presented with a confirmation dialog.
To complete the setup process, click Done on this screen.