Previous Contents Index Next |
iPlanet Portal Server 3.0 Service Pack 4 Installation Guide |
Chapter 3 Upgrading to Service Pack 4
The Service Pack 4 installation script offers the choice of upgrading the existing version of the product or performing a clean installation of iPlanet Portal Server 3.0 with Service Pack 4. Read this chapter if choosing the upgrade option that upgrades the iPlanet Portal Server 3.0 product to Service Pack 4. For a clean install, see the "Clean Installation" chapter.
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 3.0 Installation Guide for instructions on installing the Samba software.Service Pack 4 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 4 on a localized version of the iPlanet Portal Server:
Download the localization files that apply to your configured locale.
To upgrade the iPlanet Portal Server software:
Perform an upgrade to Service Pack 4.
- Localization files can be downloaded from the iPlanet website.
Install the localization files that apply to your configured locale.
Back up the entire machine on which the iPlanet Portal Server 3.0 software resides, so that it can be restored if necessary.
Stop all services for the iPlanet Portal Server 3.0 server and gateway.
Note See Stopping the Server Component Processes for information on how to correctly perform these functions.
As root, change directories to /opt/ips_sp4.
The script displays the following status:
The iPlanet Portal Server 3.0 Service Pack 4 install script will now run. See the following example for the prompts required to install this software.
- The ipsinstall script must be run from the directory in which it exists.
# cd /opt/ips_sp4
# ./ipsinstall
- The install script checks for hotpatches 1, 2 and 3 for Service Pack 3 or 3a and the Mobile Access Pack.
- If hotpatches 1 or 2 are installed, the following warning is displayed:
Patch 111829-01 detected. Service pack 4 replaces some of the content of this patch. Therefore, do not remove patch 111829-01 after upgrading to service pack 4. Abort installation? [y]/n n
- Continue the upgrade. Go to step 3.
- If hotpatch 3 is installed, the following warning is displayed:
Patch 111829-03 detected. Service pack 4 cannot run on top of this patch. Please discontinue the install and contact iPlanet Support. Abort installation? [y]/n y
- Do NOT continue the upgrade. Contact iPlanet customer support for instructions to upgrade to Service Pack 4.
- If Mobile Access Pack is installed, the following warning is displayed:
- Do NOT continue the upgrade. Check the iPlanet web site for information on this Mobile Access Pack hotpatch for Service Pack 4.
Accept the default values or enter the correct name and IP address information.
- The iPlanet Portal Server 3.0 Service Pack 4 Install Script displays the Service Pack 4 license agreement.
- Enter yes to accept the license agreement and continue with the installation. If you enter no, the installation script exits.
Note If the installation script detects missing Solaris patches, a warning message is displayed. See "Installing the Required Solaris Patches" for information on installing the necessary Solaris patches.
- The installation script attempts to determine name and IP address information about the machine on which you are installing. If the machine on which you are installing uses multiple IP addresses or multiple domains, verify that the IP address displayed by the script is the correct one for the portal.
Note The primary Portal Server in this example is server1.
Enter 1 to upgrade an existing iPlanet Portal Server installation.
- The script displays the task menu.
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.
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.
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 4 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 4.
Tip By using the diff command to compare pre-Service Pack 4 files that have been customized and the new Service Pack 4 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 © 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated March 07, 2002