Installing from Installer

Before You Begin

Please read the following important notes before you begin installing BellaDati IoT Data Collector:

• Check that your target machine meets (at least) the minimal system requirements (appropriate HW and SW, including Java).
• Your BellaDati instance is up and running, and it is accessible from your target machine.

To run installer on Linux:

• Please make sure the installer has execute privileges. You can use following command to add execute rights:

  • chmod +x iot-collector_linux-x64_x_y_z.sh

• Execute following command (you can use argument -c if you want to run installer in console mode):

  • sudo ./iot-collector_linux-x64_x_y_z.sh

1. Welcome and Information

This window will check your machine against the minimal system requirements. Upgrade to a higher-performance machine in case your configuration does not meet the criteria, to avoid experiencing a decreased performance of IoT Collector.

Click Next to proceed with the installation.

2. License Terms

Read and Accept the license agreement.

Click Next to proceed with the installation.

3. Select Destination Directory

By default, IoT Collector is installed into a predefined installation directory. Click browse to navigate to different folder if you want to modify these settings. Installer will check your free disk capacity to ensure enough space is available.

Click Next to proceed with the installation.

4. Select Installation Type

Check Advanced Installation if you want to choose deployment mode and specify all application parameters. Leave it not selected to perform basic installation with default settings.

Check Start services automatically if you want to autostart installed modules after installation and also after each machine startup. Leave it blank to start modules on your own.

Click Next to proceed with the installation.

5. Configuration for Distributed Mode

5.1. Distributed Mode - Multicast

Approve or edit the following default cluster settings:

• Multicast group - Multicast group IP address
• Multicast port - Socket port that the member listens to and sends discovery messages through
• Multicast TTL - TTL (Time To Live) value for multicast packets sent out
• Multicast timeout - Period (in seconds) during which a member waits for a multicast response from another member
• Trusted interfaces - Comma separated list of IP addresses of all trusted members
  
  

Click Next to proceed with the installation and go to step 6.

5.2. Distributed Mode - TCP/IP

Approve or edit the following default cluster settings:

• Members - Comma separated list of IP addresses of other cluster members
  
  

Click Next to proceed with the installation and go to step 6.

6. Choose Modules

Please specify count of modules that you want to install on this machine:

• Audit - Provides auditing services and status of modules and sensors
• Receiver - Collects data from multiple devices 
• Sender - Retrieves data periodically from linked receiver and execute automated actions if necessary

You will need to specify configuration parameters for each module in next steps.

Click Next to proceed with the installation.

7. Audit Configuration

7.1. Instance Configuration

Approve or edit the following default settings:

• Instance name - Name that will identify this IoT Collector instance uniquely. Good practice is to enter company name followed by environment identification.
• Drop database at startup - Flag indicating if database should be dropped during module startup
• Authentication enabled
  • Administrator password - Password for main administrator (default: BellaDati01)
  • Drop old users at startup - Flag indicating if users should be dropped during module startup
  • Merge users at startup - Flag indicating if users should be merged/updated during module startup
    
    

Click Next to proceed with the installation.

7.2. Audit - Basic Parameters

Approve or edit the following default settings:

• Name - Name that will identify this audit module uniquely
• Port - HTTP port on which audit endpoints will be running
• Body limit - Maximum allowed HTTP request body size (in bytes, default: 2 MB)
• Drop database at startup - Flag indicating if database should be dropped during module startup
• JSON limit enabled - Flag indicating if JSON data object should be limited (default: false/unlimited)
  • Maximal VARCHAR length - Length of VARCHAR column storing JSON data object
    
    

Click Next to proceed with the installation.

7.3. Audit - Security Parameters

Approve or edit the following default security settings:

• Authentication enabled
  • Viewer username - Unique viewer username
  • Viewer password - Password for viewer (default: BellaDati01)
  • Drop old users at startup - Flag indicating if users should be dropped during module startup
  • Merge users at startup - Flag indicating if users should be merged/updated during module startup
• SSL/TLS enabled
  • Keystore path - Absolute or relative path to Java keystore file (JKS)
  • Keystore password - Password of Java keystore (default: wibble)

Click Next to proceed with the installation.

8. Receiver Configuration

By default, receiver is configured as HTTP_POST_CONSUME. You can change it after the installation using the IoT Console or manually.

8.1. Receiver - Basic Parameters

Approve or edit the following default settings:

• Name - Name that will identify this receiver module uniquely
• Port - HTTP port on which receiver endpoints will be running
• Sensor ID - JSON key identifying entry that stores sensor identification
• Input mode
  • Single - Sensor sends JSON data containing only one single record
  • Bulk - Sensor sends JSON data containing multiple records
• Body limit - Maximum allowed HTTP request body size (in bytes, default: 2 MB)
• Drop database at startup - Flag indicating if database should be dropped during module startup
• JSON limit enabled - Flag indicating if JSON data object should be limited (default: false/unlimited)
  • Maximal VARCHAR length - Length of VARCHAR column storing JSON data object
    
    

Click Next to proceed with the installation.

8.2. Receiver - Security Parameters

Approve or edit the following default security settings:

• Authentication enabled
  • Sensor username - Unique sensor username
  • Sensor password - Password for sensor (default: BellaDati01)
  • Viewer username - Unique viewer username
  • Viewer password - Password for viewer (default: BellaDati01)
  • Editor username - Unique editor username
  • Editor password - Password for editor (default: BellaDati01)
  • Drop old users at startup - Flag indicating if users should be dropped during module startup
  • Merge users at startup - Flag indicating if users should be merged/updated during module startup
• SSL/TLS enabled
  • Keystore path - Absolute or relative path to Java keystore file (JKS)
  • Keystore password - Password of Java keystore (default: wibble)
    
    

Click Next to proceed with the installation.

9. Sender Configuration

9.1. Sender - Basic Parameters

Approve or edit the following default settings:

• Name - Name that will identify this sender module uniquely
• Port - HTTP port on which sender endpoints will be running
• Period - Delay after which the timer will fire new send event (in seconds, default: 60)
• Limit - Page size that is used as a filter to obtain data from receiver (default: 1000)
• Delete processed data from receiver database
• Receiver
  • Local - Receiver is located on the same machine as this sender
  • Remote - Receiver is located on the remote machine

Click Next to proceed with the installation.

9.2. Sender - Security Parameters

Approve or edit the following default security settings:

• Authentication enabled
  • Viewer username - Unique viewer username
  • Viewer password - Password for viewer (default: BellaDati01)
  • Drop old users at startup - Flag indicating if users should be dropped during module startup
  • Merge users at startup - Flag indicating if users should be merged/updated during module startup
• SSL/TLS enabled
  • Keystore path - Absolute or relative path to Java keystore file (JKS)
  • Keystore password - Password of Java keystore (default: wibble)

Click Next to proceed with the installation.

9.3. Sender - BellaDati Parameters

By default, sender is configured with automated action BELLADAT_REST - it means, it will periodically send the data to BellaDati back-end. You can change this after the installation using the IoT Console or manually.

Approve or edit the following default settings:

• Columns
  • Record ID - Code of attribute/indicator that contains record identification
  • Receiver name - Code of attribute/indicator that contains receiver identification
  • JSON - Code of attribute/indicator that contains JSON data
  • Timestamp - Code of attribute/indicator that contains timestamp
  • Mapping - List of mappings between BellaDati indicator/attribute code and JSON key
• Save to file - Flag indicating if transformed data should be saved to local file
• Send to BellaDati - Flag indicating if transformed data should be send to BellaDati
  
  • URL - BellaDati URL
  • SSL/TLS enabled - Flag indicating if BellaDati is running with SSL/TLS enabled
  • Consumer key - OAuth consumer key
  • Consumer secret - OAuth consumer secret
  • Username - Username of BellaDati user
  • Password - Password of BellaDati user
  • Data Set ID - Target DataSet identification
  • Apply import template - Flag indicating if import template should be applied during import
    • Template ID - Identification of import template
  • Split data - Flag indicating if split functionality should be applied during import
    • Column index - Index of column used to split data

Click Next to proceed with the installation.

10. Start Menu Folder

Approve or edit the name of the start menu folder.

Click Next to proceed with the installation.

11. License Key

Send obtained server ID to BellaDati support team and request license key. Enter obtained license key to the following form:

Click Next and wait while IoT Collector is installed on your computer.

12. Startup in Distributed Mode

In order to start Collector modules correctly, cluster has to be formed at first. You need to start all audit modules running on other machines at first. Receiver and sender modules will be started after the confirmation that all audit modules are up and running.

Click Next to proceed with the startup. It could take some time to start all modules.

13. Finishing Installation

The installation is complete.

Close the window.

14. Troubleshooting

• If you have any problems during installation, please try to complete installation (retry or ignore errors) and then send us following log file:

  • <installation-directory>/.install4j/installation.log

• Modules do not autostart after restart of Linux machine. You need to register/edit created services for autostart based on your distribution, version, service system (e.g. SysV, Systemd, Upstart) and init system (e.g. update-rc.d, ntsysv, chkconfig, insserv). Please keep following order during modules startup:
  1. Start all audit modules
  2. Start all receiver modules
  3. Start all sender modules
• To access IoT Collector modules after the installation is complete, point your web browser to http://localhost:<port>/ or https://localhost:<port>/ (based on entered settings in step 7, 8, and 9).
• If you have any problems with IoT Collector functionality, please send us all log files located on following location:

  • <installation-directory>/logs/