Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System Upgrade Guide for HP-UX  

Chapter 13
Communications Express

This chapter describes how to upgrade Communications Express to Java ES 2005Q4 (Release 4): Sun Java System Communications Express 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 CommsExpress-base. At least part of this path might have been specified as an installation directory when Web Server was initially installed. If not, the Java ES installer assigned a default value.

The default value of CommsExpress-base is /opt/sun/uwc.



Overview of Communications Express Upgrades

This section describes the following general aspects of Communications Express that impact upgrading to Java ES 2005Q4 (Release 4):

About Java ES Release 4 Communications Express

Java ES Release 4 Communications Express mostly represents bug fixes. There are a few new features with respect to Release 3: mail filter support, address book sharing, and proxy authentication.

Communications Express Upgrade Roadmap

Table 13-1 shows the supported Communications Express upgrade paths to Java ES Release 4.

Table 13-1  Upgrade Paths to Java ES Release 4:
Sun Java System Communications Express 6 2005Q4

Java ES Release

Communications Express Version

General Approach

Re-configuration Required

Release 3

Sun Java System Communications Express 6 2005Q1

Direct upgrade:

Perform by applying patches and re-configuring Messaging Server component.

Configuration files

Communications Express Data

The following table shows the type of data that could be impacted by an upgrade of Communications Express software.

Table 13-2  Communications Express Data Usage

Type of Data

Location

Usage

Configuration data:

Local configuration directory

var/CommsExpress-base/WEB-INF/config/uwcauth.properties

var/CommsExpress-base/WEB-INF/config/uwcconfig.properties

var/CommsExpress-base/WEB-INF/config/uwclogging.properties

MessagingServer-base/config/msg.conf and other configuration files for configuring Messaging Server MEM (webmail)

Configuration of Communications Express, including Messaging Server MEM (webmail)

Directory schema

Directory Server user/group directory

For user attributes needed to support end users

Compatibility Issues

Release 4 Communications Express does not introduce any interface changes and is backwardly compatible with earlier versions.

Communications Express Dependencies

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

Communications Express has dependencies on the following Java ES components:


Upgrading Communications Express from Java ES Release 3

This section includes information about upgrading Communications Express from Java ES 2005Q1 (Release 3) to Java ES 2005Q4 (Release 4). The section covers the following topics:

Introduction

When upgrading Java ES Release 3 Communications Express to Release 4, consider the following aspects of the upgrade process:

Communications Express Upgrade

This section describes how to perform an upgrade of Communications Express from Java ES Release 3 to Java ES Release 4. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Communications Express you should perform the tasks described below.

Verify Current Version Information

You can verify the current version of Communications Express by accessing the Communications Express login page, which shows the current version number.

Upgrade Communications Express 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, Communications Express has hard upgrade dependencies only on Messaging Server, Calendar Server, and Directory Preparation Tool. Upgrading of other Java ES Release 3 components upon which Communications Express depends is therefore optional.

However, if you choose to upgrade all Communications Express dependencies, they should be upgraded in the following order, all before you upgrade Communications Express. 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 Chapter 2, "Upgrading Java ES Shared Components".
  2. Directory Server. Instructions for upgrading Directory Server to Release 4 are provided in Chapter 3, "Directory Server and Administration Server".
  3. Web Container Software. Instructions for upgrading Web Server or Application Server are provided in Chapter 5, "Web Server" and Chapter 8, "Application Server", respectively.
  4. Access Manager (Access Manager SDK). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 9, "Access Manager".
  5. Directory Preparation Tool. Release 4 Directory Preparation Tool needs to have been run against Directory Server before configuring Release 4 Communications Express. If Release 4 Directory Preparation Tool has not already been run against Directory Server, upgrade Directory Preparation Tool to Release 4 and use it to modify and extend the schema of Directory Server in (see Chapter 10, "Directory Preparation Tool" for procedures).
  6. Messaging Server. Messaging Server components need to be upgraded to Release 4 to support Release 4 Communications Express. Instructions for upgrading Messaging Server to Release 4 are provided in Chapter 11, "Messaging Server".
  7. Calendar Server. Calendar Server components need to be upgraded to Release 4 to support Release 4 Communications Express. Instructions for upgrading Calendar Server to Release 4 are provided in Chapter 12, "Calendar Server".
Back Up Communications Express Data

The Communications Express upgrade from Release 3 to Release 4 requires re-configuration of Messaging Server MEM. The local changes can be rolled back, so there is no need to back up any data.

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 Communications Express

This section discusses considerations that impact the upgrade procedure for Communications Express followed by a description of the procedure itself.

Upgrade Procedure

The procedure documented below applies to all Communications Express components on the computer being updated.

  1. Obtain the required patches using the patch numbers from. Use this information to obtain the version numbers for the depots.
  2. Patches can be downloaded from:

    http://sunsolve.sun.com/.

  3. Log in as superuser.
  4. su root

  5. Stop Communications Express by stopping its web container.
  6. Web Server:

    WebServer-base/https-instanceName/stop

    Application Server:

    ApplicationServer-base/bin/asadmin stop-domain domainName

  7. If not already done, upgrade any shared components you wish to upgrade to Release 4.
  8. Apply the depots for Communications Express in Table 13-4.
  9. For example:

    swinstall -s ‘pwd’ <patch_ID>

  10. Confirm that the patch upgrade was successful:
  11. swlist |grep <patch_ID>

    The output should return the version details of patch <patch_ID>.

  12. Migrate configuration data from existing configuration files to Release 4 candidate configuration files.
  13. cd CommsExpress-base/sbin

    ./patch-config CommsExpress-base/install/patch

    This command prompts you for the current configuration directory and then backs up the existing configuration files. Then it merges configuration parameter values in these files with Release 4 template configuration files to create new Release 4 candidate configuration files. You should check these new files for possible conflicts, as described in the Special Installation Instructions section of the patch readme file.

  14. Install the Release 4 candidate configuration files, making them the active configuration.
  15. ./install-newconfig CommsExpress-base/install/patch

    This command installs the new Release 4 configuration files in their correct Release 4 locations.

  16. Remove the JSP class cache for Communications Express that is maintained by the web container.
  17. For the procedure, see the documentation for your web container (Web Server or Application Server).

  18. Restart Communications Express by restarting its web container.
  19. Web Server:

    WebServer-base/https-instanceName/start

    Application Server:

    ApplicationServer-base/bin/asadmin start-domain domainName

    --user admin_ID --password password

Verifying the Upgrade

You can verify the current version of Communications Express by accessing the Communications Express login page, which shows the current version number.

Once logged in, check the upgraded user interface for the new mail tab and old email and calendar events (if you are using those channels).

Also, you can check the log files for the various steps in the upgrade procedure:

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 Communications Express followed by the procedure itself.

Rollback Considerations

The procedure for rolling back the upgrade to Release 4 of Communications Express 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
  1. Log in as superuser.
  2. su root

  3. Stop Communications Express by stopping its web container.
  4. Web Server:

    WebServer-base/https-instanceName/stop

    Application Server:

    ApplicationServer-base/bin/asadmin stop-domain domainName

  5. Roll back the changes made to the Directory Server configuration directory being used by Communications Express.
  6. Roll back the re-configuration performed in Step 8.
  7. cd CommsExpress-base/sbin

    ./uninstall-newconfig CommsExpress-base/install/patch/

  8. Remove the patches in Table 13-4.
  9. swremove <patch_ID>

  10. Restart Communications Express by restarting its web container.
  11. Web Server:

    WebServer-base/https-instanceName/start

    Application Server:

    ApplicationServer-base/bin/asadmin start-domain domainName

    --user admin_ID --password password

Multiple Instance Upgrades

In some deployment architectures Communications Express is deployed on multiple computer systems to provide for scalability and to improve availability.

For example, you might have Communications Express components running on multiple computers with a load balancer to distribute the load.

In the case of load-balanced instances of Communications Express, you can perform a rolling upgrade in which you upgrade the Communications Express instances sequentially without interrupting service. You upgrade each instance of Communications Express while the others remain running. You perform the upgrade of each instance as described in Communications Express Upgrade.



Previous      Contents      Index      Next     


Part No: 819-4460-10.   Copyright 2006 Sun Microsystems, Inc. All rights reserved.