# Configuring the Settings Tab

The Settings tab configures the Atlas Copco Data Communication Service, the Atlas Copco Data Communication WebAPI Services, the Protocol Server Store database, the on-premises database, and the Atlas Copco cloud.

## ACDC

Enables settings for the Atlas Copco Data Communication Service.

Configuring ACDC

1. Verify the General settings.

   The general settings that need to be configured for the service.

2. Verify the Protocol Servers settings.

   The various controllers or tools connected to the service.

3. Verify the Protocol Server Store settings.

   The external service that keeps track of the data consumed and stored within the controller. This is important in the event of a connection failure between the controllers and the Data Communication service.

4. Verify the Internal RabbitMQ settings.

   The settings for the internal communication with the Atlas Copco Data Communication service.

5. If needed, verify the ToolsTalk 2 RabbitMQ settings.

   The connection settings between ToolsTalk 2 and the controllers using RabbitMQ.

6. Review the settings and click Save.

General
Settings | Description
--- | ---
Settings File | The file path to the settings file currently in use.
General Settings | Server IP The IP address that the controllers are connected to. Enable Graph Compression Enables/disables graph value compression in the database. Start Protocol Servers The protocol servers handling the communication between ACDC and the controllers. Select the checkbox to enable the protocol listeners. Start Consumers Enables/disables dispatching messages from the message queue and send them to DB and/or Atlas Copco cloud.
Log Settings | Level Indicates the level of detail in the information to be stored in the log. The available options are: Verbose Debug Information Warning Error Location The target location for the log files.

Protocol Servers
Settings | Description
--- | ---
Protocol Server Ports | The ports used by the specific protocol listeners. The available options are: Px2 Px2 with TLS Power Focus 4000 PIM Power Focus 4000 PowerMACS PIM PowerMACS TNOP PIM TNOP TNDCP TNDCP with TLS Enabling TLS for any protocol requires a certificate to be provided in Security Settings. To use TLS 1.3, Atlas Copco Data Communication WebAPI Services must run on Windows Server 2022 or later.
Enable Protocol Servers | Enable/disable listeners for specific protocols. The available options are: Px2 Px2 with TLS Power Focus 4000 PowerMACS TNOP TNDCP TNDCP with TLS Open Protocol SYS6000 Enabling TLS for any protocol requires a certificate to be provided in Security Settings. To use TLS 1.3, Atlas Copco Data Communication WebAPI Services must run on Windows Server 2022 or later.

Protocol Server Store
Settings | Description
--- | ---
General Settings | Port The port used by the Protocol Server Store. Hostname The host where the Protocol Server Store is installed.
Log Settings | Level Indicates the level of detail in the information to be stored in the log. The available options are: Verbose Debug Information Warning Error Location The file path where the logs are stored.
Database settings | Database Provider The database provider for storing controller data. The available options are: SQL Server Recommended for installation as an on-premise database. Data Source The IP address of the SQL Server. Initial Catalog The name of the SQL Server database. Trust server certificate Default value: False If this checkbox is cleared (default), the SQL Server must use a trusted certificate. If this checkbox is selected, the SQL Server's self-signed certificate is trusted automatically. This is not recommended due to security reasons. SQLite Recommended for any other type of installation. Location The path to where the SQLite database is stored.

Internal RabbitMQ
Settings | Description
--- | ---
General RabbitMQ Settings | Hostname The host where RabbitMQ is installed. Port The port number of the machine connecting RabbitMQ. Username The username used by Atlas Copco Data Communication when connecting to the RabbitMQ broker. Password The password used by Atlas Copco Data Communication when connecting to the RabbitMQ broker.
Internal Queue | Virtual Host The name of the RabbitMQ virtual host used by Atlas Copco Data Communication for internal communication. Management API Port The port used to access the RabbitMQ management plugin UI. Management API Scheme The API scheme used for accessing the RabbitMQ management plugin UI.
Internal Services | Virtual Host The name of the RabbitMQ virtual host used by Atlas Copco Data Communication for communicating with the Protocol Server Store service. Verification Status Verify the connection after adding the configuration settings.

External RabbitMQ
Settings | Description
--- | ---
ToolsTalk 2 RabbitMQ | Enable publishing of messages to ToolsTalk 2 (from release v2.17) via RabbitMQ. RabbitMQ must be installed before you can continue with the settings. For more information how to install RabbitMQ, see RabbitMQ Overview. Exchange Name The name of the RabbitMQ exchange that Atlas Copco Data Communication communicates with. Hostname The hostname of the RabbitMQ broker. The host where RabbitMQ broker is installed. By default, this field is empty which means RabbitMQ publishing is turned off. Specify a value to turn on RabbitMQ publishing. Port The port that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Virtual Host The virtual host name that Atlas Copco Data Communication uses when connecting to the RabbitMQ. It is required to be / if it is not possible to change within ToolsTalk 2 configuration. Default value: ACDC-TT2 Username The username Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Password The password Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. If Atlas Copco Data Communication has already been installed, restart the AtlasCopco_DataCommunication service to activate the settings.
ToolsNet RabbitMQ | Enable publishing of messages to ToolsNet via RabbitMQ. Exchange Name The name of the RabbitMQ exchange that Atlas Copco Data Communication communicates with. Hostname The hostname of the RabbitMQ broker. The host where RabbitMQ broker is installed. By default, this field is empty which means RabbitMQ publishing is turned off. Specify a value to turn on RabbitMQ publishing. Port The port that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Default value: 5672. Virtual Host The virtual host name that Atlas Copco Data Communication uses when connecting to the RabbitMQ. It is required to be / if it is not possible to change within ToolsNet configuration. Default value: ACDC-ToolsNet. Username The username that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker. Password The password that Atlas Copco Data Communication uses when connecting to the RabbitMQ broker.

## Web API

Enables settings for the Atlas Copco Data Communication WebAPI Services to collect data over a web API with an option to host using HTTPS.

Configuring Web API

1. Verify the file path for the Settings File currently in use.

2. In Port Settings, enter the Web API Port number used for hosting the Web API without enabling HTTPS. The default port number is 7110.

3. Verify the Log Settings, if required.

   Log Settings
   Settings | Description
   --- | ---
   Level | Indicates the level of detail in the information to be stored in the log. The available options are: Verbose Debug Information Warning Error
   Location | The file path where the log files are stored.

4. To configure Web API for HTTPS, in Https Settings, ensure that the Enable Https checkbox is selected.

   Enabling HTTPS requires a certificate to be provided in Security Settings. The certificate needs to be setup prior to installing the Atlas Copco Data Communication service. It will not be generated automatically by the service.

5. When using HTTPS, enter the External Web Api Https Port and Internal Web Api Https Port used for hosting Web API. The default Web API HTTPS port values are 7443 for external and 7111 for internal.

## On Premise

Enables the settings for the on-premise database. The service stores the data in a local database.

Configuring On Premise

1. Select the Enable settings for on-prem database checkbox.

2. Select the Database Provider:

   - SQL Server

3. Enter the Data Source. The IP address for an SQL Server.

   If the SQL Server is hosted on the computer running the installation, the IP address is `127.0.0.1.`

4. By default, Initial Catalog shows the name of the database. This value cannot be modified.

5. By default, when the Trust server certificate checkbox is cleared, the SQL Server must use a trusted certificate.

   If this checkbox is selected, the SQL Server's self-signed certificate is trusted automatically. This is not recommended due to security reasons.

## Alture

Enables settings for Atlas Copco cloud.

Configuring Alture

1. Select the checkbox Enable settings for Atlas Copco cloud.

2. Configure the settings accordingly.

Settings | Description
--- | ---
IOT Hub Connection String | The IoT Hub Connection String, provided by Atlas Copco.
IOT Hub Communication Protocol | The protocol used when communicating with the IoT Hub. The available options are: Amqp_WebSocket_Only Amqp
Heartbeat interval | The interval (in seconds) at which Atlas Copco Data Communication should send a message to the IoT Hub to verify that the service is functional.
Proxy Server | The URL for the proxy to use, if a proxy should be used.
Proxy Username | The username for the proxy connection.
Proxy Password | The password for the proxy connection.
Proxy Domain | The domain for the proxy connection.
Maximum Batch Size | Maximum allowed batch size to be used when sending multiple messages together to Azure IOT hub.
Cache To Disk Interval | Cache offload to disk interval (in seconds) for storing Unit information together with Result, Jobresult, Event and Program sequence numbers.

Verify that the ACDC application server supports the minimum TLS version required by the Alture installation. It is recommended to use TLS 1.2 or higher.

## Unify

Settings to configure Unify.

Configuring Unify

1. Select the Enable Unify checkbox and choose between HTTP or HTTPS as the protocol.

2. Enter a valid port number for Unify Management in Unify Backend Port.

3. Select the appropriate License File using CHOOSE FILE.

   When using Flexera licensing, run the Unify License Enabler first to get a valid license file.

4. In CDM Database Settings, enter the IP address for an SQL Server in Data Source.

   Required if On-premise and Unify are enabled.

5. By default, Initial Catalog, shows the name of the database. This value cannot be modified.

6. By default, when the Trust server certificate checkbox is cleared, the SQL Server must use a trusted certificate.

   If this checkbox is selected, the SQL Server's self-signed certificate is trusted automatically. This is not recommended due to security reasons.

7. In Log Settings, set the level of detail in the information to be stored in the log using the Level drop-down menu and the target location of the log files using Location.

   The available levels are:

   - Verbose

   - Debug

   - Information

   - Warning

   - Error

In Publishing Settings, the settings for MQTT and RabbitMQ can be configured. The settings define messages to be published to MQTT or RabbitMQ or both. The prerequisite for this is to set Topics in MQTT and Routing keys in RabbitMQ before configuring and starting the Atlas Copco Data Communication service.

Publishing Settings
Settings | Description
--- | ---
MQTT Settings | MQTT broker must be installed before you can continue with the settings. For more information on how to install an MQTT broker, see MQTT Overview. MQTT Topics are used in the MQTT ecosystem for the broker to determine which clients receive specific messages. Enable Publish To MQTT Select this checkbox to publish data to an MQTT broker. By default, this checkbox is disabled. When enabled, more settings are available: Broker URL The host where the MQTT broker is installed. A URL must be entered to be able to publish messages to MQTT broker. Username Enter the username for MQTT broker authentication. Leave this field blank, if you use the MQTT broker without authentication configured. Password The password for the broker. Leave this field blank, if you use the MQTT broker without authentication configured.
RabbitMQ Settings | RabbitMQ must be installed before you can continue with the settings. For more information how to install RabbitMQ, see RabbitMQ Overview. In RabbitMQ, exchanges are used as routing mediators that decide what messages are sent to a queue, multiple queues or discarded. Queues deliver messages to consumers using a FIFO model. Bindings are used by exchanges to route messages to specific queues. Routing keys in RabbitMQ are attached to exchanges to filter specific messages and route them to the bounded queues. Enable RabbitMQ Publishing: Toggles the RabbitMQ publishing settings to be visible. When enabled, the following setting are available: Exchange Name: The name of the RabbitMQ exchange to use. Hostname: The host where RabbitMQ is installed. (This value must be set if the Enable RabbitMQ Publishing checkbox is checked) Username: The username Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Password: The password Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Virtual Host: The name of the RabbitMQ virtual host. Port: The port Atlas Copco Data Communication is using when connecting to the RabbitMQ broker. Publish Ack Timeout: Time allowed for message acknowledgment (in seconds).
Unify V1 | The Unify version(s) of the messages that should be published. Applies to both MQTT and RabbitMQ publishing. Currently only Unify V1 is supported. The available models are: Tools Controller Result with Trace Events

## Remote Logging

Settings | Description
--- | ---
Elastic Stack | Enable loggging to Elasticsearch: Enables logging to Elasticsearch. Url: Url to Elasticsearch. Username: Username for Elasticsearch. Password: Password for Elasticsearch. Index: Elasticsearch index. The logs are sent to this index.

## Security Settings

1. In Choose Certificate, select a certificate that will be used for TLS and/or HTTPS.

2. Click Verify certificate to validate the selected certificate.

3. In Audit log settings, specify the Location where the logs must be stored. The default location is C:\ProgramData\Atlas Copco\Audit Logs\<service name>\

   Audit logs must be protected and must not be changed. By default, only the software has write access to audit log files. Normal users are blocked from accessing or changing these files.

   Audit logs must be immutable. Default permissions must be retained. Changing file permissions can affect the integrity of audit data. Responsibility for data changes lies with the customer.

   Audit logging is also available through OpenTelemetry (OTEL). OTEL uses the same settings as regular logging. To filter audit logs in OTEL, use: Attributes.LogType: "Audit"

   Audit Logs for Atlas Copco Data Communication Installation Configurator will always be in the default location.

4. After reviewing the settings, click Save and then click Close.