|
| |
| Sun Java Enterprise System Upgrade Guide for Microsoft Windows | |
Chapter 13
Communications ExpressThis chapter describes how to upgrade Communications Express from previous Java ES versions 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.
Overview of Communications Express UpgradesThis 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.
Communications Express Data
The following table shows the type of data that could be impacted by an upgrade of Communications Express software.
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:
- Shared components. Communications Express has dependencies on specific Java ES shared components (see Table 1-6 on page 39).
- Web Container. Communications Express 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). Communications Express depends upon Access Manager to provide authentication and authorization services for end users, including single sign-on.
- Messaging Server. Communications Express is used to provide web-based access to Messaging Server. In fact Communications Express directly employs the Messaging Server MEM component to access other Messaging Server back-end components, such as the Messaging Server Store and MTA components.
- Calendar Server. Communications Express is used to provide web-based access to Calendar Server.
- Directory Server. Communications Express stores configuration data and also accesses user data stored in Directory Server. As a result, Communications Express upgrades might require upgrades of Directory Server or extensions of directory schema.
- Directory Preparation Tool. Communications Express uses the Directory Preparation Tool to prepare Directory Server to support Communications Express functions. As a result, Communications Express upgrades might depend upon preparation of the directory to support new functions.
Upgrading Communications Express from Java ES Release 3This 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:
- General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version and do the reconfiguration.
- Upgrade Dependencies. While Calendar Server has dependencies on a number of Java ES shared components (see Table 1-6 on page 39), Release 4 Calendar Server is compatible with the Release 3 versions of these components. Upgrade of these shared components is therefore optional with respect to upgrade of Calendar Server to Release 4.
In addition, Release 4 Communications Express is dependent upon a web container and on Access Manager, as described in “Communications Express Dependencies” on page 269. However, these are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Communications Express to Release 4.
However, Communications Express has hard upgrade dependencies on both Calendar Server, for which it provides web-based access, and on Messaging Server for which it also provides web-based access using the Messaging Server MEM component. Both Calendar Server and Messaging Server must therefore be upgraded to Release 4 before Communications Express can be upgraded to Release 4.
In addition, Release 4 Communications Express has a hard upgrade dependency on Directory Preparation Tool; Release 4 Directory Preparation Tool is required to prepare Directory Server for Communications Express functions.
- Backward Compatibility. Release 4 Communications Express is backwardly compatible with the Release 3 version.
- Upgrade Rollback. Rollback of the Release 4 upgrade of Communications Express to Release 3 is achieved by first removing the changes made to Directory Server, removing the patches applied during the upgrade and reconfiguring communications express.
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.
- 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".
- Web Container Software. Instructions for upgrading Web Server or Application Server are provided in Chapter 5, "Web Server" and Chapter 8, "Application Server", respectively.
- Access Manager (Access Manager SDK). Instructions for upgrading Access Manager to Release 4 are provided in Chapter 9 Access Manager on page.
- 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 (see Chapter 10, "Directory Preparation Tool" for procedures).
- 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".
- 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 Communications Express. So it is advisable to take backup of UWCCfg Defaults.properties file and other property files which are available in deployed location.
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.
- Communications Express includes components used to provide web-based access to Calendar Server and a Messaging Server MEM component used to provide web-based access to Messaging Server back-end components. The upgrade patches encompass all these components.
- All Communications Express components should be deployed to the same web container. The web container should be shut down before patches are applied to the installed image.
- The Release 4 Communications Express upgrade patches are shown in Table 1-3.
Upgrade Procedure
The procedure documented below applies to all Communications Express components on the computer being updated.
- Obtain the required patches from
- Log in as superuser.
- Stop Communications Express by stopping its web container.
Web Server:
WebServer-base/https-instanceName/stopsvr.bat
Application Server:
ApplicationServer-base/bin/asadmin stop-domain domainName
- If not already done, upgrade any shared components you wish to upgrade to Release 4.
- Take the back up of properties files.
- Apply the appropriate for Communications Express patches in Table 1-3.
execute <Patch-id>.exe
- If Web Server is the container
Re-run the configurator
- If Application Server is the configurator
Undeploy CommunicationsExpress from the Application Server and then run the configurator.
- Restart Communications Express by restarting its web container.
Web Server:
WebServer-base\https-instanceName\startsvr.bat
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).
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
- Log in as superuser.
- Stop Communications Express by stopping its web container.
Web Server:
WebServer-base/https-instanceName/stopsvr.bat
Application Server:
ApplicationServer-base/bin/asadmin stop-domain domainName
- Roll back the changes made to the Directory Server configuration directory being used by Communications Express.
- Remove the patches.
execute Uninstall_<Patch-id>.bat
Rerun the configurator
- Restart Communications Express by restarting its web container.
Web Server:
WebServer-base/https-instanceName/startsvr.bat
Application Server:
ApplicationServer-base/bin/asadmin start-domain domainName
--user admin_ID --password password