28.1 Upgrading Sentinel

Use the following steps to upgrade the Sentinel server:

  1. Back up your configuration, then create an ESM export.

    For more information about backing up data, see Backing Up and Restoring Data in the Sentinel Administration Guide.

  2. (Conditional) If you have customized the configuration settings in the server.xml, collector_mgr.xml, or correlation_engine.xml files, ensure that you have created appropriate properties files named with the obj-component id to ensure that the customizations are retained after the upgrade. For more information, see Maintaining Custom Settings in XML Files in the Sentinel Administration Guide.

  3. Download the latest installer from the Download Website.

  4. Log in as root to the server where you want to upgrade Sentinel.

  5. Specify the following command to extract the install files from the tar file:

    tar xfz <install_filename>

    Replace <install_filename> with the actual name of the install file.

  6. Change to the directory where the install file was extracted.

  7. Specify the following command to upgrade Sentinel: 

    ./install-sentinel

  8. To proceed with a language of your choice, select the number next to the language.

    The end user license agreement is displayed in the selected language.

  9. Read the end user license, enter yes or y to accept the license, then continue with the installation.

  10. The installation script detects that an older version of the product already exists and prompts you to specify if you want to upgrade the product. To continue with the upgrade, press y.

    The installation starts installing all RPM packages. This installation might take a few seconds to complete.

  11. Clear your web browser cache to view the latest Sentinel version.

  12. Clear the Java Web Start cache on the client computers to use the latest version of Sentinel applications.

    You can clear the Java Web Start cache by either using the javaws -clearcache command or by using Java Control Center. For more information, see http://www.java.com/en/download/help/plugin_cache.xml.

  13. (Conditional) If the PostgreSQL database has been upgraded to a major version (for example, 8.0 to 9.0 or 9.0 to 9.1), clear the old PostgreSQL files from the PostgreSQL database. For information about whether the PostgreSQL database was upgraded, see the Sentinel Release Notes.

    1. Switch to the novell user.

      su novell

    2. Browse to the bin folder:

      cd /opt/novell/sentinel/3rdparty/postgresql/bin

    3. Delete all the old PostgreSQL files by using the following command:

      ./delete_old_cluster.sh

  14. To upgrade Collector Manager systems and Correlation Engine systems, see Upgrading the Collector Manager or the Correlation Engine.

  15. (Conditional) If you are using Kerberos authentication enable AES256 in your Java Runtime Environment since the java folder is replaced with default files during upgrade. To enable AES256 in your Java Runtime Environment, complete the following steps:

    1. Download Java Cryptography Extension (JCE) 8 from the following location: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

    2. Extract the two *.jar files and copy them to the /opt/novell/sentinel/jdk/jre/lib/security directory.

    3. (Conditional) If you are running Sentinel in an HA environment, repeat these steps on all nodes in the cluster.

    4. Restart Sentinel.