CM4D System Requirements

This topic includes basic hardware and software recommendations for CM4D products version 25.3 or higher. The specifications outlined here are only intended to be a generic guide to use as a starting point in the planning of your implementation. Your actual system needs for this application installation can vary based on factors, including number of users or activity.

The following hardware/software recommendations apply to systems running ATS CM4D Server or CM4D Client installations. In cases where your system implementation combines one or more server configurations on the same machine, the minimum specifications for the combined system types must be met.

Refer to the General Recommendations section of the topic System Requirements for more generalized prerequisites and other relevant information.

CM4D Database Servers

The Database Server hosts the Database Management System (i.e., SQL Server) for the CM4D databases. The DBMS can be local to the CM4D installation or on a centralized server within the network. All installations of ATS CM4D rely on an external database to store the quality data.

The CM4D Results Database requires the SQL Server Instance Feature - Full-Text and Semantic Extractions for Search. See the topic Results Database for the DBA for details.

Firewall ports for SQL Server: TCP 1433-1434 (default)

CM4D Upload Portal, ATS Security and Configuration Manager and ATS Licensing require individual databases. These databases can be hosted on the same database server used for CM4D.

CM4D Application Servers

The Application Server typically includes the CM4D Server desktop applications and automation services.

Prerequisites

CM4D Clients

The following software and hardware requirements must be met for the machine that will be running a CM4D Client installation. There are two primary ways the Client version of CM4D might be implemented:

• CM4D Client - A local desktop CM4D installation that connects to a centralized database and utilizes components from an Application Server or other shared network resources used by CM4D.
• CM4D Workstation - A self-contained instance of the Client install that has ATS CM4D, ATS Licensing, and the SQL Databases all on the same machine.

CM4D Clients can support a local SQL installation. However, ATS recommends a centralized SQL Instance whenever possible.

CM4D Clients

A CM4D Client has the CM4D Client (CM4D, DataSmith, DataUtility) installed locally, but relies on other supporting applications/services (DBMS, Licensing, etc.) to be running/accessible on servers in the network.

Typical use: Machines on the plant floor running CM4D Interactive or Workcell, connecting to the central server for its database and license. This could also be used for a CM4D Scheduler Client that is utilized by the server to automatically generate reports.

CM4D Workstations

This section includes the requirements for CM4D Workstation clients that will have the CM4D installation, ATS Licensing, and SQL Databases on the same workstation (machine).

Typical use: This configuration is usually the Node-locked CM4D Classic Developer and DataSmith licenses and is used by report template developers and DataSmith translator developers. Generally, this is used when by organizations that do not have the Site Automation package or does not use CM4D widely throughout a large network to need shared databases.

Other use: CM4D Interactive or CM4D Workcell systems.

---

See also:

CM4D Peruse System Requirements

CM4D Upload Portal System Requirements

Can we improve this topic?