Previous      Contents      Index      Next
Sun Java Enterprise System 2005Q4 Upgrade Guide

Chapter 13
Messaging Server

This chapter describes how to upgrade Messaging Server to Java ES 2005Q4 (Release 4): Sun Java System Messaging Server 6.2 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 Messaging Server Upgrades
Upgrading Messaging Server from Java ES Release 3
Upgrading Messaging Server from Java ES Release 2

Note	File locations in this chapter are specified with respect to a directory path referred to as MessagingServer-base. At least part of this path might have been specified as an installation directory when Messaging Server was initially installed. If not, the Java ES installer assigned a default value. The default value of MessagingServer-base depends on operating system platform: Solaris: /opt/SUNWmsgsr Linux: /opt/sun/messaging

---

Overview of Messaging Server Upgrades

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

About Java ES Release 4 Messaging Server
Messaging Server Upgrade Roadmap
Messaging Server Data
Compatibility Issues
Messaging Server Dependencies

About Java ES Release 4 Messaging Server

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

Messaging Server Upgrade Roadmap

Table 13-1 shows the supported Messaging Server upgrade paths to Java ES Release 4. The table applies to both Solaris and Linux operating systems.

Table 13-1  Upgrade Paths to Java ES Release 4:
Sun Java System Messaging Server 6.2 2005Q4 

Java ES Release	Messaging Server Version	General Approach	Re-configuration Required
Release 3	Sun Java System Messaging Server 6.2 2005Q1	Direct upgrade: Performed by applying patches.	Configuration files and configuration directory data
Release 2	Sun Java System Messaging Server 6.1 2004Q2	Direct upgrade: Performed by applying patches.	Configuration files and configuration directory data
Release 1	Sun ONE Messaging Server 6.0 (2003Q4)	No direct upgrade: But you can upgrade first to Release 3 using procedures in the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062). Then upgrade from Release 3 to Release 4.	Configuration files and configuration directory data
Pre-dates Java ES releases	Sun ONE Messaging Server 5.2	No direct upgrade: But you can upgrade first to Release 3 using procedures in the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062). Then upgrade from Release 3 to Release 4.	Configuration files and configuration directory data

Messaging Server Data

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

Table 13-2  Messaging Server Data Usage

Type of Data	Location	Usage
Configuration data	Local configuration directory: MessagingServer-base/config/msg.conf and many other configuration files for configuring Messaging Server Store, MTA, MMP, MEM (webmail)	Configuration of Messaging Server components
Configuration data	Directory Server configuration directory	Configuration of Messaging Server components
User data	Directory Server user/group directory	Storing user attributes needed to support messaging for end users
Dynamic application data	Messaging Server store: MessagingServer-base/	Store email messages, message transfer queues, and related information on behalf of users
Directory schema	Directory Server /var/opt/mps/serverroot	For user attributes needed to support end users

Compatibility Issues

Release 4 Messaging Server does not introduce any interface changes. The Messaging Server Store, MTA, MMP, and MEM components, logically distinct configurations of Messaging Server, are backwardly compatible with earlier versions.

Messaging Server Dependencies

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

Messaging Server has dependencies on the following Java ES components:

Shared components.   Messaging Server has dependencies on specific Java ES shared components (see Table 1-6).
Directory Server.   Messaging Server stores configuration data and user data needed for messaging in Directory Server. As a result, Messaging Server upgrades might require extensions of directory schema.
Directory Preparation Tool.   Messaging Server uses the Directory Preparation Tool to prepare Directory Server to support Messaging Server functions.
Access Manager (optional).   For software solutions that support single user sign-on for web-based services, Messaging Server can be configured to use Access Manager single sign-on capability.
Delegated Administrator (optional).   Delegated Administrator is the preferred utility to use for provisioning users in Directory Server so that Messaging Server has access to the user data needed to provide messaging services.

---

Upgrading Messaging Server from Java ES Release 3

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

Introduction
Release 3 Messaging Server Upgrade

Introduction

When upgrading Java ES Release 3 Messaging Server 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 is achieved by running two data configuration utilities and by importing configuration data into Directory Server.
Upgrade Dependencies.   While Messaging Server has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Messaging Server requires that NSS, NSPR, LDAP C SDK, ICU, and SASL be upgraded to Release 4. Upgrade of J2SE is optional with respect to upgrade of Messaging Server to Release 4.

In addition, Release 4 Messaging Server is dependent upon Directory Server and optionally dependent on Access Manager, as described in Messaging Server Dependencies. However, these are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Messaging Server to Release 4.

However, Release 4 Messaging Server has a hard upgrade dependency on Directory Preparation Tool; Release 4 Directory Preparation Tool is required to prepare Directory Server for messaging operations.

Backward Compatibility.   Release 4 Messaging Server is backwardly compatible with the Release 3 version.
Upgrade Rollback.   Rollback of the Release 4 upgrade of Messaging Server to Release 3 is achieved by first removing the changes made to Directory Server, removing changes to local configuration files, and removing the patches applied during the upgrade.
Platform Issues.   The general approach for upgrading Messaging Server is the same on both Solaris and Linux operating systems, however the patching technologies are different. The upgrade process therefore includes platform-specific procedures.

Release 3 Messaging Server Upgrade

This section describes how to perform an upgrade of Messaging Server 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
Upgrading Release 3 Messaging Server (Solaris)
Upgrading Release 3 Messaging Server (Linux)
Verifying the Upgrade
Post-Upgrade Tasks
Rolling Back the Upgrade (Solaris)

Pre-Upgrade Tasks

Before you upgrade Messaging Server you should perform the tasks described below.

Verify Current Version Information

You can verify the current version of Messaging Server by entering the following command:

MessagingServer-base/sbin/imsimta version

Table 13-3  Messaging Server Version Verification Outputs

Java ES Release	Messaging Server Version Number
Release 2	6.1
Release 3	6.2
Release 4	6.2p3

Upgrade Messaging Server 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, Messaging Server has hard upgrade dependencies only on the SASL shared component and on Directory Preparation Tool. Upgrading of otherJava ES Release 3 components upon which Messaging Server depends is therefore optional.

However, if you choose to upgrade all Messaging Server dependencies, they should be upgraded in the following order, all before you upgrade Messaging Server. You can skip any that might already have been upgraded.

Shared Components.  Instructions for upgrading NSS, NSPR, LDAP C SDK, ICU, and SASL 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 4, "Directory Server and Administration Server".
Access Manager (optional).  Instructions for upgrading Access Manager to Release 4 are provided in Chapter 11, "Access Manager".
Directory Preparation Tool.   Release 4 Directory Preparation Tool needs to have been run against Directory Server before configuring Release 4 Messaging Server. 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 12, "Directory Preparation Tool" for procedures).

Back Up Messaging Server Data

The Messaging Server upgrade from Release 3 to Release 4 requires re-configuration of Messaging Server in local configuration files and in the Directory Server configuration directory. The local changes can be rolled back, but it is a good idea to back up the configuration directory in case you want to roll back the Release 4 upgrade at a future point.

Obtain Required Configuration Information and Passwords

Messaging Server upgrade requires knowing the following information:

Superuser password
Directory Manager DN and password

Upgrading Release 3 Messaging Server (Solaris)

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

Upgrade Considerations (Solaris)

The upgrade of Messaging Server software to Java ES Release 4 takes into account the following considerations:

All Messaging Server components, such as Messaging Server Store, MTA, MMP, or MEM, that correspond to the same installed Messaging Server image, are upgraded at the same time. All such components should be shut down before patches are applied to the installed image.
The Release 4 Messaging Server upgrade patches for Solaris OS are shown in the following table:

Table 13-4  Patches1 to Upgrade Messaging Server on Solaris 

Description	SPARC Solaris 8, 9, & 10	X86 Solaris 9 & 10
Messaging Server core	118207-38	118208-38
Messaging Server localization	117784 -15	117785 -15

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

The procedure documented below applies to all Messaging Server components that correspond to the same installed Messaging Server image on the computer where the upgrade is taking place.

Obtain the required patches, based on Table 13-4.

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 all running Messaging Server components.

MessagingServer-base/sbin/stop-msg

If you have not already done so, upgrade the required shared components to Release 4.

Upgrade Messaging Server Dependencies.

Apply the appropriate Messaging Server patches in Table 13-4.

patchadd patch_ID

Confirm that the patch upgrade was successful:

showrev -p | grep patch_ID

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

Migrate configuration data from existing configuration files to Release 4 configuration files.
Create candidate configuration files.

cd MessagingServer-base/sbin
./patch-config MessagingServer-base/install/patch/patch_ID

This command backs up 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 examine these new files for possible conflicts, as described in the Special Installation Instructions section of the patch 118209 readme file.

This command also generates the following ldif files (LDAP directory import files):

MessagingServer-base/lib/patch/cfgdir_diff.ldif
MessagingServer-base/lib/patch/ugdir_diff.ldif

Install the Release 4 candidate configuration files, making them the active configuration.

./install-newconfig MessagingServer-base/install/patch/patch_ID

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

Note: If the install-newconfig command fails on the Solaris 10 platform, set the library path to null when running the command:

LD_LIBRARY_PATH= ./install-newconfig      MessagingServer-base/install/patch/patch_ID

Import the new configuration data generated in Step a into the Directory Server configuration directory being used by Messaging Server.

Change to the configuration directory and import the ldif files using the ldapmodify command:

cd /MessagingServer-base/config/lib

./ldapmodify -D bind_dn -w password -c
    -e patch/cfgdir_diff.rej -f patch/cfgdir_diff.ldif

./ldapmodify -D bind_dn -w password -c
    -e patch/ugdir_diff.rej -f patch/ugdir_diff.ldif

Restart the Messaging Server components that were stopped in Step 3.

MessagingServer-base/sbin/start-msg

Upgrading Release 3 Messaging Server (Linux)

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

Upgrade Considerations (Linux)

The upgrade of Messaging Server 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 Messaging Server upgrade patches for Linux OS are shown in the following table:

Table 13-5  Patches1 to Upgrade Messaging Server on Linux 

Description	Patch ID and RPM names
Messaging Server core software with S/MIME	118209-38 sun-messaging-server-6.1-12.38.i386.rpm
Messaging Server localization	117786-15 sun-messaging-l10n-Locale-6.1-8.15.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 all Messaging Server components that correspond to the same installed Messaging Server image 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.

Obtain the required patches using the patch numbers and RPM names from Table 13-5. 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 all running Messaging Server components.

MessagingServer-base/sbin/stop-msg

If you have not already done so, upgrade the required shared components to Release 4.

Upgrade Messaging Server Dependencies.

Apply the RPMs for Messaging Server in Table 13-5.

For example:

rpm -Fvh sun-messaging-server-6.1-12.38.i386.rpm

Confirm that the patch upgrade was successful:

rpm -q sun-messaging-server

The new version number of the RPM should be returned.

Migrate configuration data from existing configuration files to Release 4 configuration files.
Create candidate configuration files.

cd MessagingServer-base/sbin
./patch-config MessagingServer-base/install/patch/patch_ID

This command backs up 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 examine these new files for possible conflicts, as described in the Special Installation Instructions section of the patch 118209 readme file.

This command also generates the following ldif files (LDAP directory import files):

MessagingServer-base/lib/patch/cfgdir_diff.ldif
MessagingServer-base/lib/patch/ugdir_diff.ldif

Install the Release 4 candidate configuration files, making them the active configuration.

./install-newconfig MessagingServer-base/install/patch/patch_ID

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

Import the new configuration data generated in Step a into the Directory Server configuration directory being used by Messaging Server.

Change to the configuration directory and import the ldif files using the ldapmodify command:

cd /MessagingServer-base/config/lib

./ldapmodify -D bind_dn -w password -c
    -e patch/cfgdir_diff.rej -f patch/cfgdir_diff.ldif

./ldapmodify -D bind_dn -w password -c
    -e patch/ugdir_diff.rej -f patch/ugdir_diff.ldif

Restart the Messaging Server components that were stopped in Step 3.

MessagingServer-base/sbin/start-msg

Verifying the Upgrade

You can verify the current version of Messaging Server by entering the following command:

MessagingServer-base/sbin/imsimta version

You can also check the banner displayed when starting up Messaging Server components

See Table 13-3 for output values.

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 Messaging Server followed by the procedure itself.

Rollback Considerations (Solaris)

The procedure for rolling back the upgrade to Release 4 of Messaging Server 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)

Log in as root or become superuser.

su -

Stop all running Messaging Server components.

MessagingServer-base/sbin/stop-msg

Roll back the changes made to the Directory Server configuration directory being used by Messaging Server.

Replace the directory with the pre-upgrade directory that you backed up before beginning the upgrade procedure (see Back Up Messaging Server Data).

Roll back the re-configuration performed in Step 7.

cd MessagingServer-base/sbin
./uninstall-newconfig MessagingServer-base/install/patch/patch_ID

Remove the patches in Table 13-4.

patchrm patch_ID

Restart the Messaging Server components that were stopped in Step 2.

MessagingServer-base/sbin/start-msg

Multiple Instance Upgrades

In some deployment architectures Messaging Server is deployed on multiple computer systems to provide for high availability and scalability. For example, you might have Messaging Server MTA or Messaging Server MMP components running on multiple computers with a load balancer to distribute the load. You might also have the Messaging Server Store component running in a Sun Cluster environment to provide high availability.

In the case of load-balanced instances of Messaging Server, you can perform a rolling upgrade in which you upgrade the Messaging Server instances sequentially without interrupting service. You upgrade each instance of Messaging Server while the others remain running. In deployment architectures in which various MS subcomponents (MS Store, MTA, MMP, MEM) are deployed on different computers, upgrade components beginning in the back-end tier (MS Store) and working toward the front-end tier (such as MEM). You perform the upgrade of each instance as described in Release 3 Messaging Server Upgrade.

In the case of Messaging Server instances running in a cluster environment, those instances share the same configuration. You therefore need to apply Messaging Server upgrade patches to each of the instances, but you only need to perform the re-configuration part of the upgrade procedure once, after patches have been applied to all the instances.

---

Upgrading Messaging Server from Java ES Release 2

The procedure for upgrading Java ES 2004Q2 (Release 2) Messaging Server to Release 4 is the same as that for upgrading Release 3 Messaging Server to Release 4, with a couple of exceptions, noted below.

Upgrade Messaging Server Dependencies

As compared to the upgrade from Release 3, the Release 2 to Release 4 pre-upgrade tasks should include the upgrading to Release 4 of all shared components (see Table 1-6) and all locally-resident product components upon which Messaging Server depends:

Shared Components.  Instructions for upgrading Java ES shared components to Release 4 are provided in Chapter 2, "Upgrading Java ES Shared Components".
Directory Server.  Directory Server rarely resides on the same computer as Messaging Server, however, instructions for upgrading Directory Server to Release 4 are provided in Upgrading Directory Server and Administration Server from Java ES Release 2.
Access Manager (optional).  Instructions for upgrading Access Manager to Release 4 are provided in Upgrading Access Manager from Java ES Release 2.
Directory Preparation Tool.   Directory Preparation Tool rarely resides on the same computer as Messaging Server, however, instructions for upgrading Directory Preparation Tool and running it against Directory Server are provided in Upgrading Directory Preparation Tool from Java ES Release 2.

Release 2 Messaging Server Upgrade

The procedure for upgrading Messaging Server from Release 2 to Release 4 depends on operating system platform.

Upgrading Release 2 Messaging Server (Solaris)

To upgrade Release 2 Messaging Server to Release 4, use the instructions in Upgrading Release 2 Messaging Server (Solaris), except substitute Release 2 wherever Release 3 is referenced.

Upgrading Release 2 Messaging Server (Linux)

The procedure documented below applies to all Messaging Server components that correspond to the same installed Messaging Server image 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.

Log in as root or become superuser.

su -

Stop all running Messaging Server components.

MessagingServer-base/sbin/stop-msg

If you have not already done so, upgrade the required shared components to Release 4.

See Upgrade Messaging Server Dependencies.

Uninstall the Release 2 RPM packages.

rpm -e --noscripts sun-messaging-lib-6.1-9 \
                     sun-messaging-store-6.1-9 \
                     sun-messaging-install-6.1-9 \
                     sun-messaging-core-6.1-9 \
                     sun-messaging-mmp-6.1-9 \
                     sun-messaging-sieveui-6.1-9 \
                     sun-messaging-webmail-6.1-9 \
                     sun-messaging-core-en-6.1-9 \
                     sun-messaging-mta-6.1-9

Install the RPM for Messaging Server in Table 13-5.

rpm -i sun-messaging-server-6.1-12.38.i386.rpm

Confirm that the patch upgrade was successful:

rpm -q sun-messaging-server

The version number of the newly installed RPM should be returned.

Save off your old Release 2 configuration.

The configuration files are located at: MessagingServer-base/config

Run the Messaging Server configuration program.

cd MessagingServer-base/sbin
./configure

Perform a manual merge of the Release 2 configuration values with the new Release 4 configuration entries.
Restart the Messaging Server components that were stopped in Step 2.

MessagingServer-base/sbin/start-msg

For further details, for example to change the HTTP port using the configutil command, see the Special Installation Instructions section of the patch 118209-38 readme file.

Verifying the Upgrade

You can verify the current version of Messaging Server by entering the following command:

MessagingServer-base/sbin/imsimta version

You can also check the banner displayed when starting up Messaging Server components

See Table 13-3 for output values.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).

Previous      Contents      Index      Next

---

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