Version 24.2.9039

• System Requirements
  • .NET
  • Cross-Platform Edition
  • Internet Connection
• Supported Web Browsers
• Clustering
• DMZ Gateway
• Separate API Endpoints
• Security Best Practices

CData Arc is available in both a .NET and Java edition. The Java edition provides cross-platform support including Linux and Mac. Both editions come with an embedded Web server, but can also be deployed to other Web servers for their respective platforms.

System Requirements

Your machine must meet the minimum system requirements listed below to run Arc.

.NET

• Windows 10/Windows Server 2016 or higher.
• .NET Framework 4.5 or higher.
• 1 GB RAM recommended (2+ GB recommended for higher volumes of traffic).
• Adequate free disk space for transmission logging and writing received files. Use of an HDD drive is not recommended except for low volumes of activity.

Note: Arc functions on earlier versions of Windows, but Windows operating systems that have reached end-of-life might have limited support.

Cross-Platform Edition

• Java 11 or later is required.
• 1 GB RAM recommended (2+ GB recommended for higher volumes of traffic).
• Adequate free disk space for transmission logging and writing received files. Use of an HDD drive is not recommended except for low volumes of activity.

Internet Connection

If the application must connect with external systems, you might need the following resources:

• A persistent Internet connection.
• An external IP address for the system running the application.
• Firewall/proxy access to communicate with the external system.

Supported Web Browsers

The Arc web UI is accessed through a web browser. Arc supports the following browsers:

• Google Chrome
• Mozilla Firefox
• Safari
• Microsoft Edge

Other browsers might not support all Arc features. As a result, CData strongly recommends using a browser from the list above.

Clustering

The Clustering topic describes how to set up multiple instances of Arc to process the same data and use the same configuration. This allows for a load-balanced or high-availability setup.

DMZ Gateway

The DMZ Gateway topic explains how Arc can receive secure connections through a DMZ gateway via the use of an SSH reverse tunnel. This prevents the need to expose your internal network to outside traffic.

Separate API Endpoints

The Separate API Endpoints topic explains how Arc can host public receiving endpoints on different ports than the main administration console. This adds a layer of security redundancy to prevent external parties from gaining access to the administration console.

Security Best Practices

For information on security-related features available in Arc, and to learn about the best practices we recommend you follow, see Security Best Practices in the Administration documentation.