Skip to content

Before Installation

The installation of Data Touch consists of 10 key steps. For a successful installation, each step must be completed in the correct order.

Note

Ensure the Dataskope DAM is installed and configured before proceeding with the installation of Data Touch. Data Touch needs to be able to communicate with the DAM and Elasticsearch to function properly.

The steps are outlined below.

1. Docker Installation
2. Extracting Packages
3. Loading Docker Images
4. Init Configuration
5. Hostname Configuration
6. Dataskope Configuration
7. Metadata Configuration
8. HTTPS Configuration (Optional)
9. Deployment
10. Monitoring

Supported Browser Versions

  1. Google Chrome

    • Latest Version: 140.0.7339.207
    • Previous Versions: 139.0.7258.154, 138.0.7204.183, 137.0.7151.119

  2. Mozilla Firefox

    • Latest Version: 144.0
    • Previous Versions: 143.0, 142.0, 141.0

  3. Microsoft Edge

    • Latest Version: 142.0.3595.53
    • Previous Versions: 141.0.3537.99, 140.0.3485.130, 139.0.3405.125

  4. Safari (macOS)

    • Latest Version: 26.1
    • Previous Versions: 18.6, 17.6, 16.6

System Requirements

For optimal performance, the hardware requirements vary based on the deployment type (PoC or Production) and the scale of your database, table, and event counts. Below are the minimum system requirements:

Select a configuration to view details

  • CPUs: 8
  • Memory: 16 GiB
  • Disk: 100 GiB
  • Use Case: POC, and small-scale setups
  • CPUs: 16
  • Memory: 64 GiB
  • Disk: 500 GB SSD or NVME Storage
  • Use Case: Production deployments

Note

The actual hardware requirements may vary depending on the size of your database, the number of tables, and the volume of events being processed.

Network Requirements

Data Touch is a web application that operates both at the backend and frontend. We utilize Nginx as a reverse proxy to manage traffic to our applications, including those running in Docker containers.

Ports Required

  • HTTP: 80
  • HTTPS: 443
  • SSH: 22

Integration Ports

Data Touch needs to communicate with various services. Below is a table of the required ports:

Service Purpose Required Ports
Dataskope DAM Authentication and data fetching 8443, 9200
Data Focus Metadata Service 80, 443
SDM Metadata Service 8080, 8443

Port Configuration Note

These ports are configurable during the installation phase. Please confirm port availability before starting and ensure that these ports are open and properly configured to allow seamless communication between services and the application.

Storage Specifications

Volume Requirements

For all deployments, we need two dedicated volumes on the host:

Mount Path Purpose Recommended Allocation
/datatouch Application data storage 40% of total storage
/var/lib/docker Docker storage 40% of total storage
Unallocated Reserved for future use 20% of total storage

These volumes must be dedicated to the OS, Docker, and application operations. This configuration ensures that even if the VM fails to boot, you can continue operations on a new VM by mounting these volumes.

Note

The recommended configuration ensures optimal performance and scalability for your applications.

Production-Specific Requirements

Additional Requirements for Production Deployments

If you're deploying Data Focus in a production environment, please review and implement the following additional requirements

Virtual Infrastructure Settings

Virtualization Configuration

Resource Allocation:

  • CPU Overcommit: Maximum 2:1 ratio (recommended 1.5:1)
  • Memory Overcommit: Disabled or maximum 1.2:1 ratio
  • Vertical Scaling: Ensure resource allocation supports vertical scaling capabilities
  • Resource Reservation: Reserve minimum required CPU and memory

Backup and Snapshot Strategy

Data Protection Requirements

Mount Disk Snapshots:

  • Both /datatouch and /var/lib/docker volumes must be snapshot-capable
  • Pre-deployment snapshots: Mandatory before any updates
  • Regular snapshots: Daily incremental, weekly full snapshots
  • Retention policy: Minimum 14 days for production data
  • Recovery testing: Verify snapshot restore procedures regularly

Security and Network Hardening

Production Security

  • HTTPS Configuration: Mandatory for production
  • SSL Certificates: Use valid certificates (avoid self-signed)
  • Firewall Rules: Restrict access to required ports only
  • Network Security: Implement proper network segmentation