6.9 Configuring Services After Applying an OES Support Pack

  1. If Novell iManager is installed on the server, do the following to update all the plug-ins. If iManager is not installed on the server, proceed to Step 2.

    1. Access iManager by entering the following URL in the Address field of your Web browser:

      http://IP_or_DNS_name/nps/iManager.html

      Replace IP_or_DNS with the IP address or DNS name of your OES Linux server.

    2. Log in to iManager as user Admin or as a user with rights equivalent to Admin.

    3. In the header frame of iManager, click the Configure icon.

    4. Click Module Installation > Available Novell Plug-in Modules.

    5. Select all the modules in the list by clicking the Select All check box (the check box at the top of the list to the left of module).

    6. Click Install.

      Installing the updates might take awhile.

      Ignore the following message that might display at the end of the installation. The plug-ins have actually installed successfully.

      Can’t find bundle for base name DevResources, locale en.

    7. Log out of iManager.

  2. If Novell QuickFinder is installed on the server and you are updating from SP1 to SP2, configure the service in YaST as follows:

    1. At a command line prompt, enter

      yast novell-quickfinder

    2. When prompted that the service is already configured, select Yes to continue and press Enter to proceed.

    3. Enter the required setting to configure the service on each screen presented.

    4. When prompted to restart other services, select No and press Enter.

      The service is restarted when you reboot the server.

    5. Close YaST and continue with Step 3.

  3. If NCP™ Server Management and Novell Remote Manager (NRM) are installed on the server and you are patching a server from the initial version of OES to the OES SP2 version, do the following to ensure that the management interface plug-in for NCP Server Management is functional in NRM and any changes made to the Novell Remote Manager configuration file are saved from previous version.

    If none of these services is installed on the server or you are patching from OES SP1 to OES SP2, proceed to Step 4.

    1. Copy the following line from the old httpstkd.conf file at /etc/opt/novell/httpstkd.conf.rpmsave and any other changes made to the httpstkd.conf file and save them in the current /etc/opt/novell/httpstkd.conf file.

      load /opt/novell/lib/libnrm2ncp.so

      This line is usually at the end of the file.

    2. Continue with Step 4.

  4. Reboot the server by entering

    reboot

    IMPORTANT:Rebooting the server is required because of updates to the kernel.

    If the server has been up longer than the specified fsck check interval for that server, the server performs the fsck function after the reboot. Please allow for this to take some time, especially on servers with large file systems.

  5. If Novell Virtual Office is installed on the server, restart Tomcat by entering the following command at a shell commandline prompt:

    /etc/init.d/novell-tomcat4 restart

    Restarting Tomcat after the server boot, eliminates the chance of receiving error 500 when you load Novell Virtual Office.

    To monitor Tomcat coming up, enter the following command at a shell commandline prompt:

    tail /var/opt/novell/tomcat4/logs/catalina.out

If you have completed all the steps in Downloading the Updated ISO Images for Use with YaST Patch CD Update through Configuring Services After Applying an OES Support Pack, you are finished patching the server.