test

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

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

This document describes how to install Sun Java System Messaging Server 6.3 64–bit Edition. In future releases, this installer will include other Communications Suite components.

Note –

In addition to being able to install Messaging Server 64–bit edition, this installer also allows you install the 32–bit version.

This technical note contains the following sections:

Technical Note Revision History

Version 

Date 

Description of Changes 

1 

July 2007 

Initial release of this technical note. 

What's New with the Installer

The Sun Java System Messaging Server 6.3 64–bit Installer is a different installer from its previous version, the Communications Suite 5 Installer (which includes Sun Java System Messaging Server 6.3). See the following table of changes:

Table 1 Differences Between Messaging Server 6.3 64–bit Installer and Communications Suite 5 Installer (which includes Messaging Server 6.3)

Sun Java System Messaging Server 6.3 64–bit Installer

Communications Suite 5 Installer

Installs Messaging Server  

Installs required Shared Components and Operating System patches for Messaging Server 

Installs Veritas Cluster Agent, but not Sun Cluster Agent or Sun Cluster software (You can get Sun Cluster from the Communications Suite 5 Installer). 

Installs Java Enterprise System components (such as Directory Server, Sun Cluster) 

Installs Communications Suite: Messaging Server, Calendar Server, Delegated Administrator, Communications Express as well as Sun Cluster Agent or Veritas Cluster Agent 

Text-based Installer 

GUI-based installer and text-based installer 

No product registry; uses package database to determine whether a package is installed or partially installed. 

Uses Product Registry 

Installs 32–bit and 64–bit editions 

Installs 32–bit edition. 

What's Not Included in this Release

The following feature is not available in this release:

Upgrade: In this release, there is no automatic upgrade utility to go from Communications Suite 5 (Sun Java System Messaging Server 6.3) to Sun Java System Messaging Server 6.3 64–bit Edition. However, you are able to manually upgrade to this version of Messaging Server by choosing from three upgrade processes. See: Upgrading Messaging Server.

Preparing for Installation

This section covers the following pre-installation topics:

Checking Installation Requirements

Before you install components, use the steps in this section to make sure the system on which you are installing is ready.

Note –

The performance of your messaging server depends on many factors, including CPU power, available memory, disk space, file system performance, usage patterns, network bandwidth, and so on. For example, throughput is directly related to file system performance. If you have questions about sizing and performance, contact your Sun Java System representative.

ProcedureTo Check System Requirements

  1. Make sure you are the root user for the system.

  2. Have at least 2.2 GB free disk space for the unzipped image.

  3. Have the image already unzipped.

ProcedureTo Ensure DNS is Running and Configured Properly

  1. Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:

    domain comms.beta.com
nameserver 192.168.100.22
nameserver 192.168.100.23
nameserver 192.168.100.24
nameserver 192.168.100.25

  2. Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:

    10.1.82.52 wireless.comms.beta.com wireless loghost

  3. Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:

    hosts: files dns nis [NOTFOUND=return]

    Or, if NIS is not used:

    hosts: files dns

  4. On Solaris 10 platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the /etc/inet/ipnodes file.

    Otherwise, you'll get an error indicating that your host name is not a fully qualified domain name (FQDN).

Recommended File Systems for Message Stores

The following file systems are recommended for message stores:

Messaging Server Operating System Requirements

The 64–bit release supports the following platforms:

The 32–bit release supports the following platforms:

Patch and Package Information for Messaging Server

For the most current list of required patches for Sun Java System Messaging Server go to http://sunsolve.sun.com and select either “Patches” or “Patch Portal”. As operating system patch requirements change and patches to Java Enterprise System components become available, updates will be made available on SunSolve, initially in the form of recommended patch clusters.

Note –

The installer checks for required platform patches. You must install all required patches or the installation process will not continue.

At the time of general release, the following Messaging Server 6.3 32–bit upgrade patches are available:

Solaris Platform 

Patch Number (English) 

SPARC 

120228–21 

x86 

120229–21 

The following Messaging Server 6.3 product packages are part of this release:

English 

Localized Version 

32–bit: SUNWmessaging-server

32–bit: SUNWmessaging-server-l10n

64–bit: SUNWmessaging-server-64

64–bit: SUNWmessaging-server-l10n–64

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 http://www.sun.com/downloads. 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.

Syntax

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

Options

The general options for this command are:

Option 

Description 

-? or —help

Displays Help 

-V or —version

Displays Version of Messaging Server 

The verb is one of the following:

Verb 

Description 

install

Performs Messaging Server installation 

uninstall

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

Description 

—excludeOS

Do not apply Operating System patches during product installation 

—excludeSC

Do not install, upgrade, or patch any Shared Components 

—acceptLicense

Accept the license conditions in the LICENSE.txt file

—altroot

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.

—silent INPUTFILE

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.

—auditDistro

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

—pkgOverwrite

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.

Installing on Solaris Zones

This section explains how to install Messaging Server on Solaris 10 Zones. For an overview of Solaris 10 with Messaging Server, see: Overview of Solaris Zones in Sun Java Communications Suite 5 Installation Guide.

Solaris 10 Zones Installation Sequences

This section describes how to install Messaging Server in the four Solaris 10 Zone scenarios:

Global zone with existing non-global zones

Note –

This Zone scenario is not recommended for Messaging Server implementation. It requires the same version of shared components be running on each zone. Futhermore, the global zone should be reserved for administrative zone support.

If you install Messaging Server in a global zone with existing non-global zones, you install the appropriate OS patches, shared component patches, and Messaging Server product into the global zone. It will propagate the shared component patches into the non-global zones. To install Messaging Server in a global zone with existing non-global zones:

  1. Follow pre-installation requirements as described in Preparing for Installation

  2. Run the installer in the global zone by following the steps in To Begin Installation.

Global zone with no existing non-global zones

If you install Messaging Server in a global zone with no existing non-global zones, you need to prepare your installation as if you might add non-global zones in the future. Modifying your deployment at a later time becomes difficult if you don't plan for this step. To do this, follow the steps inGlobal zone with existing non-global zones.

Non-global whole root zone

The non-global whole root zone scenario is the equivalent of installing Messaging Server on a single box with no zones. Simply install Messaging Server as described in To Begin Installation.

Caution – Caution –

Any operations performed in the global zone (such as installations, uninstallations, and patching) affects the whole root zones.

Non-global sparse root zone

To install Messaging Server in a non-global sparse root zone, you first need to install/upgrade the applicable OS patches and shared components in the global zone. You are unable to do so in the sparse root zone, because the /usr directory (where the shared components reside) is a read-only directory in the sparse root zone.

  1. Follow pre-installation requirements as described in Preparing for Installation.

  2. Verify that you are about to install the shared components and OS patches in the global zone and not the sparse root zone.

  3. Run the installer in the global zone and only install/upgrade the OS patches and the Shared Components:

    commpkg install -upgradeSC y

    See the Installing Shared Components.

  4. Do not install Messaging Server in the global zone. To do this, add a ~ (tilde) to the component number you want to install in the sparse zone. For example, if you plan to install Messaging Server 64–bit in the sparse zone, you select ~3 during the global zone installation. The installer will know to only install dependencies and not the product itself.

  5. Once you have the shared components and OS patches installed, install Messaging Server in the sparse root zone by following the steps in the To Begin Installationsection.

Next Steps: Configuring Messaging Server for Use

Now that you've performed the basic installation of Messaging Server, this section describes the next steps:

Preparing Your Directory for Messaging Server Configuration

After installing Messaging Server 6.3 64–bit Edition, prepare your directory server for Messaging Server configuration. To do so, run the following script on your directory server machine:/opt/SUNWcomds/sbin/comm-dssetup.pl. See: Running the Directory Preparation Tool in Sun Java Communications Suite 5 Installation Guide

Note –

Running the Directory Preparation Tool is only for new configurations, not for configurations created with the migrate-config tool which is described in Upgrading Messaging Server.

Creating an Initial Runtime Configuration

After installing Messaging Server 6.3 64–bit Edition and running the comm-dssetup.pl script, run the configure program to create an initial runtime configuration to complete your installation and initial configuration of Messaging Server. For example, if you installed 64–bit Messaging Server, run /opt/sun/comms/messaging64/sbin/configure. For detailed instructions, see: Creating the Initial Messaging Server Runtime Configuration in Sun Java System Messaging Server 6.3 Administration Guide.

Note –

Creating an Initial Running Configuration is only for new configurations, not for configurations created with the migrate-config tool which is described in Upgrading Messaging Server.

Upgrading Messaging Server

This section describes three manual options to upgrade to this version of 32–bit or 64–bit Messaging Server:

ProcedureTo Migrate from 32–bit to 64–bit Messaging Server

If you have a previous version of Messaging Server (32–bit) installed and configured on your system and you want to migrate your data to the 64–bit version, you can do so by following these steps for a side-by-side upgrade:

  1. Using the Messaging Server 6.3 64–bit edition installer, install the 64–bit version of Messaging Server on the same system as your previous version of Messaging Server, but in a different directory (for example, in this procedure, /opt/sun/comms/messaging64/). See To Begin Installation.

  2. To migrate the configuration and Message Store data from the previous version of Messaging Server, run the migrate-config (migration configuration) utility:

    /opt/sun/comms/messaging64/sbin/migrate-config old-msg-svr-root

    For example:

    /opt/sun/comms/messaging64/sbin/migrate-config /opt/SUNWmsgsr

  3. Run /opt/sun/comms/messaging64/sbin/patch-config.

  4. Run /opt/sun/comms/messaging64/sbin/install-newconfig.

  5. To back out the migration, run /opt/sun/comms/messaging64/sbin/migrate-config -u /opt/SUNWmsgsr, where -u is the undo flag.

Next Steps

Once you complete the migration, stop using the old server-root directory:

Start the new server with the following command:

/opt/sun/comms/messaging64/sbin/start-msg

If you need to back out the migration, use the —u (undo) flag:

/opt/sun/comms/messaging64/sbin/migrate-config —u old-base-dir

where old-base-dir is the old server-root directory.

To restart the old Messaging Server, use: old-base-dir/sbin/start-msg

ProcedureTo Perform a 32–bit to 32–bit Upgrade (Side–by-Side)

  1. Using the Messaging Server 6.3 64–bit edition installer, install Messaging Server on the same system as your previous version of Messaging Server, but in a different directory (for example, in this procedure, /opt/sun/comms/messaging/). See To Begin Installation.

  2. To migrate the configuration and Message Store data from the previous version of Messaging Server, run the migrate-config (migration configuration) utility:

    /opt/sun/comms/messaging/sbin/migrate-config old-msg-svr-root

    For example:

    /opt/sun/comms/messaging/sbin/migrate-config /opt/SUNWmsgsr

  3. Run /opt/sun/comms/messaging/sbin/patch-config.

  4. Run /opt/sun/comms/messaging/sbin/install-newconfig.

  5. To back out the migration, run /opt/sun/comms/messaging/sbin/migrate-config -u /opt/SUNWmsgsr, where -u is the undo flag.

Next Steps

Once you complete the migration, stop using the old server-root directory:

Start the new server with the following command:

/opt/sun/comms/messaging/sbin/start-msg

If you need to back out the migration, use the —u (undo) flag:

/opt/sun/comms/messaging/sbin/migrate-config —u old-base-dir

where old-base-dir is the old server-root directory.

To restart the old Messaging Server, use: old-base-dir/sbin/start-msg

ProcedureTo Perform a 32–bit to 32–bit Upgrade (In place)

To perform an in-place upgrade:

  1. Patchadd the appropriate patch. For details, see: Patch and Package Information for Messaging Server

  2. From the msg-svr-base directory, run patch-config. For example: /opt/SUNWmsgsr/sbin/patch-config

  3. From the msg-svr-base directory, run install-newconfig. For example: /opt/SUNWmsgsr/sbin/install-newconfig

  4. To back out the upgrade, run uninstall-newconfig from the msg-svr-base directory. For example, /opt/SUNWmsgsr/messaging/sbin/uninstall-newconfig

Uninstalling Messaging Server

To uninstall Messaging Server, run commpkg uninstallin INSTALLROOT/CommsInstaller/bin/.

It uninstalls the same products that commpkg install installs. However, it does not remove OS patches installed by commpkg install. In addition, it does not remove Shared Components.

Note –

A fast way to uninstall Messaging Server in an alternate root is to simply remove the entire alternate root.

The following command-line arguments are used with commpkg uninstall:

Command-line Argument 

Description 

—rootdir path

Specify the path of rootdir, the alternate root used for multi-installation. Supported on Solaris only.

—silent INPUTFILE

Run the uninstaller silently, taking the inputs from the INPUTFILE and the command line. The command line arguments override entries in the INPUTFILE. Uninstallation proceeds without interactive prompts.

Use —dryrun to test silent uninstallation.

—dry-run or -n

Does not uninstall Messaging Server. Performs checks. Silent uninstallation INPUTFILE is created in /tmp.

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

To run a silent uninstallation, follow these steps:

  1. Run an interactive uninstallation session.

    A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created.

    Note –

    The silent installation and uninstallation files have the same file naming convention. You need to scan the contents of the file to determine if it's an installation or uninstallation silent file.

  2. Copy the state file to each host machine and edit the file as needed. .

  3. Run the silent uninstallation on each host. See the silent uninstallation usage.

Note –

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

The following is a sample uninstall silent file:

# Silent File for CommsInstaller 5.0-1.03

# Generated on 20070604120325

# root directory

ROOTDIR=/

# list of components to uninstall (using mneumonics)

COMPONENTS=MS64 MS64_L10N

Known Issues and Limitations

This section contains a list of known issues and limitations with Messaging Server 6.3 64–bit Edition:

6574627

Quota Warning Delivery Can Deadlock

If the quota warning feature is enabled in this release, you might experience the following problems: 

  • Delivery fails with a 450 4.2.1 mailbox is busy error

  • ims_master logs the message General Warning: Shutdown timeout, possible deadlock

  • Cannot expunge mailbox

Workaround: Turn off over quota notifications. For example: configutil -o store.quotanotification -v off

This issue will be addressed in a future release. 

6548217

Errors with SASL shared component when installing Messaging Server in Alternate Root.

Workaround: Install SASL patch (libsasl) in default INSTALLROOT, not in the alternate root:

commpkg install —upgradeSC y

6533514

No Sun Cluster Agent available for 64–bit version of Messaging Server 6.3.

Currently, no Sun Cluster High Availability agent is supplied for the 64–bit version of Messaging Server 6.3. If you are looking to provide cluster support for your 64–bit installation, contact Sun Support.  

If you already have installed the 64–bit version, do not use the Sun Cluster agent that came with Sun Java Enterprise System 5 or with Sun Java Communications Suite 5.  

This bug only applies to Messaging Server 64–bit installations. The Sun Cluster agents bundled with Sun Java Enterprise System 5 and Sun Java Communications Suite 5 can be used with 32–bit Messaging Server 6.3 installations. 

A Sun Cluster agent that supports the 64–bit version will be available in the near future.  

Accessing Sun Resources Online

The http://docs.sun.comSM web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities. To access the following Sun resources, go to http://www.sun.com:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions.

To share your comments, go to http://docs.sun.comand click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this book is Sun Java System Messaging Server 6.3 64-bit Installation Technical Note, and the part number is 820-2124-10.