Sun Java System Messaging Server 6.3 64-bit Installation Technical Note

Installing Messaging Server

The following topics are described in this section:

Getting the Installation Software

You can get the Sun Java System Messaging Server 6.3 64–bit Edition software as a Web download.

You can download a compressed archive of all installation files from the Sun Download Center at The Messaging Server installation files are available in zip images: one for SPARC and one for x86 platforms.

commpkg usage

The commpkg command enables you to run the Messaging Server 6.3 64–bit Edition installer. This command lays down the Messaging Server installation bits on your machine, but it does not configure Messaging Server. To configure Messaging Server after installation, see Chapter 1, Post-install Tasks and Layout, in Sun Java System Messaging Server 6.3 Administration Guide in the Sun Java System Messaging Server 6.3 Administration Guide.


commpkg [general options] verb [verb-specific options]


The general options for this command are:



-? or —help

Displays Help 

-V or —version

Displays Version of Messaging Server 

The verb is one of the following:




Performs Messaging Server installation 


Performs Messaging Server uninstallation 

Note –

Automatic Upgrade is not available at this time. You can perform a manual upgrade by following the procedures in Upgrading Messaging Server.

The verb-specific options can be one or more of the following:

verb-specific options



Do not apply Operating System patches during product installation 


Do not install, upgrade, or patch any Shared Components 


Accept the license conditions in the LICENSE.txt file


Specify an alternate root directory during a multi-host installation. The INSTALLROOT (the top level installation directory for all products and shared components) will be the alternate root.

—distro path

Specify the path to packages/patches for the products

Default: Location of commpkg script

—installroot path

Specify the path of INSTALLROOT, the top level installation directory for Messaging Server. .

Note –

The subdirectories for individual Communications Suite products (which will be a part of this installer at later releases) will be under the INSTALLROOT.


Run silent installation, taking the inputs from the INPUTFILE and the command line arguments. The command line arguments override entries in the INPUTFILE. Installation proceeds without interactive prompts.

Use —dryrun to test silent installation.

—dry-run or -n

Does not install Messaging Server. Performs checks. 

—upgradeSC [y|n]

Indicate whether or not to upgrade shared components as required. 

Warning: Upgrading Shared Components is irreversible. However, if you do not upgrade required shared components, products might not work as designed. 

Note: If the [y|n] is not specified, you will be prompted for each shared component that needs to be upgraded.

Default: n

The —excludeSC flag has precedence over this flag.


Audit the installation distribution to verify that the required patches and packages are present and that the packages have the correct versions. 


Overwrite the existing installation package. You might use this option when you are installing a shared component in a global zone where either the shared component does not exist in a global zone, or the shared component exists in the whole root zone. The default is not to override the existing package. In general, shared components should be managed in the global zone. 

To Begin Installation

  1. Log on as root to become a superuser.

  2. Start the text-based installer. Use the commpkg usage as described in commpkg usage. When commpkg is invoked, a log file will record the installation parameters.)

    # ./commpkg install

    -- LOGFILE: /tmp/CommsInstaller_20070501132825.log

  3. Accept the License Agreement. If you have already read the agreement in its entirety, you have the option of skipping the agreement and accepting the terms. To accept the terms of the agreement without viewing the entire license agreement, hit Enter to continue, then enter n to skip reading the agreement, and enter yes to accept the terms.

  4. Specify Installation Location where server files will be installed (also known as the INSTALLROOT) or accept the default location.

    Note –

    The default INSTALLROOT has changed from /opt/SUNWmsgsvr to /opt/sun/comms/messaging (for 32–bit installations) and /opt/sun/comms/messaging64 (for 64–bit installations)

    After specifying the INSTALLROOT, notices for Operating System and Shared Components patches may appear if previous versions of patches are installed on the machine.

  5. Select Products to Install

    In this release, there are four products: Messaging Server 6.3, Messaging Server 6.3 (Localized Version), Messaging Server 6.3 64–bit, and Messaging Server 6.3 64–bit (Localized Version).

  6. Generate List of Items to Install

    In this step, the installer lists all the products as well as shared components that will be installed or upgraded. If items need to be upgraded, the installer will give you the choice to upgrade.

    Caution – Caution –

    Remember, upgrading shared components is an irreversible process. However, if you do not install the correct version of the shared components, the product may not work as designed. So, proceed carefully when installing and upgrading shared components and products.

    Once you determine what you are going to install and upgrade, the installer will create a summary.

  7. Ready to Install

    Once you specify the components you're installing and upgrading, the installer is ready to install Messaging Server files into INSTALLROOT.

    If everything installs properly, you will see All tasks PASSED in the summary panel.

  8. Log Files

    Once installation has completed, time-stamped log files are created like in the following example:

    • To undo your installation, go to your undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358

    • To run silent installation for multiple installations, use the silent installation file like in the following example:/var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358

    • The installer creates a log file of the installation process in the following location. For example:/var/opt/CommsInstaller/logs/CommsInstaller_20070501135358.log

  9. Undo Installation

    If you want to remove the installation that you just ran, you can undo your installation by running the undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358.

    Undo reverses the specific steps taken during installation. It will also undo Shared Component installations. If, however, you want to pick and choose specific components to uninstall, use the commpkg uninstall command: Uninstalling Messaging Server. The uninstaller does not uninstall shared components.

  10. Directory Layout

    In the INSTALLROOT (default: /opt/sun/comms), you may see the following directories:

    • CommsInstaller, where a copy of the Installer resides.

      Note –

      The log files listed in the previous step are located in the /var/opt/CommsInstaller/log directory. If you install Messaging Server in an alternate root, the logfiles are located in the alternate root's INSTALLROOT/var/opt/CommsInstaller/log directory.

    • messaging, the 32–bit Messaging Server version

    • messaging64, the 64–bit Messaging Server version

Installing in Silent Mode

If you run the installer in Silent mode, you are running a non-interactive session. The installation inputs are taken from a silent installation file (also known as a state file), from command line arguments, or defaults.

To run a silent installation, follow these steps:

  1. Run an interactive installation session. (See To Begin Installation.) A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created.

  2. Copy the state file to each host machine and edit the file as needed. See Silent Mode File Format.

  3. Run the silent installation on each host. See the silent installation usage in commpkg usage.

Note –

Command-line arguments override the values and arguments in the state file.

Silent Mode File Format

The silent mode file (also known as a state file) is formatted like a property file: blank lines begin with a number sign (#) and properties are key/value pairs separated by an equals (=) sign. You can change the following parameters:

Installing Shared Components

For handling shared components, you have two options:

Performing Multiple Installations with an Alternate Root

Unlike the previous version of the installer, this version allows multiple installations of the same product version on the same machine by using different INSTALLROOTS.

To do so, install the product in the alternate root with the —altroot flag:

  1. Install OS patches and Shared Components in the default INSTALLROOT. See To Begin Installation. To only install the shared components, add a ~ (tilde) to the component number you want to install in the alternate root. For example, if you plan to install Messaging Server 64–bit in the alternate root, you select ~3 during the default installation. The installer will know to only install dependencies and not the product itself.

    Note –

    OS patches are always applied in the default INSTALLROOT, never in the alternate root.

  2. Install Shared Components and Messaging Server in the Alternate Root like the following example:

    commpkg install —altroot —installroot /opt/sun/comms2

    Be sure to use —installroot with —altroot to specify the alternate root.

You may create as many alternate roots as you would like. However, you should manually keep track of all the alternate roots you have created.