Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 2005Q4 Upgrade Guide 

Chapter 18
Portal Server Secure Remote Access

This chapter describes how to upgrade Portal Server Secure Remote Access 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. The chapter covers upgrades on both the Solaris and Linux operating systems:

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 18-1 shows the supported Portal Server Secure Remote Access upgrade paths to Java ES Release 4. The table applies to both Solaris and Linux operating systems.

Table 18-1  Upgrade Paths to Java ES Release 4:
Sun Java System Portal Server Secure Remote Access 6.3.1 2005Q4 

Java ES Release

Portal Server Secure Remote Access Version

General Approach

Re-configuration Required

Release 3

Sun Java System Portal Server Secure Remote Access 6.3.1 2005Q1

Direct upgrade:
Performed by applying patches.

None

Release 2

Sun Java System Portal Server Secure Remote Access 6.3 2004Q2

No direct upgrade:
Performed by upgrading first to Release 3 and then applying patches to upgrade to Release 4.

Configuration data

Release 1

Sun ONE Portal Server Secure Remote Access 6.2 (2003Q4)

No direct upgrade:
Performed by upgrading first to Release 3 and then applying patches to upgrade to Release 4.

Configuration data

Pre-dates Java ES releases

 

No direct upgrade.

 

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 18-2  Portal Server Secure Remote Access Data Usage

Type of Data

Location

Usage

Configuration data

PortalServerConfig-base/

Configuration of Portal Server Secure Remote Access

Directory schema

User data

Directory Server

Portal Server Secure Remote Access depends on user profile data that is stored in a 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:

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:

Release 3 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 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

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

Verify Current Version Information

You can verify the current version of Portal Server Secure Remote Access using the following commands:

Upgrade Portal Server Secure Remote Access 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 otherJava 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.

  1. Shared Components.  Instructions for upgrading Java ES shared components to Release 4 are provided in Upgrading Java ES Shared Components.
  2. Directory Server.  Instructions for upgrading Directory Server to Release 4 are provided in Chapter 4, "Directory Server and Administration Server".
  3. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager to Release 4 are provided in Chapter 11, "Access Manager".
  4. Portal Server.  Instructions for upgrading Portal Server are provided in Chapter 17, "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:

Obtain Required Configuration Information and Passwords

You have to log in as superuser to perform the upgrade.

Upgrading Release 3 Portal Server Secure Remote Access (Solaris)

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 (Solaris)

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

Upgrade Procedure (Solaris)

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

  1. Obtain the required patches, based on Table 18-4.

    2. Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. Stop Portal Server Secure Remote Access processes.

    4. /etc/init.d/gateway stop
    /etc/init.d/netletd stop
    /etc/init.d/rwproxyd stop

  4. If you have not already done so, upgrade the MA Core shared component and any others you wish to upgrade.

    5. See Upgrade Portal Server Secure Remote Access Dependencies.

  5. Apply the appropriate Portal Server patches in Table 18-4.

    6. Be sure to apply the Portal Server core patch before applying the two Portal Server localization patches.

    patchadd patch_ID

  6. Confirm that the patch upgrade was successful:

    7. showrev -p | grep patch_ID

    The output should return the versions of patch IDs applied in Step 5.

  7. Restart Portal Server Secure Remote Access processes.

    8. /etc/init.d/gateway start
    /etc/init.d/netletd start
    /etc/init.d/rwproxyd start

Upgrading Release 3 Portal Server Secure Remote Access (Linux)

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 (Linux)

The upgrade of Portal Server Secure Remote Access software to Java ES Release 4 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 4 upgrade patches differ from the Solaris patches.

The Release 4 Portal Server Secure Remote Access upgrade patches for Linux OS are the same as those used to upgrade Portal Server and are shown in the following table:

Table 18-5  Patches1 to Upgrade Portal Server Secure Remote Access on Linux 

Description

Patch ID and RPM names

Portal Server core

118952-12

  • sun-portal-core-6.3-25.12.i386.rpm

and a number of other RPMs for the Portal desktop and Portal Server mobile access.

Portal Server localization

119426-07

  • sun-portal-core-Locale-6.3-24.i386.rpm

and a large number of other RPMs for the Portal Server mobile access, configuration, identity, and other components.

Portal Server
localization configurator

118116-08

  • sun-portal-l10n-configurator-6.3-24.i386.rpm

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 (Linux)

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

Caution

An upgrade from Java ES Release 3 to Java ES Release 4 on Linux cannot be rolled back.

  1. Obtain the required patches using the patch numbers and RPM names from Table 18-4. Use this information to obtain the version numbers for the RPM.

    2. Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. Stop Portal Server Secure Remote Access processes.

    4. /etc/init.d/gateway stop
    /etc/init.d/netletd stop
    /etc/init.d/rwproxyd stop

  4. If you have not already done so, upgrade the MA Core shared component and any others you wish to upgrade.

    5. See Upgrade Portal Server Secure Remote Access Dependencies.

  5. Apply the RPMs for Portal Server core patch in Table 18-5.

    6. cd /tmp

    ./update

    The update script installs the RPMs and also ensures that the correct configurational changes occur as the result of the patch.

  6. Confirm that the patch upgrade was successful:

    7. rpm -qa | grep sun-portal-gateway

    The new version numbers of the RPMs should be returned.

  7. Apply the RPMs for the two Portal Server localization patches in Table 18-5.

    8. rpm -Fvh --replacefiles sun-portal-*-Locale-6.3-24.i386.rpm
    rpm -Fvh --replacefiles
         sun-portal-l10n-configurator-6.3-24.i386.rpm

  8. Confirm that the patch upgrade was successful:

    9. rpm -qa | grep sun-portal-l10n-configurator-6.3-24

    The upgrade revision numbers of the RPMs should be returned.

  9. Restart Portal Server Secure Remote Access processes.

    10. /etc/init.d/gateway start
    /etc/init.d/netletd start
    /etc/init.d/rwproxyd start

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. The steps for this verification were included in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).

In addition, you can use the following commands:

See Table 18-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 (Solaris) and Upgrade Procedure (Linux).

Rolling Back the Upgrade (Solaris)

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

Rollback Considerations (Solaris)

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 (Solaris)
  1. Log in as root or become superuser.

    2. su -

  2. Stop Portal Server Secure Remote Access processes.

    3. /etc/init.d/gateway stop
    /etc/init.d/netletd stop
    /etc/init.d/rwproxyd stop

  3. Remove the patches in Table 18-4.

    4. patchrm patch_ID

  4. Restart Portal Server Secure Remote Access processes.

    5. /etc/init.d/gateway start
    /etc/init.d/netletd start
    /etc/init.d/rwproxyd start

Multiple Instance Upgrades

In some deployment architectures Portal Server Secure Remote Access is deployed on multiple computer systems to provide for scalability and to improve availability. For example, you might have Portal Server Secure Remote Access components running on multiple computers with a load balancer to distribute the load.

In the case of load-balanced instances of Portal Server Secure Remote Access, you can perform a rolling upgrade in which you upgrade the Portal Server Secure Remote Access instances sequentially without interrupting service. You upgrade each instance of Portal Server Secure Remote Access while the others remain running. You perform the upgrade of each instance as described in Release 3 Portal Server Secure Remote Access Upgrade.

Upgrading Portal Server Secure Remote Access from Java ES Release 2

This section includes information about upgrading Portal Server Secure Remote Access from Java ES Release 2 to Java ES Release 4.

The upgrade is performed in two steps: by first upgrading Release 2 to Release 3 and then upgrading from Release 3 to Release 4. Because these two upgrade paths are distinct, this section will focus on the upgrade from Release 2 to Release 3.

Once the upgrade from Release 2 to Release 3 is complete, you can proceed with the upgrade from Release 3 to Release 4, covered in Upgrading Portal Server Secure Remote Access from Java ES Release 3.

This section covers the following topics regarding the upgrade from Release 2 to Release 3:

Introduction

When upgrading Java ES Release 2 Portal Server Secure Remote Access to Release 3, consider the following aspects of the upgrade process:

Release 2 Portal Server Secure Remote Access Upgrade

This section describes how to perform an upgrade of Portal Server Secure Remote Access from Java ES Release 2 to Java ES Release 3 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

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

Verify Current Version Information

You can verify the current version of Portal Server Secure Remote Access using the following commands:

See Table 18-3 for output values.

Upgrade Portal Server Secure Remote Access Dependencies

Java ES Release 3 does not support the coexistence of Release 2 and Release 3 shared components on a single computer.

You are therefore required to upgrade all local Java ES Release 2 components on which Portal Server Secure Remote Access depends to Release 3. For upgrade procedures see the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).

When you upgrade all local Portal Server dependencies on a computer, they should be upgraded in the following order, all before you upgrade Portal Server Secure Remote Access.

  1. Shared Components.  Instructions for upgrading Java ES shared components to Release 3 are provided in the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).
  2. Portal Server.  Portal Server Secure Remote Access is rarely dependent on a local Portal Server.
  3. Access Manager (Access Manager SDK).  Instructions for upgrading Access Manager to Release 3 are provided in the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).
  4. Directory Server.  Portal Server is rarely dependent on a local Directory Server.
Back Up Release 2 Portal Server Secure Remote Access Configuration Information

Upgrade of Portal Server Secure Remote Access to Release 3 does requires the re-configuration of Portal Server Secure Remote Access software. 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.

Upgrading Release 2 Portal Server Secure Remote Access (Solaris)

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 (Solaris)

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

Upgrade Procedure (Solaris)

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

If Portal Server Secure Remote Access is installed on the same computer as Portal Server, then follow the instructions found in Upgrading Portal Server from Java ES Release 3. Then proceed to Step 8.

  1. Obtain the required patches, based on Table 18-6.

    2. Be sure to download the exact patch revisions shown in Table 18-6

    Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. Stop Portal Server Secure Remote Access processes.

    4. /etc/init.d/gateway stop
    /etc/init.d/netletd stop
    /etc/init.d/rwproxyd stop

  4. If you have not already done so, upgrade all shared components and Access Manager (or Access Manager SDK).

    5. See Upgrade Portal Server Secure Remote Access Dependencies.

  5. If not yet running, start Directory Server and Access Manager (or Access Manager SDK).
  6. Apply the appropriate Portal Server patches in Table 18-6.

    7. Be sure to apply the patches in the order in which they are shown in Table 18-6, from top to bottom.

    patchadd patch_ID

  7. Confirm that the patch upgrade was successful:

    8. showrev -p | grep patch_ID

    The output should return the versions of patch IDs applied in Step 5.

  8. Re-configure Portal Server Secure Remote Access software:

    9. ksh

    $ cd PortalServer-base/lib
    $ ./upgradeSRA-04Q4-05Q1

  9. Restart Portal Server Secure Remote Access processes.

    10. /etc/init.d/gateway start
    /etc/init.d/netletd start
    /etc/init.d/rwproxyd start

  10. Re-configure Proxylet and Netlet services.
    1. Logon to the Access Manager console (AMCONSOLE) as the admin user.
    2. Remove Proxylet and Netlet services.

      3. Under the Identity Management tab, select the Services option. This lists all the registered services on the left panel. From SRA Configuration, select the Proxylet and Netlet check boxes. Scroll to the top on the left panel and click the Remove button. This will remove the Proxylet and Netlet service from the ORG level.

      To Verify this step manually, you may check your LDAP directory (under your organization) to make sure that the services (srapProxylet, srapNetlet) are really removed.

    3. Add the services again.

      4. Under Identity Management tab, select the Services option. Click the Add button under Services. This displays all the available services on the right panel. Choose proxylet and Netlet service check box and click OK. The newly added services will appear under SRA Configuration on your left panel.

    4. Click the newly added services and build the template file. Click the Save button.
    5. Add /portal/netlet/jnlpclient.jar and /portal/netlet/netletjsse.jar to non-Authenticated list of URLs under the gateway service. *
      • Click the Service Configuration tab.
      • Click the Gateway link under SRA Configuration. This lists all the available gateway profiles.
      • Choose the appropriate profile by clicking on the link.
      • Click the Security tab.
      • Add /portal/netlet/jnlpclient.jar in the edit field under Non-authenticated URLs and click the Add button.
      • Add /portal/netlet/netletjsse.jar in the edit field under Non-authenticated URLs and click the Add button.
      • Click the Save button at the bottom of the page.
    6. Restart your gateway server.

      7. /etc/init.d/gateway stop
      /etc/init.d/gateway start

  11. Upgrade Portal Server Secure Remote Access from Release 3 to Release 4.

    12. Follow the instructions in Upgrading Portal Server Secure Remote Access from Java ES Release 3.

Upgrading Release 2 Portal Server Secure Remote Access (Linux)

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 (Linux)

The upgrade of Portal Server Secure Remote Access software to Java ES Release 3 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 3 upgrade patches differ from the Solaris patches.

The Release 3 Portal Server Secure Remote Access upgrade patches for Linux OS are shown in the following table:

Table 18-7  Patches to Upgrade Portal Server Secure Remote Access to Release 3 on Linux 

Description

Patch ID and RPM names

Portal Server core

118020-16

sun-portal-module-6.3-25.i386.rpm

where module is any of about 70 different software modules

Mobile Access core

119515-01

  • sun-mobileaccess-1.0-25.i386.rpm
  • sun-mobileaccess-config-1.0-25.i386.rpm

Portal Server fixes

118952-01

  • sun-portal-core-6.3-xx.y.i386.rpm
  • sun-portal-configurator-6.3-xx.y.i386.rpm
  • sun-portal-mobileaccess-6.3-xx.y.i386.rpm
  • sun-portal-desktop-6.3-xx.y.i386.rpm
  • sun-portal-sample-6.3-xx.y.i386.rpm
  • sun-portal-mobileaccess-config-6.3-xx.y.i386.rpm

Upgrade Procedure (Linux)

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

If Portal Server Secure Remote Access is installed on the same computer as Portal Server, then follow the instructions found in Upgrading Portal Server from Java ES Release 3. Then proceed to Step 8.

  1. Obtain the required patches using the patch numbers and RPM names from Table 18-6. Use this information to obtain the version numbers for the RPM.

    2. Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

  2. Log in as root or become superuser.

    3. su -

  3. Stop Portal Server Secure Remote Access processes.

    4. /etc/init.d/gateway stop
    /etc/init.d/netletd stop
    /etc/init.d/rwproxyd stop

  4. If you have not already done so, upgrade all shared components and Access Manager (or Access Manager SDK).

    5. See Upgrade Portal Server Secure Remote Access Dependencies.

  5. If not yet running, start Directory Server and Access Manager (or Access Manager SDK).
  6. Apply the RPMs for Portal Server in Table 18-6.
    1. cd /tmp
    2. Unzip the 118020 patch file, read the README file and run the following script:

      3. ./upgradeportalrpms

      The update script installs the RPMs and also ensures that the correct configurational changes occur as the result of the patch.

    3. Unzip the 119515 patch file, and follow the instructions in its README file.
    4. Unzip the 118952 patch file, and follow the instructions in its README file.
  7. Confirm that the patch upgrade was successful:

    8. rpm -qa | grep sun-portal-gateway
    rpm -qa | grep sun-mobileaccess

    The new version numbers of the RPMs should be returned.

  8. Re-configure Portal Server Secure Remote Access software:

    9. ksh

    $ cd PortalServer-base/lib
    $ ./upgradeSRA-04Q4-05Q1

  9. Restart Portal Server Secure Remote Access processes.

    10. /etc/init.d/gateway start
    /etc/init.d/netletd start
    /etc/init.d/rwproxyd start

  10. Re-configure Proxylet and Netlet services.
    1. Logon to the Access Manager console (AMCONSOLE) as the admin user.
    2. Remove Proxylet and Netlet services.

      3. Under the Identity Management tab, select the Services option. This lists all the registered services on the left panel. From SRA Configuration, select the Proxylet and Netlet check boxes. Scroll to the top on the left panel and click the Remove button. This will remove the Proxylet and Netlet service from the ORG level.

      To Verify this step manually, you may check your LDAP directory (under your organization) to make sure that the services (srapProxylet, srapNetlet) are really removed.

    3. Add the services again.

      4. Under Identity Management tab, select the Services option. Click the Add button under Services. This displays all the available services on the right panel. Choose proxylet and Netlet service check box and click OK. The newly added services will appear under SRA Configuration on your left panel.

    4. Click the newly added services and build the template file. Click the Save button.
    5. Add /portal/netlet/jnlpclient.jar and /portal/netlet/netletjsse.jar to non-Authenticated list of URLs under the gateway service. *
      • Click the Service Configuration tab.
      • Click the Gateway link under SRA Configuration. This lists all the available gateway profiles.
      • Choose the appropriate profile by clicking on the link.
      • Click the Security tab.
      • Add /portal/netlet/jnlpclient.jar in the edit field under Non-authenticated URLs and click the Add button.
      • Add /portal/netlet/netletjsse.jar in the edit field under Non-authenticated URLs and click the Add button.
      • Click the Save button at the bottom of the page.
    6. Restart your gateway server.

      7. /etc/init.d/gateway stop
      /etc/init.d/gateway start

  11. Upgrade Portal Server Secure Remote Access from Release 3 to Release 4.

    12. Follow the instructions in Upgrading Portal Server Secure Remote Access from Java ES Release 3.

Verifying the Upgrade

The upgrade of Portal Server Secure Remote Access to Release 3 is verified by confirming that the upgrade patches have been properly applied. The steps for this verification were included in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).

In addition, you can use the following commands:

See Table 18-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 (Solaris) and Upgrade Procedure (Linux).

Rolling Back the Upgrade

The upgrade of Portal Server Secure Remote Access from Release 2 to Release 3 cannot be rolled back.

Multiple Instance Upgrades

In some deployment architectures Portal Server Secure Remote Access is deployed on multiple computer systems to provide for scalability and to improve availability. For example, you might have Portal Server Secure Remote Access components running on multiple computers with a load balancer to distribute the load.

In the case of load-balanced instances of Portal Server Secure Remote Access, you can perform a rolling upgrade in which you upgrade the Portal Server Secure Remote Access instances sequentially without interrupting service. You upgrade each instance of Portal Server Secure Remote Access while the others remain running. You perform the upgrade of each instance as described in Release 3 Portal Server Secure Remote Access Upgrade.



Previous      Contents      Index      Next     

Part No: 819-2331-13.   Copyright 2006 Sun Microsystems, Inc. All rights reserved.