|
| |
| Sun Java Communications Suite 5 Upgrade Guide | |
Chapter 6
Upgrading Communications ExpressThis chapter describes how to upgrade previous versions of Communications Express to Sun Java System Communications Express 6.3. The chapter provides an overview of upgrade considerations for the different upgrade paths. The chapter covers upgrades on both the Solaris and Linux operating systems:
Overview of Communications Express UpgradesThis section describes the following general aspects of Communications Express that impact upgrade:
About Communications Express 6.3
Communications Express 6.3 represents a major release with respect to Communications Express 6.2 (Java Enterprise System 2005Q4). Communications Express supports features such as password encryption in configuration files, configuration tool automation, shared and multiple address books, and calendar attachments.
In addition, several of its internal implementations have been changed, impacting the upgrade procedure:
- The use of a mail proxy servlet filter to de-couple Communications Express from the Messaging Server MEM component. The MEM component has changed this release, and need not run on the same computer as Communications Express. As a result of this de-coupling, you need to migrate customizations from the current MEM location to a new Communications Express location. (For information about changes in Messaging Server MEM, see About Messaging Server 6.3.)
- The previous dependency of Communications Express upon Access Manager (Access Manager SDK) to support Schema 2 directory lookups has been removed in version 6.3. However Access Manager (Access Manager SDK) is still needed to provide single sign-on authentication and authorization services for end users.
Changes in Communications Express File Locations
Prior to Communications Suite 5, the html/js/gif/jpg files used by Communications Express to display the Mail User Interface resided in the Messaging Server packaging (in the msg-svr-base/config/html directory). Beginning with Communications Suite 5, Communications Express picks up these files from the Communications Express packaging. If you are upgrading to Communications Suite 5, you will use a Communications Express migration script to move the user customizations from the Messaging Server area to the Communications Express area. This is a one-time migration move.
For a Messaging Server upgrade from a pre-Communications Suite 5 version to a Communications Suite 5 version (or later), the Communications Express files in Messaging Server packaging will be removed. A copy of the entire config/html area is placed in msg-svr-base/data/preJES5/config/html which the Communications Express migration script will use. In addition, a copy of the previous version of saved files in lib/config-templates/html will be saved to msg-svr-base/data/preJES5/lib/config-templates/html.
When upgrading Communications Express and its Messaging front-end server from pre-Communications Suite 5 to Communications Suite 5 (or later), it is recommended that you upgrade Messaging Server first.
Note that in Communications Suite 5, you no longer need to have the mshttpd process running on the back-end servers since mshttpd can talk IMAP to the back-end servers. In addition, in Communications Express no longer requires that the Messaging Server mshttpd be running on the same machine as Communications Express since the html/js/gif files are now being loaded from the Communications Express area.
Communications Express Upgrade Roadmap
Table 6-1 shows the supported Communications Express upgrade paths to Communications Express 6.3. The table applies to both Solaris and Linux operating systems.
Communications Express Data
The following table shows the type of data that could be impacted by an upgrade of Communications Express software.
Communications Express Upgrade Strategy
Your strategy for upgrading Communications Express depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Communications Suite components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.
This section is to particularize that general discussion to Communications Express by presenting issues that might influence your Communications Express upgrade plan.
Compatibility Issues
Communications Express does not introduce any public interface changes and is therefore backwardly compatible with Communications Express 6.2 (Java Enterprise System 2005Q4), however changes in internal implementations impact the upgrade procedure.
In particular, the de-coupling of Communications Express from the Messaging Server MEM webmail server component requires you to migrate customizations to a new location, and allows you to move the (webmail server) MEM component to a remote computer if you wish.
Communications Express Dependencies
Communications Express dependencies on other Communications Suite 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 Communications Suite components:
- Shared components. Communications Express has dependencies on specific Communications Suite shared components (see Table 1-6).
- Web Container. Communications Express depends upon web container services, which can be provided either by Java Enterprise System Web Server or Java Enterprise System Application Server.
- Access Manager (or Access Manager SDK). Access Manager (Access Manager SDK) provide for single sign-on authentication and authorization services for end users. This is an optional dependency.
- 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.
Web Container Upgrade Scenarios
Communications Express can be deployed in a web container provided by either Web Server or Application Server. As a result, the upgrade of Communications Express can be complicated by the possibility of also having upgraded the web container in which it is deployed. In this regard, there are a number of web container upgrade scenarios possible, enumerated in the following table.
You must be careful when upgrading Communications Express (for example when re-configuring or re-deploying Communications Express) to provide values appropriate to the upgrade scenario in Table 6-3 that applies, especially when there is a major version upgrade of the web container.
Upgrading from Communications Express 6.2 (Java Enterprise System 2005Q4)This section includes information about upgrading from Communications Express 6.2 (Java Enterprise System 2005Q4). The section covers the following topics:
Introduction
When upgrading Communications Express 6.2 (Java Enterprise System 2005Q4) Communications Express 6.3, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is performed by applying patches to the Communications Express 6.2 (Java Enterprise System 2005Q4) version. Re-configuration of Communications Express, including the new webmail implementation, is achieved using configuration utilities.
- Upgrade Dependencies. While Communications Express has dependencies on a number of Communications Suite shared components (see Table 1-6), Calendar Server is compatible with the Communications Express 6.2 (Java Enterprise System 2005Q4) versions of these components. Upgrade of these shared components is therefore optional with respect to upgrade of Calendar Server to 6.3.
However, Communications Express has hard upgrade dependencies on both Calendar Server and Messaging Server, for which it provides web-based access. Both Calendar Server and Messaging Server must be upgraded to version 6.3 before Communications Express can be upgraded to 6.3.
In addition, Communications Express 6.3 has a hard upgrade dependency on Directory Preparation Tool; Directory Preparation Tool is required to prepare Directory Server for Communications Express functions.
Communications Express 6.3 is also dependent upon a web container, as described in Communications Express Dependencies. However, this is a soft upgrade dependency; upgrade of the web container is optional with respect to upgrade of Communications Express to 6.3.
- Backward Compatibility. Communications Express 6.3 is backwardly compatible with Communications Express 6.2 (Java Enterprise System 2005Q4), even though there have been changes in its internal implementation.
- Upgrade Rollback. Rollback of the 6.3 upgrade of Communications Express to Communications Express 6.2 (Java Enterprise System 2005Q4) is achieved by removing changes to local configuration files and then removing the patches applied during the upgrade.
- Platform Issues. The general approach for upgrading Communications Express is the same on both Solaris and Linux operating systems, however the patching technologies are different. The upgrade process therefore includes platform-specific procedures.
Communications Express 6.2 (Java Enterprise System 2005Q4) Upgrade
This section describes how to perform an upgrade from Communications Express 6.2 (Java Enterprise System 2005Q4) 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 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.
http://hostName:port/uwc/auth
Upgrade Communications Express Dependencies
It is generally recommended that all Communications Suite components on a computer system (and in a computing environment) be upgraded to Communications Suite 6.3. However, Communications Express has hard upgrade dependencies only on Messaging Server, Calendar Server, and Directory Preparation Tool. Upgrading of other Communications Suite 5 product 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 Communications Suite shared components are provided in Chapter 2, "Upgrading Communications Suite Shared Components".
- Directory Server. Instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
- Web Container Software. Instructions for upgrading Web Server or Application Server are provided in the Java Enterprise System Upgrade Guide.
- Directory Preparation Tool. Directory Preparation Tool needs to have been run against Directory Server before configuring Communications Express. If the Directory Preparation Tool has not already been run against Directory Server, upgrade Directory Preparation Tool and use it to modify and extend the schema of Directory Server. See the Chapter 3, "Directory Preparation Tool" for procedures.
- Messaging Server. Messaging Server components need to be upgraded to 6.3 to support Communications Express 6.3. Instructions for upgrading Messaging Server to 6.3 are provided in Chapter 4, "Upgrading Messaging Server".
- Calendar Server. Calendar Server components need to be upgraded to support Communications Express. Instructions for upgrading Calendar Server to 6.3 are provided in Chapter 5, "Upgrading Calendar Server".
Back Up Communications Express Data
The Communications Express upgrade from Communications Express 6.2 (Java Enterprise System 2005Q4) to 6.3 requires re-configuration of the webmail implementation. The local changes can be rolled back, but as a precaution you can back up the uwcconfig.properties and uwcauth.properties files.
Obtain Required Configuration Information and Passwords
You have to log in as superuser to perform the upgrade. Depending on the web container you are using, you might need the corresponding administrator user ID and password.
Upgrading Communications Express 6.2 (Solaris)
This section discusses considerations that impact the upgrade procedure for Communications Express followed by a description of the procedure itself.
Upgrade Considerations (Solaris)
The upgrade of Communications Express software takes into account the following considerations:
- Communications Express includes components used to provide web-based access to Calendar Server and Messaging Server back-end components. The upgrade patches encompass changes in all these components.
- The Messaging Server MEM component used to implement webmail has been de-coupled from Communications Express. As a result, the (webmail server) MEM need not run locally. (To move the MEM component to a remote computer, see Post-Upgrade Tasks.) In addition, customizations need to be moved from their current MEM location to a new Communications Express location.
- 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 Communications Express upgrade patches for Solaris OS are shown in the following table:
Table 6-5 Patches1 to Upgrade Communications Express on Solaris
Description
SPARC
Solaris 9 & 10
X86
Solaris 9 & 10
Communications Express core
122793-12
122794-12
Communications Express localization
118042-19
118042-18
1Patch revision numbers are the minimum required for upgrading Communications Express. If newer revisions become available, use the newer ones instead of those shown in the table.
Upgrade Procedure (Solaris)
The procedure documented below applies to all Communications Express components on the computer being updated.
- Obtain the required patches, based on Table 6-5.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- Stop Communications Express by stopping its web container.
Web Server 6.x:
WebServer-base/https-instanceName/stopWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/stopserv
Instance Server--
WebServer7Config-base/https-configName/bin/stopservApplication Server 8.x:
AppServer8-base/bin/asadmin stop-domain --user admin_ID
--password password domainName- If you have not already done so, synchronize all shared comonents to Release 5.
See Upgrade Communications Express Dependencies.
- Apply the appropriate Communications Express core and, if needed, localization patches in Table 6-5, in that order.
patchadd patch_ID
- Confirm that the patch upgrades were successful:
showrev -p | grep uwc
The output should return the versions of patch IDs applied in Step 5.
- Migrate configuration data from existing configuration files to the 6.3 configuration files.
- Move configuration data from existing configuration files to 6.3 configuration files for both core and, if needed, localization patch files.
cd CommsExpress-base/sbin
./patch-config CommsExpress-base/install/patch/patch_ID
[-m MessagingServer-base]where the -m option migrates customizations from their current MEM location to a new location. If you omit this option, you will be prompted for this location the first time you run patch-config, but not on subsequent runs.
The patch-config script prompts you for the current Communications Express configuration directory and then backs up the existing configuration files. It then prompts for new configuration parameters needed for the upgrade:
Table 6-6 Information Requested by patch-config Script
Information
Description
Webmail proxy admin id
Admin user id for webmail proxy authentication: must match setting on Messaging Server Store (see Post-Upgrade Tasks for Messaging Server Version 6.3)
Webmail proxy admin password
Admin password id for webmail proxy authentication: must match setting on Messaging Server Store (see Post-Upgrade Tasks for Messaging Server Version 6.3)
Webmail authentication only ssl
(true/false)Enable proxy authentication to webmail from CE over SSL
Webmail port [80]
Webmail server non-ssl port
Webmail ssl port (Optional) [443]
Webmail server ssl port (needed only if webmail authentication is set to true)
Directory Server Base DN
Required for direct access to Directory Server (rather than by way of Access Manager SDK)
Access Manager SSL login URL
Support SSO using AM SSL login URL
The patch-config script then merges configuration parameter values in these files with template configuration files to create new 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.
- Install the candidate configuration files, making them the active configuration. Do this for both core and, if needed, localization files
./install-newconfig CommsExpress-base/install/patch/patch_ID
This command installs the new configuration files in their correct locations.
- Reconfigure the Messaging Server MEM to enable integration with Communications Express.
The configutil command below is needed in addition to those used when upgrading Messaging Server MEM to version 6.3, as documented in Chapter 4, "Upgrading Messaging Server," in the section Post-Upgrade Tasks for Messaging Server Version 6.3.
MessagingServer-base/sbin/configutil
-o local.webmail.sso.uwcenabled -v 1The configutil commands below are also available if required:
MessagingServer-base/sbin/configutil
-o service.http.allowadminproxy -v yesMessagingServer-base/sbin/configutil
-o local.service.http.proxy.admin -v adminMessagingServer-base/sbin/configutil
-o local.service.http.proxy.adminpass -v orionorionMessagingServer-base/sbin/configutil
-o local.webmail.sso.uwcenabled -v 1- Remove the JSP class cache for Communications Express that is maintained by the web container.
For the procedure, see the documentation for your web container (Web Server or Application Server).
- Restart Communications Express by restarting its web container.
Web Server 6.x:
WebServer-base/https-instanceName/startWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/startserv
Instance Server--
WebServer7Config-base/https-configName/bin/startservApplication Server 8.x:
To start the Application Server instance, you start the Domain Administration Server (DAS), then the node agent under which the instance was migrated, and finally the instance itself using the following commands:AppServer8-base/sbin/asadmin start-domain --user admin_ID
--password password domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, the following conventions are used:
Upgrading Communications Express 6.2 (Linux)
This section discusses considerations that impact the upgrade procedure for Communications Express followed by a description of the procedure itself.
Upgrade Considerations (Linux)
The upgrade of Communications Express software on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux upgrade patches differ from the Solaris patches.
The Communications Express upgrade patches for Linux OS are shown in the following table:
Table 6-7 Patches1 to Upgrade Communications Express on Linux
Description
Patch ID and RPM names
Communications Express core
122795-12
Communications Express localization
118044-19
1Patch revision numbers are the minimum required for Communications Express upgrade. 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 all Communications Express components on the computer being updated.
Caution
An upgrade from Communications Express 6.2 (Java Enterprise System 2005Q4) to Communications Express 6.3 on Linux cannot be rolled back.
- Obtain the required patches using the patch numbers and RPM names from Table 6-7. Use this information to obtain the version numbers for the RPM.
Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
- Log in as root or become superuser.
su -
- Stop Communications Express by stopping its web container.
Web Server 6.x:
WebServer-base/https-instanceName/stopWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/stopserv
Instance Server--
WebServer7Config-base/https-configName/bin/stopservApplication Server 8.x:
AppServer8-base/bin/asadmin stop-domain --user admin_ID
--password password domainName- If you have not already done so, synchronize all shared components to Release 5.
See Upgrade Communications Express Dependencies.
- Apply the RPMs corresponding to the core and, if needed, localization patches for Communications Express in Table 6-7, in that order.
For example:
rpm -Fvh sun-uwc-6.1-10.2.i386.rpm
To apply localization patches, additional prepatch and postpatch scripts need to be executed. For example:
sh 118-044-19.prepatch
rpm -Fvh sun-uwc-<locale>-6.1-11.11.i386.rpm
sh 118044-19.postpatch
- Confirm that the patch upgrades were successful:
rpm -qa | grep uwc
The output should return the version of RPM in Step 5.
- Migrate configuration data from existing configuration files to 6.3 configuration files.
- Move configuration data from existing configuration files to 6.3 candidate configuration files for both core and, if needed, localization patch files.
cd CommsExpress-base/sbin
./patch-config CommsExpress-base/install/patch/patch_ID
[-m MessagingServer-base]where the -m option migrates customizations from their current MEM location to a new location. If you omit this option, you will be prompted for this location the first time you run patch-config, but not on subsequent runs.
The patch-config script prompts you for the current configuration directory and then backs up the existing configuration files. It then prompts for new configuration parameters needed for the upgrade:
Table 6-8 Information Requested by patch-config Script
Information
Description
Webmail proxy admin id
Admin user id for webmail proxy authentication: must match setting on Messaging Server Store (see Post-Upgrade Tasks for Messaging Server Version 6.3)
Webmail proxy admin password
Admin password id for webmail proxy authentication: must match setting on Messaging Server Store (see Post-Upgrade Tasks for Messaging Server Version 6.3)
Webmail authentication only ssl
(true/false)Enable proxy authentication to webmail from CE over SSL
Webmail port [80]
Webmail server non-ssl port
Webmail ssl port (Optional) [443]
Webmail server ssl port (needed only if webmail authentication is set to true)
Directory Server Base DN
Required for direct access to Directory Server (rather than by way of Access Manager SDK)
Access Manager SSL login URL
Support SSO using AM SSL login URL
The patch-config script then merges configuration parameter values in these files with the 6.3 template configuration files to create new configuration files. You should check these new files for possible conflicts, as described in the Special Installation Instructions section of the patch readme file.
- Install the 6.3 candidate configuration files, making them the active configuration. Do this for both core and, if needed, localization files
./install-newconfig CommsExpress-base/install/patch/patch_ID
This command installs the new 6.3 configuration files in their correct 6.3 locations.
- Reconfigure the Messaging Server MEM to enable integration with Communications Express.
The configutil command below is needed in addition to those used when upgrading Messaging Server to 6.3, as documented in Chapter 4, "Upgrading Messaging Server," in the section Post-Upgrade Tasks for Messaging Server Version 6.3.
msg-svr-base/sbin/configutil
-o local.webmail.sso.uwcenabled -v 1- Remove the JSP class cache for Communications Express that is maintained by the web container.
For the procedure, see the documentation for your web container (Web Server or Application Server).
- Restart Communications Express by restarting its web container.
Web Server 6.x:
WebServer-base/https-instanceName/startWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/startserv
Instance Server--
WebServer7Config-base/https-configName/bin/startservApplication Server 8.x:
To start the Application Server instance, you start the Domain Administration Server (DAS), then the node agent under which the instance was migrated, and finally the instance itself using the following commands:AppServer8-base/sbin/asadmin start-domain --user admin_ID
--password password domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, the following conventions are used:
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.
http://hostName:port/uwc/auth
See Table 6-4 for version values.
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:
CommsExpress-base/install/patch/122795-12
CommsExpress-base/install/patch/122795-12/patch-config_20050729164754.log
CommsExpress-base/install/patch/122795-12/install-newconfig_20050729164838.logPost-Upgrade Tasks
As mentioned in About Communications Express 6.3, the (webmail server) MEM component has been de-coupled from Communications Express so that the MEM can reside remotely.
If you wish to move the MEM component to a remote computer, you need to specify the hostname and port number of the remote (webmail server) MEM component by manually editing the following configuration file:
var/CommsExpress-base/WEB-INF/config/uwcconfig.properties
The relevant parameters are shown in the table below.
Rolling Back the Upgrade (Solaris)
This section describes considerations that impact the upgrade rollback procedure for Communications Express followed by the procedure itself.
Rollback Considerations (Solaris)
The procedure for rolling back the upgrade from 6.3 of Communications Express is pretty much the reverse of the procedure for upgrading to 6.3. The re-configurations are rolled back and the patches are removed.
Rollback Procedure (Solaris)
- Log in as root or become superuser.
su -
- Stop Communications Express by stopping its web container.
Web Server 6.x:
WebServer-base/https-instanceName/stopWeb Server 7.0:
Admin Server--
WebServer7Config-base/admin-server/bin/stopserv
Instance Server--
WebServer7Config-base/https-configName/bin/stopservApplication Server 8.x:
AppServer8-base/bin/asadmin stop-domain --user admin_ID
--password password domainName- Roll back the re-configuration performed in Step 7.
The approach depends on that used to perform the re-configuration:
Remote Messaging Server MEM.
- Start up the Communications Express configurator script.
CommsExpress-base/sbin/uwc-config
- Revert configuration information to Communications Express 6.2 (Java Enterprise System 2005Q4) values.
Local Messaging Server MEM.
cd CommsExpress-base/sbin
./uninstall-newconfig CommsExpress-base/install/patch/patch_ID- Remove the patches in Table 6-5.
patchrm patch_ID
- Restart Communications Express by restarting its web container.
Web Server:
WebServer-base/https-instanceName/startApplication Server 8.x:
To start the Application Server instance, you start the Domain Administration Server (DAS), then the node agent under which the instance was migrated, and finally the instance itself using the following commands:AppServer8-base/sbin/asadmin start-domain --user admin_ID
--password password domainNameAppServer8-base/sbin/asadmin start-node-agent
--startinstances=false --user admin_ID --password password
nodeagentNameAppServer8-base/sbin/asadmin start-instance --user admin_ID
--password password instanceNameIn the above commands, the following conventions are used:
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 6.2 (Java Enterprise System 2005Q4) Upgrade.
Upgrading from Communications Express 6 (Java Enterprise System 2005Q1)The procedure for upgrading Communications Express 6 (Java Enterprise System 2005Q1) to Communications Express 6.3 is the same as that for upgrading Communications Express 6.2 (Java Enterprise System 2005Q4) Communications Express to 6.3.
To upgrade Communications Express 6 (Java Enterprise System 2005Q1) to Communications Express 6.3, use the instructions in Upgrading from Communications Express 6.2 (Java Enterprise System 2005Q4), except substitute Communications Express 6 (Java Enterprise System 2005Q1) wherever Communications Express 6.2 (Java Enterprise System 2005Q4) is referenced.
Upgrading from Communications Express 6 (Java Enterprise System 2004Q2)The procedure for upgrading Communications Express 6 (Java Enterprise System 2004Q2) to Communications Express 6.3 is the same as that for upgrading Communications Express 6.2 (Java Enterprise System 2005Q4) to Communications Express 6.3, with a couple of exceptions, noted below.
Upgrade Communications Express Dependencies
The pre-upgrade tasks for upgrading Communications Express 6 (Java Enterprise System 2004Q2) to Communications Express 6.3 are similar to those for upgrading Communications Express 6.2 (Java Enterprise System 2005Q4) to Communications Express 6.3, with the exception that the upgrade of Communications Express dependencies must include the upgrading to 6.3 of all shared components (see Table 1-6) and all locally-resident product components upon which Communications Express depends.
When upgrading 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 Communications Suite shared components are provided in Chapter 2, "Upgrading Communications Suite Shared Components".
- Directory Server. Directory Server rarely resides on the same computer as Communications Express, however, instructions for upgrading Directory Server are provided in the Java Enterprise System Upgrade Guide.
- Web Container Software. Instructions for upgrading Web Server are provided in the Java Enterprise System Upgrade Guide.
- Access Manager (or Access Manager SDK). The previous dependency of Communications Express upon Access Manager (Access Manager SDK) to provide authentication and authorization services for end users, including single sign-on, has been removed in 6.3.
- Directory Preparation Tool. Directory Preparation Tool rarely resides on the same computer as Communications Express, however, instructions for upgrading Directory Preparation Tool and running it against Directory Server are provided in the Chapter 3, "Directory Preparation Tool."
- Messaging Server. Messaging Server MTA needs to be upgraded to 6.3 to support Communications Express 6.3. Instructions for upgrading Messaging Server to 6.3 are provided in Upgrading Messaging Server from Messaging Server 6.1 (Java Enterprise System 2004Q2)
- Calendar Server. Calendar Server rarely resides on the same computer as Communications Express, however, instructions for upgrading Calendar Server to 6.3 are provided in Upgrading from Calendar Server 6 (Java Enterprise System 2004Q2)
Communications Express 6 (Java Enterprise System 2004Q2) Upgrade
The procedure for upgrading from Communications Express 6 (Java Enterprise System 2004Q2) to 6.3 depends on the web container in which you are deploying Communications Express software.
Upgrading Communications Express 6 (Java Enterprise System 2004Q2): Web Server Web Container
To upgrade Communications Express 6 (Java Enterprise System 2004Q2) to Communications Express 6.3, when deploying into a Web Server web container that has been upgraded to 6.3, follow the instructions in Upgrading Communications Express 6.2 (Solaris) or Upgrading Communications Express 6.2 (Linux), except substitute Communications Express 6 (Java Enterprise System 2004Q2) wherever Communications Express 6.2 (Java Enterprise System 2005Q4) is referenced.
Upgrading Communications Express 6 (Java Enterprise System 2004Q2): Application Server Web Container
The upgrade of Communications Express 6 (Java Enterprise System 2004Q2) to Communications Express 6.3, when deploying into an Application Server web container that has been upgraded to 6.3, is not currently supported.