Chapter 16 Portal Server Secure Remote Access

This chapter describes how to upgrade Portal Server Secure Remote Access from previous Java ES versions to Java ES 2005Q4 (Release 4): Sun Java System Portal Server Secure Remote Access 6 2005Q4.

The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4.



Note	File locations in this chapter are specified with respect to a directory path referred to as PortalServer-base. It is the same directory path used for Portal Server file locations. At least part of this path might have been specified as an installation directory when Portal Server was initially installed. If not, the Java ES installer assigned a default value. The default value of PortalServer-base is C:/Sun/PortalServer.

Overview of Portal Server Secure Remote Access Upgrades

This section describes the following general aspects of Portal Server Secure Remote Access that impact upgrading to Java ES 2005Q4 (Release 4):

About Java ES Release 4 Portal Server Secure Remote Access

Java ES Release 4 Portal Server Secure Remote Access mostly represents bug fixes. There is no major new functionality with respect to Release 3.

Portal Server Secure Remote Access Upgrade Roadmap

Table 16-1 shows the supported Portal Server Secure Remote Access upgrade paths to Java ES Release 4.

Table 16-1 Upgrade Paths to Java ES Release 4: Sun Java System Portal Server Secure Remote Access 6 2005Q4 S
Java ES Release	Component	General Approach	Re-configuration Required
Release 3	Sun Java System Portal Server Secure Remote Access 6 2005Q1	Direct upgrade: Performed by applying patches.	Yes

Portal Server Secure Remote Access Data

The following table shows the type of data that could be impacted by an upgrade of Portal Server Secure Remote Access software.

Table 16-2 Portal Server Secure Remote Access Data Usage
Type of Data	Location	Usage
Configuration data	PortalServer-base/Config	Configuration of Portal Server Remote Access
Directory schema User data	Directory Server	Portal Server Secure Remote Access depends on user profile data that is stored in the directory.
Dynamic application data	None	Portal Server Secure Remote Access does not persistently store application data such as session state.

Compatibility Issues

Release 4 Portal Server Secure Remote Access does not introduce any interface changes. Portal Server Secure Remote Access is backwardly compatible with earlier versions.

Portal Server Secure Remote Access Dependencies

Portal Server Secure Remote Access dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Portal Server Secure Remote Access software. Changes in Portal Server Secure Remote Access interfaces or functions, for example, could require upgraded version of components upon which Portal Server Secure Remote Access depends. The need to upgrade such components depends upon the specific upgrade path.

Portal Server Secure Remote Access has dependencies on the following Java ES components:

Shared components. Portal Server has dependencies on specific Java ES shared components (see Table 1-6).

Portal Server. Portal Server Secure Remote Access provides secure remote access to Portal 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 Secure Remote Access from Java ES Release 3

This section includes information about upgrading Portal Server Secure Remote Access from Java ES 2005Q1 (Release 3) to Java ES Release 4. The section covers the following topics:

Introduction

When upgrading Java ES Release 3 Portal Server Secure Remote Access 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 Secure Remote Access is not required.

Upgrade Dependencies. While Portal Server Secure Remote Access has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Portal Server Secure Remote Access 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 Secure Remote Access to Release 4.

In addition, Release 4 Portal Server Secure Remote Access is dependent upon Portal Server, Access Manager, and Directory Server as described in Portal Server Secure Remote Access Dependencies. Upgrade of Portal Server Secure Remote Access to Release 4 requires that Portal Server also be upgraded. However, the dependencies on Access Manager and Directory Server are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Portal Server Secure Remote Access to Release 4.

Backward Compatibility. Release 4 Portal Server Secure Remote Access is backwardly compatible with the Release 3 version.

Upgrade Rollback. Rollback of the Release 4 upgrade of Portal Server Secure Remote Access to Release 3 is achieved by rolling back the patches applied during the upgrade.

Portal Server Secure Remote Access Upgrade

This section describes how to perform an upgrade of Portal Server Secure Remote Access from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Portal Server Secure Remote Access you should perform the tasks described below

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 Secure Remote Access dependencies, they should be upgraded in the following order, all before you upgrade Portal Server Secure Remote Access. 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 Chapter 2, "Upgrading Java ES Shared Components."

Directory Server. Instructions for upgrading Directory Server to Release 4 are provided in Chapter 3, "Directory Server and Administration Server."

Access Manager (Access Manager SDK). Instructions for upgrading Access Manager to Release 4 are provided in Access Manager.

Portal Server. Instructions for upgrading Portal Server are provided in Chapter 15, "Portal Server."

Back Up Release 3 Portal Server Secure Remote Access Configuration Information

Upgrade of Portal Server Secure Remote Access to Release 4 does not require the re-configuration of Portal Server Secure Remote Access software. However, as a safety measure you can back up the following directories where configuration information is stored:

Upgrading Portal Server Secure Remote Access

This section discusses considerations that impact the upgrade procedure for Portal Server Secure Remote Access followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Portal Server Secure Remote Access software to Java ES Release 4 takes into account the following considerations:

All Portal Server Secure Remote Access instances corresponding to the same installed Portal Server Secure Remote Access image are upgraded at the same time. All such instances should be shut down when patches are being applied to the installed image.

Upgrade Procedure

The procedure documented below applies to Portal Server Secure Remote Access on the computer where the upgrade is taking place.

Obtain the required patches, based on Table 1-3.

Patches can be downloaded from:

http://sunsolve.sun.com

Stop Portal Server Secure Remote Access processes.

net stop SRA.Gatway.<instancename>

net stop SRA.netlet.<instancename>

net stop SRA.rewriter.<instancename>

Apply the appropriate Portal Server patches in Table 1-3.

Run the <Patch-id>.exe

Restart Portal Server Secure Remote Access processes.

net start SRA.Gatway.<instancename>

net start SRA.netlet.<instancename>

net start SRA.rewriter.<instancename>

Verifying the Upgrade

The upgrade of Portal Server Secure Remote Access to Release 4 is verified by confirming that the upgrade patches have been properly applied.

Post-Upgrade Tasks

Rolling Back the Upgrade

This section describes considerations that impact the upgrade rollback procedure for Portal Server Secure Remote Access followed by the procedure itself.

Rollback Considerations

The procedure for rolling back the upgrade to Release 4 of Portal Server Secure Remote Access 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