Importing TLS or SSL certificate for the SMTP Server

The TLS or SSL certificate enables secure communication between the Analyzer detail view server and the SMTP Server to send alerts.

1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
2. Stop the crond service using the command:

   service crond stop

3. Stop the megha service using the command:

   /usr/local/megha/bin/megha-jetty.sh stop

4. Navigate to the Java keystore directory. For example:

   cd /usr/java/jdk1.8.0_291-amd64/jre/lib/security

5. If the jssecacerts file does not exist, create it.
6. Import the TLS or SSL certificate into the Analyzer detail view server using the keytool command:

   keytool -importcert -alias Alias_name -keystore Truststore_file_path -storetype jks -file TLS_OR_SSL_certificate_file_path

   Note: You can define any unique alias name for TLS or SSL certificate.

   For example:

   keytool -importcert -alias aliasName -keystore jssecacerts -storetype jks -file /tmp/server.crt

   Note: Enter the truststore password when prompted.
7. Make sure that the megha user has the read permission for the jssecacerts file. If not, change the permissions as in this example:

   chmod o+r jssecacerts

8. Start the megha service and verify the status:

   /usr/local/megha/bin/megha-jetty.sh start
   /usr/local/megha/bin/megha-jetty.sh status

9. Start the crond service and verify the status:

   service crond start
   service crond status

   Note: If you upgrade the JDK in the future, make sure that the jssecacerts file is copied in the upgraded JDK directory.

   For example: If you upgrade JDK from v1.7.0 to v1.8.0, copy the jssecacerts file from /usr/java/jdk1.7.0_291-amd64/jre/lib/security to /usr/java/jdk1.8.0_251-amd64/jre/lib/security.

   After copying the jssecacerts file, make sure that megha user has read permission for the jssecacerts file.