By joesciallo on May 15, 2013
Introduced in the latest Messaging Server release (7 Update 5 Patch 28), Unified Configuration offers up a more "unified" approach to administering your messaging configuration:
- You don't have to manage multiple configuration files with differing formats, and that you have to edit by hand (and so risk potentially causing an error): instead, you use one administrative tool, msconfig, and all legacy configuration files (with some small exceptions) are consolidated into three configuration files (config.xml being where most configuration data is stored). In addition, Unified Configuration performs validation checking to prevent introducing some configuration errors.
- You no longer have to deal with configuration settings that themselves are not that straight-forward, and in Unified Configuration, you can use the same settings for many options among the MMP, MTA, and message store configurations.
Getting started with Unified Configuration, I found the following tips and information very useful:
- Use the configutil -H command to translate the legacy configutil option names to Unified Configuration names. For example:
# configutil -H -o logfile.imap.expirytime
Configuration option: logfile.imap.expirytime
Unified Config Name: imap.logfile.expirytime
- Upgrading to Messaging Server 7 Update 5 (patch 28) does not mean that you HAVE to run Unified Configuration. You can upgrade and continue to run just as you are in legacy configuration. When/if you want to start using Unified Configuration, then you would use the configtoxml Command to update the configuration.
- You can run msconfig in either interactive or non-interactive mode. As I have been getting used to Unified Configuration, I find that using interactive mode is very helpful, as the parser lets you know if you have entered an incorrect syntax. Also, you don't have to accept the configuration change until you write it to the configuration.
- Getting more help: run the msconfig help command to get a list of online help topics.
- When you deal with editing blobs like channels, invoke the editor like this: msconfig edit channels, or for a specific channel, msconfig edit tcp_local. The msconfig edit command invokes the editor specified by the EDITOR shell variable. This is a much easier way to edit things than by trying to use an msconfig set command.