Sun Java Enterprise System Upgrade Guide for HP-UX |
Chapter 15
Portal ServerThis chapter describes how to upgrade Portal Server to Java ES 2005Q4 (Release 4): Sun Java System Portal Server 6 2005Q4. The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4.
Overview of Portal Server UpgradesThis section describes the following general aspects of Portal Server that impact upgrading to Java ES 2005Q4 (Release 4):
About Java ES Release 4 Portal Server
Java ES Release 4 Portal Server is functionally the same as Release 3, but contains bug fixes made since Release 3.
Portal Server Upgrade Roadmap
Table 15-1 shows the supported Portal Server upgrade paths to Java ES Release 4.
Portal Server Data
The following table shows the type of data that could be impacted by an upgrade of Portal Server software.
Compatibility Issues
Release 4 Portal Server does not introduce any interface changes. Portal Server components, including the mobile access component, are backwardly compatible with earlier versions.
Portal Server Dependencies
Portal Server dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Portal Server software. Changes in Portal Server interfaces or functions, for example, could require upgraded version of components upon which Portal Server depends. The need to upgrade such components depends upon the specific upgrade path.
Portal Server has dependencies on the following Java ES components:
- Shared components. Portal Server has dependencies on specific Java ES shared components (see Table 1-6).
- Web Container. Portal Server depends upon web container services, which can be provided either by Java ES Web Server or Java ES Application Server.
- Access Manager (or Access Manager SDK). Portal Server depends upon Access Manager to provide authentication and authorization services for end users, including single sign-on.
- Directory Server. Portal Server accesses user data stored in Directory Server. As a result, Portal Server upgrades might require extensions of directory schema.
Upgrading Portal Server from Java ES Release 3This section includes information about upgrading Portal Server from Java ES 2005Q1 (Release 3) to Java ES 2005Q4 (Release 4).
Note
The aforementioned upgrade path is not currently supported. For more information, see the Sun Java System Portal Server 6 2005Q4 Release Notes (http://docs.sun.com/doc/819-2575).
The section covers the following topics:
Introduction
When upgrading Java ES Release 3 Portal Server to Release 4, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version. Re-configuration of Portal Server is required only if the web container upon which Portal Server depends is upgraded or changed.
- Upgrade Dependencies. While Portal Server has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Portal Server is compatible with the Release 3 version of these components. Upgrade of these shared components, except for Mobile Access Core (MA Core), is therefore optional with respect to upgrade of Portal Server to Release 4.
In addition, Release 4 Portal Server is dependent upon a web container, Access Manager, and Directory Server as described in “Portal Server Dependencies” on page 306. However, these are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Portal Server to Release 4. Since JES4 portal uses libjss4.sl, sun-jss upgrade may be required.
Portal Server Upgrade
This section describes how to perform an upgrade of Portal Server from Java ES Release 3 to Java ES Release 4 on HP-UX platform.
Pre-Upgrade Tasks
Before you upgrade Portal Server you should perform the tasks described below.
Verify Current Version Information
You can verify the current version of Portal Server using the following command:
Table 15-3 Portal Server Version Verification Outputs1
Java ES Release
Portal Server Version Number
Release 3
6.3.1
Release 4
6.3.1
1The only difference between Release 3 and Release 4 is a patch. You can check for the Release 4 patches using the swlist <patch_ID>.
Upgrade Portal Server Dependencies
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. However, Portal Server has a hard upgrade dependency only on the Mobile Access Core (MA Core) shared component. Upgrading of other Java ES Release 3 components upon which Portal Server depends is therefore optional.
However, if you choose to upgrade all Portal Server dependencies, they should be upgraded in the following order, all before you upgrade Portal Server. You can skip any that might already have been upgraded.
- Shared Components. Instructions for upgrading Java ES shared components to Release 4 are provided in Upgrading Java ES Shared Components.
- Directory Server. Instructions for upgrading Directory Server to Release 4 are provided in Directory Server and Administration Server.
- Web Container Software. Instructions for upgrading Web Server or Application Server are provided in Web Server and Application Server, respectively.
- Access Manager (Access Manager SDK). Instructions for upgrading Access Manager to Release 4 are provided in Access Manager.
Back Up Release 3 Portal Server Configuration Information
Upgrade of Portal Server to Release 4 does not require the re-configuration of Portal Server software. However, as a safety measure you can back up the following directories where configuration information is stored:
Obtain Required Configuration Information and Passwords
You have to log in as superuser to perform the upgrade. If you are using Web Server as a web container, no configuration information is needed. However if you are using Application Server as a web container, you will need the Application Server administrator user ID and password.
Upgrading Portal Server
The upgrade of Portal Server software to Java ES Release 4 takes into account the following considerations:
- All Portal Server instances corresponding to the same installed Portal Server image are upgraded at the same time. All such instances should be shut down by shutting down the web container when patches are being applied to the installed image.
- The Release 4 Portal Server upgrade patches for HP-UX are shown in the following table:
Table 15-4 Patches1 to Upgrade Portal Server
Component
Patch-ID
Portal Server Core
121519-01
Portal Server Locale
121930-01
1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.
Upgrade Procedure
The procedure documented below applies to Portal Server on the computer where the upgrade is taking place.
- Obtain the required patches, based on Table 15-4.
Always use the latest patch revision available, unless directed to use a specific revision.
Patches can be downloaded from:
- Log in as superuser.
su root
- Stop Portal Server by stopping its web container.
Web Server:
WebServer-base/https-instanceName/stop
Application Server:
ApplicationServer-base/bin/asadmin stop-domain domainName
ApplicationServer-base/bin/asadmin stop-node-agent hostName_domainName
- If you have not already done so, upgrade the MA Core shared component and any others you wish to upgrade.
- Apply the appropriate Portal Server patch in Table 15-4.
swinstall -s <absolute-location>/<patch_ID> <patch_ID>
- Confirm that the patch upgrade was successful:
swlist <patch_ID>
- Restart Portal Server by restarting its web container.
Web Server:
WebServer-base/https-instanceName/start
Application Server:
ApplicationServer-base/bin/asadmin start-domain domainName --user admin_ID --password password
- Re-deploy the Portal Server web application to your web container.
PortalServer-base/bin/deploy redeploy
The redeploy command redeploys content from PortalServer-base/web-src to /var/PortalServer-base/https-hostName/deploy-dir/web-apps. Any customizations to the Portal Server web application should therefore be first made to /web-src and then deployed to /web-apps. Any changes you might make under /web-apps should be replicated in /web-src before running the deploy command, or such changes will be overwritten.
- Stop and restart the web container.
While not required in all situations, restarting the web container ensures that Portal Server starts in a clean state.
Verifying the Upgrade
The upgrade of Portal Server to Release 4 is verified by confirming that the upgrade patches have been properly applied. The steps for this verification were included in Upgrade Procedure.
In addition, you can use the following command:
See Table 15-3 for output values.
Beyond these tests of the patch upgrade you can verify that what previously worked still works and that bug fixes of interest have actually been fixed.
Post-Upgrade Tasks
There are no post-upgrade tasks beyond the steps described in Upgrade Procedure.
Rolling Back the Upgrade
This section describes considerations that impact the upgrade rollback procedure for Portal Server followed by the procedure itself.
Rollback Considerations
The procedure for rolling back the upgrade to Release 4 of Portal Server is pretty much the reverse of the procedure for upgrading to Release 4. The re-configurations are rolled back and the patches are removed.
Rollback Procedure
- Log in as superuser.
su root
- Stop Portal Server by stopping its web container.
WebServer-base/https-instanceName/stop (Web Server)
ApplicationServer-base/bin/asadmin stop-domain --d instanceName (Application Server)
- Remove the patches in Table 15-4.
swremove <patch_ID>
- Restart Portal Server by restarting its web container.
Web Server:
WebServer-base/https-instanceName/start
Application Server:
ApplicationServer-base/bin/asadmin start-domain domainName --user admin_ID --password password
- Re-deploy the Portal Server web application to your web container.
PortalServer-base/bin/deploy redeploy
The redeploy command redeploys content from PortalServer-base/web-src to /var/PortalServer-base/https-hostName/deploy-dir/web-apps. Any customizations to the Portal Server web application should therefore be first made to /web-src and then deployed to /web-apps. Any changes you might make under /web-apps should be replicated in /web-src before running the deploy command, or such changes will be overwritten.
- Stop and restart the web container.
While not required in all situations, restarting the web container ensures that Portal Server starts in a clean state.
Multiple Instance Upgrades
In some deployment architectures Portal Server is deployed on multiple computer systems to provide for scalability and to improve availability. For example, you might have Portal Server components running on multiple computers with a load balancer to distribute the load.
In the case of load-balanced instances of Portal Server, you can perform a rolling upgrade in which you upgrade the Portal Server instances sequentially without interrupting service. You upgrade each instance of Portal Server while the others remain running. You perform the upgrade of each instance as described in Portal Server Upgrade.