# Before Installation

The following preparations have to be made prior to installation of Atlas Copco Data Communication:

- Ensure that the server(s) that are to run Atlas Copco Data Communication meet the hardware and software requirements.

- Ensure that the firewall is configured to allow communication through the required ports.

- Install RabbitMQ and make sure that the setup corresponds to the Atlas Copco Data Communication configuration. Refer to RabbitMQ Prerequisites in RabbitMQ Overview.

Port No | Protocol | Firewall | Description | Configurable
--- | --- | --- | --- | ---
9010, 9011 | TCP | External | Power Focus 4000 | Yes
9012, 9013 | TCP | External | PowerMacs Protocol version 3 | Yes
9014, 9015 | TCP | External | ToolsNet Open Protocol | Yes
9016 | TCP | External | Power Focus 6000 | Yes
9017 | TCP | External | Power Focus 6000 with TLS | Yes
6700 | TCP | External | ToolsNet Data Collection Protocol | Yes
5672 | TCP | Internal | Port used for the internal RabbitMQ broker | Yes
7110 | TCP | External | Web API port used by integrated products, for example ToolsNet Web | Yes
7443 | HTTPS | External | Secure Web API port used by internal and external applications | Yes
7111 | TCP | Internal | Internal Web API port for Atlas Copco Data Communication | Yes
7112 | TCP | Internal | Internal Web API port for Atlas Copco ProtocolServerStore service. | Yes
15672 | TCP | Internal | Internal Web Management port for internal RabbitMQ broker | Yes

Ensure that the database server is installed, properly configured, and running.

## Hard Disks and Data Files

Contact the database administrator to decide the following settings:

1. Ensure that there is enough free hard disk space for Production data.

2. Decide which hard disk volume and folder should be used for Production data.

The SQL server transaction log file grows when delete maintenance is running. This log file is truncated when the database is backed up. The database administrator must have a strategy for keeping a reasonable log file size.