Sun ONE logo      Previous      Contents      Index      Next     

iPlanet Portal Server 3.0 Service Pack 5 Installation Guide

Chapter 3

Upgrading to Service Pack 5

The Service Pack 5 installation script offers the choice of upgrading the existing version of the product or performing a clean installation of iPlanet Portal Server with Service Pack 5. Read this chapter if choosing the upgrade option that upgrades the iPlanet Portal Server product to Service Pack 5. For a clean install, see the "Clean Installation" chapter.


Note

If iPlanet Portal Server 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. This is especially applicable to the Compass 3.01C Release Notes found on: http://docs.iplanet.com



Upgrading to Service Pack 5

When upgrading to iPlanet Portal Server Service Pack 5, perform the upgrade only on machines that have iPlanet Portal Server Service Pack 3 or greater installed. Upgrading from iPlanet Portal Server Service Pack 1 or Service Pack 2 to iPlanet Portal Server Service Pack 5 is not supported.


Note

If this is an upgrade where the portal server runs as user non-root, or user nobody, go to the appropriate sections in this installation guide.



Standard Upgrade

If the Samba software has been installed, this procedure removes it. The Samba software, along with other third-party software originally shipped with the iPlanet Portal Server product, is contained in a file called ThirdParty.tar.gz and can be downloaded from the www.iplanet.com website. See “Appendix B” in the original iPlanet Portal Server Installation Guide 3.0 for instructions on installing the Samba software.

Service Pack 5 can be installed on localized versions of the iPlanet Portal Server product, but localized versions are not supported without installing updated localization files. To successfully upgrade to Service Pack 5 on a localized version of the iPlanet Portal Server:

  1. Download the localization files that apply to your configured locale.
  2. Localization files can be downloaded from the iPlanet website.

  1. Perform an upgrade to Service Pack 5.
  2. Install the localization files that apply to your configured locale.

To upgrade the iPlanet Portal Server software:

  1. Back up the entire machine on which the iPlanet Portal Server software resides, so that it can be restored if necessary.
  2. Stop all services for the iPlanet Portal Server server and gateway.

  3. Note

    See Stopping the Server Component Processes for information on how to correctly perform these functions.


Accessing the Install Script

  1. As root, change directories to /opt/ips_sp5.
  2. Run the ipsinstall script.
  3. The ipsinstall script must be run from the directory in which it exists.

    # cd /opt/ips_sp5

    # ./ipsinstall

    Theinstall script checks for hotpatches 1, 2 and 3 for Service Pack 3 or 3a and the Mobile Access Pack.

  1. Accept the default values or enter the correct name and IP address information.
  2. Inspecting system.

    What is the iPS hostname of this machine? [server1]

    What is the subdomain ("." for none)? []

    What is the domain? [sesta.com]

    What is the ip address of server1.sesta.com? [192.168.01.01]

    Inspecting iPS components.

    The script displays the task menu.

  3. Enter 1 to upgrade an existing iPlanet Portal Server installation.
  4. Options:

    1) Continue upgrade

    2) Continue as a clean install (current installation will be removed)

    3) Continue install (current installation will not be removed)

    4) Remove current installation

    5) Exit

    Choice? [5] 1

  5. If any of the iPlanet Portal Server processes are still running, the installation script displays a warning message and process information. If the processes detected by the script are related to the iPlanet Portal Server, abort the upgrade, and stop the processes before proceeding. See Stopping the Server Component Processes and Stopping the Proxies and the Gateway Component’s Processes for instructions.
  6. If any ports required by the iPlanet Portal Server product are temporarily in use, the installation script displays a warning message and port information. If other applications are running on the ports required by the iPlanet Portal Server product, exit the applications and wait for the ports to close before proceeding. The applications may need to be configured to use other ports.

The script displays the following status:

Reading current configuration.

Checking running status.

Pre-upgrade processing.

Installing server.

Installing SUNWwtsdd...

Installing SUNWwtws...

Installing SUNWwtsvd...

Installing SUNWwtdt...

Installing SUNWwtnm...

Installing SUNWwtnf...

Installing SUNWwtrw...

Installing SUNWwtdoc...

Installing SUNWwtsam...

Installing SUNWwtds...

Starting server.

Installing gateway.

Installing SUNWwtgwd...

Starting gateway.

Post-upgrade processing.

Upgrade complete.

Please look in /var/sadm/install/logs/ipsinstall.611

for saved certificates, attributes, properties and templates.

If you have made any customizations to iPS before this upgrade, you may need to merge your changes back.

When the upgrade process is finished, your screen prompt is returned. Look at the file /var/sadm/install/logs/ipsinstall.process.id/install.log to verify that no errors in the upgrade have occurred.

If your previous iPlanet Portal Server installation was customized, see "Restoring Customizations" for more information.


Restoring Customizations

If you performed customizations on your previous iPlanet Portal Server installation, the installation script saves these customizations in /var/sadm/install/logs/ipsinstall.process_id. Generally, the same steps used for the initial customizations development can be used when reinstating your customizations into a Service Pack 5 installation. After restoring customizations, run the iPlanet Portal Server product to verify that your customizations work without errors. Certain customizations could be affected by changes in Service Pack 5.


Tip

By using the diff command to compare pre-Service Pack 5 files that have been customized and the new Service Pack 5 files, changes can be viewed so that previous customizations can be reinstated.


See "After Installation" for information on restoring saved certificates.



Previous      Contents      Index      Next     


Copyright 2003 Sun Microsystems, Inc. All rights reserved.