Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
Arctera Insight Information Governance Installation Guide
- Understanding the Arctera Insight Information Governance architecture
- About Arctera Insight Information Governance
- About the Management Server
- About the Collector worker node
- About the Indexer worker node
- About the Classification worker node
- About the Self-Service Portal node
- About Communication Service
- About the DataInsightWatchdog service
- About the DataInsightWorkflow service
- About Arctera Insight Information Governance installation tiers
- Preinstallation
- Installing Arctera Insight Information Governance
- About installing Arctera Insight Information Governance
- 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 Classification Server or Collector worker node
- Installing Arctera Insight Information Governance in Azure Cloud Environment
- Installing Arctera Insight Information Governance in AWS Cloud Environment
- Upgrading Arctera Insight Information Governance
- Post-installation configuration
- Installing Windows File Server agent
- Getting started with Information Governance
- Uninstalling Arctera Insight Information Governance
- Appendix A. Installing Information Governance using response files
About Communication Service
Each node in a Information Governance deployment runs a process called Communication Service. This service is responsible for all inter-node communication. Communication Service uses Secure Sockets Layer (SSL) to secure communication between the Information Governance nodes. The SSL keys are generated during installation.
By default, Communication Service connects through sever port 8383. This port must be visible to bi-directional HTTPS traffic between all Information Governance nodes. The service is also responsible for scheduling various tasks on a Information Governance node, which include, scheduling file system scans and uploading files to the Indexer worker node.