|
| |
| Sun Java Enterprise System Upgrade Guide for Microsoft Windows | |
Chapter 11
Messaging ServerThis chapter describes how to upgrade Messaging Server from previous Java ES versions to Java ES Release 4: Messaging Server 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 the following:
Overview of Messaging Server UpgradesThis section describes the following general aspects of Messaging Server that impact upgrading to Java ES Release 4:
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 11-1 shows the supported Messaging Server upgrade paths to Java ES Release 4.
Messaging Server Data
The following table shows the type of data that could be impacted by an upgrade of Messaging Server software.
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 Admin (optional). Delegated Admin 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 3This section includes information about upgrading Messaging Server from Java ES Release 3 to Java ES Release 4. The section covers the following topics:
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, 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.
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 windows platform. The section covers the following topics:
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:
# msg_svr_base\sbin\imsimta version
Table 11-3 Messaging Server Version Verification Outputs
Java ES Release
Messaging Server Version Number
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 other Java 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 3, "Directory Server and Administration Server."
- Access Manager (optional).
- 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 10, "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:
Upgrading Messaging Server
This section discusses considerations that impact the upgrade procedure for Messaging Server followed by a description of the procedure itself.
Upgrade Considerations
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 upgrade patches are shown in Table 1-3.
Upgrade Procedure
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 1-3.
Patches can be downloaded from:
http://sunsolve.sun.com
- Log in as administrator.
- Stop all running Messaging Server components.
# msg_svr_base\sbin\stop-msg
- If not already done, upgrade the required shared components to Release 4.
- Apply the Messaging Server patches in Table 1-3.
- Run pre-patch.pl before executing patch.
perl.prepatch.pl <Server-Root> <Patch-id>
- Apply the patch by running <Patch-id>.exe
- Run post-patch.pl after applying the patch
perl.postpatch.pl <Server-Root> <Patch-id>
- Migrate configuration data from existing configuration files to Release 4 candidate configuration files.
- Create candidate configuration files.
Run patch-config.pl
perl patch-config.pl <Server-Root> <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 < > readme file.
This command also generates the following ldif files (LDAP directory import files):
msg_svr_base/lib/patch/cfgdir_diff.ldif
msg_svr_base/lib/patch/ugdir_diff.ldif
- Install the Release 4 candidate configuration files, making them the active configuration.
Run install-newconfig.pl
perl install-newconfig.pl <Server-Root> <patch-id>
This command installs the new Release 4 configuration files in their correct.
- Import the new configuration data generated in Step6a 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 msg_svr_base\lib
# Run ldapmodify -D bind_dn -w password -c
-e patch\cfgdir_diff.rej -f patch\cfgdir_diff.ldif
# Run 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.
# msg_svr_base\sbin\start-msg
Verifying the Upgrade
You can verify the current version of Messaging Server by entering the following command:
You can also check the banner displayed when starting up Messaging Server components
See Table 11-3 for output values.
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 Messaging Server followed by the procedure itself.
Rollback Considerations
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
- Log in as administrator.
- Stop all running Messaging Server components.
# msg_svr_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).
- Remove the patches in Step 9.
- Run prebackout.pl before Uninstall_<Patch-id>.bat
- Run Uninstall_<Patch-id>.bat to rollback
- Run post-backout.pl after uninstall.
- Restart the Messaging Server components that were stopped in Step 2.
# msg_svr_base\sbin\start-msg