25.2 Upgrading the Appliance through WebYaST

NOTE:Appliance upgrades from versions prior to Sentinel 7.2 must be done using the zypper command line utility because user interaction is required to complete the upgrade. WebYaST is not capable of facilitating the required user interaction. For information about using zypper to upgrade the appliance, see Section 25.1, Upgrading the Appliance by Using zypper.

  1. Log in to the Sentinel appliance as a user in the administrator role.

  2. Back up your configuration, then create an ESM export. For more information, see Backing Up and Restoring Data in the NetIQ Sentinel Administration Guide.

  3. (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 NetIQ Sentinel Administration Guide.

  4. If you want to upgrade the Sentinel Appliance, click Appliance to launch WebYaST.

  5. If you want to upgrade a Collector Manager or Correlation Engine Appliance, specify the URL of the Collector Manager or Correlation Engine computer using port 4984 to launch WebYaST as https://<IP_address>:4984, where <IP_address> is the IP address of the Collector Manager or Correlation Engine. Complete Step 7 through Step 10.

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

  7. (Conditional) If you have not already registered the appliance for automatic updates, register for updates.

    For more information, see Section 13.3.3, Registering for Updates.

    If the appliance is not registered, Sentinel displays a yellow warning that indicates that the appliance is not registered.

  8. To check if there are any updates, click Updates.

    The available updates are displayed.

  9. Select and apply the updates.

    The updates might take a few minutes to complete. After the update is successful, the WebYaST login page is displayed.

    Before upgrading the appliance, WebYaST automatically stops the Sentinel service. You must manually restart this service after the upgrade is complete.

  10. Restart the Sentinel service by using the Web interface.

    For more information, see Section 13.4, Stopping and Starting the Server by Using WebYaST.

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