SmartSense Server Config
Introduction
This manual describes the configuration of the server-side components of the GBS SmartSense application. GBS SmartSense is an application designed to monitor GBDS Clusters, allowing the user to view live reports on the environment's health and performance.
The configuration procedure should be done only after the installation step. For more information, refer to GBS Apps Setup Manual.
Configuration
The configurations steps are:
Configure Tomcat;
Configure Certificates;
Generate encrypted password;
Install the Elastic Stack (ELK);
Configure the config.properties;
All steps are described below. An example config.properties file is found in the Configuration File Example section.
All lines must be present in the configuration file. Commenting or deleting lines may cause unexpected behavior. For further information, contact Griaule Support Team.
Tomcat Configuration
Edit the Tomcat configuration file to configure the certificates and port that the application will use.
vi /var/lib/tomcats/smart-sense/conf/server.xmlTo change the port, look for Connector port=. This is the port for the backend operations.
Certificates Configuration
To enable SSL authentication, search for connector port= in the file /conf/server.xml.
There are two entries. The commented one is the configuration for SSL. Remove the comment delimiters <!-- and -->, and adjust these settings:
The parameter port should be the desired network port for the application.
Change the path of keystoreFile and truststoreFile to the proper values. Do the same for keystorePass and truststorePass.
The parameter clientAuth="true" will require authentication from server-side to client-side and from client-side to server-side. This means that the client will need to import the certificate in the browser to be able to access the application.
When clientAuth is set to true, the system administrator must provide the certificate.pfx file for the end-users.
Database password encryption
In the config.properties file, the jdbc.password parameter is an encrypted password. To generate the encrypted password, perform the following steps:
Go to the following directory:
Execute the command:
The encrypted password will be displayed after the message: “Encrypted password is:”
Application properties file
To configure the application properties file, open with:
The most important changes in this configuration file are the jdbc.url, jdbc.username, jdbc.password, and gbds.url properties. Configure the parameters according to the environment.
The complete configuration file is shown in the Configuration File Example section.
SmartSense Configuration
The last step is configuring IP and port of the application that the end-user will access. It must be the same IP and port configured in the Tomcat Configuration section.
Make sure that the smart-sense.ip, smart-sense.port, and smart-sense.protocol configuration parameters are correctly specified in the config.properties file. In many cases, the IP will be the same for various applications. However, each application will have a different and unique port.
Nodes (optional)
Optionally, instead of using the SmartSense GUI, you may configure the nodes that will be monitored directly inserting them in the table smartsense.hosts in the database. To do so, run the following command in the database, replacing the placeholders with the correct values:
Installing the Elastic Stack (ELK)
Move on to the ELK installation manual for detailed instructions on how to install and configure the Elastic Stack.
Finish Configuration
After all configuration steps are complete, go back to the GBS Apps Setup Manual - Configuration Section.
Configuration File Example
This section shows an example of the config.properties file.
Last updated
Was this helpful?

