Creating Upgrade Files to Update your Configuration

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

• About Upgrade Files

• To Run the UpgradeMsg5toMsg6.pl Perl Script

About Upgrade Files

Prior to running an upgrade utility to move from Messaging Server 5.2 to 6, 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 Messaging Server 6 configuration files and creates two sets of files for each configuration file: *.CHANGES files and *.MERGED files.

The *.CHANGES files and *.MERGED files are generated in the work space directory, /var/tmp/UpgradeMsg5toMsg6.ScratchDir.

The *.CHANGES files show critical configuration file differences between Messaging Server 5.2 and the current version of Messaging Server. These files highlight the configuration entities that are only found in Messaging Server, the configuration entities from Messaging Server 5.2 that are obsolete in this current version of Messaging Server, and the configuration entities that are only found in the Messaging Server 5.2. 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 the current version of Messaging Server configuration values and settings. In general, configuration parameter values from Messaging Server 5.2 are retained over the current version of Messaging Serverif:

• There is no default value in the current version of Messaging Server, or

• The value specified in your 5.2 configuration is not a default setting.

Table 2–1 lists the configuration files that generate *.MERGED or *.CHANGES files.

Table 2–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 Messaging Server 6 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

To Run the UpgradeMsg5toMsg6.pl Perl Script

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

Before You Begin

Both your 5.2 and current version of Messaging Server can be running at this point.

If your Messaging Server 5.2 and 6 versions are on the same machine, start with Step 2.

Steps

1. If your Messaging Server 5.2 and 6 versions are not on the same machine, transfer, extract and copy the Messaging Server 5.2 server-root directory to the current version of Messaging Server.

   If your server versions are installed on the same machine, you can skip this step.

   If your Message Store is too large to transfer from one system to another, you can transfer just the essential portions of the server instance to the new system. There are comments inside of the UpgradeMsg5toMsg6.pl which cover this in detail.

   You don't have to copy the Messaging Server 5.2 store data to the Messaging Server 6 2005Q4 system, however, you must ensure that the Messaging Server 5.2 mboxlist directory is accessible during the upgrade process.

2. Run the UpgradeMsg5toMsg6.pl upgrade script.

   By default, this script is located in msg_svr_base/sbin.

   Run the script against the msg-instance of 5.2 version and the msg_svr_base of the current version of Messaging Server. For example:

   perl UpgradeMsg5toMsg6.pl /usr/sunone/server5/msg-budgie \ /opt/SUNWmsgsr

   where /usr/sunone/server5/msg-budgie is the msg-instance of the 5.2 Messaging Server and /opt/SUNWmsgsr is the msg_svr_base of the current version of Messaging Server.

   The process creates *.MERGED and *.CHANGES files (as described in About Upgrade Files).

3. Carefully review the *.MERGED files to determine if you need to adjust the settings.

   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 current version of Messaging Server installation.