|
| |
| Sun Java System Portal Server 6 2004Q2 Migration Guide | |
Chapter 17
Planning the Upgrade from Sun ONE Portal Server 6.2 to Sun Java System Portal Server 6 2004Q2This chapter provides an overview and discussion on how to plan for upgrading users, roles, organizations, components, templates, providers, channels, and properties files from Sun™ ONE Portal Server 6.2 to Sun Java™ System Portal Server 6 2004Q2.
This chapter contains the following sections:
Overview of Upgrade ProcessThe Sun Java System Portal Server 6 2004Q2 product uses the Sun Java System Identity Server 2004Q2 service as its LDAP data store and management interface. The Sun ONE Portal Server 6.2 product used the Sun ONE Identity Server 6.1 service as its LDAP data store and management interface. Although the Sun Java System Identity Server 2004Q2 and the Sun ONE Identity Server 6.1 products are similar in structure and provide many of the same services, changes to the product require you to upgrade the Sun ONE Identity Server 6.1 to Sun Java System Identity Server 2004Q2 before you can upgrade your Sun ONE Portal Server 6.2 software to the Sun Java System Portal Server 6 2004Q2 software.
Note
The Sun ONE Portal Server 6.2 product can be deployed into a variety of web containers including the Sun™ ONE Web Server, the Sun™ ONE Application Server, the IBM Websphere Application Server, and the BEA Weblogic Application Server; however, when upgrading your Sun ONE Portal Server 6.2 installation into a Sun Java System Portal Server 6 2004Q2 installation you must deploy it into the same brand of web container. In addition, the IBM Websphere Application Server and the BEA Weblogic Application Server must also run on a separate machine than where Sun Java System Identity Server 2004Q2 is installed and configured. See Installing Portal Server and Identity Server on Separate Machines for more information.
These are the high-level steps to upgrade from Sun ONE Portal Server 6.2 to Sun Java System Portal Server 6 2004Q2. (Subsequent chapters provide step-by-step instructions for performing the actual process.)
- Before you upgrade, back up any web container customized files related to Portal Server 6.2, including:
- Customized console JSP pages
- Customized authentication JSP pages
- JAR files for customized modules
- Customized sample Portal Server desktop
- Before you start the Sun ONE Portal Server upgrade process, shut down all instances on all nodes running the Sun ONE Portal Server software in your system. The upgrade process involves changes that do not allow the old Sun ONE Portal Server software version to be run at the same time as the new Sun Java System Portal Server software version.
- Upgrade all nodes running the Sun ONE Portal Server software in your system using the Java Enterprise System 2 installer to install shared components. See the Java Enterprise System 2004Q2 Installation Guide for more information.
- Upgrade the Sun ONE Identity Server 6.1 software to use shared components for the Sun Java System Identity Server 2004Q2 version on all nodes running the Sun ONE Portal Server software in your system using the Java Enterprise System 2 installer. See the Java Enterprise System 2004Q2 Installation Guide for more information on upgrading Identity Server.
- Apply to each node running the Sun ONE Portal Server 6.2 software patches specific to Sun Java System Portal Server 6 2004Q2. See Chapter 18, "Upgrading from Sun ONE Portal Server 6.2 to Sun Java System Portal Server 6 2004Q2".
- Restart your systems and allow user traffic.
Installing Portal Server and Identity Server on Separate MachinesFor Java Enterprise System 2004Q2, Sun Java System Portal Server can be installed and configured to run with either:
By default, Sun Java System Portal Server 6 2004Q2 and Sun Java System Identity Server 2004Q2, Sun Java System Directory Server 2004Q2, and a web container are installed on the same physical machine, with the following subcomponents selected for Sun Java System Identity Server:
You can install Sun Java System Portal server with a third-party web container (such as BEA WebLogic or IBM Websphere); however, Sun Java System Identity Server 2004Q2 supports third-party web containers differently. In this case, upgrading Portal Server for a third-party web container will require an additional machine and a reconfiguration of Portal Server and Identity Server software. SeeUpgrading Portal Server on a Third-Party Web Container for more information on third-party web container support
Upgrading Multiple NodesUse the following information to help plan the upgrade process when upgrading multiple nodes:
- Your upgraded Sun Java System Portal Server 6 2004Q2 system can consist of one or more nodes running the Sun ONE Portal Server 6.2 software, all of which share a single logical Sun™ ONE Directory Server for its LDAP data store. The upgrade process to Sun Java Enterprise System 2004Q2 involves changes that do not allow the Sun ONE Portal Server 6.2 software version to be run at the same time as the new Sun Java System Portal Server2004Q2 software version. Therefore, before you start the upgrade process you must completely shut down all instances running the Sun ONE Portal Server 6.2 software in your system.
- Once the LDAP data has been upgraded and the primary or first Sun ONE Portal Server 6.2 node has been upgraded to Sun Java System Portal Server 6 2004Q2, you may restore traffic to your upgraded Sun Java System Portal Server 6 2004Q2 system. Subsequent nodes may be upgraded while the primary Sun Java System Portal Server 6 2004Q2 node is in operation.