Page History
Sv translation | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
Before you beginPlease read the following important notes before you begin installing BellaDati IoT Data Collector:
StepsBelow are the steps in short:
In the next chapters, each step is described in detail. 1. Get IoT Data CollectorManual installation is based on running particular modules as Java programs, thus you need the IoT Data Collector JAR distribution. You can visit BellaDati Download Page for information about the current version and fordownloading instructions. Once you have downloaded the the JAR distribution archive, you can unzip it's content, which should contain (see Files and directories to get more details about the content):
2. Obtain server-IDAudit module is distributed as iot-collector-audit-x.y.z.jar file. You can start it by executing the following command:
This command will start the audit with the default configuration of the cluster and audit. If necessary, it is also possible to manually specify these files:
When you start the Audit module for the first time, it automatically creates file server-id.txt in your installation directory. 3. Obtain license keyOnce you have the server-ID, you can request the license key from BellaDati support, either by creating request in our Help desk, or by contacting our support at support@belladati.com. 4. Configure Audit moduleEach module configuration is container in appropriate conf.json file. Default filename for Audit module configuration is confg-audit.json, however the name can be changed and then just reflected when starting the module. The default configuration is sufficient, unless you are deploying HA or multi-server IoT Data Collector instance. The only field you need to change is "license" (there are two "license" field, update both).
For complete configuration example, click below.
5. Configure other modules6. Start collector modulesWhen all configuration is set, you can proceed to starting all modules. The first module to be started is always Audit.
|
Sv translation | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
Before you beginPlease read the following important notes before you begin installing BellaDati IoT Data Collector:
StepsBelow are the steps in short:
In the next chapters, each step is described in detail. 1. Get IoT Data CollectorManual installation is based on running particular modules as Java programs, thus you need the IoT Data Collector JAR distribution. You can visit BellaDati Download Page for information about the current version and fordownloading instructions. Once you have downloaded the the JAR distribution archive, you can unzip it's content, which should contain (see Files and directories to get more details about the content):
2. Obtain server-IDAudit module is distributed as iot-collector-audit-x.y.z.jar file. You can start it by executing the following command:
This command will start the audit with the default configuration of the cluster and audit. If necessary, it is also possible to manually specify these files:
When you start the Audit module for the first time, it automatically creates file server-id.txt in your installation directory. 3. Obtain license keyOnce you have the server-ID, you can request the license key from BellaDati support, either by creating request in our Help desk, or by contacting our support at support@belladati.com. 4. Configure Audit moduleEach module configuration is container in appropriate conf.json file. Default filename for Audit module configuration is confg-audit.json, however the name can be changed and then just reflected when starting the module. The default configuration is sufficient, unless you are deploying HA or multi-server IoT Data Collector instance. The only field you need to change is "license" (there are two "license" field, update both).
For complete configuration example, click below.
5. Configure other modules6. Start collector modulesWhen all configuration is set, you can proceed to starting all modules. The first module to be started is always Audit. |