6.3-1.04_x86: core patch install procedure
Folks,
I was running:
Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007)
and installed: Patch-ID# 120229-20
to bring ver to:
Sun Java(tm) System Messaging Server 6.3-1.04 (built May 9 2007; 32bit)
Question: regarding the upgrade of the config files:
How do I know if I want to upgrade the config files? In this case I am running an instance that has not gone to production and has had very little customization done at this point, however I am unclear what changes the config file upgrade will entail.
**Note from patch README:
After applying the patch, the configuration files may need to be
upgraded. You may continue to run the Messaging Server with the old
configuration files till you are ready to install the new
configuration files.
[834 byte] By [
goubeauxa] at [2007-11-27 10:07:50]

# 1
Hi,
> How do I know if I want to upgrade the config files?
> In this case I am running an instance that has not
> gone to production and has had very little
> customization done at this point, however I am
> unclear what changes the config file upgrade will
> entail.
With regards to the messaging-server patches (120228/120229/120230) there are very little in the way of config file changes for MTA related files. The changes usually revolve around the html/js files provided for messenger express, which you will want to upgrade as they address bugs primarily. This is especially true of UWC/CE patches which definitely need the 'config' files to be changed.
> **Note from patch README:
>
> After applying the patch, the configuration files may
> need to be
> upgraded. You may continue to run the Messaging
> Server with the old
> configuration files till you are ready to install the
> new
> configuration files.
There are two steps to the process, the first step is determining which files need to be updated/replaced/deleted (patch-config) and the second step is applying those changes (install-newconfig).
After running the patch-config command, you will be provided with a list of files that have been modified/are to be replaced/deleted and have conflicts that you need to address. You can review all of these prior to running install-newconfig to ensure that they won't cause problems.
If you are not comfortable with the process I would recommend trying it out first in a test-environment (which ideally you should do anyway prior to making any changes in production).
Regards,
Shane.