Sun Java™ System Migration Guide for Messaging Server for Microsoft Windows

Messaging Server 6 2004Q2 is installed and configured on a different system from the Messaging Server 5.2 system.



Note	Unlike previous versions of Messaging Server, you cannot upgrade your existing Messaging Server without first installing and configuring Messaging Server 6 2004Q2. Also note that you cannot use this upgrade program with Messaging Server versions older than version 5.2. Therefore, you must first migrate or upgrade to Messaging Server 5.2, install Messaging Server 6 2004Q2 and then run this upgrade program. See the iPlanet Messaging Server 5.2 Migration Guide and Installation Guide for more information on migrating to Messaging Server 5.2.

Existing Messaging Server 5.2 installations are configured with MTA Direct LDAP Lookup not with imsimta dirsync.

In addition, Messaging Server 6 2004Q2 does not support multiple instances. If you have multiple instances of Messaging Server version 5.2, you may only choose one instance to upgrade to Messaging Server 6 2004Q2. Furthermore, running the upgrade utility more than once in an attempt to migrate multiple instances will overwrite your configuration.

Overview of the Upgrade Process

There are two steps to upgrading from Messaging Server 5.2 to Messaging Server 6.0. The following topics outline the process:

Creating Upgrade Files to Update your Configuration

This section describes how special upgrade files are created in order to update your configuration on your Messaging Server 6.0 system:

About Upgrade Files

Prior to running an upgrade utility to move from Messaging Server 5.2 to 6.0, you first need to run the UpgradeMsg5toMsg6.pl Perl script (located in msg_svr_base/sbin).

UpgradeMsg5toMsg6.pl compares your 5.2 configuration files with your 6.0 configuration files and creates to sets of files for each configuration file: *.CHANGES files and *.MERGED files.

The *.CHANGES files and *.MERGED files are generated in the workspace directory, msg_svr_base/sbin/tmp/UpgradeMsg5toMsg6.ScratchDir.

The *.CHANGES files show critical configuration file differences between Messaging Server 5.2 and Messaging Server 6.0. These files highlight the configuration entities that are only found in Messaging Server 6.0, the configuration entities from Messaging Server 5.2 that are obsolete in Messaging Server 6.0, and the configuration entities that are only found in the Messaging Server 5.2. Note that not all *.CHANGES files will show differences between the versions of configuration files, and not all configuration files will generate *.CHANGES files.

The *.MERGED files are a consolidation of Messaging Server 5.2 and 6.0 configuration values and settings. In general, configuration parameter values from Messaging Server 5.2 are retained over the Messaging Server 6.0 version if:

The following table lists the configuration files that generate *.MERGED or *.CHANGES files:

Table 1 Messaging Server Configuration Files That Generate *.MERGED or *.CHANGES files
Configuration Information	Description	Generates *.MERGED File	Generates *.CHANGES File
job_controller.cnf	Job Controller File	X	X
conversions	Conversions File	X
channel_option, where channel is an SMTP channel	SMTP channel option files	X
native_option	Native channel option file (exception to channel_option)	X	X
channel_headers.opt, where channel is an SMTP channel	Header option files	X
dispatcher.cnf	Dispatcher File	X	X
imta_tailor	Tailor File	X	X
option.dat	Global MTA Option File	X	X
aliases	Aliases File	X
imta.cnf	MTA Configuration File; only the include references (like file directory locations) are changed. Rewrite rule and channel settings are retained from your 5.2 configuration. To include LMTP in your imta.cnf, copy the LMTP information from your 6.0 imta.cnf file.	X	In some instances, a *.CHANGES file may be generated.
mappings	Mappings File	X
mappings.locale	Localized Mappings File	X
internet.rules	Internet Rule Configuration File	X
backup-groups.conf	Backup Group Definitions	X	X
configutil	Changes of configuration parameters in local.conf and msg.conf configuration files.		X

Running the UpgradeMsg5ToMsg6.pl Perl Script

To run the UpgradeMsg5toMsg6.pl to create sets of files by which you will be able to update your configuration, follow these steps:

Extract and copy the Messaging Server 5.2 server-root directory to the Messaging Server 6.0 system.

If your Message Store is too large to transfer from one system to another, you can map the drive (if u have the supporting tools) onto the 6.0 system.



Note	You don't have to copy the Messaging Server 5.2 store data to the Messaging Server 6.0 system, however, you must ensure that the Messaging Server 5.2 store data is accessible during the upgrade process.

Both your 5.2 and 6.0 systems can be running at this point.

Run the UpgradeMsg5toMsg6.pl upgrade script (located in msg_svr_base/sbin) against the msg-instance of 5.2 version and the msg_svr_base of the 6.0 version. For example:

perl UpgradeMsg5toMsg6.pl C:/MS5.2/msg-budgie C:/Sun/Server-root

where C:/MS5.2/msg-budgie is the msg-instance of the 5.2 Messaging Server and C:/Sun/Server-root is the msg_svr_base of the 6.0 Messaging Server.



Note	Messaging Server 6.0 does not support multiple instances. If you have multiple instances of Messaging Server version 5.2, you may only choose one instance to upgrade to Messaging Server 6.0. Furthermore, running the upgrade utility more than once in an attempt to migrate multiple instances will only result in you overwriting your configuration.

*.MERGED and *.CHANGES files (as described in Table 1) will be created.

Carefully review the *.MERGED files; if you don't want to use the suggested recommendations, you must manually adjust the settings.

This utility does not update the Messenger Express customization files. Therefore, you need to manually change these files in order to keep the relevant information from Messaging Server 5.2 and add any new information from the Messaging Server 6.0 installation.

Running the Upgrade Utility

This section describes the do_the_upgrade.pl utility (located in msg-svr-base/sbin/tmp/UpgradeMsg5toMsg6.ScratchDir), a perl script that is made up of four sub-scripts. The following topics are covered in this section:

Overview of the Upgrade Utility

The do_the_upgrade.pl utility is made up of four shell scripts that, with your *.MERGED files, update the configuration and file directory locations of your MTA configuration, your configutil parameters, backup parameters, and your mboxlist database in your Messaging Server 6.0 system.

You can either run the do_the_upgrade.pl utility, or you can individually run one or more of the scripts that make up the do_the_upgrade.pl utility (make_mta_config_changes.pl, make_configutil_changes.pl, make_backup_config_changes.pl, and make_mboxlistdb_changes.pl).


Note	When executing either the do_the_upgrade.pl utility or any of the sub-scripts, be sure that neither Messaging Server 5.2 nor 6.0 is up and running.

After running the do_the_upgrade.pl script, you can either continue to reference your 5.2 partition paths (though you will not be able to remove your Messaging Server 5.2 server-root directory) or you can manually move the 5.2 store partitions to the appropriate Messaging Server 6.0 directory location. You should perform this step prior to restarting Messaging Server.

MTA Configuration

The MTA upgrade configuration sub-script that makes up of part of the do_the_upgrade.pl utility is called make_mta_config_changes.pl (located in msg-svr-base/sbin/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_mta_config_changes.pl script backs up, renames, and moves the *.MERGED server configuration files to their original names and locations within the Messaging Server 6.0 file directory structure.

Once the script has finished renaming and moving the files, it automatically runs the imsimta cnbuild command to recompile the MTA configuration.

configutil Parameters


Note	If you want to upgrade an MTA relay machine from Messaging Server 5.2 to Messaging Server 6.0, you only need to run the make_mta_config_changes.pl and the make_backup_config_changes.pl (described in Backup Configuration).

The configutil upgrade configuration sub-script that makes up part of the do_the_upgrade.pl utility is called make_configutil_changes.pl script (located in msg-svr-base/sbin/tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_configutil_changes.pl script incorporates new or updated parameters in the msg.conf and local.conf files. If default values are not specified in configutil parameters in Messaging Server 6.0, any Messaging Server 5.2 values are carried forward to the Messaging Server 6.0 version.

Backup Configuration

The backup upgrade configuration sub-script that makes up part of the do_the_upgrade.pl utility is called make_backup_config_changes.pl script (located in msg-svr-base/sbin /tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_backup_config_changes.pl script upgrades the configuration of your backup services such as those in your backup-groups.conf file.

mboxlist Database

The mboxlist database upgrade configuration sub-script that makes up part of the do_the_upgrade.pl utility is called make_mboxlistdb_changes.pl script (located in msg-svr-base/sbin /tmp/UpgradeMsg5toMsg6.ScratchDir).

The make_mboxlistdb_changes.pl script transfers and upgrades your 5.2 mboxlist database and upgrades it to the Messaging Server 6.0 directory structure. The script copies the four *.db files (folder.db, quota.db, peruser.db, and subscr.db) from server-root/msg-instance/store/mboxlist on your Messaging Server 5.2 system to msg_svr_base/data/store/mboxlist on your Messaging Server 6.0 system.


Sun Java Enterprise System Messaging Server Migration Guide for Microsoft Windows