25.2 Upgrading Sentinel as a Non-root User

If your organizational policy does not allow you to run the full upgrade of Sentinel as root, you can upgrade Sentinel as another user. In this upgrade, a few steps are performed as a root user, then you proceed to upgrade Sentinel as another user created by the root user.

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

    For more information on backing up data, see Backing Up and Restoring Data in the NetIQ 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 Backing Up and Restoring Data in the NetIQ Sentinel Administration Guide.

  3. Download the installation files from the NetIQ Downloads Website.

  4. Specify the following command at the command line to extract the install files from the tar file:

    tar -zxvf <install_filename>

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

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

  6. Extract the squashfs RPM from the Sentinel install files.

  7. Install the squashfs on the Sentinel server. 

    rpm -Uvh <install_filename>

  8. Specify the following command to change to the newly created non-root novell user: novell:

    su novell

  9. (Conditional) To do an interactive upgrade:

    1. Specify the following command:

      ./install-sentinel

      To upgrade Sentinel in a non-default location, specify the --location option along with the command. For example:.

      ./install-sentinel --location=/foo

    2. Continue with Step 11.

  10. (Conditional) To do a silent upgrade, specify the following command:

    ./install-sentinel -u <response_file>

    The installation proceeds with the values stored in the response file. The Sentinel upgrade is complete.

  11. Specify the number for the language you want to use for the upgrade.

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

  12. Read the end user license and enter yes or y to accept the license and continue with the upgrade.

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

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

  14. 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.

  15. (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 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

  16. (Conditional) If you are upgrading from Sentinel 7.1.1 or earlier, the installer does not migrate the security intelligence (SI) data by default. To migrate SI data from Sentinel 7.1.1 or earlier, manually enable SI data migration as follows:

    1. Switch to novell user.

      su novell

    2. Open the /etc/opt/novell/sentinel/config/server.xml file.

    3. Add the following property in the BaseliningRuntime component section:

      <property name="baselining.migration.check">true</property>

    4. Restart the Sentinel server.