Previous     Contents     Index     Next     
iPlanet Portal Server 3.0 Service Pack 4 Installation Guide



Chapter 2   Downloading Service Pack 4


The iPlanet Portal Server 3.0 Service Pack 4 (iPS3.0SP4-01) software can be downloaded from the iPlanet web page as a series of compressed files.

Caution

Do not apply iPlanet Portal Server Service Pack 4 to an iPlanet Portal Server that has had Service Pack 3 or 3a and hotpatch 3 applied. Contact iPlanet customer support for instructions to upgrade to Service Pack 4. Service Pack 4 does not include hotpatch 3.




Contents of iPS3.0SP4-01.tar


The following directories and files are included in iPS3.0SP4-01.tar. For instructions on downloading and assembling the compressed files see the "Downloading Service Pack 4 Software From the iPlanet Web Page" section.

  • iPlanet Portal Server Service Pack 4 packages and scripts

    • attribute

    • ipsinstall

    • locale

    • patches

    • property

    • SUNWicgSA

    • SUNWicgSS

    • SUNWj2dem

    • SUNWj2dev

    • SUNWj2man

    • SUNWj2rt

    • SUNWwtdoc

    • SUNWwtds

    • SUNWwtdt

    • SUNWwtfw

    • SUNWwtgwd

    • SUNWwtnf

    • SUNWwtnm

    • SUNWwtrw

    • SUNWwtsam

    • SUNWwtsvd

    • SUNWwtsdd

    • SUNWwtws

    • template

    • update

    • LICENSE.txt

    • readme.txt

    • Installation Guide in HTML

    • SP4IG.pdf



Preparing for Installation

Before you begin installing Service Pack 4, see the following sections for pre-installation tasks.


Downloading Service Pack 4 Software From the iPlanet Web Page

The iPlanet Portal Server 3.0 Service Pack 4 software is available from the iPlanet.com web page:

http://iplanet.com/downloads/download

The software can be downloaded as a single file or as five 50-Megabyte files. For the 50-Megabyte files, additionally download the checksums file and the assembleiPS3SP4 script for assembling the individual files into a single Service Pack 4. The following instructions describe how to check the integrity of the files once they have been downloaded and how to assemble the files for installation.


Note If the iPlanet Portal Server 3.0 installation contains individual gateway and platform servers, the Service Pack 4 software must be installed on all servers.


The following procedures assume that /opt is the installation directory.

  1. In a terminal window, become root.

  2. Create a directory in which to download the Service Pack 4 files and make sure your browser has write permission to that directory. For example, /opt/ips_sp4:

    
    # cd /opt
    # mkdir ips_sp4

  3. Download single large file (iPS3.0SP4-01.tar.gz) or the following files into the directory created in Step 2.

    • iPS3.0SP4-01.tar.gz.aaa

    • iPS3.0SP4-01.tar.gz.aab

    • iPS3.0SP4-01.tar.gz.aac

    • iPS3.0SP4-01.tar.gz.aad

    • iPS3.0SP4-01.tar.gz.aae

    • checksums

    • assembleiPS3SP4

    If you downloaded the single large file go to Step 5.

  4. In /opt/ips_sp4, run the assembleiPS3SP4 script to verify the integrity of downloaded files.

    
    # cd /opt/ips_sp4/
    # ./assembleiPS3SP4

If the script determines that the correct number of files are present and that their data has not been corrupted, a single compressed tar file iPS3.0SP4-01.tar.gz is created, which contains all the Service Pack 4 files.

  1. Run the gunzip command to extract the iPS3.0SP4-01.tar file.

    
    # /usr/bin/gunzip iPS3.0SP4-01.tar.gz

  2. Run the tar command to extract the contents of the iPS3.0SP4-01.tar file.

    
    # /usr/bin/tar -xvf iPS3.0SP4-01.tar


    Caution

    		Do NOT apply Service Pack 4 on a system that is running Service Pack 3 or 3a with hotpatch 3. Contact iPlanet customer support for instructions to upgrade to Service Pack 4.



Removing Patches

For a clean install on a Service Pack 3 or 3a installation that has applied a hotpatch, remove the hotpatch.

Caution

For an upgrade, do NOT remove any 111829-xx patch. This is a hotpatch that has been applied to iPlanet Portal Server software.


To remove a hotpatch that has been applied do the following:

  1. List the Service Pack 3 or 3a hotpatch.


# showrev -p |grep 111829

Caution

If the patch is 111829-03 (hotpatch 3), do not apply iPlanet Portal Server Service Pack 4. Contact iPlanet customer support for instructions to upgrade to Service Pack 4. Service Pack 4 does not include hotpatch 3.


  1. As root, use the following command to remove the patch.

    
    # patchrm 111829-xx


Installing the Required Solaris Patches

The iPlanet Portal Server product is shipped with Solaris patches that are required or recommended for the iPlanet Portal Server software. The directory /opt/ips_sp4/patches contains patch directories for each supported version of Solaris. Use the patches in the directory that corresponds to the version of Solaris on which you are installing the iPlanet Portal Server product. Solaris patches are periodically updated, and can be downloaded from www.sunsolve.sun.com.

To install the required or recommended Solaris patches:

  1. As root, change directories to the patch directory that corresponds to the version of the Solaris operating environment on which the iPlanet Portal Server product is installed. For example, if the iPlanet Portal Server product is installed on the Solaris 8 operating environment:

    
    # cd /opt/ips_sp4/patches/solaris8/solaris_2.8_patch_cluster

  2. Run the install_cluster installation script. Depending on the computer on which the Solaris patches are being installed, installation time can take several hours.

    
    # ./install_cluster

  3. Reboot your computer.

    
    # reboot


Stopping the Server Component Processes

Before upgrading or installing the Service Pack 4 software, stop the following services if they are running:

  • Directory server

  • Web server


    Note If both the server and gateway components are running on one machine, stop both processes before starting the installation.



    Note The following instructions assume that the installation directory is /opt.


  • Issue the following command to see which directory server and web server processes are running. Note the processes that are associated with the Portal Server software, then reissue the command after stopping the processes to verify that they have been stopped.

          
    # /usr/bin/ps -eo pid,args | grep /opt/netscape
    446 ./ns-slapd -f /opt/netscape/directory4/slapd-server1/config/slapd.conf -i /opt/
    467 ns-httpd -d /opt/netscape/server4/https-server1.sesta.com/con
    458 ./uxwdog -d /opt/netscape/server4/https-admserv/config
    466 ./uxwdog -d /opt/netscape/server4/https-server1.sesta.com/con
    459 ns-httpd -d /opt/netscape/server4/https-admserv/config
    29857 ./ns-admin -d /opt/netscape/directory4/admin-serv/config

    In this example, the process id numbers correspond with the following processes. All of the following processes must be stopped before installing or upgrading to Service Pack 4.

               
    446
    		directory server process
    467
    		web server process
    458
    		watchdog process for web server admin service
    466
    		watchdog service for the web server
    459
    		admin service for the web server
    29857
    		admin service for the directory server

  • Stop the iPlanet Portal Server server component. This step stops the directory server and web server processes.


    Note If running iPlanet Portal Server 3.0 or iPlanet Portal Server Service Pack 1, start and stop the server component.


               
    # /etc/init.d/ipsserver start
    stopping auth helpers ... done.
    stopping web server ... done.
    stopping directory server ... done.
    starting auth helpers ... done.
    starting directory server ... done.
    starting web server ... done.
    # /etc/init.d/ipsserver stop
    stopping auth helpers ... done.
    stopping web server ... done.
    stopping directory server ... done.

    • If running iPlanet Portal Server Service Pack 2, Service Pack 3, or Service Pack 3a, stop the server component.

          
      # /etc/init.d/ipsserver stopall
      stopping auth helpers ... done.
      stopping web server ... done.
      stopping directory server ... done.

  • Verify that all directory server and web server processes are stopped. The processes that were running in Step 1 should no longer be displayed.

    
    # /usr/bin/ps -eo pid,args | grep /opt/netscape

  • If the directory server is still running (process 446), use the following command to stop it.

    
    # /opt/netscape/directory4/slapd-servername/stop-slapd

  • If any other processes are still running, issue a kill -TERM process_id for each directory server process or web server process that is running under iPlanet Portal Server. For example:

    
    # kill -TERM 467


Stopping the Proxies and the Gateway Component Processes

Before installing or upgrading to Service Pack 4, the following processes need to be stopped.

  • ipshttpd proxy process

  • ipsnetletd proxy process

  • gateway Java™ process

  • Issue the following command to see which gateway processes are running. By viewing the processes that are currently running, you can reissue the command after stopping the processes to verify that they have been stopped.

          
    # /usr/bin/ps -eo pid,args|grep java
    481 /usr/java/bin/../jre/bin/../bin/sparc/native_threads/java
    -ms32m -mx128m -class
    503 /usr/java/bin/../jre/bin/../bin/sparc/native_threads/java
    -ms32m -mx128m -class
    741 /usr/jave/bin/../jre/bin/../bin/sparc/native_threads/java
    -ms32m -mx128m -class

    In this example the process id numbers correspond with the following processes.

         
    481
    		ipshttpd process
    503
    		ipsnetletd process
    741
    		gateway process

  • Stop the ipshttpd or ipsnetletd proxies that are running on the server component.

    
    # /opt/SUNWips/bin/ipshttpd stop
    # /opt/SUNWips/bin/ipsnetletd stop

  • Stop the iPlanet Portal Server gateway component.

    
    # /etc/init.d/ipsgateway stop

  • Verify that the processes have been stopped. The processes that were running in Step 1 should no longer be displayed.

    
    # /usr/bin/ps -eo pid,args|grep java

    If any of the processes are still running, issue a kill -TERM process_id for each proxy process that is running under iPlanet Portal Server. For example:

    
    # kill -TERM 481


Stopping the Third-Party Software Processes and the Channels

Before performing a clean installation of or upgrading to Service Pack 4, stop all iPlanet Portal Server third-party software and channels that push data to the iPlanet Portal Server product.

It is especially important to stop channels that push data to the iPlanet Portal Server product because some channels write into iPlanet Portal Server directories.

Consult the manuals for each channel and for third-party software for instructions on shutting them down.


Installed Software Modules, Customizations, and Third-Party Products

If iPlanet Portal Server 3.0 software has been previously installed and other modules have been configured to run on top of this software, it is important to read all release notes and updates that pertain to the added modules. Patches and additional configuration steps may be required. Also, any customizations must be backed up or documented before Service Pack 4 is installed, so the customizations can be restored after the upgrade.

When Service Pack 4 is applied, it upgrades Java 1.2.2_05 or 1.2.2_07 to Java 1.2.2_09.

If the Java link (/usr/java) has been modified, Service Pack 4 overwrites the link to point to the new JVM™. For example, if /usr/java was linked to Solaris_JDK_1.2.2_9 and the Rhino software was installed into /usr/java/jre/lib/ext, then the Rhino software would actually be in /usr/Solaris_JDK_1.2.2_9/jre/lib/ext/js.jar and would need to be moved or copied to /usr/java/jre/lib/ext. Otherwise, the contents of the link become inaccessible.


Saving the Certificates Used by the Server Component

If using certificates on the iPlanet Portal Server server component, save the certificates in a safe location before the upgrade process, and restore them after the upgrade is complete.

The following procedure assumes that /opt is the installation directory.

To save the certificates:

  1. As root, change directories to the certificate directory. In the following example, /opt is the base directory.

    
    # cd /opt/netscape/server4

  2. Create a tar file of the alias directory and copy it to a safe location. In the following example the compressed alias directory is copied to /usr/tmp.

    
    # tar cf /usr/tmp/alias.tar alias

For instructions on upgrading the iPlanet Portal Server product to Service Pack 4, see the "Upgrading to Service Pack 4" chapter.

For instructions on upgrading the iPlanet Portal Server product to Service Pack 4 if running a Non-Root installation, see the "User Non-Root" chapter.

For instructions on upgrading the iPlanet Portal Server product to Service Pack 4 if running as User Nobody, see the "User Nobody" chapter.


Previous     Contents     Index     Next     
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated March 07, 2002
f