The CM4D Server Installation includes the core CM4D products, automation, scheduled reporting, alarm notification, web reporting, and database user privileges. This type of installation is installed on a network Server and licensed with a Named Server License. The Server installer is used for network application servers that host the services, applications, and/or databases that will be accessed from Client machines throughout the network. It includes the core CM4D products, Database Utilities and the services: DataSmith Batch, CM4D Scheduler and EventSmith. The Server installation is also used in conjunction with the CM4D Results Services and the CM4D web application installations (Peruse, Upload Portal, Web), but these can be installed on a different server. The CM4D Server install is typically used by large networks running Automation services, with multiple Clients connecting to the server for database access, document storage, and ATS licensing.

CM4D Server Installations require a Named (Node Locked) Server license to run the CM4D Scheduler, CM4D Launcher and DataSmith Batch services. This license is requested automatically on the ATS Licensing Server when any of those services attempt to start for the first time.

The CM4D Client Installation includes the core CM4D products without the automation services. This type of installation is typically installed on a non-server machine and licensed as either a Concurrent or Named License. The Client installer is used for either a standalone workstation or a server client system that will connect to a database or automation server on the network. It includes the core CM4D products - Classic (also Interactive and Workcell), DataSmith, DataUtility, DbConnect, and SiteManager. 

There are two different configurations in which the same Client install of ATS CM4D is used:

• Server Client - A local CM4D installation that connects to a network Server for access to the CM4D Site database and ATS Licensing. This configuration is typically used for 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.
• Workstation - A self-contained instance of the Client install that has ATS CM4D, ATS Licensing, and the CM4D database all on the same machine. Generally, this is used by organizations that do not have the Site Automation package or does not use CM4D widely throughout a large network to need shared databases. This configuration typically used by CM4D Classic report template developers and DataSmith translator developers using Node-locked CM4D Classic Developer and DataSmith licenses.

The Results services are the central mechanism that transfers data from CM4D into the Results database.

• Results Sender - Processes the data events from CM4D, extracts the data from the databases and sends the data to Results Loader. In the case of a modified CAD image, a message is sent to the StreamCacheSmith service. This service requires a connection to the CM4D Site database and the Transport/Persistence database(s).
• Results Loader - Updates the Results database with minimum database locks. This service requires a connection to the CM4D Results database and the Transport/Persistence database(s).
• StreamCacheSmith - Converts 3D CAD images into the HOOPS streaming format used over the web by CM4D Peruse. The stream cache images are stored in the Site database and streamed to clients as-needed for rendering on the client-side HOOPS Viewer. This service requires a connection to the CM4D Results database and the Transport/Persistence database(s) and must be installed on the same machine as the HOOPS Communicator Server.

These services are installed using the ATS CM4D Results Services installer, which provides deployment flexibility to add service instances in larger organizations.

See the topic Results Transport for technical details on how these services can be distributed and monitored for optimal performance.

The Results services are typically installed on the same machine as CM4D Server, but the Results services are a separate installer from CM4D Server to allow one or more of the services to be distributed to additional servers. To support scalability for larger organizations the services can run on a single computer or multiple computers, and multiple instances of each service can be added and distributed throughout your network.

Only ONE instance of each of the three Results Services is supported per server.

The Results services can be deployed as Windows services (default install option) or as docker images.

The Results loader service can work without any connection to the Site database (e.g. in the cloud connected via a RabbitMQ queue). The connection is entered during the installation of the service.