SmartSense Server Configuration
Introduction
This manual describes the configuration of the server-side components of the application GBS SmartSense. GBS SmartSense is an application developed to monitor GBDS Clusters, allowing the user to view real-time reports about the health and performance of the environment.
The configuration procedure should be done only after the installation step. For more information, consult the GBS Apps Installation Manual.
Configuration
The configuration steps are:
Configure Tomcat;
Configure the Certificates;
Generate the encrypted password;
Install the Elastic Stack (ELK);
Finalize the configurations in the config.properties file.
All steps are described below. An example of the file config.properties can be found in the section Configuration File Example.
All lines must be present in the configuration file. Commenting out or deleting lines may cause unexpected behavior. For additional information, contact the Griaule Support Team.
Tomcat Configuration
Edit Tomcat's configuration file to configure the certificates and the port the application will use.
vi /var/lib/tomcats/smart-sense/conf/server.xmlTo change the port, search for Connector port=. This is the port for 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 -->, then adjust the following parameters:
The parameter port must be the desired network port for the application.
Change the path of the keystoreFile and the truststoreFile to the appropriate values. Do the same for the keystorePass and the truststorePass.
The parameter clientAuth="true" will require server authentication to the client and client authentication to the server. This means the client will need to import the certificate into the browser to be able to access the application.
When clientAuth is set to true, the system administrator must provide the file certificate.pfx to end users.
Database Password Encryption
In the file config.properties, the parameter jdbc.password is an encrypted password. To generate the encrypted password, follow these steps:
Go to the following directory:
Run the command:
The encrypted password will appear after the message: "Encrypted password is:"
Save the encrypted password. It will be used in later configurations.
Application Configuration File
To configure the file, open it with:
The most important changes in this file are the parameters jdbc.url, jdbc.username, jdbc.password and gbds.url. Configure them according to your environment.
The complete configuration file is shown in the section Configuration File Example.
Remember to replace the encrypted password generated in the section Database Password Encryption in this file.
SmartSense Settings
The last step is to configure the IP and port of the application that the end user will access. It must be the same IP and port configured in the section Tomcat Configuration.
Make sure the configuration parameters smart-sense.ip, smart-sense.port and smart-sense.protocol are correctly specified in the file config.properties. In many cases, the IP will be the same for several applications. However, each application will have a different and unique port.
Nodes (optional)
Optionally, instead of using the SmartSense graphical interface, you can configure the nodes to be monitored by inserting them directly into the smartsense.hosts table in the database. To do this, execute the following command in the database, replacing the placeholders with the correct values:
Installing the Elastic Stack (ELK)
Go to the ELK Installation Manual for detailed instructions on how to install and configure the Elastic Stack.
Finishing the Configurations
After completing all configuration steps, return to the GBS Apps Installation Manual - Configuration Section.
Configuration File Example
This section shows an example of the file config.properties.
Last updated
Was this helpful?

