Veritas Data Insight Installation Guide
- Understanding the Veritas Data Insight architecture
- About Veritas Data Insight
- About the Management Server
- About the Collector worker node
- About the Indexer worker node
- About the Classification Server
- About the Self-Service Portal node
- About Communication Service
- About the DataInsightWatchdog service
- About the DataInsightWorkflow service
- About Veritas Data Insight installation tiers
- Preinstallation
- Installing Veritas Data Insight
- About installing Veritas Data Insight
- Federal Information Processing Standards (FIPS)
- Performing a single-tier installation
- Performing a two-tier installation
- Performing a three-tier installation
- Installing the Management Server
- Installing the worker node
- Installing the Classification Server
- Installing the Self-Service Portal
- Installing a Linux Indexer worker node
- Installing Veritas Data Insight in Azure Cloud Environment
- Installing Veritas Data Insight in AWS Cloud Environment
- Upgrading Veritas Data Insight
- Post-installation configuration
- Installing Windows File Server agent
- Getting started with Data Insight
- Uninstalling Veritas Data Insight
- Appendix A. Installing Data Insight using response files
About SSL client/server certificates
Veritas Data Insight secures all data flowing between the Management Server and the Worker nodes using the Secure Socket Layer/Transport Layer Security (SSL/TLS) protocol. The SSL/TLS protocol not only encrypts the data that is transmitted, Veritas Data Insight also uses it for mutual authentication between servers.
Data Insight implements authentication with the mandatory use of client and server-side certificates or keys. Connections between the Data Insight servers use a single, self-signed certificate. The Management Server generates the certificate at install time and is unique to your deployment. It is present on the Management Server node in the keys folder under the data folder. The file is called commd.keystore. When you configure worker nodes, this file must be manually copied over to the new worker node before installation.